Approach
A clear process, engineered for fewer surprises.
Five stages, each with a defined outcome. You always know what we’re working on, what it costs and what comes next.
01
Discover
Understand the problem before solving it.
Typical timeframe:1–3 weeks
What happens
- Stakeholder interviews and workshops
- Review of existing systems, data and constraints
- Goals, users and measures of success
- Risks identified early, while they’re cheap to fix
What you receive
- A discovery report with scope, risks and an estimate
- A prioritised feature roadmap
02
Design
Make it real before we build it.
Typical timeframe:2–4 weeks
What happens
- User journeys and information architecture
- Wireframes and interactive prototypes
- Visual design and a reusable design system
- Technical architecture and delivery plan
What you receive
- A clickable prototype
- Design system and specifications
- Architecture and delivery plan
03
Engineer
Build in small, tested increments.
Typical timeframe:6–16 weeks
What happens
- Two-week sprints with a demo at the end of each
- Automated testing and peer code review
- Security built in, informed by the Essential Eight
- Continuous deployment to a staging environment
What you receive
- Working software every sprint
- Access to staging and your code repository
- Written sprint summaries
04
Launch
Go live calmly.
Typical timeframe:1–2 weeks
What happens
- Performance, accessibility and security checks
- Data migration and production set-up
- Monitoring and alerting switched on
- Training and handover for your team
What you receive
- A production release
- Runbooks and documentation
- Hands-on launch support
05
Evolve
Improve with real usage.
Typical timeframe:Ongoing
What happens
- Usage and performance monitoring
- Improvements prioritised with you
- Maintenance, updates and security patching
- Planning for the next release
What you receive
- Monthly reports
- Agreed response times
- A roadmap for what’s next
Timeframes are typical for a first release and are confirmed after discovery.
Engagement models
Three ways to work together.
Pick the model that fits where you are. Many clients start with a fixed-scope discovery, then move to a dedicated team or retainer.
01
Fixed scope
Best when the brief is clear
A defined scope, timeline and price agreed upfront. Ideal for well-understood projects, discovery phases and audits.
- Fixed price and timeline
- Changes quoted before work starts
- Milestone-based payments
02
Dedicated team
Best when the product keeps growing
A senior team working as an extension of yours, billed per sprint. Priorities can change as you learn.
- Scope flexes sprint to sprint
- Scale the team up or down
- Fortnightly planning with you
03
Ongoing retainer
Best after launch
A monthly allocation for maintenance, improvements and support, with agreed response times.
- Monthly hours or outcomes
- Security updates and monitoring
- Priority support
Communication
How we keep you in the loop.
No black boxes. You’ll see the work, the budget and the risks as they happen, in tools you already use.
Rituals
- Kick-off workshop
- Fortnightly sprint planning and demos
- A 15-minute weekly check-in
- Quarterly roadmap review
Tools
- Slack or Microsoft Teams, your choice
- A shared project board
- Code in your own GitHub or Azure DevOps
- Figma for design review
Reporting
- Written sprint summaries
- Budget spent and forecast
- Risk and decision log
- Release notes