02 / 09 · Capability
Software & Product
From a clickable prototype to a product in production.
What this is
MVPs, internal tools, customer portals and mobile apps. We scope tightly, build in visible increments, and write the tests and documentation that decide whether a system is still maintainable a year later.
Included under this pillar
- MVP builds for startups
- Internal tools and admin panels
- Customer portals and dashboards
- Mobile apps — React Native and PWA
- API development and integrations
- Database design and data modelling
- Legacy system migration
- Prototypes and demos for fundraising
- Code review, refactoring and debt audits
- QA and automated test suites
The process
How software actually gets built.
| Step | Phase | What happens | You get | When |
|---|---|---|---|---|
| 01 | Discovery | Who uses it, what breaks today, and what "working" would actually mean. | Requirements doc and success criteria | Week 1 |
| 02 | Spec & Architecture | Data model, service boundaries, integration points and the build-vs-buy calls. | Technical spec and architecture diagram | Week 2 |
| 03 | Sprint Build | Two-week increments. You see working software at the end of each one, not a status report. | Deployable increment per sprint | Weeks 3–8 |
| 04 | UAT | Your team uses it against real workflows while we still have the context loaded. | Tested build and a triaged fix list | Week 9 |
| 05 | Ship | Production deploy, monitoring, error tracking and rollback path in place before launch. | Live system and runbook | Week 10 |
| 06 | Support Window | Thirty days where anything that surfaces is ours to fix, not yours to report. | Stabilised system and handover | Weeks 11–14 |
What you get
Everything below, every time.
0Deliverables
- 01Technical spec and architecture diagram
- 02Source code in your repository
- 03Automated test suite
- 04CI/CD pipeline
- 05Error tracking and monitoring
- 06API documentation
- 07Runbook and deployment guide
- 0830-day post-launch support
How it is scoped
Scoped per sprint against a fixed spec. Most MVPs run six to ten weeks of build.
Questions
Asked and answered.
Do we own the code?
Yes, from the first commit. It lives in your repository under your account.
Can you take over an existing codebase?
Yes. We start with a paid audit so neither of us is guessing about what is in there.
What stack do you build on?
Chosen per project and justified in the spec. We do not have a hammer we need every project to be a nail for.