We say no to some projects. Not because we are picky about who we work with, but because starting before a team is ready costs the client money and costs us the result we are paid to deliver. A short honest conversation at the start is cheaper than weeks of expensive confusion later.
What “ready to ship” means
It does not mean a finished specification. It means five things are true.
- There is a real problem and a person who has it. You can name who the product is for.
- Someone can decide. One person with the authority to say yes, and an hour or two every week to do it.
- The first version is small enough to finish. You know what you would cut if you had to.
- The budget is agreed. Not unlimited, but real, and approved by whoever signs.
- You can reach users soon. Even five people willing to try it in the first month.
What it does not mean
- A perfect specification. Specifications change once real users touch the product.
- A large budget. A small, real budget beats a big, vague one.
- Certainty. You will be wrong about things. What matters is that someone can decide what to do next.
A quick self-check
Answer yes or no to each. Four or more yeses and you are probably ready. Fewer, and a short conversation with users or a small proof of concept will save you money.
- Can I describe who the product is for in one sentence?
- Can I describe what it must do on day one, and what can wait?
- Is there one person who can decide, quickly, every week?
- Do I have a budget I can commit to?
- Can I put the first version in front of real people within a month of it being built?
Why it matters for you, not just for us
A team that is not ready pays twice: once to build something, and again to rebuild it when the answers to those five questions arrive. Engineers are the most expensive way to discover that nobody decided what the product is for.
What we do when you are not ready
We tell you on the first call. Then we suggest the cheapest next step, which is often not building at all:
- A proof of concept, from $3,500 and 2 weeks, if the question is whether the hard part works.
- A product design sprint if the question is what the product should look like.
- A conversation with five users that costs nothing but time.
- Coming back when the answers are clearer. We would rather hear from you then.
What it feels like when you are ready
A shortlist of engineers within 24 hours, a paid two-week pilot on a real piece of your roadmap, and a working demo every Friday. The work starts because the decisions have already been made. That is where our speed comes from. It is the same reason a small team with clear decisions can beat a bigger one.