ProcessHow we work
Eight stages, each with something you can see.
From the first conversation to long term maintenance. Every stage has a deliverable and a clear expectation of you and of us.
01The stages
Discovery to maintenance.
Discover
Expect direct questions and honest feedback on feasibility before any commitment.
- 01
Discover
We learn how your organisation works today, who the software serves and what success looks like in plain terms.
Deliverables
- Stakeholder interviews
- Workflow and pain point map
- Constraints covering budget, timeline and compliance
What to expect
Expect direct questions and honest feedback on feasibility before any commitment.
- 02
Scope
The problem is narrowed to a first release that is genuinely useful, with explicit boundaries and a written proposal.
Deliverables
- Prioritised scope and out of scope list
- Written proposal with versioned estimates
- Delivery plan and milestones
What to expect
Estimates are ranges with assumptions, not a single magic number.
- 03
Design
Flows, information architecture and interface design are validated with the people who will use the product.
Deliverables
- Flows and wireframes
- Interactive prototype
- Design system tokens and components
What to expect
Design reviews happen on real devices, including small and low end phones.
- 04
Architect
Data model, permissions, integrations and hosting are decided and documented before heavy build begins.
Deliverables
- Data and permission model
- Integration contracts
- Hosting, environments and cost plan
What to expect
You see the architecture decisions and their trade offs in writing.
- 05
Build
Work ships in vertical slices that work end to end, so you can test real functionality every week or two.
Deliverables
- Working increments on a staging environment
- Progress notes against milestones
- Running demo at each checkpoint
What to expect
No long silent build phases. Progress is visible and testable.
- 06
Assure
Quality, security and accessibility are checked deliberately, not assumed.
Deliverables
- Automated tests and manual QA matrix
- Security and permissions review
- Performance and accessibility checks
What to expect
Known issues are listed with severity before launch, not discovered afterwards.
- 07
Launch
Deployment, data migration where needed, training and a monitored go live.
Deliverables
- Production deployment and rollback plan
- Training sessions and guides
- Monitoring and alerting configured
What to expect
A calm launch with a clear owner on both sides.
- 08
Maintain
Ongoing updates, support and improvements with defined response expectations.
Deliverables
- Maintenance agreement
- Scheduled dependency and security updates
- Improvement backlog and reviews
What to expect
Response expectations are written down and measured.
02What to expect
Promises we keep on every project.
- 01
A named point of contact
One person who knows your project end to end and answers within working hours.
- 02
Written, versioned proposals
Scope, assumptions and price in a document you can compare across versions.
- 03
Working software early
Thin vertical slices on a staging URL you can click through, not slide decks.
- 04
Your accounts, your code
Hosting, domains and repositories are created in your name from day one.
- 05
Honest status
Milestones are marked done only when they are tested with real data.
- 06
Documentation as we go
Handover notes and runbooks are written during the project, not after it.
Next step
Ready for stage one?
A discovery conversation costs nothing and usually saves weeks.
