How we work
A delivery process you can follow week by week.
Seven phases, each with clear outputs and a clear decision for you to make. You always know what phase we're in, what it produces and what happens next.
- 01
Discovery
1–2 weeks
Understand the business, the users and the technical constraints before anything is estimated.
What happens
- Working sessions with your stakeholders
- Review of existing systems, data and code
- Success metrics and non-negotiables
- Early risk identification
What you get
- Discovery brief
- Risk register
- Order-of-magnitude estimate
Your involvement: Two or three working sessions, plus access to the people and systems involved.
- 02
Strategy
1 week
Decide what to build first and exactly how it will be built.
What happens
- Architecture and data model
- Technology choices with trade-offs written down
- Scope, milestones and acceptance criteria
- Delivery plan and team
What you get
- Architecture document
- Milestone plan
- Fixed scope and pricing
Your involvement: Review and approve the scope, milestones and architecture.
- 03
Design
1–3 weeks
Design the product experience and lay the technical foundation in parallel.
What happens
- User flows and interface design
- Clickable prototypes
- API contracts
- Environments and CI/CD pipeline
What you get
- Versioned designs for approval
- API specification
- Running staging environment
Your involvement: Review designs in the portal and approve each version.
- 04
Build
Depends on scope
Ship working software in short, reviewed iterations.
What happens
- One- to two-week iterations
- Code review on every change
- Demos of working software
- Weekly written updates
What you get
- Working increments on staging
- Weekly updates in the portal
Your involvement: Join demos and answer questions as they come up in the portal.
- 05
Quality
Runs alongside build
Prove it works before your users find out it doesn't.
What happens
- Automated unit, integration and end-to-end tests
- Manual QA against acceptance criteria
- Security and dependency review
- Performance and accessibility checks
What you get
- QA report
- Resolved issue list
Your involvement: User acceptance testing on staging.
- 06
Launch
Days, not weeks
Release safely, with a plan for when things go wrong.
What happens
- Production deployment
- Monitoring and alerting
- Data migration and rollback plan
- Handover and documentation
What you get
- Live product
- Runbook
- Technical documentation
Your involvement: Final sign-off before release.
- 07
Evolve
Ongoing
Keep the product healthy, secure and improving after launch.
What happens
- Dependency and security updates
- Incident response
- Performance tuning
- Roadmap iterations
What you get
- Monthly maintenance report
- Prioritised improvements
Your involvement: Prioritise the roadmap with us.
Communication rhythm
Predictable, written, and in one place.
You shouldn't need a status meeting to find out what happened. This is the cadence every client gets, through the client portal.
Every week
A written update in your portal: completed, in progress, next, and anything we need from you.
Every iteration
A demo of working software on staging — not slides.
Every milestone
A formal review. You approve or request changes; the decision is recorded against the exact version.
Whenever it matters
Project health changes (on track, at risk, blocked) are shown immediately, with the reason and the plan.
Engagement models
Three ways to work with us.
Best for · A defined product, MVP or feature
Project delivery
Fixed scope, milestones and price agreed up front. Change is handled openly through written change requests.
- Discovery and architecture
- Milestone-based billing
- Approval at every milestone
Best for · Ongoing product development
Dedicated team
A stable team of engineers, led by a technical lead, working through your roadmap with priorities you set each iteration.
- Technical lead + engineers
- Iteration planning with you
- Monthly billing
Best for · Live products that must stay healthy
Maintenance & support
Security updates, monitoring, incident response and small improvements for products we built or inherited.
- Monitoring and alerting
- Dependency and security updates
- Monthly report
Questions
About working with us.
How do you price projects?
Fixed-scope projects are priced per milestone after a short discovery phase. Dedicated teams are billed monthly. Either way, you receive a written proposal with scope, assumptions, milestones and pricing before anything is committed.
Who will actually work on my project?
A team led by a technical lead, with a project manager as your main point of contact. Every team member is visible in your client portal.
Who owns the code and infrastructure?
You do. Source code, infrastructure and documentation live in your own accounts from day one, so there is no lock-in.
Can you take over an existing codebase?
Yes. We start with a short technical assessment — architecture, code quality, security, test coverage and deployment — and give you a written report with a prioritised plan before proposing any work.
Will you sign an NDA?
Yes. We're happy to sign an NDA before you share details. Client work only appears on our website with the client's written permission.
How will I know how the project is going?
Through your client portal: a written update every week, milestone progress, approvals, files and messages in one place. You'll also join regular demos of working software.
Start a project
Tell us what you're building.
Three short questions about your project. We reply within one business day — with questions that show we read it.