Build Decision
What we check before we decide whether to build.
We decide whether Logics7 takes your product on. The Build Decision: proceed, reshape or decline — in writing, with reasons, within seven working days. Before any code. Mark Prais, our CEO, takes it.
The eight things we look at
| # | What we check | Questions we ask |
|---|---|---|
| 1 | Who the user is | Who has the problem? How do they handle it today? |
| 2 | Who pays | Is the payer the user? What do they pay for today? |
| 3 | What problem is solved | What happens for the user if nothing changes? |
| 4 | What alternatives exist | What do people use instead, including a spreadsheet or doing nothing? |
| 5 | How the product can acquire users | Which channel reaches them, and what does a user cost to reach? |
| 6 | Whether monetisation can work | Price, payment model, and the point where the numbers hold |
| 7 | What first version makes sense | What is the smallest version that tests the riskiest assumption? |
| 8 | Whether we should take it on | Are we ready to build it and run it with you after launch? |
For a product that fits, this includes an internal global market analysis.
What the Build Decision is not
- Not a forecast. It doesn't tell you whether the product will succeed. It tells you whether we take it on, and why.
- Not a report. The research behind it stays internal; you get the decision and its main reasons.
- Not a service we sell. It comes before either of us commits money.
What you send us
A deck or a one-page brief, a prototype link if there is one, and any evidence about users or the market. Nothing confidential.
What the letter contains
One line with the decision. Three to five reasons, one sentence each. What happens next. Signed by Mark Prais, CEO.
After each outcome
- Proceed. A manager comes to a meeting prepared for your product, with a written offer: scope, roles, budget, IP, milestones and the commercial structure.
- Reshape. We tell you what would have to change (the scope, the model or the first version) and why.
- Decline. You hear it before you spend on development, with the main reasons. Where it helps, we name the kind of option that may suit you better.
Why we would say no
If we proceed, we build and run the product ourselves after launch, and we take on up to ten new Product Partnerships a year. A yes we can't stand behind would stay our problem for years.
When the Build Decision applies
For a new standalone digital product, once a first conversation shows it may fit. An existing business goes through Annual Product Operations; a live product through Existing Product Review, where the outcome is Mark Prais's decision, with the reasons.
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.
We reply within one working day. The form opens with this route already selected.