Basenine

A 20-minute call. You keep the migration plan either way.

A website rebuild and Claude setup for B2B marketing teams without a developer:

Ship new pages the day you need them. On brand, without a developer, and without breaking your site.

You describe the page you need, Claude builds it from your design system, and you approve it and ship it the same afternoon, all on a site we build for you on Sanity and Astro with Claude set up on your machine.

A 20-minute call. You keep the plan either way.

This is what getting one campaign page live looks like today.

  1. 01 It starts with a message: the expo page needs to be live, ASAP.
  2. 02 The brief lives in a Google Doc.
  3. 03 The draft gets written in Claude, off your site.
  4. 04 The design lives in a Figma file.
  5. 05 Someone asks the dev team to build it.
  6. 06 It lands in the backlog. Earliest slot: two weeks.
  7. 07 Someone rebuilds it by hand in Webflow.
  8. 08 The mobile layout breaks. Nobody warned you.
  9. 09 Sales finds it before you do.
  10. 10 And the expo is tomorrow.
  11. Now it's one system: describe the page, approve it, and ship it the same afternoon.

A client who moved

Frankly

Danish insurance startup with over $4M raised

2–3 hrs

Frankly's campaign landing page, built by their CXO with Claude.

3 mo → 1 wk

Mickey's estimate for 100 landing pages, before and after.

The website bottleneck

Your marketing team is AI-native. Your website isn't.

Your team drafts pages, copy and whole campaigns with Claude in an afternoon. Then the work reaches the website and stops, because there are only three ways to get a new page live, and none of them works.

Door 1

Ask a developer.

Then you wait two days if you're lucky and two weeks if you're not, for a change you could describe in one sentence. Most small teams don't have a developer, so the message goes to an agency that starts with “Help.”

Door 2

Do it yourself in Webflow.

You open it once a month, so you relearn it every time. The line between editing and development is thin, and it's easy to cross without noticing. Change one section and the mobile layout needs fixing. Even when it works, it doesn't quite look like the pages your designer made. And Webflow never warns you what else your change just affected.

Door 3

Point AI at Webflow.

Webflow's own AI is slow and makes mistakes, and someone still has to clean up after it. We asked one for a simple redirect last month and were told it was an enterprise-plan feature. The work moved. It didn't go away.

So the ideas wait. The campaign ships late, or smaller, or not at all.

A 20-minute call to map what moves, what gets rebuilt and what it costs.

The agentic website model

Webflow solved the last website problem. It didn't solve this one.

Webflow gave marketing teams something they badly needed: control of the site without a developer for every change. From 2018 to 2023, that was the breakthrough.

It mattered because code felt out of reach. That's no longer true. Marketers are getting technical, using GitHub and Claude Code to ship what once required developers.

The bigger teams have already moved.

55%

run a headless, code-owned site past 1,000 employees

21%

do the same at 50–100 employees

Source: MKT1's study of 100 fast-growing B2B companies

“Webflow used to seem easy. After using this setup, it seems so complex.”

Mickey Switzer, CXO, Frankly

What changes

What changes when your website runs on Claude

You describe the landing page you need, and it's live that afternoon. It looks like the rest of your site, and nobody had to file a ticket. No crossed fingers.

  1. 01

    Your team already writes the page with Claude. Today it stops there, because nobody can publish it. One step closes that gap, and it takes an afternoon.

  2. 02

    Ask AI for smaller text and it invents an 80% modifier nobody wanted. The “Brand Rails” setup is why that stops happening, and why your team’s pages come out looking like your designer made them.

  3. 03

    Leaving Webflow means you’ll need a developer again, right? Wrong. Your team keeps changing pages the same way they’d ask a person.

  4. 04

    Three versions of your homepage behind a toggle, so you can click between them before you choose. One sentence to ask for.

  5. 05

    The easiest thing you’ll stop doing: compressing images and hunting through ten open-source tools to do it.

  6. 06

    What happens to the pages you talked yourself out of, once the website stops being the hard part.

  7. 07

    “Which posts brought the most traffic last quarter?” A question you ask Claude directly, instead of waiting on your agency’s next report.

  8. 08

    Your CEO forwards a Lovable demo, a YouTube build, a LinkedIn post about someone who shipped a site with AI in a weekend. You can do that. The difference is it goes out on your brand, through your components, and it’s still your website afterwards.

  9. 09

    Something breaks at 5pm on a Friday. Today you message the agency and wait until Monday. Now you tell Claude what’s broken and ask it to fix it.

  10. 10

    How to add schema, meta fields and redirects by asking for them in plain English. No plugin, no ticket, no enterprise plan.

