Build / Launch Something New
Get the idea out of your head and into the market.
New products stall for ordinary reasons: unclear scope, no one owning it, and a first version that tried to do everything. We help you find the smallest version worth launching, then build it.
What usually gets in the way
The things people tell us first.
None of these are unusual. Most businesses have three or four of them at once, and they are rarely caused by what they look like they are caused by.
How we approach it
What the work actually looks like.
Pressure-test the idea before building it
Who it is for, what it replaces, and what has to be true for it to work. Cheap to do, expensive to skip.
Find the smallest version that proves the point
The first release should answer one question, not cover every feature you eventually want.
Build it properly, so version two is possible
A prototype that cannot be extended is a cost. We build so the second year is cheaper than the first.
Launch, measure, then decide
Including being willing to tell you the honest answer if the market says no.
What we might build
The technical part, named plainly. Which of these applies depends entirely on what we find — often it is fewer of them than people expect.
- Product discovery and scoping
- Rapid prototyping
- AI product and platform development
- Technical architecture
- Launch and measurement
- Ongoing product engineering
How we’d measure it
Agreed with you before anything is built, measured against your own starting point afterwards.
- Time to first release
- Adoption in the first 90 days
- Cost to build and run
- Whether the original assumption held
We don’t publish guaranteed returns and we don’t quote other organisations’ results as if they were yours.
Is this the oneholding you back?
Five questions and we'll tell you whether your answers actually point here — or somewhere else.