Challenge: two weeks to publish one page
Sigma's marketing team is five people. They support a go-to-market org of more than 200, at a company that more than doubled its ARR in the year ending January 2026.
A year ago, a new page took close to a month, or two weeks on a good one. The site was on a different platform, and the time it took to publish pages was, in the words of the marketing leader, Luke Stanke, "our number one problem." Marketing was running two to three iterations behind the field, which he traces to a mix of resourcing and the technology supporting it.
Luke leads marketing at Sigma, and he wanted structured content in place before any agent touched the site. The goal was never a faster website. It was a website that other people at the company, and agents, could build on without waiting on his team.
We needed structured data, and that's where Sanity came in for us, by far. Someone nontechnical on our marketing team can make an update, and so can someone more technical. We had such a bottleneck before.
Luke StankeMarketing Leader
Solution: structure first, then agents
Maciej Trzciński, a developer at Tonik, built the system and helped migrate Sigma's site to Sanity. About half of the old site was already structured, in 36 collections that mapped cleanly to Sanity documents. The other half was built by hand with no real content model. For those pages, Maciej scraped the text, images, and links, then shaped them against the Sanity schema. The result was about 1,600 documents.
The importers were built to be rerun without creating duplicates, so Sigma's team could keep updating content and changing designs during the migration. When issues turned up in the source data, Maciej reshaped it with Sanity's migration tooling and imported it again instead of starting over.
Having the same schema in the studio and in the code made the migration quick. I could give Claude Code the schema and an HTML page and have it remap everything. It's one source of truth.
Maciej TrzcinskiDeveloper
A page builder an agent can read
The Sigma site is assembled from 128 section types shared across 11 page categories, all drawing on one shared page builder. Instead of 11 different page building systems, there is one shared vocabulary for building pages. Every section carries four things:
- Schema: defines the valid fields and the shape of the data. It lives in Sanity, so content is validated against it and an agent can check its own output.
- Readme: explains what the section is for, when to use it, what inputs it accepts, and what good usage looks like.
- Screenshot: shows what the section looks like. It is a visual reference for the agent and a preview for the editor in the page builder, so nobody picks a section by its name.
- Skill: covers how to use or build that section.
The schema makes a page machine-readable. The other three make it machine-buildable, because two sections can take identical fields and still belong in completely different places on a page. To build a page, the page builder agent reads the prompt, works out what kind of page it is, and composes it from sections that already exist. It quotes the readme line that justifies each pick, so a reviewer can scan the reasoning.
When no existing section fits, a create-section skill builds a new one instead of improvising a one-off for that page.
When the section we need doesn't exist yet, the agent creates a new one. It generates everything required for the block: the components, schema, readme, screenshot, CI checks and tests. Once the new section is added, it becomes part of the shared page builder.
Maciej Trzciński, Developer, Tonik
Because the page builder is shared, a new section is available on all 11 page types from that moment on.
Workflow one: an account page from a single prompt
Luke builds an account-based marketing (ABM) landing page from one prompt. The agent reads Sigma's own telemetry on similar customers in the prospect's industry, pulls their Wistia video transcripts, matches them to the topic, and places the right videos itself.
A page takes about five minutes to build and under two minutes to check. Whoever built it is mostly looking for an obvious blunder, like the wrong company name. Then it goes to staging for review before it ships.
The same workflow is now in the hands of Sigma's business development reps (BDRs), who build their own account pages instead of filing a request and waiting. About 40 BDRs use it today, shipping about five pages a week each for their target accounts. Sigma's sales motion is rep-led, not product-led, so pages built for specific accounts are a core part of how they build relationships and sell.

Reps start in Claude to build a first version, then open the page builder in Studio to make hand edits in an interface that feels familiar and safe. Luke says he operates almost solely out of Claude himself, and that the Sanity backend is what lets less technical colleagues make small changes without worrying they will break something.
Our BDRs create the prompt, and the agent generates the page in Sanity. Given that we don’t have to deploy new code out of this, it doesn’t take long to get the pages live. It basically takes five minutes or less per page.
Luke StankeMarketing Leader
Workflow two: blog recommendations that stay fresh
Sigma has between 600 and 700 blog posts live at any time. The calls to action and recommended content at the bottom of each one used to be somewhat arbitrary: you reach the end of a post, and you get related articles.
Now a blog agent runs a basket analysis on performance once a week, using Sigma's own analytics product, and pushes updated recommendations into Sanity. What gets recommended reflects what is actually being read together. It is a small, repeating gain.
Results: higher conversion, less overhead
A year ago, Sigma's marketing team published about one or two new pages a month. Today, 40 BDRs ship on average five account pages a week each, roughly 200 a week.
The impact is still early to tally altogether. Sigma estimates that ABM pages are about 2 percentage points higher for web-to-lead conversion, and the blog adds another 2 to 3 percentage points. Small, repeatable increases like these add up to a larger picture of a business that is growing revenue 2x annually.
For the marketing team, the website stopped being the bottleneck. The web team at Sigma is three to four people. They rotate a 30-minute meeting on Mondays, decide what to act on, assign it in the room, and are done for the week.
In Luke’s words,
It's everyone's collective jobs in their one area to make it easy for everyone else to go do that one thing.
The other measure that can’t be confined to a number, Luke says, is attention. The space the website takes up in the team's heads, compared with a year ago, is "microscopic."
The outcome
The website is no longer something one team builds for everyone else. BDRs make their own account pages, agents add new sections to the shared library, and the web team spends 30 minutes a week deciding what to do next.




