websites

[ What is it? ]

Webflow, built properly.

Webflow is genuinely good at what it was built for: letting a design-led team run a serious site without developers. Most Webflow sites don’t get the most out of it. They’re built page by page, the class names drift, the CMS is shaped for the demo, and two years in nobody wants to touch the homepage.

We build Webflow sites the way we build everything else: as a system, not a set of pages. The same design discipline and more than a decade of standards we put into every build, inside the platform, plus the agent setup most Webflow sites never get.

[ Who it’s for ]

Your team designs visually.
Webflow was built for that.

Your designers want to shape pages on a visual canvas, not in a brief.

They work by seeing the page take shape. Webflow gives them that, and a component system keeps it consistent.
You’re on Webflow already, and want it built properly this time.

The site grew page by page and it shows. We rebuild it on Lumos or Mast, with components your team can reuse.
You want an agent helping at scale, on a platform your team already knows.

Your agent works through the Webflow MCP on bulk and repeat work, while your team stays in the Designer.

[ What’s included ]

More than a Webflow site.

Conversion-first design and build.

The same design discipline as every Signal Studio project: a brand system, component thinking, pages built to win customers.
A component system on a recognised framework.

Every section a component with properties your team sets, built on Lumos or Mast, so a new page is assembled, not rebuilt. Variables and class naming set up so the tenth page looks like it belongs with the first, and the next designer, developer or agent can read the site on day one.
Your agent, connected.

The Webflow MCP set up on your site, and agent skills that know your framework, your components and your CMS, so your team can brief changes to the agent it already uses.
A CMS architecture that won’t strangle you.

Collections planned for how your content actually grows, not for the demo.
SEO and the machine layer, as far as the platform allows.

Clean structure, real metadata, structured data where Webflow permits it, a deliberate crawler posture. Done completely, so search engines and the AI systems answering your buyers can read what the site says.
Your team enabled.

Editors trained, conventions documented, and a first session briefing the agent together, so changes don’t queue behind the one person who knows how the site is wired.

Discovery
Transform
Run & grow

[ The agent layer ]

The Webflow MCP, connected.

Webflow’s MCP lets an agent read and change your site directly: pages, components, CMS items, settings. We set it up on your site and connect it to the agent your team already uses: Claude, ChatGPT, Cursor, or whatever comes next.
Skills written for your build.

An agent pointed at a Webflow site cold will guess, and guessing drifts. So we write agent skills for your site: which framework it’s built on, which components exist and what their properties do, how the class naming works, how a page gets assembled and what your CMS collections hold. The agent builds the way the site was built, not the way it improvises.
Editing at scale.

Your team briefs the change in plain language and the agent does the legwork: a new landing page from existing components, forty CMS items updated in one pass, the same fix rolled across every page that needs it. Changes land on staging, and nothing goes live until someone on your team publishes it.

Built on Lumos or Mast, the recognised Webflow frameworks, not a pile of one-off classes. Components with properties, a documented naming system, spacing and type set as variables, a CMS structured for how your content grows, and SEO settings done completely. It reads the same to your next designer, your next developer and your agent. The platform serves your team, never the other way around.

[ Later, if it comes ]

Your migration partner will already know every corner
of your site.

The teams that leave Webflow describe the same moment: the site became a growth channel, and the platform that made things easy started making them slow. If that moment comes for you, you won’t be starting a vendor search.

We build agentic websites on owned code as our flagship, we migrate teams off Webflow with rankings intact, and every Webflow site we build is shaped for the move: a component system that maps one-to-one to code, naming and content structured so that if the day comes, it’s weeks, not a rebuild.

[ Proof ]

Webflow work we run today.

[ 01/ Landlord Studio ]

Property management software for landlords in the US and UK. A five-year-old Webflow build redesigned, migrated onto a component-driven framework, and handed to a marketing team that now builds its own pages with AI.
Read case study
[ 02/ Autohive ]

An AI-agent company's first website, built on a component framework their designers, marketers and agents could all work in, so their marketing team builds its own landing pages and updates without waiting on anyone.
Read case study
[ 03/ Future of Marketing Work ]

An Auckland event on how marketers adapt to digital transformation and AI, brought together by a university, the AI community and an events group. We made the brand, the website and the print.
Read case study

[ Related services ]

Other ways we build.

Agentic websites

Our flagship. A marketing website your team runs with its own agent. Best for: teams ready to brief a change and ship it the same day.

Agentic websites
Headless CMS websites

The same foundation, with a familiar editor on top. Best for: teams where some people live in their agents and others want a CMS.

Headless CMS websites
Astro websites

The framework under our builds: fast, server-rendered, readable by machines. Best for: teams who want to know exactly what they’d own.

Astro websites

Why would a studio whose flagship is owned code still build Webflow sites?

Because the right answer depends on the team, not on what we like building most. A team that changes its site quarterly, has no developer and loves the editor it already knows is well served by Webflow. We would rather build that team a Webflow site that is fast, well structured and ready for an agent, and be the people who already know the site if owning the code ever makes sense.

Can a Webflow site rank in AI search?

Yes, when it is built deliberately: clean structure, real metadata, structured data where the platform allows, and proof written in text rather than locked in images. What a platform site cannot give you is full control of the machine layer, or checks built into the code itself. If that becomes the limit for your team, we will tell you.

Can our agent work on a Webflow site?

Yes. Every Webflow site we build comes ready for one. We connect Webflow's MCP to the agent your team already uses, and write skills for your build so the agent knows your components, your class naming and your CMS collections. Changes land on staging, and nothing goes live until someone on your team publishes it.

Will you tell us if we should not be on Webflow?

Yes, and in writing. Discovery looks at where your site stands and what the platform will cost you at your rate of change. If the answer is to own your code, we will say so before you have spent anything on a build.

What happens to the site when we later move to owned code?

It was built for that day. Naming, structure and content are shaped so the move is a migration rather than a rebuild, and because we built the Webflow site, we are not starting by learning it. The Webflow migration page shows how that move runs.

Do you do Webflow retainers?

Yes. It is the same monthly rhythm we run on every site after launch: shipping, measuring and improving, inside what the platform allows. We run those today.