The Spread Kit

A free Overyield tool. Everything you need to sell one fixed-price landing page at the market anchor, produce it for about a dollar of model spend, QC it so the quality holds, and publish the receipt that wins the next gig.

You do not need code. You need $20 of OpenRouter credit, a browser, a Google Sheet, and one buyer who needs a page this week. Work top to bottom. The first practice build takes an evening. A live gig takes 2 to 3 hours of your time, not counting winning it.

What you are running (the 60-second overview)

A margin trade. Between June 16 and June 25, 2026, open models became best-in-class for commercial web work while costing 5 to 16x less than frontier models: GLM 5.2 ran a $2.38 Opus 4.8 task for 44 cents on one benchmarked task (Startup Ideas Podcast, Jun 23) and took #1 on Design Arena for website design (Jun 16). Buyer prices for landing pages did not move. You sell at the old anchor, produce at the new cost, and keep the spread.

Three rules before you start:

  1. You are not selling AI. You are selling a delivered page. The chain stays in the basement.

  2. Never compete on price. The moment you discount, you have joined the race to the bottom and left the trade.

  3. QC every unit. The leaderboard win (Jun 16) is a crowd vote, not a client acceptance test. Your review layer is the product.

The artifact structure (set this up first, 15 minutes)

One folder per operation: Spread Desk - [Month YYYY], containing:

  • 01-briefs (one doc per prospect: their brief, your teardown)

  • 02-drafts (the generated page files, one subfolder per gig, versioned v1, v2...)

  • 03-qc (filled QC checklists and eval runs)

  • 04-delivered (final files as sent, plus the client’s acceptance message)

  • 05-receipts (screenshots of the OpenRouter activity page per gig, plus the published receipt text)

One Google Sheet, "The Spread Ledger," five tabs:

  1. Pipeline: prospect, source, date contacted, teardown sent (Y/N), reply, status.

  2. Quotes: prospect, bracket offered ($900 / $500 / $350), bracket taken, date.

  3. Gigs: client, price, deposit date, delivery deadline, delivered date, revisions used, final payment date.

  4. Costs: gig, plan-pass cost, execution cost, review cost, retries, total model spend (from the OpenRouter activity page, rounded UP).

  5. Receipts: gig, price charged, total model cost, production time, delivery time, published link.

The Ledger is not bookkeeping. Tab 5 is your marketing asset. More on that in Step 8.

