Your video testing is capped by your production budget. We build you a system that turns your product photos into ads, on your products, with your approved claims, and you leave owning it.
Your own private repo. The video skills installed. Your first ten ads shipped. Four live builds with John Aspinall.
Each clip opens on the brand's Amazon image, then shows what Video OS made from it. All three together cost 170 Higgsfield credits, under $10 on a $59 plan.
Listing photo → Amazon Sponsored Brands VideoAlani Nu Cherry Slush. Three shots, claims from the listing title set in exact type.One ad → four testsPure Bamboo sheets. Each variant changes one thing: the setting, the person, or the colorway.Product photo → UGC adCeraVe lotion. AI-generated creator, labeled on screen. Every line comes from the listing.
Spec concepts made for demonstration. Not affiliated with or endorsed by Alani Nu, Pure Bamboo, or CeraVe. AI-generated.
what you own
02 / What you leave with
Generic AI video gets your product wrong. Yours reads your brand first.
The public video tools are engines. None of them know your specs, your approved claims, or which ad already works. That layer is what we build, and it lives in a repo you keep.
01
Your brand brain.
Product specs, an approved claims list, customer language from your 5-star and 1-star reviews, and a style guide pulled from your best ads. Every skill reads it before it makes anything.
02
The engines, installed.
Higgsfield and the video skills, pinned to versions that work, with a cost quote before every paid render. Seedance, Kling, and Grok, each used for the job it does best.
03
Ads you can ship.
Amazon Sponsored Brands Video, UGC-style ads, product showcases, and variants of your winners, reframed for every placement with exact on-screen text.
The repo is transferred to your own GitHub account in week four. Your brand data stays yours.
Inside your repo
Your brand brain, in folders your AI reads.
Every student gets a private GitHub repo built around their brand. The knowledge folder holds the facts. The skills folder does the work. No skill makes anything until it has read your brain first.
Your repo arrives about 60% filled before week one.
knowledge/claims/approved-claims.yaml
- claim: "Fragrance free" status: approved- claim: "Lightweight, never greasy" status: approved- claim: "Cures dry skin" status: banned # not on the label
No skill can put a claim on screen that isn't approved here.
skills/winner-multiplier
reading brain… specs.yaml · approved-claims.yaml style-contract.md · best-ad.shots.yamlplan: 3 variants, one change eachquote: 45 credits → waiting for your OK
Simplified illustration. The full repo ships with 10–15 skills and is transferred to your own GitHub account in week four.
week by week
03 / The four-week build
One layer a week. Every session ends in a commit.
Short teaching. Long live builds. Your repo arrives partly filled from your intake, so week one starts on your products, not a blank page.
Four live 1-hour Tuesday sessions. Tuesdays 2-3 PM Eastern.
Twenty years of marketplace creative. Applied to your products.
01
Week 01Tuesday, October 27
Build your brand brain.
Your repo arrives about 60% filled from your intake: product specs, customer language from your reviews, a style guide pulled from your winning ads, and a draft claims list. We correct it together, approve your claims, and install it in Claude Code or Codex.
You leave withA reviewed brand brain and an approved claims list.
02
Week 02Tuesday, November 3
Lock the product, install the engines.
Get your hero SKU locked in approved stills, then install Higgsfield and the pinned video skills. Grok is an optional lane. Every paid render gets a cost quote first.
You leave withAn approved still set and your first five test clips.
03
Week 03Tuesday, November 10
Run production.
Turn a brief into a timed shot list, render in batches, and run the winner multiplier on your best ad: variants that each change one thing, the hook, the setting, the person, or the colorway.
You leave withFive to ten variants of an ad that already works.
04
Week 04Tuesday, November 17
Ship at volume.
Add exact on-screen text for specs, prices, and claims, reframe to every placement, run the QA check, and set a weekly cadence. Your repo is transferred to your own GitHub account, live in the session.
You leave withTen or more finished ads and a repo you own.
how it runs
04 / How your repo gets built
You bring the brand. The repo does the remembering.
01Intake.
Send your ASIN or product URL, packshots, top three ads, known claims, and your GitHub username.
02Pre-fill.
John creates your private repo and the intake skills fill it before week one: specs, review language, style guide, draft claims.
03Lock it in class.
You correct the pre-fill, approve your claims, and lock the style guide. One review from John before production starts.
04It becomes yours.
In week four the repo is transferred to your GitHub account. You keep everything, John keeps nothing of yours.
in their words
05 / Operators who have built with John
The difference is getting it working.
Experiences from earlier Operator Intelligence programs. Each operator built around their own business.
“One of the highest-value investments I've made. … I've built workflows and automations that turn projects that used to take days or weeks, and cost thousands, into systems I now run in minutes with no added expense.”
Regina GomezBrand owner · days of work, now minutes
“I joined John's Operator Intelligence, and it cleared a lot up for me. It helped put me on a path to implement what I wanted, trained me to understand how to use it, and helped me get everything to interact.”
Dave SupingerFounder, Ardor Growth · tools talking to each other
“Signed up for cohorts that aren't just a presentation leaving me to figure it out. By the end, he has personally ensured they get implemented.”
Jon ScrivanoBrand owner · built with him, not after him
“I chose to work with John so that I can be part of the group that is staying ahead of the curve.”
You sell products online. You need more video than you can shoot.
Built for ecommerce brand owners and operators on Amazon, Shopify, or TikTok Shop, and for agency owners producing creative for clients. Not for local businesses.
You don't need to code. Bring one product you sell, the packshots you already have, and one ad that has worked for you.
Your time
One live one-hour session each week, plus 1–2 hours of production between sessions.
Your tools
Claude Code or Codex, and your own Higgsfield account for rendering. Grok is optional. Subscriptions and render credits are paid by you and are not included in the cohort fee.
What renders cost
The three demo ads on this page cost 170 Higgsfield credits together, under $10 on a $59 plan. You see a cost quote before every paid render.
Your participation
Work on your own products, approve your own claims, and flag where you're stuck so we fix it in the room.
your seat
07 / Your place in the room
Let's get your video engine running.
Four live weeks of building on your products, then a repo you own.
Four weekly one-hour live build sessions, recorded
Your own private Video OS repo, pre-filled from your intake
10–15 installable video skills plus the pinned engines
Your first ten or more finished ads and a 30-day cadence plan
Operator Intelligence School free for life, all past and future replays
Weekly Operator Hours
Enrollment open
Operator Intelligence: Video OS
$799one payment
Operator Intelligence alumni: private code at checkout
October 27, November 3, 10, and 17 Tuesdays 2-3 PM Eastern
Secure checkout via Stripe. Your purchase reserves your seat.
All cohort sales are final. Seats are committed after checkout. No refunds once you've purchased a seat. Read the terms.
Claude Code or Codex, Higgsfield, and render credits are paid by you and are not included.
After you enroll
01Reserve your seat.
Stripe confirms your purchase and sends you the intake form.
02Send your intake.
Your ASIN or product URL, packshots, top ads, known claims, and your GitHub username.
03Get your repo.
You're invited to your private Video OS repo, already partly filled, before week one.
04Build live.
Bring your product. We start making ads from it.
ask away
Before you join
Good questions. Straight answers.
Something specific about your products? Email John.
Do I need to know how to code?
No. You describe the work, follow along, and approve the output. The repo, the skills, and the setup steps are built for operators, not engineers.
What exactly do I leave with?
Your own private GitHub repo: a brand brain (product specs, approved claims, customer language, a style guide from your winning ads), the video skills that read it, the engines installed, and your first finished ads. The repo is transferred to your GitHub account in week four.
Which tools do I need, and what do they cost?
Claude Code or Codex, and your own Higgsfield account for rendering. Grok is optional. Tool subscriptions and render credits are paid by you and are not included in the cohort fee. For scale, the three demo ads on this page cost 170 Higgsfield credits together, under $10 on a $59 plan.
Can I use real people in my ads?
Only with their written consent. AI-generated creators get disclosed on screen. Every claim in an ad has to be on your approved list first. Those rules are built into the skills.
Is this for local businesses?
No. It is built for ecommerce brand owners and operators selling on Amazon, Shopify, or TikTok Shop, and for agency owners producing creative for clients.
What if I miss a session?
Every session is recorded and replays are shared. Live attendance is best because we fix your setup in the room. If you fall behind, bring it to Operator Hours.
What is the refund policy?
All cohort sales are final. Seats are committed after checkout. No refunds once you've purchased a seat.
Regina GomezBrand owner · days of work, now minutes
Dave SupingerFounder, Ardor Growth · tools talking to each other
Jon ScrivanoBrand owner · built with him, not after him
Daniela BolzmannCEO, Mindful Goods