How a project runs
Four stages with clear outputs. You always know where the project is, what it has cost, and what comes next.
- Stage 1
Discover
1–2 weeksWe meet the people who will use the system and the people who pay for it. We map the current workflow, find the constraints nobody wrote down, and agree what the first release must do.
What you get
- Workflow map and problem statement
- Prioritised scope for a first release
- Risks and open questions
- Estimate with assumptions stated
- Stage 2
Design
1–3 weeksArchitecture, data model, integrations and screens are designed together, so the interface and the system underneath agree. You review clickable screens before any heavy build starts.
What you get
- Solution architecture and data model
- Wireframes and key screens
- Integration contracts
- Delivery plan by sprint
- Stage 3
Build
Sprints of 2 weeksDevelopment runs in two-week sprints. Every sprint ends with a demo of working software in a test environment, and a short written update: what shipped, what is next, what changed.
What you get
- Working release each sprint
- Automated tests and CI/CD pipeline
- Sprint demo and written update
- Backlog you can see and reprioritise
- Stage 4
Run
OngoingWe take the system live with monitoring and a rollback plan, train your team, and hand over documentation. Then we stay on for support and improvements for as long as you want us.
What you get
- Production deployment and monitoring
- Handover documentation and training
- Support agreement with response times
- Roadmap for the next increments
Questions we get asked
- How do you price projects?
- Discovery is a fixed fee. Build work is either fixed-scope with a defined release, or a dedicated team on a monthly basis. Every estimate states its assumptions so you can see what moves the number.
- What if requirements change mid-project?
- They usually do. Sprint planning is where changes are priced and prioritised, in the open, so you decide what trades off against what.
- Which tools do we use to communicate?
- Whatever your team already uses — Teams, Slack, email — plus a shared board for the backlog and a weekly call during active development.
- Who owns the code and infrastructure?
- You do, from the first commit. Repositories, cloud subscriptions and domains are created in your name.
Start with a discovery conversation.
Thirty minutes, no slides. Tell us what is slowing the business down and we will tell you what we would do about it.