[ What is an agentic site? ]
The site runs on briefs, not tickets.
An agentic website is a marketing site where AI is the operating layer, not a bolt-on. The code and the content live together in your GitHub repository, under your name. The repo is the CMS. When your team needs a change, a new campaign page, a pricing update, a case study, they describe it in plain language to the agent they already use. The agent builds it inside your encoded brand and design rules, and the change arrives as a preview. The AI proposes, you approve what ships. Or, in the language your developers would use: agents commit, you approve the diff. Nothing ships itself.
That loop is the whole product. It is why the Thursday campaign page exists on Tuesday, and why every edit is reviewable and reversible in your site’s own history. The agent is a first-class editor, not an afterthought, and your team is the editor-in-chief.
[ Who it’s for ]
Your team made the jump to AI.
Your website didn’t.
For B2B SaaS and software companies where the website is a growth channel, and the marketing team is carrying a number.
-
Your team uses AI every day, for everything except the website.
Briefs, research and campaigns moved to AI months ago. The website is still a ticket to someone else.
-
A page you plan in an afternoon takes weeks to go live.
The plan is quick. The wait is the queue: estimates, handoffs and a deploy somebody else owns.
-
Every change waits on a designer, a developer or an agency
Marketing wants the change, design owns the look and engineering owns the deploy. Nobody owns the website.
[ What’s included ]
The full system, handed over
with the keys.
For B2B SaaS and software companies where the website is a growth channel, and the marketing team is carrying a number.
-
The keys
Code and content in your GitHub repository, under your name, from the first commit. The repo is the CMS. No CMS subscription, no per-seat fees, no platform sitting between you and your own site. If we disappeared tomorrow, everything still works and it is all still yours.
-
Your agent ships it.
Your team briefs the change in plain language to the agent it already uses, the agent makes it inside the rails, and the change lands on a preview. The AI proposes, you approve what ships. No admin panels, no ticket queue.
-
Your brand, encoded.
A structured brand.md in the codebase where the agent works: your voice, colours, type, spacing, components and the rules for using them. Every change, from anyone, on any day, is made against it. Five years in, it still looks like day one.
-
Our standards, baked into the rails.
More than a decade of design and development standards, encoded as the guardrails and skills your agent runs on: what it may touch, how a page gets built, what gets checked before anything ships.
-
The machine layer.
Structured data, schemas, llms.txt and a clean sitemap, with the site fast and server-rendered underneath, so the AI systems answering your buyers can read, retrieve and cite what your site actually says.
-
The handover.
Not a PDF. Playbooks, paired working, and your team shipping their first supervised changes in week one.
- Discovery
- Transform
- Run & grow
[ A word that gets used loosely ]
Not a site builder. Not just rails.
A system your team runs.
The term is getting popular, so here is what it means on this page.
-
It is not an AI site builder, or a platform with an agent bolted on.
Builders generate a site quickly and leave you operating it the old way, usually on their platform. Platforms that add an MCP or an API let an agent reach in through a keyhole: it can’t see the whole site, can’t run it, can’t check its own work before it ships. An agentic website is about operation, not generation: the agent is how the site is run, changed, and improved for years, on code you own.
-
Bring your agent. We build the rails.
The site is plain, structured files that any capable agent can read and edit, so it works with the tools your team already uses: Claude, Claude Code, ChatGPT, Gemini, Cursor, Codex. The rails, the brand.md, the components, the skills and the checks that run before anything ships, live in the site rather than in the agent. Switch tools next quarter and nothing about your site has to change.
-
And a team that runs it.
Anyone can prompt a page into existence now. Without rules in the code, the agent reinvents the stack every session and the tenth page doesn’t match the first. Making sure every page is fast, on brand, and built to convert is the work, and rails alone don’t do it. So we tune the system to your brand, prove it working, and train your marketers on it until the everyday is theirs. The operating interface is a plain-language brief and a preview. You do not need a developer on staff to run it.
Our builds run on Astro, the framework built for exactly this kind of site: content-first, extremely fast, server-rendered for the machine audience.
Nothing in the stack is exotic or roll-your-own; every part is widely used, documented, and replaceable. The stack serves the ownership, never the other way around.
[ Proof ]
Built for SaaS teams like yours.
[ Related services ]
Other ways we build.
-
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.
-
Webflow websites
Built to your design, not the nearest template. Best for: design-led teams who want a visual editor they already know.
-
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.
[ Questions we hear most ]
The honest answers.
Can’t find your answer?
Book a Discovery call and ask us directly.
Or email hello@signalstudio.co.nz
What is an agentic website?
A marketing site whose code and content live in your own repository, and whose day-to-day changes are made by an AI agent working inside encoded brand and design rules, with a person approving every change before it goes live. It's also built so the AI systems your buyers use can read and cite it: structured data, schemas and llms.txt are part of the build, not an add-on. The full definition is on the Agentic websites page.
Does our marketing team need to be technical?
No. Nobody on your team writes code, opens a terminal or learns git. They describe the change the same way they already brief a designer, look at it on a preview, and approve it. The guardrails and the agent do the engineering. Teams ship their first supervised changes in the first week of handover.
Which AI tools does it work with?
Whichever your team already uses. Because the site is plain files in your repository, it works with Claude, Claude Code, ChatGPT, Gemini, Cursor and Codex today, and with whatever replaces them. The rules live in the site, not in the tool, so switching tools changes nothing about the site.
We're on Webflow, WordPress or Framer. Do we have to start from scratch?
Usually not. Most agentic builds start as a migration: your design largely kept, your rankings protected with a per-URL redirect plan, and your content landing in your repository. Everything underneath the design is replaced. Moving off a platform doesn't mean a publishing freeze.
What stops the agent from breaking the site or going off-brand?
The same thing that stops a new hire: rules and review. Your brand rules and design system are encoded where the agent works, so an off-brand page can't be built. A broken layout or a missing meta description fails before it ships, not after a visitor sees it. And nothing ships itself. The AI proposes the change, you see it on a preview, and you approve what goes live. Every change is in your site's history, so any change can be undone.
Who owns the code, the content and the data?
You do, from the first commit. Code and content sit in your repository under your name. There's no CMS subscription and no platform holding a copy. Leave at any point and take all of it: code, content, data, documentation. No exit fees, nothing held back. We put that in writing.
Can the wider team still use a normal CMS?
Yes, when it's genuinely wanted. We can hook a headless CMS into the same foundation so editors publish through a familiar interface while the marketers who work with agents work through the repo. It's one site with one set of rules either way. The honest version of that conversation is on the Headless CMS websites page.
What happens to our SEO, and how AI search reads us?
Both are built in. The site is fast, server-rendered and structured, with schemas, llms.txt and a clean sitemap, so search engines and the AI systems answering your buyers' questions can read and cite what it says. When your team changes a page, the machines see the change the same day, not next quarter.
How long does a build take?
It depends on the roadmap, which is what Discovery produces. What we can promise is the cadence: something visible ships every fortnight, from the first fortnight, on a live preview you can see the whole way through. No big reveal at the end.
How do we start?
Book a Discovery call. It's a working session with the people who own your website: where you're at, what's blocking you, and what an agentic website would look like for your team. You leave with a clear picture either way.
Can’t find your answer?
Book a Discovery call and ask us directly.
Or email hello@signalstudio.co.nz