04 · Compounding
Retainer. Monthly.
Monthly partnership. We keep the system running, evolving, and getting smarter — month over month, with one Slack channel and one founder on call.
Best for
- Clients post-MVP or post-Full Build who want continuous iteration
- Operators running AI-powered systems who need a builder on call
- Teams who've outgrown freelance support but don't want a hire
Not for
- "Fix it once and leave" needs — that's an Audit
- Pure infra/devops support — we build, we don't sysadmin
What you get
Concrete deliverables.
- 01Build hours per month · scope agreed monthly
- 02Monthly improvements and new features shipped via PR
- 0324-hour response on issues, business hours
- 04Quarterly strategy session · roadmap review
- 05Direct Slack channel with one founder on call
- 06Production monitoring + on-call rotation
The timeline
Monthly.
- Month startRoadmap review. Top priorities locked. Build hours allocated.
- Mid-monthContinuous PR shipping. Slack always-on. Demo if stakeholders want it.
- Month endRetro. What shipped, what didn't, why. Invoice + next month's scope.
- Quarterly90-min strategy session. Roadmap reset. Long-term direction confirmed.
Common questions
Questions we get a lot.
What's included in the build hours?
Anything we agree on in the monthly scope. Features, fixes, infra work, documentation. We don't separate "dev" from "ops" — it's all one pool.
Can we ramp build hours up or down month to month?
Yes. Most clients flex by 20–40% based on what's coming. We agree the next month's scope at month-end.
What if we want to add a second team member from your network?
Yes. We bring in specialists per domain — extra builder, designer, or domain expert — billed at their day rate, transparent.
How fast do you respond to outages?
24 hours business hours by default. Critical-path systems can move to a 4-hour SLA at extra cost.
Can we cancel mid-month?
After the three-month minimum, yes — month-end notice. We always finish what's already in flight before stopping.