04 / BUILD
Build what the next decision actually requires.
Build is focused execution. The aim is to create the smallest credible product, system, or experience that can test an assumption, deliver a useful outcome, or reach the next meaningful milestone.
The phases give the work structure, but the process is iterative. New evidence can change the strategy, what gets built, and what happens next.Research → Test → Learn → Adjust
THE DECISION
What needs to exist now, at what level of quality, so the team can learn or deliver without creating unnecessary cost and technical debt?
DIRECT ANSWER
What should an MVP prove?
An MVP should reduce a specific uncertainty. It may need to show that users can complete the core task, that behaviour changes, that delivery is feasible, or that a commercial exchange can happen. Shipping quickly is not enough if the build cannot answer the decision.
WHAT NEEDS TO BE UNDERSTOOD
Start with the uncertainty behind the decision.
- The assumption or milestone the build must address
- The smallest scope that remains credible to users and stakeholders
- The required balance of speed, quality, cost, and technical durability
- The analytics and research needed to learn after release
ASSUMPTIONS TO RESOLVE
Make the claims visible before acting on them.
- The selected workflow solves the priority problem
- Users can understand and complete the core task
- The technical approach is appropriate for the current stage
- The team can learn before scope and complexity expand
WHAT MARCUS HELPS WITH
Shape the work around the decision.
- Prototype and MVP development
- Web and SaaS development
- Onboarding, user accounts, dashboards, and internal tools
- Conversion flows and product refinement
- Analytics, experimentation, and implementation support
WHAT YOU MAY RECEIVE
Useful outputs, not a fixed package.
Depending on the decision, the work may include:
- A bounded MVP or prototype scope
- Product requirements and decision criteria
- A website, SaaS MVP, or core product flow where appropriate
- Analytics and experiment-ready implementation
- A clear list of deferred scope and technical trade-offs
WHAT GOOD EVIDENCE LOOKS LIKE
Evidence must fit the claim.
Build evidence comes from prototype tests, usability sessions, task completion, behaviour, conversion, retention, operational performance, and customer commitment. Research continues while the product is being shaped and after it is live.
WHO THIS WORK SERVES
The phase is shared. The context is not.
Founders and startups use Build for prototypes, MVPs, web products, and SaaS execution. Premium brands may use it for digital experiences, commercial platforms, or AI-enabled workflows. Investor involvement is usually through portfolio execution support.
WHAT JUSTIFIES THE NEXT COMMITMENT
Move forward when the product or system can generate the next useful evidence or reliably deliver the agreed milestone.
WHAT HAPPENS NEXT
Translate the product and its evidence into a clear story for customers, partners, teams, or investors.