How a project actually runs
Four stages, each ending with something concrete you receive before the next one starts. No black boxes, no silent scope changes.
What we commit to
- Code ownership
- Yours
- Scope changes
- Written first
- Pricing
- Fixed per phase
- Handover
- Documented
What happens, and what you get
Each phase is priced and approved separately, so you are never committed to the full cost up front. Durations are typical for a scoped project.
- 1–2 weeks
Discovery and scoping
We map how the business actually works before proposing anything — your workflow, constraints, users and what a good outcome looks like.
- Written problem definition
- Scope and assumptions
- Fixed price for phase one
- 1–2 weeks
Structure and interface direction
We turn that into a concrete plan: information architecture, screen or page structure, and the technical approach.
- Architecture outline
- Interface direction
- Delivery timeline
- 6–14 weeks
Build and weekly review
Work ships in reviewable increments. You see progress every week and can change direction between phases rather than at the end.
- Weekly working builds
- Review sessions
- Written change notes
- 1–3 weeks
Launch and support
Go-live is a milestone, not the finish line. You get handover, documentation, a warranty period and optional ongoing support.
- Deployment and handover
- Documentation
- Post-launch warranty
What we need from you
Projects slip most often because a decision is waiting on someone. These are the points where we need input.
- Discovery
- One decision-maker available for two workshops.
- Design
- Feedback on key screens within three working days.
- Build
- A named contact for questions, and access to any existing systems.
- Launch
- Someone to run through the training and own it afterwards.
Next step
Start with a scoping conversation
Tell us what you are trying to build or fix. You will get an honest view of scope, cost and whether we are the right team for it.