Each phase has its own deliverables and its own exit, so you can start with one and stop after any of them.
Know what you have before you move it.
Most rebuilds go wrong in week six, when someone finds the plugin nobody listed. We list it in week one. You get a written answer, including when that answer is to stay put.
We crawl every URL, list every plugin and integration, and measure speed, accessibility and search health on the site you have now.
Every content type, plugin, form and integration gets a line: moved by the importer, rebuilt, replaced or retired.
Before anything changes we record your rankings, top pages and traffic, so launch is judged against facts.
Already on Astro and it isn’t as fast or as easy to run as it should be? We review the code, the content setup and the build, and tell you what to fix first.
Keep the brand. Lose the template.
A theme gives you someone else’s structure. We start from what your team actually publishes, then design the blocks they’ll use to publish it.
We turn your pages and posts into structured content: real fields, relations and permissions, instead of one big text box.
Bring a Figma file or let us design one. Either way it becomes Astro components with named tokens, so the site stays consistent as it grows.
Your team builds pages from approved sections, so a new landing page takes minutes and still looks right.
New site or a move, the same standards.
Your current site stays live the whole time. Nothing switches over until the new one has passed its checks.
A new marketing site, publication or brand site, built from the content model up and deployed to Cloudflare.
We export your content, map it to a structured content model and bring it into Astro. Templates, page-builder layouts and add-ons are rebuilt as Astro components.
Already on Sanity, Contentful or Storyblok, or set on one? We build the Astro front end on top of the CMS that suits your team, not the one that’s easiest for us.
There’s no importer for these, so we script the content across and rebuild the design, which also frees you from the platform’s monthly bill.
CRM, forms, payments, booking, internal APIs. We write TypeScript EmDash plugins that ask for the narrowest permissions that work.
We test the new site against the old one, walk every redirect, then switch DNS. Your old site stays available until we’ve verified the live one.
The same team after launch.
A launched site is the start of the work. Stay with us for as much or as little as you need, or take the code and go. It’s yours either way.
One plan at $99 a month: patches, updates, monitoring and unlimited tasks, with same-day turnaround and a report on what was done.
We teach your team the admin on your own site, then leave the recording and the guide behind.
Every EmDash site has an MCP server. We connect the agents you use, scoped to the same permissions as a person, so drafts stay drafts until someone approves them.
Technical SEO, content fixes, landing pages and tests, reported every quarter in terms of leads.
Once one site is done, the next costs less: shared components, the same playbook and one place to manage it all.
Send us the address. We’ll rebuild your homepage in Astro, then you can decide what to do next.
