FOUR PHASES,
ONE ORDER.
Every Monolit Labs build runs through four phases: discover, define, build, then launch and improve. The build is priced in the second phase, and nothing is built until both sides have signed the same scope. Below is what happens in each phase, what we need from you, and what you hold at the end.
- 01Discover
- 02Define
- 03Build
- 04Improve
HOW A BUILD RUNS.
- PHASE 01 · DISCOVER
Discover
Conversations with the people who do the work, a look at the tools and data already in place, and an honest answer on whether a build is the right move at all.
OUTCOMEA written problem statement both sides agree on.
- PHASE 02 · DEFINE
Define
We test the approach against your systems, list what it depends on and where it can fail, and write it into a proposal with milestones and a price.
OUTCOMEA signed scope, with its exclusions written down.
- PHASE 03 · BUILD
Build
Design and engineering run in milestones you review. Each one is tested with real data and the people who will use it, not demonstrated on a clean example.
OUTCOMEWorking software, accepted milestone by milestone.
- PHASE 04 · LAUNCH & IMPROVE
Launch &
ImproveWe deploy, hand over access and documentation, and watch how the system behaves under real use. Ongoing support runs on the terms the proposal sets.
OUTCOMEA system your team runs, with what it needs to keep running it.
WHAT EACH PHASE ASKS OF YOU.
- PHASE 01
Discover
YOU BRINGThe people who run the workflow today, access to the tools involved, and the cases that go wrong most often.
YOU DECIDEWhether to continue to a proposal, start with a paid AI Consultation, or stop. If we are not the right team, you hear it here.
- PHASE 02
Define
YOU BRINGOne decision-maker, answers to the open questions, and any limits on data, hosting or budget.
YOU DECIDETo sign the proposal, ask for changes, or stop before any build cost is committed.
- PHASE 03
Build
YOU BRINGContent, data and third-party access on the dates the plan sets, and reviews inside the agreed window.
YOU DECIDEWhether each milestone meets the acceptance criteria written into the proposal.
- PHASE 04
Launch & Improve
YOU BRINGThe people who will run the system day to day.
YOU DECIDEWho holds the system after launch: your own team, with documentation and access, or ours, under a support arrangement.
WHAT MOVES A DATE.
The build is the most predictable part of a project. Dates slip on the inputs around it: an API key a supplier is slow to issue, content that arrives after the design is signed, a decision waiting on three people, a review that takes two weeks instead of two days. So every input in the proposal has a named owner and a date, and progress is reported against milestones. A slip shows up at the milestone it affects, not on launch day.
GETTING TO A PRICE.
A price arrives in phase two, written into the proposal beside the scope it pays for.
HOW A PROPOSAL IS BUILTALL THE ANSWERSBUILD THE SYSTEM
THE BUSINESS
ACTUALLY NEEDS.
The first phase starts with a free 30-minute call. Describe the problem and we will tell you whether it needs a build.