Step 1: The $20 setup (OpenRouter)

  1. Create an account at openrouter.ai and load $20 of credit. That is the entire capital requirement.

  2. In settings, review the data and privacy options. Turn OFF any option that shares your prompts for training, and prefer providers with a no-retention policy where the routing settings allow it. This matters the moment client material enters a prompt.

  3. Find your three models (search the model list by name):

  4. Execution: GLM 5.2. The receipts: #1 on Design Arena for website design (announced Jun 16), Tailwind in 91% of sessions, $4.40 per million output tokens (AI Daily Brief, Jun 22); a landing page for 6 cents vs 49 cents on Opus 4.8 (AI Daily Brief, Jun 18).

  5. Planning: a frontier model (Opus-class) or OpenRouter’s Fusion router, which scored within 1% of Fable 5 at roughly half the cost (AI Daily Brief, Jun 18). Thinking is the expensive, rare part. Spend here.

  6. Review: a third model family (a Gemini- or GPT-class model). Different family matters: a model reviewing its own family’s output shares its blind spots.

  7. Why a router instead of one vendor: on June 12, 2026, Fable 5 was suspended with 90 minutes of warning (Moonshots EP #265, Jun 18). A single-vendor pipeline can die mid-delivery. A routed one reroutes and your deadline survives.

Alternative execution model if GLM 5.2 is unavailable or fails your eval: Kimi K2.7 Code, which produced landing pages at 94% lower cost than Fable 5 in a single head-to-head test (TLDR AI, Jun 18). Run Step 3 before trusting either.

Step 2: The three-model chain (the exact prompts)

2a. The PLAN prompt (frontier model or Fusion, one pass)

You are a senior web strategist. Below is a client brief for a fixed-price landing page. Produce a build spec, not the page itself. The spec must contain: 1. Page goal in one sentence (the single action a visitor should take). 2. Section list in order (hero, proof, features, pricing, FAQ, CTA, footer: keep only what this brief earns). 3. Copy outline per section: headline direction, one supporting line, the CTA wording. 4. Brand tokens: colors, font pairing, tone in three adjectives, drawn from the brief or the client’s existing site. 5. An acceptance checklist of 8 to 12 testable statements (“the hero states the offer in under 12 words,” “pricing shows three tiers,” “no claim appears that is not in the brief”). Hard rules: invent NO statistics, NO testimonials, NO client names, NO logos. Where social proof would normally go, specify a clearly labeled placeholder. Flag anything in the brief that is ambiguous instead of guessing. BRIEF: [paste the client brief]

2b. The EXECUTE prompt (GLM 5.2, expect 3 to 6 runs)

You are building a production landing page from the spec below. Output a single self-contained HTML file using Tailwind via CDN. Hard rules: - Follow the spec’s section list and copy outline exactly. Do not add sections. - Invent NO statistics, NO testimonials, NO named customers, NO awards. Use the placeholders the spec defines, marked [PLACEHOLDER]. - Semantic HTML (header, main, section, footer), working anchor navigation, a functional mailto or form stub as specified. - Mobile-first: every section must hold together at 375px width. - Include a JSON-LD structured data block per the spec (Organization or Product, plus FAQPage if the page has an FAQ). - Images: use solid-color or gradient placeholder blocks with alt text describing what the final image should be. Do not hotlink stock photos. SPEC: [paste the plan output]

Run it, open the file in your browser, and iterate: paste back the spec plus a numbered change list (“1. hero headline swap to variant B, 2. tighten section spacing, 3. FAQ answers to two sentences”). Each run costs cents. Budget 3 to 6 runs. When it is done: deliver the single HTML file itself, or drop it on any free static host for preview.

2c. The REVIEW prompt (third model family, one pass)

You are a QA reviewer for a fixed-price landing page delivery. Below are (1) the build spec with its acceptance checklist and (2) the final HTML. Audit the page against every checklist item. Then audit for: invented statistics or testimonials (fail the page if ANY unverifiable claim appears), broken or placeholder links, missing alt text, heading hierarchy, mobile layout risks, contrast problems, spelling, and whether the JSON-LD block is present and coherent with the visible content. Output: PASS or FAIL per checklist item, then a numbered punch list of fixes ordered by severity. Do not rewrite the page. SPEC: [paste] HTML: [paste]

Fix the punch list with targeted execution runs. Then do the one thing no model does reliably: look at it yourself, on your phone, like a buyer would.

Step 3: The 10-task golden mini-eval (run BEFORE any client work)

Never swap a model into paid work untested. This is the afternoon that makes any swap safe, this quarter and every quarter after. Run all 10 tasks on your execution model, score pass/fail, and require 8 of 10 with zero fails on tasks 5 and 6.

| # | Golden task | Pass condition |
|---|---|---|
| 1 | Hero section from a 3-line brief | States the offer in under 12 words, one CTA |
| 2 | Three-tier pricing table | Correct prices from the brief, middle tier highlighted |
| 3 | Responsive nav | Collapses cleanly at 375px |
| 4 | FAQ section from 5 supplied Q&As | No answers invented beyond the supplied text |
| 5 | The fabrication trap: “add social proof” with no proof supplied | Uses labeled placeholders; invents NO names, numbers, or quotes |
| 6 | The statistics trap: “make the results section compelling” | Refuses to invent metrics; flags the missing data |
| 7 | JSON-LD block for a named business | Validates (paste into a schema validator), matches page content |
| 8 | Brand-token adherence (supplied hex codes + font) | Uses only the supplied tokens |
| 9 | Copy rewrite to an 8th-grade reading level | Shorter sentences, meaning preserved |
| 10 | A 4-section page in one shot | All sections present, coherent order, valid HTML |

Log the run in 03-qc. Re-run the full eval every time you change execution model, and skim it monthly: routed models can change behavior underneath you without an announcement.

Step 4: The QC checklist (run on EVERY delivery)

Print it. Check boxes. This checklist is why the client pays you and not the raw model.

  • [ ] Every factual claim on the page traces to the brief or the client’s own materials. No invented statistics, testimonials, customer names, or awards. (This is the #1 open-model failure mode. Hunt for it.)

  • [ ] All links resolve. Form or mailto actually works. No [PLACEHOLDER] left visible.

  • [ ] Phone-check at 375px: nav, hero, tables, footer.

  • [ ] The vision workaround: models judge their own rendered output poorly, so screenshot the page (desktop + mobile) and either inspect by eye or feed the screenshots to a vision-capable model with “list every visual defect.” Do both on your first five gigs.

  • [ ] Contrast and readability quick pass (light text on light backgrounds is a common slop pattern).

  • [ ] Spelling and casing pass, including the meta title and description.

  • [ ] JSON-LD validates and matches the visible content.

  • [ ] OG title, description, and image tags present (the page will be shared; make the preview clean).

  • [ ] Images licensed or placeholder-flagged for the client to supply. Never ship scraped photos.

  • [ ] Load sanity: single file, no dead external requests.

  • [ ] Final read-aloud of the copy, top to bottom. If a sentence sounds like a robot wrote it, rewrite it yourself.

Step 5: The bracketed pricing script (Do-style, never mention your costs)

Budget excavation first. On the call or in chat, before any number leaves your mouth:

“So I scope this right: were you budgeting a few hundred for this, a few thousand, or somewhere in between?”

Whatever they answer, quote the bracket, highest first:

“I price this three ways. $900: a multi-section marketing site, copy pass, mobile QC, agent-ready structured data, analytics install, and a 30-day tweak window. $500: the standard landing page, copy pass, two revision rounds, mobile QC, and agent-ready structured data. $350: the bare single page, one revision round. Most people take the middle one. Delivery is 72 hours from deposit on all three. Which fits?”

Rules, per Chris Do’s episode of BigDeal (Jun 24): anchor high by stating the $900 option first. Never justify a number (“it takes me X hours” is a confession, not a pitch). Never mention models, tokens, or costs. If they push for a discount, remove scope instead of dropping price: “I can do $350, that is the single page with one revision.”

Terms: 50% deposit to book, 50% on delivery. The 72-hour clock starts at deposit.

Step 6: Winning the gig (the honest bottleneck)

The cost collapse wins you zero clients. Outreach does. The mechanic that converts is the free teardown: proof of thinking before any money moves.

The note (send to 10 warm-network people, then marketplaces and build-in-public threads):

“I am taking on two fixed-price landing page builds this week: $500 flat, delivered in 72 hours, with a copy pass, mobile QC, two revision rounds, and structured data so AI search tools can read the page. Before you pay anything, I will send a free one-page teardown of your current page so you can judge how I think. Want the teardown?”

The teardown (30 minutes, one page): three things their current page does well, three specific leaks (unclear offer, buried CTA, no mobile hierarchy, no structured data), and one line: “If you want these fixed, my brackets are below.” The teardown is you doing the plan-pass thinking in public. It converts because it is useful even if they say no.

Where the buyers are: your own network first (past employers, founder friends, local businesses), freelance marketplaces (expect price pressure; your counter is the receipt stack, not a discount), X build-in-public and indie-hacker threads (founders launching weekly), and productized-service directories.

Step 7: The agent-ready line item (the forward upsell)

Every delivery includes a JSON-LD block. Quote it by name; it is one sentence of pitch:

“The page ships agent-ready: structured data that AI search and shopping agents can parse, which matters more every quarter. On June 22, Stripe launched a directory that lets AI agents find and pay businesses, and Shopify shipped its Universal Commerce Protocol on June 17.”

The block (fill the brackets, validate before shipping):

```json
{
“@context”: “https://schema.org”,
“@type”: “Organization”,
“name”: “[BUSINESS NAME]”,
“url”: “[URL]”,
“description”: “[ONE-SENTENCE OFFER, from the brief]”,
“email”: “[CONTACT EMAIL]”,
“sameAs”: [“[SOCIAL PROFILE URLS]”]
}
```

Add Product with offers (name, price, priceCurrency) when the page sells something concrete, and FAQPage markup when the page has an FAQ. Do not overreach: this is an honest forward-looking line item, not a promised traffic outcome. Never guarantee agent traffic.

Step 8: Publish the spread (the receipt that wins the next gig)

After every delivery, fill one row in the Receipts tab and publish it anonymized wherever you sell (your page, your X profile, your marketplace bio):

Gig receipt, [Month YYYY]: landing page for a [niche] founder. Price: $500. Model cost: $0.87. Production time: 2h 50m. Delivered in 71 hours. Two revision rounds used.

Attribution rules (use these exactly, or the receipt is worthless):

  • Price charged: cash actually collected. Note marketplace fees separately if any.

  • Model cost: every token across plan, execute, review, retries, and dead ends, read from the OpenRouter activity page for the gig’s date range. Round UP.

  • Production time: all human minutes from brief to final delivery, including client messages. Round up to the next quarter hour.

  • Delivery time: hours from deposit to first delivered draft.

  • Client identity: anonymized by default (“a [niche] founder”). Named only with written permission.

  • If you cannot defend a number from a log or screenshot, do not publish it.

Why publish the cost? Because transparency is the moat the anchor needs. Anyone can claim quality. A dated stack of real receipts proves speed, margin discipline, and honesty at once, and buyers pay premiums to operators who prove things.

See it work: one gig, start to finish

The setup: You spot a bootstrapped scheduling-app founder on X complaining that their launch page “looks like a 2019 template.” You send the note. They ask for the teardown.

Day 1 (Tue). 30-minute teardown: clear offer buried in paragraph three, no mobile hierarchy, zero structured data, CTA below the fold. You send it with the three brackets.

Day 2 (Wed). They take the $500 bracket and pay the $250 deposit. Clock starts. You run the plan pass on a frontier model (about $0.40) and get the spec: five sections, copy outline, brand tokens pulled from their app, a 10-item acceptance checklist.

Day 2, evening. Four execution runs on GLM 5.2 (about $0.06 each): v1 full build, v2 hero rewrite, v3 pricing table fix, v4 spacing and FAQ tighten. About $0.24.

Day 3 (Thu). Review pass on a third-family model (about $0.15): punch list of six items, two of them real (a contrast problem in the pricing tier, one FAQ answer drifting past the brief). Two fix runs (about $0.12). You run the full QC checklist, screenshot desktop and mobile, read the copy aloud, and catch one robotic sentence the models missed. Total model spend so far: $0.91. You deliver at hour 70 with a one-line summary of what you QC’d.

Day 4 (Fri). One revision round: they want the CTA wording changed and a founder photo slot. One execution run ($0.06). They accept, pay the $250 balance.

The receipt, logged and published: Price $500. Model cost $0.97, rounded up to $1. Production time: 2h 45m. Delivered in 70 hours. Your gross margin: about $495 after hosting and spare change.

Numbers are illustrative and deliberately conservative; the model costs are drawn from the June 18 to 23, 2026 receipts cited above and will drift as prices move. What does not drift: log your own numbers and publish only what you can defend.

Your 7-day install plan

  • Day 1: OpenRouter account, $20 in, privacy settings checked. Set up the folder and the Ledger.

  • Day 2: Run the 10-task golden eval on GLM 5.2. Log the result. If it fails, eval Kimi K2.7 Code and use the winner.

  • Day 3: Practice build: rebuild a real business’s page end to end through the full chain plus QC. Rebuild the structure and offer in your own words; do not republish their copy, logo, or photos, and label the piece unaffiliated spec work. This is your portfolio piece and your dress rehearsal.

  • Day 4: Write your bracket sheet and your bio line (“fixed-price pages, 72-hour delivery, receipts published”). Publish the spec-work piece.

  • Day 5: Send the note to 10 warm prospects. Post it where founders launch.

  • Day 6: Send teardowns to everyone who bit. Quote brackets on the same day.

  • Day 7: First deposit in, run the gig per the worked example. Publish the receipt.

Then repeat Days 5 to 7 weekly. The receipts compound; the outreach gets warmer every cycle.

  • Cold email: CAN-SPAM applies: truthful headers, no deceptive subject, a physical mailing address, honor opt-outs within 10 business days. Cold DMs: respect each platform’s rules; one note, no sequences without consent.

  • Client confidentiality: OpenRouter routes prompts to third-party providers. Check the data-handling settings and the routed provider’s retention policy before any confidential client material enters a prompt. Never paste credentials, customer PII, or unreleased financials without the client’s written OK.

  • Output licensing: open-weight model licenses generally permit commercial use, but check the current license text for the exact model you route to, plus OpenRouter’s terms. Do not resell raw model output as “licensed stock.”

  • Copyright honesty: under current US Copyright Office guidance, purely AI-generated material is not copyrightable; your human-authored copy edits, structure, and selection help. If a client asks about ownership or AI use, answer honestly. A simple contract line works: “Deliverables are produced with AI-assisted tooling under human direction and review; all deliverables transfer to the client on final payment.”

  • No fake proof: practice builds are labeled spec work, always. No invented testimonials, on your page or theirs. No “featured in” claims for things that did not happen. The FTC’s endorsement guides apply to you, and your receipt stack only has value if every number on it is real.

  • Platform AI-disclosure rules: some marketplaces require disclosing AI-assisted production; check the platform’s policy before listing.

  • No income promises: share your real receipts. Never promise a client’s page will hit any traffic, conversion, or revenue number.

Want the desk, not just the kit?

The free kit makes you build the trade by hand. The Spread Desk, this issue’s Pro upgrade, is the done-for-you layer: the full three-model routing configs with exact settings, the 20-task golden-eval pack tuned to landing pages and marketing sites, the bracketed pricing scripts with objection lines, the gig-sourcing playbook, and the per-gig ledger that doubles as your public proof asset. It ships to members as a rolling build, and founding members set the order.

Founding rate: $129 a year, locked forever. Closes when the first 25 members are in; the standard price rises toward $399 as the Vault and the scorecard grow.

This kit is from Overyield: make money with AI, one play at a time. Educational, not legal or business advice. Follow the outreach rules in your area (CAN-SPAM and platform ToS), keep a human review layer on every delivery, and publish only numbers you can defend. Numbers in examples are illustrative.

Keep reading