Product·2 min read
Shaping a product: from a problem to a first release
Before a feature list, a first product needs one decision: how it should solve the problem as a whole. What shaping connects, and what it does not promise.
Notes for founders building a first product.
Short and practical. What to bring to a first call, how a product gets shaped, what happens to a prototype you built yourself, and how the work is structured.
Latest insights
Getting started·2 min read
What to bring to your first call about a software product
You do not need a specification. What the introductory call covers, and what happens afterwards.
Prototypes·2 min read
Keep, improve or rebuild: what happens to your AI-built prototype
A prototype you built yourself is worth bringing. How Planning decides what to keep, what to improve and what to rebuild before customers rely on it.
How we work·2 min read
Why Planning and Build are separate decisions
A first product is taken on in two steps. What each one gives you, and why you can stop after Planning.
Bring the problem you understand.
A short call to see whether Planning is the right next step. No preparation needed, and nothing is signed on the call.
- 01
Send a message
Your name and email are all we need.
- 02
Have a short call
No preparation. We see if Planning fits.
- 03
Get a written proposal
If it fits. Nothing starts until you sign.