Our process
Short cycles. Honest updates. No surprises.
A small senior team, working software every two weeks, and a fixed quote paid in milestones. After launch, an optional care plan keeps it secure, monitored and improving, with response times in writing.
- To a written scope and quote
- 48h
- Between working releases
- 2 wks
- Bug-fix warranty
- 60 days
- Notice to end a care plan
- 30 days
The commercial model
Pay once to build. Choose care after launch.
Step 1: the build
One-time project
A fixed quote for an agreed scope, paid in milestones. You own the code and accounts once it's paid.
- Paid discovery, credited to the build if you go ahead
- Written scope, timeline and fixed quote
- Milestone payments tied to delivery
- Changes agreed in writing before work starts
- 60-day bug-fix warranty after launch
- Source code, documentation and accounts handed over
Step 2: after launch
Monthly care plan
A monthly subscription that keeps your software secure, monitored and improving, with response times in writing.
- Hosting, monitoring and daily backups
- Security patches and dependency updates
- Agreed response times for issues
- Development time each month for improvements
- Monthly report in plain English
- Cancel with 30 days' notice
Delivery
From brief to live in five steps
Every project runs the same way, so you always know what happens next and what you're approving.
- 1
Discover
We learn how your business works, agree the goals and send a written scope and fixed quote.
- 2
Design
You approve a clickable prototype screen by screen before any code is written.
- 3
Build
Two-week sprints. At the end of each one you try the real product.
- 4
Launch
We go live at a quiet hour, train your team and hand over every account.
- 5
Care
A monthly plan keeps it secure, fast and improving as you grow.
After launch
Care plans that keep it sharp
Monthly plans, quoted for your system. Each includes everything in the one before it.
Essential
For websites and smaller systems that need to stay safe and online.
- Uptime and error monitoring
- Daily backups, tested quarterly
- Monthly security and dependency updates
- Business-hours support by email
- A small amount of change time each month
- Monthly report
Growth
Most chosenFor business systems and apps your team relies on every day.
- Everything in Essential
- Faster response times
- More development time each month, unused hours roll over one month
- Mobile OS, app store and certificate upkeep
- Performance and SEO health checks
- Quarterly roadmap call
Scale
For platforms where downtime costs money.
- Everything in Growth
- Out-of-hours cover for critical issues
- Dedicated account lead
- Custom service levels and uptime target
- Staging environment and release management
- Security review every year
Service levels
Response times, in writing
Targets during UK business hours. Out-of-hours cover for critical issues is part of the Scale plan.
- Critical1 hour
System down or unusable for everyone
Workaround within 4 hours
- High4 working hours
A key feature is broken, with a workaround
Fix within 2 working days
- NormalNext working day
A minor fault affecting some users
Next scheduled release
- Request2 working days
A change or improvement
Planned with you
Other models
When the scope will keep moving
Dedicated team
Developers working only on your product, month to month. Best for long roadmaps.
Time and materials
Flexible scope, billed for time spent with weekly reports. Best for evolving products.
Technical retainer
A set number of senior hours each month for advice, reviews and oversight.
Questions
Before you ask
What does the warranty cover?
Any fault in what we agreed and delivered, fixed free for 60 days after you accept the launch. New features and changes are planned separately.
Do we have to take a care plan?
No. Care plans are optional and run month to month with 30 days' notice. Most clients choose one because it keeps the same team on their system.
Can we change plans later?
Yes. You can move between plans at the start of any month.
What isn't covered by a care plan?
New features beyond the monthly development time, faults in third-party services, and changes made by other suppliers. We'll always tell you before any extra work.
When do we own the code?
Ownership of the code and accounts passes to you once the project is paid.
Tell us what you need built.
Share the problem in a few lines. After one call you'll get a written scope and a fixed quote within 48 hours.