Are you in operations and spending time and effort building business cases to improve your business processes?
How Pitchmap got started
I’m fanatical about speed in business. I love shaving a few minutes off a process by removing steps that aren’t adding value or reducing the error rate at a particular step.
Now that I’m spending most of my time building business cases to support process improvement projects I find it ironic that this is often an area ripe for improvement. I regularly see business cases where a vast amount of time and effort has been put into a project before two fundamental questions are answered:
Answering the first question requires a comprehensive view of your business and deep subject matter expertise. Your business is unique and your processes must accommodate your uniqueness.
Answering the second question is much easier and can largely be automated. This is where Pitchmap comes in. Pitchmap is like a caterer for your party. It’s up to you to make the party fun (clear vision) but you don’t need to worry about serving the food or drinks (financial foundation). If you can create the vision, Pitchmap can tell you how much to invest in the project.
To find out more about Pitchmap, visit pitchmap.com.
Who can use Pitchmap?
Pitchmap is targeted at three groups of users:
Why is it called “Pitchmap”?
When you’re preparing a business case, you’re not in process improvement, you’re in sales. You are no different than a Silicon Valley startup looking for funding from venture capitalists. That’s why we’ve called our application “Pitchmap”—it’s a process map designed to deliver the pitch rather than deliver the improvement.