A 20-minute call. You keep the plan either way.

How it works

Claude builds your pages. Brand Rails keeps them yours.

Brand Rails is the system we build into every site. Claude can only build from components your designer approved, and every change arrives as a draft you preview before it goes live. So everything Claude ships looks like your site, and nothing reaches your visitors until you've seen it.

The rails came from our first three migrations and every mistake we made on them.

We design it with you.

Positioning, messaging, visual direction and your core pages, designed by people with taste. If your messaging isn't settled yet, we start there, because a fast website repeating the wrong message is worse than a slow one.

Step 01 · Design

We build it in code and lay the rails.

Your site is rebuilt on Sanity and Astro, and you'll never have to read any of the code. Every section becomes an approved component. Then we write down the details Claude would otherwise guess, like what an active tab looks like, so it gets them right the first time.

A migration takes two to three weeks. With a redesign first, design and build run in parallel, so the whole project takes 10–12 weeks.

Step 02 · Build

We set it up on your machine.

We connect Claude to your site on your own computer and walk your team through it. Then the new site goes up on a staging domain for a week, and you test it, break it and try everything before it goes live.

Step 03 · Set up

What your day looks like after launch

A 20-minute call. You keep the plan either way.

From a client who moved

When you don't work in Webflow every day, you have to onboard yourself every time, and you know that everything you do can still break. Now I basically just describe what I want and it updates. Our Tech BBQ landing page was done in two or three hours, and the full campaign was ready the next day. The website was almost the smallest part of it.

Mickey SwitzerCXO, Frankly

The offer

What you get

Most teams come to us with a site they like and a stack they can't ship from. That's the migration: same design, same content, same rankings, live on the new stack in two to three weeks. If the site needs rethinking first, we design it and then migrate.

Most teams start here

Migration

$5K–$10K

2–3 weeks

Your site as it is today, rebuilt on Sanity and Astro with Brand Rails and Claude set up, so your team ships pages from the day it's live.

  • Your blog and CMS content moved across
  • Your current design rebuilt as approved components
  • Brand Rails: the component library and the rules Claude builds by
  • Claude connected on your machine, plus a walkthrough
  • SEO continuity: one-to-one redirects, metadata, structured data, performance
  • A staging week before anything goes live
  • 30 days of support after launch

If the site needs rethinking

Redesign and migration

$10K–$30K

10–12 weeks

Positioning, messaging and a new design by people with taste, then the same migration underneath it. Design and build run in parallel, so changing platform doesn't add a phase.

  • Everything in the migration
  • A positioning and messaging review
  • Visual direction and your core pages designed
  • New sections built as components, not one-offs
  • 60 days of support after launch

After launch, the only running costs are the CMS and hosting.

You don't go live until you're confident.

The new site runs on a staging domain first, and your team tests it, breaks it and tries every edge case. It goes live when you say so, and we stay with you afterwards to fix anything that comes up.

You'll know what moves, what gets rebuilt and what it costs.

Why not just…

You have other options. Here's where each one stops.

Each of these works for someone. None of them gets a small team shipping new, on-brand pages by itself.

Build it yourself with AI

Fast to start, and your CEO may already have sent you the Lovable link. But you become the person building pages at midnight, the pages drift off-brand, and they aren't connected to your CMS, your SEO or the rest of your site.

