Keep Your Site. Change What It Does.
You already have a site you like. ZINC moves it, page for page, onto a foundation your own AI agent can run, governed by Dispatch from the first commit.
Move Beyond Your CMS. Keep the Rest.
CMS platforms were built for editors and templates. AI agents work best in the code that runs your site.
Your design. Matched at representative pages and viewports, differences documented before cutover.
Your content and blog. Every page and post, moved.
Your search equity. URLs, redirects, titles, and structured data, mapped and verified.
Your integrations. Forms, analytics, and CRM, each with an agreed destination.
Your code. In your own repository. No lock-in.
Assess. Migrate. Connect. Launch.
Two timelines, stated separately. A working preview takes days; production launch is scoped around your content, integrations, and approvals.
Assess and Architect
We map the site, the integrations, and how your team works, then pick the stack: Astro on Cloudflare or Netlify for content-led sites, Next.js on Vercel for app-like ones. We sell none of them.
Migrate and Connect
We build the new site in parallel while yours stays live, verify it page by page, then connect Dispatch: roles set, approvals on, first change practiced.
Launch and Hand Off
We cut over, monitor, and hand off your Website Operating Playbook: ownership, supported agent tasks, brand guidance, review duties, recovery, training, and when to call ZINC.
Migrate As-Is, Improve, or Redesign.
Approve a migration without approving a rebrand. Pick the path that fits.
Migrate as-is: your site, on the foundation you need
Migrate and improve: plus conversion, performance, accessibility, and AEO
Redesign and migrate: a new site by ZINC, born AI-native
Every path lands on Dispatch, first 90 days of Team included
Fixed quote after a short assessment: inclusions, exclusions, and recurring costs shown
The Safety Net Is the Point.
An AI-built site with no system around it is the real risk: nobody knows what changed, a bad change goes live, and marketers wait on developers again. Dispatch answers all three.
Every change previewed before it ships
Approvals follow roles; high-risk work needs two people
Any change restored in one click
Your team edits by asking, not by filing tickets
Turn Dispatch off and the site keeps running
We Migrate From Where You Are
WordPress, Webflow, Squarespace, Wix, HubSpot CMS, Framer, and legacy platforms. If your platform still fits your team, we will say so.
Sites Already Running This Way.
Named case studies follow as clients agree.
A Law Firm
Webflow to Astro on Cloudflare. 47 routes, git-based blog, governed from cutover.
A Financial Advisory Firm
To Astro on Netlify. Two design variants delivered as live previews.
This Site
Webflow to Next.js on Vercel. Verified page by page, run on Dispatch with Claude Code on the repo.
ZINC helped us rethink how our website drives growth. Their AI-powered approach transformed our content and visibility, delivering measurable gains in both traffic and qualified leads.
See Your Site AI-Ready.
Give us your URL. We rebuild two representative pages on an agent-ready stack, run one real change through Dispatch, and come back with a stack recommendation, an integration and plugin risk map, and a straight read on whether enablement, migration, or a build fits. No commitment.
FAQs
Straight answers on moving a site.
B2B and informational sites, roughly 20 to 300 pages, with lead forms, a blog, service pages, and CRM connections. Ecommerce stores, membership systems, and plugin-heavy applications need separate discovery. Sometimes staying put is the right answer, and we will say so.
URLs are preserved or mapped, metadata and indexability are validated, and the site is monitored after launch. Google itself anticipates some fluctuation after a site move. A careful process is the promise, not a guarantee.
Two numbers, stated separately. A working preview of representative pages takes days. Production launch is scoped around your content, integrations, and approvals, and both numbers appear in every quote.
Not for day-to-day changes. Your team asks, reviews, and approves in Dispatch. ZINC stays on as operator, advisor, or escalation contact if you want us to.
Yes. If Webflow still fits your team's workflow, we may recommend keeping it. If cost, code portability, agent access, or operational speed has become the constraint, we recreate the site on an open, agent-ready stack and preserve the design and content.
It is retired. Content moves into the repository, or into a headless content backend if you need one. No more seats, plugins, or page-builder hosting.
A fixed-quote project after a short assessment. Every quote shows the one-time fee, inclusions, exclusions, acceptance criteria, launch estimate, stabilization period, recurring costs, and a full comparison with what you pay today.
See What Your Site Could Be.
Start with the free preview. Leave knowing which path fits, who runs the site after, and what it costs.