03 // the build
the one-time build.
A clean migration to Storyblok + Astro — the setup the pod then takes over. Pure HTML to the browser, visual editing for marketing, edge caching for everyone, and a cutover that never drops a ranking.
(02)
four phases, in order
Incremental by design. Nothing goes live unproven.
[01] · phase
map
Every URL, template, and content type inventoried. The full redirect map and data audit are done before a single component is written.
[02] · phase
model
Storyblok-first schemas modeled around your publishing workflow — typed blok contracts, visual editor preview. Sanity supported as an alternative.
[03] · phase
build
Zero-JS Astro layouts with islands only where interactivity is real. Surrogate-key edge caching and CI performance budgets — 95+ Lighthouse out of the box.
[04] · phase
cutover
Every legacy URL behind a tested 301, crawl-diffed before and after. DNS and edge routing flip atomically with instant rollback.
(03)
what ships
rebuild the system behind the storefront.
(01) A fully custom Astro platform
Storyblok-connected, content-driven layouts delivering pure HTML by default.
(02) Typed blok contracts
Content models with visual editor preview, so marketing composes pages without tickets.
(03) Edge caching and pipelines
Surrogate-key invalidation, edge workers, and a deployment pipeline configured and documented.
(04) 95+ Lighthouse out of the box
Every template ships against a JS and LCP budget, verified in CI before it can regress.
(04)
the safety rails
What a migration must never cost you.
[01]
100% redirect preservation
Every legacy URL maps to a tested 301 with schema parity, verified by crawl diffs before and after launch.
[02]
Zero-downtime cutover
DNS and edge routing flip atomically with instant rollback. Visitors never see a maintenance page.
[03]
No feature freeze
Strangler-pattern extraction: high-traffic routes move first, behind a proxy. Marketing keeps shipping during the migration.
[04]
Budgeted, not hoped
Every template ships against a JS and LCP budget, verified in CI before it can regress.
(05) · the price
one build, fixed scope
A number against your estate — templates, redirect surface, data, integrations. Confirmed before anything starts.
The fractional systems pod
Continuous bi-weekly sprints — content modeling, performance, integrations, edge and cache. Capped at three clients.
The 5-day read
The entry. We profile your platform and size the work — 100% credited toward a sprint within 30 days.
(06)
what a migration is not
Boundaries keep the cutover honest.
(01) rebuild the platform
We update the content model, rendering, caching, and deployment pipeline with the storefront.
(02) incremental cutover
Routes move one at a time. Each one is verified in production before the next moves.
(03) post-launch support
After cutover, the pod monitors Core Web Vitals, fixes regressions, and maintains the CMS on the same stack.
(07)
questions
What people ask before scoping the build.
(01) How is the number set?
Against your estate: number of templates and content types, the redirect surface, data cleanup, and integrations. You get a fixed-scope number before anything starts — not an hourly rate card.
(02) How long does it take?
It depends on the estate, but routes move one at a time, so your biggest wins ship in the first weeks — not at the end. You get a timeline with the scope.
(03) Will we lose rankings?
No — that's the whole design. 100% redirect preservation with schema parity, crawl-diffed before and after, and an atomic flip with instant rollback. Search equity carries across.
(04) Can the old site keep running during the build?
Yes. Strangler-pattern: the legacy platform stays live while routes are extracted behind a proxy. Feature delivery continues throughout.
(05) What happens after cutover?
The fractional systems pod. Monitoring, CWV fixes, content modeling, and integrations — the same principals who built the platform, on continuous bi-weekly sprints, from day one.
ship the one-time build.
One project. A sub-second platform, visual editing, and edge caching — then the pod keeps it fast.