A fit when
- You have an Astro site your team owns, often after a NewBase migration.
- You want steady shipping without hiring a full-time web engineer.
- One clear queue beats an agency black box or a freelancer who disappears.
Ongoing
Your site keeps moving after launch.
Every migration includes 30 days of hypercare: I check indexing, traffic, forms and redirects closely after launch. Continuous development is what comes next: $2,500 a month of ongoing work on the codebase you own. You send one request; I ship a preview; you approve. Pause or cancel any month. No minimum term.
$2,500 a month · one request at a time · typically two to three business days · pause or cancel any month
Built as the next step after a NewBase migration, once hypercare has confirmed the move held, or for an Astro site your team already owns. If you are still on Webflow, Framer, or WordPress, start with a migration first.
What is included each month.
The pains this covers are the ones that show up after launch: the site is expensive to keep changing, marketing cannot ship without a developer, and AI tools cannot safely work on a locked platform.
-
One shipping slot
One active request at a time. That is the monthly capacity: focused work with a clear finish line, not a pile of tickets in parallel.
-
The Console request queue
Submit the ask, see status, review the preview, approve or request changes. The Console is the ops surface for this retainer, not a separate product.
-
Monitoring between ships
I keep a light watch on the live site after publishes: failed forms, broken journeys I notice, and the usual post-ship checks. It is care, not a 24/7 ops contract.
-
Small redesigns
Layout and component changes that fit the system you already have: a section rework, a new page from existing parts, a tighter mobile pass. Not a brand overhaul.
-
CMS help
Sanity support when day-to-day editing is not enough: fields, collections, permissions, stuck drafts, and the odd model tweak so marketing can keep publishing.
-
Preview before publish
Every change lands in a preview first. You approve or ask for changes before it goes live.
How a request works.
Same loop every time: ask, preview, approve, publish. You can see a workflow concept with sample data on the demo; Continuous development is how you get that loop on your real site.
-
You submit a request
Through the Console, or the channel agreed at kickoff. One outcome per request: the page, the change, and what “done” looks like.
-
I clarify scope if needed
If it is bigger than one slot, I split it or I quote it separately. The two-to-three-day clock starts once the ask is clear.
-
A preview lands
I do the work in the repo and CMS you own. You get a preview link and a short note on what changed.
-
You approve or request changes
Approve ships it. Requesting changes sends it back into the same slot until it is right.
-
Publish and close
I publish, mark it done, and the slot opens for the next request.
What is not included.
- A full redesign or new design system. That is scoped and priced on its own.
- Parallel workstreams. One active request at a time means one, not three lanes.
- Net-new product UI, apps, or multi-site programs.
- Hosting account moves, DNS ownership transfers, or platform procurement.
- Rush work under two business days, unless you and I agree it in writing first.
- Pure Webflow, Framer, or WordPress maintenance. If the site should stay on the builder, stay there or hire a partner for that platform.
If a request is bigger than one slot, I split it across months or I quote it as a separate piece of work. I will say so before starting, not after.
Price and term.
$2,500 per month, billed in advance. One active request at a time, typically two to three business days once scoped. There is no minimum term. Pause or cancel any month; the retainer does not renew, and there is no charge after the current month.
It picks up where hypercare ends. The 30 days included with every migration cover the move: indexing, traffic and the checks after cutover. Continuous development covers what you want to build next. Start when hypercare ends, or later once the team has settled into the CMS. It is optional. The full commercial wording is on the terms page.
Who it is for, and who it is not.
Not a fit when
- You need parallel tracks or an embedded engineer in your standups.
- The site should stay on Webflow, Framer, or WordPress for visual editing.
- You want a full redesign or a multi-brand program first. Scope that separately.
Still on a builder platform? See what a migration costs, or run the cost calculator before you and I talk.
Next step
Ready to keep shipping?
Send your site
I can scope a migration. Send a brief and I will reply by email with next steps.