01
Keep
Stay safe and stay up
The floor. We patch libraries, renew certificates and fix what breaks. Nothing new gets built. Good for a stable product with a small user base.
Launch is
the halfway mark
The first release proves the idea. Everything after it decides whether the idea earns money. We keep your product patched, watched and moving. The engineers on the retainer are the ones who wrote the code.
- 03 Plans on this page
- 04 Areas we watch
- 05 Stages per month
- 01 Team, build and support
Three ways to keep going
Pick the level of care the product needs today. You can move up or down at the end of any month. The team stays the same across all three.
02
Keep and improve
Fixes plus a small backlog
Everything above, plus a monthly slice of build time. You spend it on the queue you already have. Most teams sit here after their first launch.
03
Evolve
A roadmap, not a queue
A standing squad on your product. Discovery, design and release run on the same clock as the fixes. This is a build engagement that never stopped.
| Scope | Keep | Keep and improve | Evolve |
|---|---|---|---|
| Security patches | Included | Included | Included |
| Bug fixes | Included | Included | Included |
| Monitoring and alerts | Included | Included | Included |
| Monthly build time | None | A fixed slice | A standing team |
| Design work | None | On request | In the sprint |
| Growth and tracking work | None | On request | In the sprint |
| Queue order | Scheduled | Standard | First |
What we watch
Support gets cheap when problems are found early. So we instrument the product on day one and read it every week. Four things get a permanent eye on them.
Alerts land in a channel you sit in too. You see the same signal we do, at the same moment.
- 01
Errors
Crashes and failed requests reach us before a user writes in. We keep the trail so a fix starts with facts, not guesses.
- 02
Speed
Pages and screens get timed on real devices. Slow is a bug here. We treat it like one and book the work.
- 03
Dependencies
Libraries age. We track what your app pulls in, read the advisories and update on a schedule you approve.
- 04
Money paths
Signup, checkout and billing get checked every release. These flows earn the revenue, so they never ride on hope.
What a month looks like
Same five stages, every month, in this order. You always know which one we are in and what lands next.
- 01
Triage
New reports land in one queue. We size each one and tell you what it costs before we touch it.
- 02
Fix
Breakage first, always. Small fixes ship as they are ready, not at the end of the month.
- 03
Harden
Patches, backups and access reviews. Quiet work that only shows up when it was skipped.
- 04
Build
The agreed slice of new work. You choose what goes in it. We show a demo before it merges.
- 05
Report
A written note: what shipped, what it cost, what we suggest next. Numbers come from your own tools.
Retainers usually start from a build. See how the same team handles SaaS and product development or a web development project, and how QA and testing keeps releases boring.
Before you ask
You did not build it. Can you still take it over?
Yes. We start with a read of the code and the tools around it. You get a short written verdict with the risks we found and what each one takes to clear.
What if nothing breaks this month?
Then the hours go to the backlog or to hardening. Unused time is not billed twice and it never turns into busy work.
Do we keep our own access?
Always. Code, servers and analytics stay in your accounts. We work inside them. Ending the retainer takes a revoked key, not a migration.
Can support and growth run together?
That is the point of one team. The same sprint can carry a fix, a new screen and a campaign change. Nothing waits on a handoff.
Hand us the product you already have
Send the repo, the stack and the thing that worries you most. We reply with a read of the risks, the plan that fits and a start date.