On 24 September 2026, Benson was an empty Turborepo starter. Ten days later, on 4 October, I relaunched it at trybenson.com with a Shopify app, a WooCommerce plugin, a dashboard, a marketing site, a press release and a series of explainer films. By the end of the second week, the repository held 836 commits, 44 product specs, about 655,000 lines of TypeScript and 785 test files.
The original roadmap estimated 14 to 18 weeks for the same scope. AI agents did most of the typing; I made the decisions. It's the first time I haven't had to cut an idea down to fit the hours I had.
The product Shopify switched off
I first saw the problem from inside the affiliate industry. I began my career on the paid search team at Vouchercloud, where coupon extensions came up constantly. A shopper would find a brand through a review site or a creator, but a pop-up at checkout would claim the last click and the commission.
I'd worked on the idea for a couple of years before Benson opened early access in August 2022. One script tag removed discount-extension pop-ups across more than fifty extensions and stopped auto-tried codes at Shopify Plus checkouts. Then Shopify announced the end of checkout.liquid, the template that let apps change the checkout page. From August 2024, Plus checkouts moved into a sandbox apps can't edit, so Benson's checkout protection stopped working, as the relaunch announcement sets out. Shopify now marks
I'd sold the business by then. Under its new owner, it stalled.
The problem kept growing. A December 2024 investigation into how Honey claimed affiliate credit led to class actions from creators. In January 2026, the networks acted: Rakuten Advertising removed Honey,
impact.com followed, and
Awin said Honey had breached its publisher policies. AI shopping agents were also arriving at checkouts and doing the same job on a shopper's behalf. So I bought the brand back.
Set the strategy before the agents build
The first commit after the starter wasn't code. It held a product plan, a decisions record, a design system and the first specs. I needed the strategy settled before an agent touched the codebase, because an agent will build the wrong thing quickly if that's what the instructions ask for.
The strategy came down to three verbs: See, Stop and Own.
- See labels every session as a person, a coupon extension, an AI agent or automation, and shows what each one costs. Detection and agent analytics are free on every plan, because a store can't decide anything about traffic it can't see.
- Stop hides extension pop-ups on the storefront by rule and caps how many codes a visitor can try. An observe mode shows what would be hidden before anything changes.
- Own replaces the extension with the store's own coupon assistant, in its own colours, for a fixed monthly price instead of commission.
A holdout sits behind all three. Every switch a merchant flips can run against a control group, so the result is measured rather than modelled. The honest answer to "is this extension costing me money?" is sometimes no. A tool that can't say so isn't worth trusting. The holdout guide on trybenson.com explains the method for merchants.
The positioning took longer to settle than the architecture. Benson isn't trying to win a war with extensions. Extensions and agents aren't going away, so the long-term aim is to make them play by the rules and let merchants work with them instead of fighting them.
Write the spec, then hand it over
I wrote 44 PRDs, or product requirement documents. Each says what a feature does, why it exists, what done looks like and how it gets tested. I ordered the backlog so each feature built on the last: data layer and tenancy, storefront loader, detector, ingest pipeline, dashboard, Shopify app, blocker, checkout policies, widget and its editor, experiments, billing and email.
I ran the build as an orchestrator. My backlog runner skill takes the next PRD and hands each task to a fresh Opus agent, which writes tests before code. A second pass reviews the change adversarially for ways it could be wrong; a third simplifies it. Only then does it become a commit, one per feature. Agents worked in parallel in their own git worktrees, so the Shopify app, worker and marketing site could all move forward.
My job changed shape. I wrote specs, read diffs and rejected work that met the letter of a PRD but missed the point. I also took the problems agents are bad at: what the product should say, what a merchant will believe, and which Shopify constraint is real and which is a rumour. When a step needed a person, such as the Shopify Partner dashboard, a payment provider or a DNS change, the agents built up to that seam and stopped. I picked it up.
The first build week produced 550 commits. Of those, 169 landed on 25 September alone, when the core product came together: loader, detector, ingest, rollups, dashboard, Shopify app and pixel, blocker, widget, experiments and billing.
What got built
Benson is a monorepo of ten apps and fifteen packages:
- A storefront loader with a 2.5KB gzipped budget, so it doesn't cost the merchant page speed. Its signature catalogue recognises the major coupon and cashback extensions, six AI shopping agent signatures and the common automation frameworks.
- An ingest pipeline on Redis Streams, a worker for rollups, billing, insights and lifecycle jobs, and Postgres with row-level security built up over 75 migrations.
- A dashboard and an embedded Shopify admin with a live session feed, attribution, an insights inbox, A/B experiments with guardrails and white-label PDF reports for agencies.
- A Shopify app with a theme embed, a web pixel and a Discount Function that enforces a strict code policy in extension sessions. A WooCommerce plugin and install guides cover other platforms.
- An optional Cloudflare Worker that spots agents which only fetch pages and never run JavaScript.
- A marketing site with documentation, pages for each audience, playbooks and articles.
The hardest lesson from the original Benson shaped the checkout design. Shopify doesn't let any app change what extensions show at checkout, so the new Benson treats the storefront and checkout as separate jobs. It hides pop-ups on storefront pages; at checkout, a Discount Function decides which codes work. I didn't want to promise a merchant something Shopify could take away again.
Treat AI agents as customers too
AI agents show up twice in Benson. First, as traffic: stores are starting to see shoppers who are really software acting for a person. Merchants will need to decide what those agents can see and do, including how many codes they're allowed to try. That's conversion rate optimisation for bots, and I think it'll matter as much as it does for people.
Second, as an interface. Benson has its own MCP server, using the protocol AI assistants use to connect to other tools, so a merchant can ask their own agent about their store. Every change an agent proposes is previewed first and needs the merchant's confirmation. After a fortnight of building with agents, I wasn't going to let one change a store's checkout without a person saying yes.
Make the launch part of the product
In the second week, I spent most of my time on the launch. Agents produced the material from briefs I wrote:
- A press release, a short wire version, a fact sheet with approved quotes, pitch emails and an interview brief.
- A target list of 192 researched outlets, wires, directories and communities. The day after the relaunch, 19 individually written pitches went to e-commerce and retail trade press, alongside newsletter and community posts.
- Eight articles on trybenson.com covering coupon control on Shopify, holdout measurement, partnership decisions and the MCP server.
- A lead magnet,
Discount Extensions 101: The BFCM Playbook, researched, fact-checked and laid out as a PDF.
- A launch film and ten explainer films built in Remotion with a voiced mascot host, plus ad cuts for Meta, Reddit and X.
- A Shopify App Store submission on 3 October, with review videos and the fixes Shopify's checklist asked for.
Measurement went in before the traffic did. PostHog tracks the product journey, and server-side conversion APIs for Meta, Reddit, LinkedIn and X follow the consent each account gives at sign-up.
What changed for me
I've been building products for fifteen years. I knew how to build most of what I could imagine, but I had the same 24 hours as everybody else, so ambitious ideas got cut down or never started. Benson is the first time that constraint didn't decide the scope.
The pace felt a bit unstoppable, but the agents aren't magic. Scaffolding, plumbing and the fourth version of a settings page now happen while I work on the decisions that need me. The judgement is still mine. Separating storefront from checkout, putting a holdout behind every switch and refusing to promise what Shopify won't allow came from having run Benson before. Agents let me act on those decisions at once.
Benson is a work in progress. The Shopify App Store review is pending, the Product Hunt launch is set for 13 October and the backlog keeps growing. But the product is live, and I'm proudest that it exists at the size I imagined.
trybenson.comBensonSee which coupon extensions and AI agents shop your store, and decide what they're allowed to do.
Research and sources
Checked 2026-10-07. Next review: 2027-04-07. Listings and availability can change.
Benson · Checked 2026-10-07 · Primary source
The 2022 early-access launch, the move of Shopify Plus checkouts to a sandbox in August 2024, and the relaunch on 4 October 2026.
Shopify · Checked 2026-10-07 · Primary source
Shopify marks checkout.liquid as deprecated and documents the sunset dates for checkout customisation.
Rakuten Advertising becomes first major network to remove PayPal Honey following attribution controversy
Affiverse Media · Checked 2026-10-07 · Secondary source
Rakuten Advertising removed Honey from its network in January 2026.
impact.com just kicked Honey off its network
PPC Land · Checked 2026-10-07 · Secondary source
impact.com removed Honey from its network in January 2026.
PPC Land · Checked 2026-10-07 · Secondary source
Awin said its investigation found breaches of its publisher policies by Honey.
Benson · Checked 2026-10-07 · Primary source
How Benson measures each control against a holdout group.
Benson · Checked 2026-10-07 · Primary source
The Benson MCP server previews every change and asks the merchant to confirm it.
Benson · Checked 2026-10-07 · Primary source
The Black Friday and Cyber Monday playbook published as Benson's lead magnet.
Shopify
