I offer three day consulting gigs in London and Europe. If neither of us is satisfied after the first day of discovery, I won't charge you anything. I won't produce any powerpoint for you, but instead initiate the right conversations. My rates are high, as I want you to listen very carefully to what I say. But three days means it won't be drawn out into a long coaching gig. There's no magic, and you can do this with the right people.
If you have a failed project, or trying to go Agile, I'm happy to help you to move forward. Most of my advice will be of the hard variety, like canning the project, firing half of the staff (or much preferable, ensure to hire well), and to not blame the programmers for a bad business idea. The easiest, proven, way to succeed is to ensure that your technical leaders are excited about the actual problem you're trying to solve. Only add members to their team when they explicitly ask. Large teams will fail, as the individual members won't feel empowered enough to influence the end result.
Writing software doesn't scale well. And it can only scale if you have very strong leaders in place and the junior staff is prepared to follow them. Boring software has no right to exist - as the market will tell you.
It is important to think very hard before embarking on the mission to write any software. There are two kinds of systems, the first kind can be bought or outsourced and is not core to your business. The second kind is the manifestation of your very business, and failure there means failure for the company.
That means you have to treat it very seriously. Good software is expensive to write, but bad software even more so.
And I've seen some messed up projects in my days. Most of them were not possible to save, which is why three days is enough. I hope yours is.
And if you decide to build a system, I strongly recommend ThoughtWorks, my (soon to be) previous employer.