Working software, early.
Better every phase.
Apps are planned in phases. The first phase delivers a small working version you can use and test. Each later phase builds on what you learn from it.
- Typical length
- Planned in phases
- Best for
- Marketplaces, SaaS products, and internal tools
- Starts with
- A free call about your project
Step by step.
Sign-offs are marked. Nothing moves past one without your approval.
- Start
Talk it through
The problem, the people using it, and what the first version must do.
You get: Written proposal - Before the build
Map it
User flows, data model, and features split into phases.
You get: Phase plan and quote Your sign-off - Phase 1
Design
Core screens and a clickable prototype.
You get: Approved prototype Your sign-off - Phase 1
Build
A first working version on a test server, with real accounts and data.
You get: Working first version - Each phase
Release and learn
Release, watch how people use it, and plan the next phase.
You get: Released version and next plan Your sign-off
Who does what.
Your part is small but it matters. Here it is, next to mine.
| Step | You |  Me |
|---|---|---|
| Talk it through | Describe the problem and who has it. | Ask about users, data, and the workflows the app must support. |
| Map it | Choose what belongs in the first phase. | Map the flows and data, and quote the first phase. |
| Design | Click through the prototype and test it with real users if you can. | Design the screens and adjust them based on what you find. |
| Build | Try it as you would use it, and report what feels wrong. | Build, test, and share a working version you can log in to. |
| Release and learn | Decide what the next phase should fix or add. | Release, monitor, and quote the next phase. |
What you get.
The pieces a typical app or platform build delivers. Your quote lists exactly which ones apply.
-
Phase plan
Features grouped into phases, each with its own scope and quote.
-
Prototype
Clickable screens to test the idea before it is built.
-
A working app
Accounts, data, and the core workflow, running on a real server.
-
Data model
A database designed for the records your app keeps and the questions you ask of them.
-
Documentation
Plain notes on how the app is built, deployed, and extended.
-
Code in your repository
Every line of code lives in a repository you own from the first commit.
Projects that ran this way.
Work that followed the app or platform build steps.
The services involved.
Each one has its own page with more detail.
How is an app priced?
Each phase has its own fixed quote, so you decide how far to go one phase at a time.
Who owns the code?
You do. The code lives in a repository in your name from the first commit.
Can you work with my developers?
Yes. I can lead the build, or plan and design it for your team to build.
Other kinds of projects.
The same five steps, shaped for different work.
Good work starts with a conversation.
Tell us about your business, what’s working, and what you’d like to do better.