How we work
Six phases. You always know which one you are in.
- 01
Discovery
How the business really works, including what nobody wrote down.
- Scope and priorities
- Roles and journeys
- Constraints and deadlines
- What to leave out of v1
- 02
Design
Interface and prototype, usable before we build it.
- Every screen in scope
- Clickable prototype
- Design system and tokens
- Responsive per device class
- 03
Architecture
The decisions that are expensive to change later.
- Data model and schema
- API contracts
- Technology choices, with reasons
- Environments and backups
- 04
Build
Short cycles, with something working to look at throughout.
- Staging from early on
- Regular demos, visible backlog
- Tests as part of the work
- Documentation written live
- 05
Launch
Data migrated, people trained, and a way back if needed.
- Production and cutover plan
- Data migration
- Handover and training
- Monitoring and alerts
- 06
Care
Fixes, updates and what comes next.
- An agreed response path
- Security and dependency updates
- Performance monitoring
- A roadmap for what is next
FAQ
Questions we get asked
How long does a project take?
It depends on scope. We tell you honestly after discovery, and early if it changes.
How do you price work?
After discovery, so the number means something. Fixed price for a defined scope, agreed phases otherwise.
What do you need from us during the project?
One person who can decide, and prompt feedback at review points. Projects slip waiting for decisions.
Can you work on a system somebody else built?
Often. We review the code and data model, then say honestly whether to continue, refactor or rebuild.
Let's build together
Ready to build something?
Tell us what you need. You get an honest view of scope, approach and cost — no obligation.