Skip to content

Work · Website engineering

A software company

Website content moved out of a CMS and into code, so marketers and agents ship changes through the same pull requests as engineers.

Sector
B2B software, name withheld
Year
2026 to now
Site
Not shown
Merged pull requests, equal 168-day periods

All merged pull requests

255
570

By people, excluding release automation

78
346

Distinct accounts contributing

3
10

With v0 session links

0
199

BeforeWith usNovember 14, 2025 to April 30, 2026, against May 1 to October 15, 2026.

The brief

Our client makes business-management software and runs its marketing site on Vercel. We are not able to name them. When we took over the website on May 1, 2026, routine updates waited on developers, and the content lived in Contentful, where neither stakeholders nor the AI tools they were starting to use could work with it directly.

The aim was to make website updates easier to move forward, let stakeholders work on the site with tools such as Claude Code, Codex and other agents, and free the engineers for higher-leverage work.

What we did

Content migration, Git-based editing workflow, Agent and marketer documentation and Website engineering

We migrated the structured content out of Contentful into files in the website's repository and retired Contentful as the live CMS. Pages now read repository-backed JSON, and newer pages use typed, code-driven content, so content and components change together through one Git workflow.

Alongside the content, we wrote what people and agents need in order to use it: page-template guides, AI authoring documentation, marketer setup instructions and stakeholder playbooks. LLM-oriented page guides and Claude instructions landed in June, the content export and runtime migration in July alongside an authoring guide for Claude Code and v0, and marketer onboarding, stakeholder workflows and prompting guidance in August.

A requested edit now has a clear route to a reviewable change. A stakeholder can work with an agent on a headline, a page or a blog post, then bring it into the same pull-request process as the rest of the site. The merged work since then runs from everyday publishing to pages for a new AI product, a code-driven reporting page, a multi-step demo-form experiment, GA4 page-context instrumentation, a Vercel runtime migration and server-rendered FAQ schema.

The results

Across equal 168-day periods before and after May 1, 2026, merged pull requests rose from 255 to 570. Pull requests from people, excluding release automation, rose from 78 to 346, and the number of distinct accounts contributing went from 3 to 10. The first merged pull request with an explicit v0 session link appeared on July 24; by October 15 there were 199.

2.2×

merged pull requests

4.4×

pull requests by people

3 to 10

accounts contributing

199

changes made with v0 sessions

MeasurePrior 168 daysWith us, 168 daysChange
All merged pull requests2555702.24×
Pull requests by people, excluding release automation783464.44×
Distinct accounts contributing310+7
Merged pull requests with v0 session links0199199

Source: the client's website repository, reviewed October 16, 2026. Equal 168-day UTC windows: November 14, 2025 to April 30, 2026, and May 1 to October 15, 2026. Pull request counts include automation and branch promotions and measure merged repository activity, not unique features or production deployments. User-account counts exclude verified release automation and are distinct logins, not people. Operational benefits are our account of the engagement.

The client's name is withheld at their request, so there are no screenshots on this page.

This is the kind of work we do as website engineering. Tell us what you are working on at hello@outsidethebox.dev.

Next