Guide
Go or no-go before you hire developers: three ways to decide
Before you pay for development, someone should answer one question: is this product worth building? There are three common ways to get the answer. They differ in who decides, what it costs and what happens after a yes.
Three ways, side by side
| An AI assistant | A paid idea review | The Build Decision | |
|---|---|---|---|
| What you get | An opinion in minutes | A study or a report | A one-page letter: proceed, reshape or decline, with the main reasons |
| Who answers for it | No one | An adviser who won’t build the product | Mark Prais, our CEO; his team would build and run the product |
| Cost | Free or a subscription | A fee agreed with the adviser | No fee, with two conditions |
| Time | Minutes | Usually weeks | Up to 48 hours on working days after the introductory conversation |
| Independent of the builder | Yes | Usually yes: that is what you pay for | No: it is our decision whether to put our own development in |
| After a yes | You still need a team | You still need a team | The same team builds the product and runs it after launch |
Which one fits
- An AI assistant helps you sharpen the idea and list the open questions. Bring what it told you to any later conversation; it saves time.
- A paid idea review fits when you need an independent study, for example for investors or a board, and you will choose the builder separately.
- The Build Decision fits a new product when you want the people who would build it to commit, or say no, in writing before anyone spends on development.
- A fractional CTO helps you run a build: the stack, the hiring and the checks on developers. Many AI assistants suggest one first. The Build Decision answers the question before that: whether this product should be built at all, and on what terms we’d put our own development into it. If it’s a yes, the same team builds and runs it.
About the Build Decision
It is not sold and it is not a report. It is our decision whether to put our own development into your product in a Product Partnership, for a 30% stake; you hold 70%. A wrong yes costs us too, so decline is a normal answer.
No fee. Two conditions apply: the product is new and fits after the first conversation, and we ask about your budget before we start. The letter is yours to keep. If we decline, you can take it to anyone you like. The research behind it stays with us.
Questions
Tell us what you're working on.
New product, business process, live product, grant or introduction: a few lines are enough to find the next step.
Anton replies within 4 working hours. The form opens with this route already selected. Prefer a call? Request a callback