Reserved capacity, week after week.
From $2,200 a month for a fixed number of days each week, committed to your roadmap. A senior engineer building your product continuously — without a hire, a recruiter, or a twelve-month commitment.
This is not support. It's delivery.
A support retainer is reactive: something breaks or needs changing, you raise it, we respond within an agreed window. It carries a small allowance for changes and it's the right product when your software mostly needs to stay healthy.
Ongoing development is the opposite shape. Days are reserved in advance, work is planned rather than triggered, and the measure is what shipped this month — not how fast tickets got answered.
The two are deliberately separate because they pull against each other. Deep work on a multi-day feature and a one-day incident response window can't share the same calendar honestly. Sold together, both get done worse.
You have a roadmap and nobody to build it.
- A live product with paying users and a list of things it needs next
- A founder who has been doing the building and needs their week back
- A company between engineering hires who can't afford to stall for three months
- A business where software is important but not important enough to justify a full-time salary and the search that precedes it
- Anyone who launched an MVP and now needs version two, three and four
Reserved days, planned in cycles.
Reserved capacity
You book a set number of days each week and they're held for you. Not a pool of hours to draw down — specific days, on the calendar, not sold to anyone else.
Two-week cycles
At the start of each cycle we agree what's being built. At the end you get working software and a written summary. Priorities can change between cycles; changing them mid-cycle costs more than it saves.
You set the what, we set the how
You decide what the product should do. Architecture, sequencing and technical trade-offs are ours — that's the part you're hiring fifteen years of experience for.
Everything visible as it happens
Work lands in your repository through pull requests you can read. Deployed to a staging environment continuously. No reveal at the end of the month.
Priced by reserved days, billed monthly.
| Commitment | Roughly | Price |
|---|---|---|
| One day a week Steady progress on a short roadmap. Suits a live product with a modest backlog. | 4–5 days/mo | $2,200/mo |
| Two days a week Meaningful shipping every cycle. The most common choice. | 8–9 days/mo | $4,200/mo |
| Three days a week Continuous delivery on an active roadmap. | 12–13 days/mo | $6,000/mo |
Includes the full maintenance baseline — monitoring, backups, security patches and dependency updates — at no extra charge, since we're already in the codebase every week. Two-month minimum, then month to month with thirty days' notice. Capacity is limited and booked in advance.
What's committed and what isn't.
- Days are reserved, not banked. Unused days don't accumulate — the capacity was held for you whether or not it was used. If you're consistently not filling the time, we'll suggest moving down.
- Work happens on business days. Reserved days are agreed at the start and kept consistent so you know when things move.
- Urgent production issues are handled within the reserved days, and they push planned work rather than adding to it. If something is genuinely on fire, it comes first — and the roadmap slips by that much, visibly.
- This is not 24/7 cover. One engineer cannot honestly provide it. If your system needs round-the-clock response, you need a rota of people, and you'll be told that plainly.
- Scope changes between cycles are free. Scope changes inside a cycle waste the planning and usually cost you a day. It's your call, but you'll hear the trade-off.
- Notice runs both ways. Thirty days from either side, so neither of us is trapped.
Before you book.
How is this different from the support retainer?
Support is reactive, with a small change allowance — it keeps working software working. This is proactive and reserved in days — it builds new things on a schedule. If your main need is "don't let it break," take a support plan. If it's "we have a roadmap and nobody to build it," take this.
Can I have both?
You don't need both. Ongoing development already includes the maintenance baseline, because we're in the codebase every week anyway.
Why not just hire a developer?
If you have a year of full-time work and a six-figure budget, hire — and we'll help you interview. Reserved capacity makes sense when the work is real but not full-time, when you need senior judgment rather than volume, or when a three-month hiring search would cost you more than the salary difference.
What if I need more than three days a week?
Then you're close to needing a full-time person, and you'll be told so rather than sold a fourth day. We can help you hire and hand over cleanly.
What if my priorities change?
Change them between cycles, freely — a two-week cycle exists precisely so that you're never more than two weeks from a course correction.
Who owns the code?
You do, entirely, from the first commit. It lives in your repository and deploys to your cloud account. No proprietary frameworks, no lock-in, nothing that requires us to stay.
What happens if you become unavailable?
Everything is documented and in your repository as it's written, so another engineer can pick it up without archaeology. Cover arrangements are agreed in writing before we start.
Tell us what's on the roadmap.
Twenty minutes. Describe the product and what it needs next, and we'll tell you how much capacity that actually takes — including if the answer is less than you expected.