Consultancy
Judgement, written down, before you build.
A short engagement that ends in one document: what to build, what not to, and the reasons. Fixed fee. Use it to brief a team, raise money or decide to stop.
Book a conversation- [Duration]
- From first call to written judgement
- [Fee]
- Fixed, agreed before the first call
- 1
- Document. Decisions, reasons, next steps
- Both
- Sides of the seam. Critic and engineer, same person
The problem
Products fail at the point where someone who understood the argument handed it to someone who did not.
Consultancy here is not a deck. It is a written judgement by someone who has published criticism and shipped production software, so the recommendation already knows what it will cost to build.
What you get
1.1
A written judgement
What to build, what not to, and why. Specific enough to brief a team from, short enough to read in one sitting.
1.2
The build estimated
What each option costs in time and money, from someone who would be willing to build it.
1.3
A clear next step
Build it with the studio, build it elsewhere, or stop. All three are good outcomes.
Then
Judgement
The document, delivered and walked through on a call.
Asked before
Is this a sales pitch for a build?
No. The document is the product. Stopping is a recommended outcome when it is the right one.
What do you need from us?
Access to the people who understand the problem, whatever exists today, and an honest budget range.
Can it cover an existing product?
Yes. A review of what exists and what to do with it is a common shape.
How is it priced?
One fixed fee, agreed before the first call. [Fee].