Shared channel
A Slack or Teams channel with your engineers, your designer and your delivery lead in it. Ask anyone directly.
Our process
Six stages, and what you actually get from each
The same framework runs on a $20,000 website and a $300,000 platform - the depth changes, the sequence does not. You own the deliverables at every stage, including if you decide to finish elsewhere.
01
Discover
We learn the business before the software - goals, constraints, competitors, the people who will use it and what success is actually measured by.
Deliverables
- Stakeholder interviews
- Analytics review
- Competitive teardown
- Technical audit of anything existing.
02
Define
Scope, architecture and a costed roadmap. You get documentation you own, whether or not you build it with us.
Deliverables
- User flows
- Information architecture
- Technical specification
- Sprint plan
- Line-item estimate.
03
Design
Wireframes to a full design system, tested with real users before anyone writes production code.
Deliverables
- Wireframes
- Clickable prototype
- Visual design
- Component library
- Accessibility review.
04
Build
One-week sprints with a working demo at the end of each one. You see progress in software, not slide decks.
Deliverables
- Sprint development
- Code review on every pull request
- Automated tests
- Staging deploys.
05
Launch
Load testing, security review, SEO migration checks and a rollback plan before anything goes live.
Deliverables
- QA cycle
- Performance testing
- Redirect mapping
- Analytics verification
- Go-live runbook.
06
Grow
Post-launch measurement and iteration - because the version that launches is never the version that performs best.
Deliverables
- Monitoring
- Monthly reporting
- CRO testing
- Feature iteration
- Ongoing support SLA.
Communication
How we stay in sync
The parts of agency work that go wrong are almost never technical. They are communication failures that compounded quietly.
Fortnightly demos
A live walkthrough of working software every second Friday. Thirty minutes, recorded, with the build available to click through yourself.
Open project board
Linear or Jira, visible to you at all times. Every ticket, every estimate, every blocker.
Written decisions
Architecture and scope decisions recorded with the options we considered and why we chose one. Useful in month two, essential in year two.
Response SLA
Under four hours during your business day for normal questions; immediate escalation for anything affecting production.
Outcome reporting
At 30, 60 and 90 days post-launch: what the agreed metrics did, and what we recommend next.
FAQ
Process questions
Do we have to start with discovery?
For anything beyond a small, well-defined build, yes. Discovery is where the expensive mistakes get caught - before they are built. On smaller projects it compresses to a few days rather than a few weeks.
What if requirements change mid-project?
They usually do. On dedicated-team engagements you simply re-prioritize the backlog, at no commercial cost. On fixed-scope projects, changes go through a written change order with cost and timeline impact, so there are no surprises on the invoice.
Can we use our own project management tools?
Yes. We work in your Jira, Linear, Asana, Monday or Notion rather than making you learn ours. If you do not have one, we set up Linear and hand it over.
How involved do we need to be?
Budget about two to four hours a week from one decision-maker: the demo call, feedback on deliverables, and answering questions about your business. Projects where nobody has that time take significantly longer.
What happens if we want to pause?
Fixed-scope projects can be paused at any milestone boundary. Dedicated team engagements require 30 days notice. In both cases you keep everything built up to that point, in a working state.
Let’s scope your project - free, and without a pitch deck
Book a 45-minute call. We will ask about your goals, your constraints and your timeline, then send a written recommendation with real numbers. If we are not the right fit, we will tell you who is.