Where it stopsYou get pages, not a website your team can keep running.

Use Webflow's own AI

AI writing into Webflow is slow and makes mistakes, and someone still has to tidy up after it. Teams that try it usually end up running a workaround on top of Webflow.

Where it stopsThe cleanup still lands on a person.

Hire a migration shop

They move your content to a better CMS and leave. It's a one-off engineering project with no shipping layer on top, so your team is no faster than before.

Where it stopsNew pages still need someone technical.

Switch to a platform builder

Prismic, Storyblok and the like let you move fast inside a fixed ceiling: developers build the blocks, and your team rearranges them.

Where it stopsAnything genuinely new goes back in the queue.

Keep doing it by hand

The familiar path. Every small change waits, the backlog grows, and each campaign ships a little later than the last.

Where it stopsThe site keeps falling behind the team.

Basenine Labs

We rebuild your site in code, lay Brand Rails so Claude only builds from approved components, set it up on your machine, and stay 30 to 60 days after launch.

Where it goesYour team ships new pages the day they need them, on brand, without a developer.

Not sure which route fits your team? That's what the call is for.

Questions

What teams ask before they move

Do we need a developer after launch?

No, not for everyday work. Your team builds pages, updates copy, adds schema and ships landing pages by describing them to Claude. Genuinely new components come through us, or Claude drafts one for you to review. When Frankly brought an SEO agency onto their new site, the agency needed no onboarding instructions.

We only just rebuilt on Webflow. Isn't it too soon?

Frankly had just finished a new Webflow site too. Mickey called the switch “a tough sell.” Leadership agreed once they saw a campaign page go up in an afternoon. And usually only the content has to move, so the new pages you paid for become the design you rebuild from.

Will we lose our rankings?

Not if the migration is done properly. Every URL gets a one-to-one redirect, and metadata, structured data and performance are checked against a migration checklist before launch.

Will anything go missing, like schema, meta fields or redirects?

Everything you have today comes across. After launch, you add more by asking: “Add FAQ schema to the pricing page.” Redirects aren't locked behind a pricing plan.

What if someone on the team would rather click than type?

Sanity has a visual editor for changing text and images directly. The Claude workflow is the fast path, not the only one.

How long does it take?

Two to three weeks for a migration: your current design and content, rebuilt on the new stack. 10–12 weeks if we redesign first, with design and build running in parallel, so changing platform doesn't add a phase.

Our messaging isn't settled yet.

Then we start there. We don't write copy until the positioning is right. Once you're live, rewriting a page is a sentence, not a project.

How do I justify this to leadership?

Show them the velocity. At Frankly, one campaign page was what changed leadership's mind. Before your call, we'll send you a one-page case for your CEO covering what changes, what it costs and what stops needing a queue.

Who it's for

Built for the one or two people who run the website.

Whether you lead creative or marketing, the same setup does a different job for you.

If you lead creative

Full art-direction control.

Want three versions of the homepage before you choose? Ask for a toggle and click between them. Experiments that used to need a sprint now take an afternoon.

If you lead marketing

Pages that look designed, without waiting for a designer.

What makes a site feel like quality is built into the components. A page your team ships is made of the same parts as the one we designed.

It's not for you if

  • Your team doesn't want to work with AI tools, especially with a very complex CMS. Webflow is the better call, and we build those too, with AI built in. See the Webflow route →
  • You're happy with your current pace
  • Brand doesn't matter to you

This is for you if

  • One or two people run the whole website, and neither is a developer
  • Your team already drafts with Claude, or wants to
  • Campaigns keep waiting on the website
  • The pages you build yourself never quite match the ones your designer made
  • Brand consistency matters
  • You want to own your site, not rent it

Ship your next page the day you need it.

Twenty minutes on your site, your stack and your next campaign. You'll leave with a plan for what moves, what gets rebuilt and what it costs, whether or not you work with us. Nothing goes live until you're confident it works.