Decide what to build before anyone builds it.
Most software projects are shaped by whoever is being paid to build them. We give you an independent view of whether the software is worth building, what it should be, and what it will realistically take — grounded in your business case, not a vendor's capacity.
“The most valuable advice we give is sometimes that the software should not be built the way it was imagined — or built at all.”
The decisions this engagement is built to resolve.
- Should this software even be built?
- Should you build, buy, or configure an existing product?
- Do you need a mobile app, or would a web application be enough?
- What belongs in the MVP — and what should wait?
- What is a realistic budget and timeline before you commit?
Inside the engagement.
The areas we examine and the ground we cover on your behalf.
Idea assessment
A structured read of the problem, the users, and whether software is the right instrument to solve it.
Feasibility
Technical, commercial and operational feasibility examined together, so the answer holds up beyond the demo.
Build vs buy
Whether an off-the-shelf or configurable product would serve you better than custom development.
MVP definition
The smallest version that proves the business case — and a clear line around what is deferred.
Web vs mobile
Where your users actually are, and the platform decision that follows from it rather than from fashion.
Technology direction
A neutral view of the architectural direction, free of any stack we happen to staff.
Preliminary architecture
A high-level shape for the system that a vendor can build against and be measured against.
Estimated budget
An independent budget range, so you know what 'reasonable' looks like before quotes arrive.
Realistic timeline
A delivery timeline calibrated to scope and complexity, not to a sales conversation.
Major risks
The handful of risks most likely to derail the project, named early while they are still cheap to manage.
Deliverables
- Feasibility & strategy report with a clear recommendation
- Build / buy / configure decision with rationale
- MVP scope outline and deferral list
- Platform and preliminary architecture direction
- Independent budget range and indicative timeline
- Prioritised risk register
Outcomes
- 01You commit money with conviction, not on faith.
- 02You enter vendor conversations already knowing what good looks like.
- 03You avoid building the wrong thing well.
Further reading
Do You Really Need a Mobile App for Your MVP?
A native app is the most expensive way to test an idea. Often it is also the wrong one.
Why Software Development Quotes Vary So Dramatically
The same brief can return a $10,000 quote and a $120,000 quote. Here is what that spread is actually telling you.
What Every Software SOW Should Define
A statement of work is the last cheap chance to prevent an expensive dispute. Most leave out the things that matter.
Other ways we help
Bring an independent advisor into this decision.
Tell us where your project stands. We’ll show you exactly how an independent view would change the outcome.