How we ship
products.
Software fails in predictable ways: open scope, a deadline with no owner, decisions made too late. The method closes those doors before the contract.
Open scope, a deadline with no owner and late decisions. The method closes those doors before the contract.
Chapter 01
Paid discovery
Understanding the business before designing the first screen: problem, users, risks and what already exists.
What comes out of it
- Written problem
- Users and flows
- Risks
- Architecture
You decide
Whether the problem described is the real problem.
Chapter 02
Scope
What's in, what's out and why. This is where the fixed price and the contract date come from.
What comes out of it
- Written scope
- Fixed price
- Date in the contract
You decide
What goes in now and what waits.
Chapter 03
Design
Flows and screens designed in Figma and validated with you before they become code.
What comes out of it
- Flows
- Screens
- Design system
You decide
Approving each flow before it becomes code.
Chapter 04
Build
Our in-house dev team codes in short cycles, with the product running from the first weeks.
What comes out of it
- Running product
- Short cycles
- Integrations
You decide
Testing the real product, not just the Figma file.
Chapter 05
Launch
The product live, with domain, analytics, security and access in your name.
What comes out of it
- Domain
- Analytics
- Security
- Access in your name
You decide
The day it opens to users.
Chapter 06
Evolution
The product gets better every month, with the AI agent flagging bugs, improvements and data that doesn't add up.
What comes out of it
- AI agent
- Monthly report
- Priorities for the month
You decide
What to improve first next month.
Terms used
Method glossary
- Paid discovery
- The first step, where we understand the problem, the product and the business before defining scope, price and timeline.
- Fixed scope
- A contract model where scope, price and timeline are set before work starts and don't change without agreement.
- Design system
- A set of components, visual rules and tokens (colors, type, spacing) that the whole product uses, in design and in code.
- MVP
- Minimum Viable Product: the smallest version of the product that solves the core problem and can go live for real users.
- Deploy
- Pushing a new version of the code to the server where the system runs, making the change available.
- Ongoing evolution
- Ongoing work to improve the product after it ships: fixes, new features and adjustments based on real usage.