Build
Engineer to spec with weekly demos and visible progress.
Build is the longest phase. Engineering executes against the signed spec, code is reviewed before merge, and we demo working software on a weekly cadence so you can adjust early. Your repository is the single source of truth from the first commit.
We work in milestones, not in opaque months. Each milestone has acceptance criteria from the SOW, and you sign off as we hit them. If something needs to change mid-build, we use written change orders so scope, cost, and timeline impact are explicit.
Build typically runs 4 to 10 weeks for a v1, longer for phased releases.
Activities in this phase
- Sprint planning against milestones
- Feature development and code review
- Automated testing and CI setup
- Weekly demos of working software
- Progress reports against SOW milestones
- Change-order management
- Pair programming with your team (optional)
Inputs
- Signed design artifacts
- Repository access
- Cloud/infrastructure access
- Test data and integration credentials
Deliverables
- Working source code in your repository
- Continuous integration pipeline
- Automated test suite
- Weekly demo recordings
- Progress reports against milestones
- Change orders where applicable
Who is involved
- Engineering team from our side
- Tech lead from your side (optional)
- Product owner for demos and sign-off
Decisions locked in
- Feature acceptance per milestone
- Change-order approvals
- Code review standards
Acceptance criteria
- Each milestone meets SOW acceptance criteria
- Code review and CI green
- Demo approved by product owner
Frequently asked
How often do we see working software?
Weekly. Every Friday we demo what was built that week against the milestone goals. You can watch the recording if you cannot attend live.
What if priorities change mid-build?
We use written change orders. Scope, cost, and timeline impact are quoted before the change is accepted. Both sides know what they are agreeing to.
Do you write automated tests?
Yes. Unit tests, integration tests, and end-to-end tests for critical paths. The depth is sized to the risk and longevity of the code, which we agree during Discovery.
Ready to start a discovery call?
A 30-minute call to understand the work. A signed Statement of Work before any code is written.