Ongoing product engineering for products that can't stand still.
A team that already knows your code keeps the roadmap moving, ships on a steady rhythm, and handles the updates, fixes and monitoring that keep a live product healthy.
- A team that stays
- Releases on a rhythm
- Monthly plan, 15 days' notice
When a product needs a team, not another project.
Launch is where most of the learning starts. These are the signs a product needs steady hands rather than a one-off build.
- 01
The roadmap keeps growing
Customers ask for more every month, and there's no team to build it at a steady pace.
- 02
Fixes wait for a freelancer
Bugs sit until someone is free, and each new person has to relearn the code.
- 03
Updates keep getting skipped
Frameworks, OS versions and dependencies fall behind, and the risk piles up quietly.
- 04
Nobody watches production
You hear about outages from customers instead of from alerts.
- 05
Hiring a full team isn't sensible yet
You need several skills but not several full-time hires, at least not yet.
- 06
Your build partner disappeared
The agency that built it has moved on, and you need someone to take over properly.
One project after another, or a team that stays?
Ad-hoc projects suit a product that rarely changes. A live product with an active roadmap is cheaper and safer with continuity.
| Consideration | Project by project | Ongoing product team |
|---|---|---|
| Context | Project by projectRelearned at the start of every project | Ongoing product teamKept and built on month after month |
| Pace | Project by projectBursts, then gaps | Ongoing product teamA steady release rhythm |
| Maintenance | Project by projectUsually skipped between projects | Ongoing product teamBuilt into every month |
| Monitoring | Project by projectNobody's job | Ongoing product teamWatched, with alerts |
| Commercials | Project by projectA new quote every time | Ongoing product teamA monthly plan, 15 days' notice |
If your product rarely changes, a lighter monthly care plan may be all you need. We'll suggest the smallest setup that keeps it healthy.
Everything a live product needs, every month.
New features and the unglamorous upkeep, handled by the same people, so neither gets dropped.
- 01
Roadmap delivery
New features planned with you, built in sprints and shipped in order of what matters most to your customers.
- Prioritisation
- Sprints
- Demos
- 02
Regular releases
Changes shipped on a predictable rhythm, reviewed and tested on staging before they reach your users.
- Release notes
- Staging
- Rollbacks
- 03
Monitoring and incidents
Errors, uptime and performance watched, so problems are spotted and fixed before customers report them.
- Uptime alerts
- Error tracking
- Incident notes
- 04
Maintenance and updates
Framework, OS and dependency updates applied on schedule, and security patches as soon as they're released.
- Dependencies
- OS updates
- Security patches
- 05
Experiments and improvements
Small tests on onboarding, pricing pages and key flows, read honestly and kept only if they work.
- A/B tests
- Onboarding
- Conversion
- 06
Monthly reporting
One page every month: what shipped, what we fixed, what we're watching and what's next.
- What shipped
- Health
- Next month
From handover to a steady rhythm.
Whether we built the product or not, the first month is about understanding it properly. After that it's a rhythm you can plan around.
- 01
Onboard and audit
If we didn't build it, we read the code, set up access and fix anything urgent before taking on features.
You get- Audit notes
- Access set up
- 02
Agree the plan
A monthly scope covering features, upkeep and support, with priorities set together.
You get- Monthly plan
- Priorities
- 03
Build and release
Two-week sprints, demos on staging and releases on a predictable rhythm.
You get- Releases
- Release notes
- 04
Watch and maintain
Monitoring, updates and fixes running alongside feature work, every month.
You get- Monitoring
- Updates applied
- 05
Report and replan
A monthly readout and a short call to set the next month's priorities.
You get- Monthly report
- Next month's plan
What we build is yours. In writing.
Software you'll run for years shouldn't tie you to the people who wrote it. Once the work is paid for it's yours outright, handed over in accounts you control.
- 01
Code and IP
Full ownership of the code and design files passes to you on payment. No licence fees, ever.
- 02
Your own accounts
Repositories, hosting, stores and domains are handed over in your name, not kept in ours.
- 03
Documentation
Setup guides, architecture notes and a record of key decisions, so any capable team can pick it up.
- 04
Confidentiality
We sign an NDA before you share anything sensitive, and treat your data that way throughout.
How a good product team behaves.
Continuity is the point, so these hold every month, not just in the first one.
- Continuity
The same people
A consistent team that knows your product, rather than whoever happens to be free.
- Rhythm
Predictable releases
A release cadence you can plan launches and announcements around.
- Quality
Reviewed and tested
Every change reviewed and checked on staging before it reaches your users.
- Safety
Patched promptly
Security updates applied as soon as they're released, not saved for later.
- Clarity
Plain reporting
A one-page monthly report in plain language, plus a weekly written update.
- Freedom
No lock-in
Month to month on 15 days' notice, with a documented handover if you ever move on.
Start where you are, with a fixed quote first.
Every engagement starts with an itemised proposal. Pick the model that fits what you already know.
- 01Discovery sprintThe problem is clear, the solution isn't yet
- 02Fixed-scope buildRequirements are understood and agreed
- 03Dedicated product teamThe product is live and keeps growing
Recent work from the studio.
A look at what we've designed, built and launched recently.
Need something other than ongoing work?
If the product needs a bigger change first, start with one of these.
- Product ModernisationThe codebase needs serious work before steady feature delivery is realistic.
- Dedicated Development TeamsYou want engineers working inside your own team and process.
- Custom Software DevelopmentYou need a new system built before there's anything to maintain.
- Digital MarketingThe product is healthy, and the next job is getting more people to it.
Questions
The things people
ask us first.
If yours isn’t here, send it over. We reply within 1 hour, guaranteed, and you’ll get a straight answer rather than a brochure.
What's included in a monthly plan?
+
An agreed mix of feature work, maintenance, monitoring and support, set out in writing for each month. You can shift the balance from month to month as priorities change.
Can you take over a product another team built?
+
Yes. We start with an audit and a short onboarding period to understand the code, fix anything urgent and set up access, then move into the regular rhythm.
How quickly do you respond to problems?
+
Production issues are watched with alerts, and we reply to messages within the hour. The response times for different kinds of issue are agreed in the monthly plan.
Is there a minimum commitment?
+
Plans run month to month, and either side can end them with 15 days' written notice. If you move on, we hand over the code, accounts and documentation.
How is this different from a dedicated team?
+
With ongoing product engineering we own delivery and run the process for you. With a dedicated team, engineers work inside your own process and report to your product lead.
Do you handle app store and OS updates?
+
Yes. iOS, Android, browser and framework updates are tested and applied as part of the monthly upkeep, so the product keeps working as platforms change.
Where ambitious
ideas become reality.
We design, develop, and support digital experiences that turn ambitious ideas into meaningful products.