Souped — GTM & Positioning Master (v6)

Date: 2026-07-23 Owner: Ismael Larrosa (Capicua) Status: Text mirror of the master. The master surface is souped-gtm-recap.html (published at the artifact URL below) — one page holding strategy + living status log. This md carries the same content in text form for grep/agents; when they disagree, the HTML wins. Together they supersede souped-positioning-v5-master.md, souped-positioning.md, and the April GTM docs (souped-gtm-plan.md, souped-gtm-onepager-for-janis.md, 01-90-day-gtm-plan.md).

Source-of-truth rule (updated). In v5 the live site was canonical. v6 inverts this temporarily: the positioning below is the decided direction; the live site (www.souped.app) still carries v5 copy and must be updated to match. Until the site ships v6, this file wins. Once the site is updated, the site becomes canonical again.

📍 The master site: https://full-pine.getsouped.app — the only publishing home (as of 2026-07-23). Tabbed site with menu bar (Overview · OPE · Positioning · Market · Product & Motions · Record · Library). Source: souped-gtm-recap.html; deploys from the private repo Ismaellarrosa/souped-gtm (local clone: Souped/site/) on push to main. Publish flow: edit MDs / recap.html → python3 embed_mds.py (renders library + stages site/index.html) → commit + push in Souped/site/. The old Claude artifact (claude.ai/code/artifact/d48f1cb8…) is frozen as a snapshot — do not redeploy it. Its Status Log section is the running record — newest entry first, entries never deleted. Update rule: whenever reality changes (UVEG decision, site update, panel results, Stripe ships, a plan step completes), append a dated entry to the log in the HTML, refresh the affected status tables, redeploy to the same artifact URL, and mirror substantive strategy changes into this md.

0. What changed in v6

1. New master positioning (below) — replaces "Every founder deserves a personal chef — yours comes with the full brigade" as the public hook. Chef/brigade become product-layer vocabulary, not headline copy.
2. Janis outbound plan retired. The 300–400 mailbox cold-email motion never launched and is no longer part of the plan. The ICP tiering and hook bank survive as targeting assets (§4, §7).
3. 90-day plan (Apr–Jun) closed out. Targets not hit as written; superseded by the forward plan in §11.
4. Current reality reconciled — UVEG pending, product-station statuses, game-loop design in progress.

One-Page Endgame — v2 (updated 2026-07-23)

The ProductLed OPE canvas, rebuilt against v6 canon. Supersedes outputs/01-one-page-endgame.md (2026-04-06). Pictures are honest resets, not the April targets. (Numbers in the Pictures are proposals — Ismael to confirm.)

Changed from OPE v1 (Apr 6): Obvious Choice rewritten to v6 (chef framing out) · moats re-sequenced per the contrarian audit (day-1 moat leads; Fond demoted to month 3+; "Free Moat" deleted — there is no permanent free tier) · "Brain" → Fond · pictures reset to reality (April's "100 paying by May" never happened) · EIR field signal added to Ideal Customer.

1. Positioning v6 — the master lines

You shipped an app. Souped builds the business with you. Wake up knowing the next move. The world's first Startup Kitchen. From crude to seasoned. Service!

The five layers (Dunford-inspired), remapped

Why these lines (what each one does)

• "You shipped an app" — enters at the ICP's exact moment (shipped-and-stuck). This is the migration on-ramp v5 flagged as the #1 copy gap: it addresses founders with an existing app instead of reading "start fresh." It also carries the Critical Event the contrarian audit demanded — the app is already live, already fragile.
• "Souped builds the business with you" — co-builder frame, not service frame. Aligns with the June explainer's "the cofounder your builder never was." With you, not for you: the founder stays the hero. Uses the category verb (businesses, per Play Bigger canon).
• "Wake up knowing the next move" — the daily briefing (Nacha's function) expressed without naming her, per the voice-persona architecture. It's the retention promise on the front door: the reason to stay after the 90-minute deploy.
• "The world's first Startup Kitchen" — the category claim, unchanged from Play Bigger work. Kitchen metaphor now concentrates at the category level; the hook and promise carry zero food vocabulary. This resolves v5's term-density gap (Kitchen/Chef/Brigade/Menu/Courses/Prix Fixe overload).
• "From crude to seasoned. Service!" — the journey, unchanged since v2. It names the transformation Mateo is buying (hero-framed: he gets seasoned) and caps it with the kitchen's call at go-live. It closes every pitch, trailer, and explainer — the signature sign-off, not a headline.

The Dunford matrix (5 components, derived in order)

The layers above are how positioning is expressed. This matrix is how it's derived — Dunford's components, each feeding the next. Sources: Turbocheck P1–P4, beachhead segmentation, Play Bigger.

Reading it downward is the pitch's logic chain: given what Mateo would otherwise do (1), only Souped has these (2), which buy him this (3), he's the one who cares most (4), and "Startup Kitchen" is the frame that makes it all click (5) — and the market is arriving on schedule (+).

The differentiator — the dialogue, not the toolbox (added 2026-07-23)

What makes Souped unique is not the technical attributes (CMS, SEO, OAuth, Stripe out of the box — that's the floor). It's how you co-create: building the business in dialogue with an intelligence embodied in Nacha — a cofounder who helps you build it and challenges you. The platform forces mindful answers; the mindful answers make the founder understand their own business. Three rooms, escalating pressure:

The compounding trick: your answers become your opponents. The more mindful the founder, the sharper the training — and Fond keeps all of it. Courses teach. Tools execute. Duolingo drills. Souped makes you face the table.

Canon change (2026-07-23): one voice. Nacha is the only speaking persona in the co-creation flow — the Brigade cooks in silence (it remains proof/product vocabulary, not a speaker). This supersedes v5 §5's three-persona choreography. Open call: does Funes keep his one-line risk-brake under the one-voice rule, or does his warning become Nacha's? (Funes canon says keep minimal — default is he stays, rare and gated.) Spine/Psychological Component/ needs a matching update.

Where chef & brigade live now

Chef and brigade are retired from headline copy but remain: - In-product: station names and kitchen vocabulary, unchanged. Voice: one speaker — Nacha (canon change 2026-07-23, see "The differentiator" above). The brigade is silent vocabulary, no longer a speaking persona; Funes's gated one-liner is an open call. v5 §5 and Spine/Psychological Component/ remain the reference for Nacha's voice rules (tone, no exclamations, "Captain") but their three-persona choreography is superseded. - As proof structure: the 8 stations / "$80K team" comparison in features and pricing sections. - The $80K anchor stays. "A team like this costs ~$80K/month" remains the price wedge — it no longer needs the brigade metaphor to work.

Language rules (carried forward + updated)

• Never describe Souped as "AI." Behavioral language only: always on, gets smarter, meets you where you are. ("AI builders" naming the Bolt/Lovable category is fine — that's their name.)
• The world is the kitchen at category level. No boat/ship metaphor. Nacha may still say "Captain."
• Brigade in English, brigada in Spanish — in-product.
• Avoid "real company" — flagged abstract in cold tests.
• Say "won't let you drift," never "you can't leave" (commitment device, not trap).
• Metaphor budget: hook + promise stay metaphor-free; category line carries "Kitchen"; stations carry the rest. Don't re-densify.

Open copy calls for the site update — panel round 5 recommendations (2026-07-23, awaiting Ismael's confirm)

Full findings: souped-panel-round5.md. The v6 hook survived (3/3 recall, perfect filter); the hero architecture needs surgery:

• CTA → "See your next move. Free." (C2 won 2–1 + steals C1's working ingredient). Hard condition: the click must deliver a real next-move artifact immediately.
• Sub-line promoted to co-hero: "Brand, billing, and monitoring — wrapped around the app you already have. No rebuild." — 3/3 comprehension + recall; the only phrase that told everyone what the product is.
• Category line exits the hero. 0/3 identified the product from it; "world's first" = hostility trigger; EIR parsed "Kitchen" as food entrepreneurship. It returns to the original v5 placement: pills, PR, About. Tagline ("crude" read as insulting the reader's app) → internal + cook-show sign-off only.
• Pricing honesty resolved: lead "$12/mo, or $10 billed annually"; month-to-month visible first; qualify every "from $10/mo" in outreach; state the 1% cap (needs a number).
• Two doors: keep the post-ship front door; add "Still carrying the idea? Start here." side door (idea-phase converts 0/3 on the current hero, 3/3 recognized "the idea gets heavier every week").
• Show, don't claim: morning-brief screenshot on the page, one boss-fight transcript, free first-three-questions pre-signup. All three panels independently demanded artifact over claim.
• ⚠ Packaging escalation (Pablo): hero promises billing; Stripe is gated behind Kitchen Plus — 2/3 Mateos flagged bait-and-switch unprompted. No copy fixes this.

2. Category — Startup Kitchen (Play Bigger, current)

Full playbook: souped-play-bigger.md (Jun 2026). Essentials:

• Category: Startup Kitchen. Verb: Souped builds businesses (descriptor, not tagline).
• The missing: AI builders create apps; nobody turns an app into a business (brand, revenue, monitoring, intelligence) in one workflow. TAM ~$600M by 2028 (conservative).
• Master froto: "I have an app" → "I have a business."
• The real competitor is prayer (Turbocheck P1): most founders ship crude code and hope. Souped competes with inaction, not with Bolt.
• Category game plan: Phase 1 (now): prove the kitchen with vibe coders — cook show, case studies. Phase 2: designers + Pantry. Phase 3: analyst/press recognition. Phase 4: budget line item.
• Contrarian-audit hedge (still standing): category creation on a bootstrapped budget is a conscious bet. Fallback if conditioning stalls: reposition as "the production layer for AI-built apps" without losing the games.

Competitive state (refreshed 2026-07-23 — full delta: souped-competitive-delta.md): - Billing fell as a differentiator — Lovable Payments, Replit+RevenueCat/Stripe, Bolt, Rocket.new all ship it. Stop leading with it. - CoFounder.AI (launched Jun 25) is the first direct guidance competitor — our daily-plan mechanic at $39/mo, "Software-as-a-Partner" press. Counter: their cofounder gives advice; ours operates your actual product. - Still unowned, still ours: founder-facing monitoring (the 12-detector floor) + the decision-challenging/boss-fight layer. These carry the claims now. - Lovable is the existential clock ($500M ARR, ~$13B, assembling our stack from the build side). Durable counter: the layer on top of apps built anywhere + the game layer they have no DNA for. Import-from-any-builder friction removal = strategic work. - The 1% is still unique in the market — but expect "0% fees" weaponized against us (Lovable/Replit advertise taking no cut). Counter-story: 1% buys the floor + the cofounder, not checkout. Flat pricing is itself a wedge against credit/token cost-anxiety. - Retired framing: "can't afford a dev team" as a pain — dead last for 3/3 panel Mateos; AI builders already solved it in their heads. The $80K figure survives only as a price-comparison anchor.

3. ICP / Beachhead

Wave 1 (locked, scored 22/22): shipped-and-stuck vibe coders. Solo founders / teams <5 with a live-or-nearly-live app built on Bolt, Lovable, Cursor, Replit, v0, or Base44. Fragile code, no monitoring, no billing, generic brand. $0–$100K revenue. North America first. Found on Twitter/X talking about the pain.

• Persona: Mateo — 25–40, solo, non/semi-technical, <$100/mo tooling budget.
• Best-fit signals (Turbocheck P4): shipped with a builder; has real users or about to launch; feels the "it works" → "it's a business" gap; can't afford $5K+/mo dev help; values taste; lives in build-in-public communities.
• Wave 2 (deferred): design-native founders — different pain (autonomy, not reliability). Not until Wave 1 validates.
• Wave 3 (2027 frame): agencies, LATAM, verticals.

Targeting tiers (retained from the outbound work — channel-agnostic):

Note how v6's hook is Tier A's hook, promoted to the master positioning — the beachhead moment is now the front door.

Field signal (2026-07-23 — three months of conversations)

The audiences who have understood Souped's value prop fastest and best: 1. Entrepreneurs-in-residence at business schools and startup accelerators — they've watched cohorts hit the app→business wall repeatedly; Souped names a problem they already carry. 2. First-time founders at the idea phase — pre-ship, hungry for the guidance layer.

What this does and doesn't change: - Wave 1 stays locked (Mateo, shipped-and-stuck) — this is a signal, not a re-segmentation. - It strengthens the Kitchen X wedge: UVEG (a university) being the furthest-along deal is consistent with this, not a fluke. EIRs are the natural champions inside Tier C institutions — arguably the buyer persona for Kitchen X. - Watch-item / tension: the v6 hook ("You shipped an app") speaks post-ship. The fastest-understanding audiences are pre-ship. Options if the signal keeps strengthening: an idea-phase on-ramp door in the copy, or an EIR-specific message ("Your cohort's ideas deserve a kitchen") — without diluting the front door. - Action: add an EIR persona and an idea-phase first-timer persona to the v6 panel test (plan step 1) so we measure this instead of anecdote it.

4. Offer & pricing (canonical, per live site)

• Lead with Kitchen Plus. "$80K/month team → $12/month + 1%" is the wedge. The 1% is the alignment story ("we only earn when you earn") and the ACV-expansion answer to the contrarian audit's thin-ACV gap.
• Code ownership: "Your code is yours. Export anytime. No lock-in." Standard Next.js on Vercel with Neon.
• ⚠ Open pricing-honesty call (unresolved from v5): the "$12 + 1%" wedge is annual-only; month-to-month Plus is $18 + 1%. Either make annual the unmissable default at signup or lead with $18. Decide before any paid or outbound push.

5. Product — proof structure (8 stations, status Jul 2026)

Supporting: Chaski (alerts) shipped · UAT previews shipped (needs polish) · Barlog (auth) in progress · Pantry (marketplace) designed, not built.

Game loop (in design, 2026-07-08 — future differentiator): plates → cards (asset/token) → deck → Tables (Encounters) → the Critic (boss). "A flight simulator for founding." Feeds the card + outcome data moat. Not yet on site; positioning payoff lands post-ship. See v5 §4A and docs/game-systems-resources-and-struggle.md.

6. Messaging — tested and banked

Cold-test validated (4 panel rounds, Apr 2026): - "$10/mo" price anchor — 100% recall - "90 minutes" — lands - Lead magnet "The 7 Silent Killers of Half-Baked Apps" — 100% recall - "$80K → $12 + 1%" price-shock wedge - "You bring the taste. We have the chops."

Hook bank: "3am at billify.app" · "$80K → $12 + 1%" · "You shipped. Now what?" · "Your fire deserves a kitchen" · "400 hours or 90 minutes" · "We only earn when you earn."

30s explainer (locked script, EN+ES): problem-led, "the cofounder your builder never was," closes on "From crude to seasoned. Service!" Blocked on product screen recordings. See souped-explainer-30s.md.

Pitch script v2 (2026-07-23): DM openers for Tier A + idea-phase + EIR/Kitchen X, conversation flow (incl. the 1% objection), cook-show open/close, one-liner bank — all v6 canon; "real company" purged. See souped-pitch-script.md (in the Library). Note: pitch lines are written to v6 canon but share the v6 lines' status — not yet panel-tested.

Still missing (carried from v5, unresolved): 1. Social proof — zero real-app URLs, testimonials, or cook-show clips anywhere. Skeptics won't convert without one. 2. Migration story — resolved at positioning level by v6's hook; still needs a "bring your existing app, users never notice" section on the site.

7. GTM motions — status

GTM stage (Maja): still Stage 0 → 1 (Proof of Concept → Proof of Monetization). Stage 1 is gated on The Check (Stripe) shipping and first self-serve payers. UVEG would be Stage 1 revenue via the institutional side door.

8. Retention — the right side of the Bowtie

Standing commitments from the contrarian audit (unchanged):

• Owner: Ismael, until there's a team.
• Target: ≥85% day-30 GRR (No Touch benchmark). NRR >100% via Plus rev share + future expansion.
• 4-level churn playbook stands; rest days are canon — if the kitchen is quiet, Nacha says so and leaves ("silence is a feature"; diminishing cadence after week 1).
• Moat sequencing: day-1 moat = daily plan + monitoring (turning it off feels terrifying). Fond becomes the moat at month 3+. Don't sell the moat; sell the next move. (v6's promise line — "wake up knowing the next move" — is the retention mechanic stated as the pitch.)
• At this ACV, retention is the business model. Define churn-intervention triggers before scaling acquisition.

9. Maja Voje checklist — where each piece stands

10. Current reality — July 2026

• Product: live at souped.app (American Dream v3, still v5 copy). Stripe/The Check and Barlog in progress; Fond in development; Pantry designed.
• Revenue: no self-serve payers yet (Stage 0). UVEG $13k Kitchen X proposal pending decision — would be first revenue + first case study + first co-brand deployment.
• Outbound: Janis plan stalled, never launched — retired in v6.
• Positioning: v6 lines decided (this doc); site update pending; not yet cold-tested.
• Design work in flight: game loop (Plates/Cards/Deck/Tables/Critic), Captain's Log (Nacha briefings — the feature behind "wake up knowing the next move").

11. Forward plan — next 90 days (Jul 23 → Oct 2026)

One goal, unchanged in spirit from April: first paying customers + one repeatable motion. Sequenced by what unblocks what:

Kill/scale discipline (kept from April): 60-day checkpoint on whatever motion is live — scale, rework, or kill. No extensions.

12. What this file supersedes

Reference only, downstream of this file: - souped-positioning-v5-master.md, souped-positioning.md (v5 §5 and Spine/Psychological Component/ remain the reference for Nacha's voice rules; their three-persona choreography is superseded by the one-voice rule, §1) - souped-gtm-plan.md, souped-gtm-onepager-for-janis.md, email-to-janis.md — retired - souped-gtm-contrarian-audit.md — findings absorbed (§2 hedge, §4 pricing, §8 retention) - souped-positioning-brief.md (v4), souped-landing-copy-v3.md, souped-turbocheck-v1.md - /gtm-strategist-skills/outputs/ — the full April research corpus (Maja Voje framework deliverables, cold tests, copy kits, decks)

Souped — Play Bigger Playbook (Current)

Date: 2026-06-25 · Updated to v6: 2026-07-23 Source: Play Bigger: How Pirates, Dreamers, and Innovators Create and Dominate Markets (Ramadan, Peterson, Lochhead, Maney, 2016) Category: Startup Kitchen Company: Souped (public brand) / VibeTools (internal) CEO: Ismael Larrosa, Capicua

Canonical alignment (updated to v6, 2026-07-23). This playbook is downstream of the v6 master (souped-gtm-recap.html / souped-gtm-master-v6.md) and has been fully reconciled to it: v6 hook + promise in the POV stack, cold pitch, and trailer; Kitchen 0/Plus/X pricing; The Counter rename; v6 metaphor budget in the word lists. The Startup Kitchen category is unchanged. Originally downstream of the live site and souped-positioning.md. It replaces the April Play Bigger files (11-play-bigger-checklist.md, 12-play-bigger-master-playbook.md), which are now historical. Corrections applied: the category verb is businesses (Souped builds businesses — used as a descriptor); the tagline is "From crude to seasoned. Service!" (retires "Souped builds businesses" as the signature line); The Pass = Health Monitor; there is no permanent free tier (7-day free trial); the intelligence layer is Fond. (The June note "all Souped pricing is TBD" is obsolete — pricing shipped: Kitchen 0 / Plus / X, see the v6 update below.) Status reflects July 2026 reality.

What changed in the v6 update (2026-07-23)

• Hook: "You shipped an app. Souped builds the business with you." replaces the personal-chef hook. Promise: "Wake up knowing the next move." Chef/brigade retire to product-layer vocabulary (stations, in-product wording, the $80K proof comparison). POV stack, cold pitch, and trailer updated below.
• Pricing is live, not TBD: Kitchen 0 ($10/mo annual, $12 monthly), Kitchen Plus ($12/mo + 1% annual, $18 monthly), Kitchen X (custom). The $80K anchor stays.
• The Counter renamed from "The Plate" (decided 2026-07-08; site change pending) — "Plate" now means the game/prep act.
• Reality flags: UVEG $13k Kitchen X proposal pending; Janis cold outbound retired; site still carries v5 copy.

What changed from the April version (June update, kept for record)

• Verb: "Souped builds businesses" — not "products," not "apps." This is the category claim.
• The Pass = Health Monitor (12 detectors). The old taxonomy that mapped The Pass to a dashboard and The Plate to Health Monitor is retired.
• Free tier removed: the on-ramp is start free for 7 days, no card — not a permanent $0 tier. The "walking billboard" logic no longer applies.
• Fond, not "Brain." Fond is the name of the intelligence/memory functionality.

1. The Magic Triangle

A category king designs three things at once, in sync.

1.1 Product Design — product/category fit

Assessment: The product already is a kitchen — App Discovery is mise en place, Brand Studio is seasoning, Spark is the fire, Health Monitor is quality control at the pass. Strong fit. Open dependencies: Stripe billing and Barlog are not yet complete.

1.2 Company Design — company/category fit

Culture: design-native (craft, not code); taste as the entry requirement; elevation, not repair ("Make It Tasty"); the spectacle is the marketing (the cook show); speed with craft (fast and beautiful).

Business model: start free for 7 days (no card) → paid tiers (Kitchen 0 / Plus / X — live; see v6 master §4). Bootstrapped; revenue funds growth; the cook show is zero-cost distribution.

Assessment: a design studio is a kitchen — it produces craft through expert process. Natural fit. Gap: the team hasn't been formally aligned on "Startup Kitchen" as the category (POV meeting still outstanding).

1.3 Category Design — category/market fit

• Category name: Startup Kitchen
• One line: From crude to seasoned. Service! (Souped builds businesses — the category descriptor, not the tagline.)
• Assessment: the category doesn't exist yet. AI builders (Bolt, Lovable, Cursor) create apps; monitoring tools watch apps; design tools mock up apps. Nobody takes an app and turns it into a business — product design, brand, revenue, monitoring, intelligence — in one workflow. The Startup Kitchen fills a gap nobody named.

2. Category Discovery

2.1 The Insight

• Market insight: vibe-coded apps aren't production-grade. The "last 30%" between a working app and a real business needs a team that costs ~$80K/month. Solo founders can't afford that, so they ship fragile apps and pray. Nobody solves this.
• Technology insight: Capicua's internal design-studio tools (Skills, Fond, Health Monitor) — built to run the agency — can be productized. The product team is built into the platform as invisible Skills.
• The "missing": no Startup Kitchen exists. AI builders create apps; nobody creates businesses. The gap between "app" and "business" is the missing.

2.2 Dave's Three Questions

1. Explain like I'm five — what problem do you solve? People build apps with AI tools. The apps kind of work — but they look generic, break silently, can't scale, have no brand, no monitoring, no way to make money. Fixing that costs ~$80K/month. Souped does it for a fraction, in 90 minutes. → In ten words: We turn apps into businesses.

2. If you solve it perfectly, what category are you in? Not an AI builder, monitoring tool, or design tool. A kitchen that takes raw ingredients (ideas, apps) and cooks them into businesses (brand, revenue, monitoring, intelligence). → In ten words: The Startup Kitchen — the world's first.

3. If you win 85% of that category, how big is it? Bolt (~$400M ARR), Lovable, Replit (30M+ users) produce thousands of "almost-businesses" weekly. Conservative TAM ~$600M by 2028, expanding into designers, agencies, enterprise. → In ten words: Every AI-built app is a customer. ~$600M by 2028.

2.3 Fact Finding (11 facets) — summary

Vision, customers, problem, product, ecosystem, competition, business model, GTM, and organization are all defined (see souped-positioning.md and the GTM corpus). Funding: bootstrapped, no external raise planned. Use cases: see §5.3. Pricing: live — Kitchen 0 / Plus / X (see v6 master §4).

2.4 Category Name

Startup Kitchen. "Startup" = the outcome (a business, not just a product). "Kitchen" = brand-native (Souped's whole universe is a kitchen). Two words, simple, memorable, different. The cook show is the category made visible.

2.5 Category Design Document (6 sections)

1. Landscape: AI builders = grocery stores (raw ingredients). Monitoring tools = health inspectors. Design tools = recipe books. Nobody runs the kitchen — where ingredients become meals and meals become restaurants. Souped is the first Startup Kitchen.

2. Ecosystem: Feeders (Bolt, Lovable, Cursor, Replit) → raw ingredients. Adjacent (Figma, Framer) → mockups. Substrate (Vercel, Neon, Supabase) → utilities. Utility (Stripe) → payments. Distribution (cook show, Twitter/X, YouTube, Discord).

3. Frotos (from → to):

4. Name & description: Startup Kitchen. Where AI builders create apps, a Startup Kitchen builds businesses. The entry requirement isn't code — it's taste.

5. The case for the category: Every week, thousands ship apps with AI builders. They work — kind of. Generic, fragile, no brand, no monitoring, no revenue. The "last 30%" costs ~$80K/month, so most ship the 70% version and pray. The Startup Kitchen solves this: idea to live business in 90 minutes. If the category wins, every vibe coder, designer, and agency has an $80K/month product team's output for a tiny fraction. The billion-dollar one-person company stops being a myth.

6. Game plan: Phase 1 (months 1–6): prove the kitchen with vibe coders; cook show; case studies. Phase 2 (6–18): open to designers; Pantry; community. Phase 3 (18–36): analyst/press recognition; competitors play by Souped's rules. Phase 4 (36+): "Startup Kitchen" is a budget line item; enterprise; ecosystem.

3. Point of View (POV)

3.1 The Locked Stack

(v5 lines retired: hook "Every founder deserves a personal chef"; Hamlet main "personal chef for your startup." Chef/brigade are product-layer vocabulary now.)

3.2 The Cold Pitch

You shipped an app. It works — but it's not a business. No brand. No billing. No monitoring. No plan for tomorrow. Souped builds the business with you. Brand, billing, monitoring — wrapped around the app you already have. No rebuild. And every morning: you wake up knowing the next move. 90 minutes to Service. Always on after that. The world's first Startup Kitchen. Start free at souped.app — no card needed.

To test cold (with the v6 panel round): does "builds the business WITH you" read as co-builder or as vague? Does "wake up knowing the next move" land as the retention promise? Does "no rebuild" defuse the migration objection?

3.3 The POV (movie-trailer format)

White text on black. One slide at a time. For internal alignment, cook-show intro, keynote.

• Every week, thousands ship apps with AI builders.
• Bolt. Lovable. Cursor. Replit. The tools are incredible.
• In 90 minutes, anyone can go from idea to working code.
• But the builders stop there.
• No brand. No billing. No monitoring. No plan for tomorrow.
• "I had the idea. I built the app. But somewhere between 'it works' and Service!, I hit a wall."
• Not talent. Experience. Tools. Guidance. Nobody showed up.
• The part that turns code into a business requires a team. Salaries, tools, benefits. ~$80,000 before they write a line.
• So what do most people do? They ship the code. They pray. They lose users silently. They feel like frauds.
• And the industry calls this a success.
• UNTIL NOW.
• You shipped an app.
• Souped builds the business with you.
• Brand. Billing. Monitoring. Wrapped around the app you already have.
• And every morning — you wake up knowing the next move.
• 90 minutes to Service. Always on after that.
• Built by operators, for founders who hit the wall between their spark and their shot.
• The world's first Startup Kitchen.
• From crude to seasoned. Service!

3.4 POV in Action (5 deployments)

1. Hiring filter: "If you believe every idea deserves to be a business — and the gap between 'app' and 'business' is the defining problem of the vibe-coding era — we want to talk. If shipping generic AI output is good enough for you, we're not the right kitchen."
2. Investor narrative: "We're not a better AI builder. We're creating a category — the Startup Kitchen. Builders are grocery stores selling raw ingredients. We're the kitchen that turns them into businesses. We're designing the category, not chasing a market."
3. Employee alignment: everyone can deliver the POV in 2 minutes. Test: "What does Souped do?" Feature names (Spark, Health Monitor) = not aligned. "We're a Startup Kitchen — we build businesses" = aligned.
4. Product filter: every request, TBD, and sprint decision passes through "Does this help the kitchen cook a better business?" If it only makes Souped a slightly better builder, skip it.
5. Brand alignment: every surface respects the v6 metaphor budget — hook + promise metaphor-free ("you shipped," "the next move"); "Startup Kitchen" at category level; chef/brigade/stations vocabulary in product and proof layers only.

Words to use (marketing): you shipped, builds the business with you, the next move, no rebuild, always on, daily plan, tried-and-true, practical, kitchen (category level), taste, cook, serve, Service!, spark, scar tissue, operator, meets you where you are, businesses. Words for product surfaces only (not headlines): personal chef, the brigade, stations, recipe, ingredients, seasoning, mise en place, sear, plate — the kitchen vocabulary lives in-product and in the proof/features layer, per the v6 metaphor budget (hook + promise metaphor-free; category line carries "Kitchen"). Words to avoid: platform, solution, tool, software, AI-powered, AI cofounder, leverage, optimize, disrupt, course, MBA, curriculum, "learn how to" (Souped doesn't teach — it does), "real company" (flagged abstract in cold tests), "you can't leave" (say "won't let you drift").

4. Mobilization

4.1 Lightning Strike

• Strike: Episode 1 of "Service!" — the live cook show.
• Format: YouTube Live, ~90 minutes, a real vibe coder's app elevated to a business on camera. Target Tuesday 2PM ET.
• Master controller: Ismael (given team size).
• Delivers: live proof the category is real; before/after content; "Startup Kitchen" enters public vocabulary; 8–12 social clips for the following week.

Readiness (Jun 2026):

• [x] Website reflects "Startup Kitchen" language (live at souped.app)
• [ ] Website updated to v6 positioning (hero, migration section, CTA decision — site still carries v5 copy)
• [ ] v6 lines panel-tested (same rig as rounds 1–4)
• [ ] Stripe billing integrated (in progress — launch dependency)
• [ ] Barlog auth gateway (in progress)
• [ ] Guest confirmed from outreach list + app pre-diagnosed
• [ ] YouTube Live + OBS tested; Spark tested under stream conditions
• [ ] Tamara ready to produce clips
• [ ] Discord ready for "Make It Tasty" submissions
• [ ] Promotion posted 48h before

4.2 Four Seminal Documents

A. Category Blueprint (external-facing)

THE STARTUP KITCHEN BLUEPRINT
=============================
TODAY (2026)
├── AI builders create apps (Bolt, Lovable, Cursor)
├── Apps aren't businesses — no brand, monitoring, billing, intelligence
├── The "last 30%" costs ~$80K/month
└── Souped launches the first Startup Kitchen

YEAR 1: The Kitchen Opens
├── Cook show proves the concept live
├── Vibe-coded apps → live businesses
├── Community forms around "Make It Tasty"
├── Paid tiers prove willingness to pay (Kitchen 0 / Plus / X — live)
└── Category earns first press

YEAR 2: The Menu Expands
├── Designers enter the kitchen (Wave 2)
├── Pantry launches (Chopped Blocks, Canned Soups, Spice Rack)
├── Fond compounds across kitchens — every business makes the next smarter
├── Agency tier
└── "Startup Kitchen" becomes a recognized category

YEAR 3+: The Kitchen Chain
├── Enterprise internal tools
├── Third-party Skills developers (the supply chain)
├── "Service! Live" conference
└── Competitors adding production features are playing in Souped's kitchen, by Souped's rules

B. Product Taxonomy (kitchen names)

The eight stations, aligned to the live site. External marketing uses kitchen names; docs may use product names; the cook show uses kitchen names exclusively.

Supporting (not stations): Chaski carries alerts from the pass to wherever you are (Discord, email, push). Skills are the invisible recipe book (architecture, design, motion, DevOps, PM). Pantry is the supply room (marketplace). In-product voice: one speaker, Nacha (canon 2026-07-23 — the brigade is silent vocabulary; Funes's gated one-liner is an open call); see the v6 master's "Differentiator" section.

C. Formal Use Cases

Use Case 1 — Mateo's broken Bolt app (Wave 1). Mateo shipped a task app with Bolt 3 months ago. 47 users. Generic UI, silent errors, slow loads, no billing. He feels like a fraud. On the cook show: The Ticket (App Discovery, live) → The Seasoning (Brand Studio, audience votes) → The Blueprint (preview gut-check) → The Fire (Spark builds; Skills fire invisibly) → The Counter (deploy, custom domain) → The Pass (Health Monitor's 12 detectors go live; Chaski wired to his Discord; Stripe billing — once shipped) → "Service!" His before/after reaction is the viral clip. He leaves with a production-grade business and a daily plan — on Kitchen Plus, $12/mo + 1% when he earns.

Use Case 2 — Sofia's Figma graveyard (Wave 2, designer). 6 years' design experience, 4 side projects stuck in Figma, never coded, hates dev handoff. App Discovery feels like home (these are product-design questions). Brand Studio is her native language. Spark produces design-first output. She ships a live finance tracker in 90 minutes — "2 years in Figma. 90 minutes in the kitchen. Service!"

Use Case 3 — Agency client project (Wave 3). A 6-person agency gets "we need an MVP for a pet-grooming marketplace." Before Souped: a $15K, 6–8 week project. With Souped: App Discovery + Brand Studio + Spark + Health Monitor in one session; a live MVP delivered same-day. The agency delivers a business, not a Figma file, and uses Souped on every project after.

D. Category Ecosystem & Control Points

Players: Bolt / Lovable / Cursor / Replit (feeders — every app is a potential customer, not a competitor); Figma / Framer (adjacent; Souped starts where they end; Wave 2 entry); Figma Make (emerging Wave 2 threat — watch); Vercel / Neon / Supabase (substrate); Stripe (utility); Base44 (closest builder comp; Souped out-delivers on output quality); Google Stitch (watch — distribution could flood the market with ingredients); Twitter/X, YouTube, Discord (distribution + community); press and analysts (category evangelism).

Control points (Souped's leverage): 1. Skills (the recipe book) — competitors can't replicate 10+ invisible product disciplines by copying one feature. 2. Fond — compounds over time; after months, switching costs are enormous. 3. Health Monitor (The Pass) — once it's on, turning it off feels terrifying. 4. The cook show — a live, public kitchen is a spectacle nobody else has.

5. Lightning Strikes + Hijacks

5.1 Thunderclaps (pre-strike teasers)

• Week 1: "AI builders are grocery stores. But where's the kitchen?" (no context)
• Week 1: survey hook — "Shipped a vibe-coded app? Tell us what happened next."
• Week 2: "We're building something for people who ship with AI tools. Not a better builder — a different thing."
• 48h before Episode 1: "This Bolt app has 47 users. It works — but it's not a business yet. We're cooking it into one. Live. Tuesday 2PM ET." (+ "before" screenshot)
• 24h before: "Tomorrow: the world's first Startup Kitchen opens. 90 minutes. One app. One transformation. Live."

5.2 Strike Cadence (3–6 in year one)

Dates are relative to the committed strike date, which gates on Stripe + Barlog.

5.3 Hijack Playbook

Chief Hijacker: Tamara. Monitors Twitter/X daily, armed with the POV and pre-written templates. Goal: 2–3 hijacks/week in the first 3 months.

6. Flywheel

How it spins: cook show attracts vibe coders → some sign up → they cook apps into businesses → Fond learns from every business → Skills improve → next business is better → live businesses become walking proof → before/after clips fuel Twitter/X → more audience → more "Make It Tasty" submissions → revenue funds the kitchen → repeat, with more data, proof, and momentum each turn.

Experience-curve advantages: Data (Fond knows patterns after N businesses no competitor can match) · Skills refinement (every build sharpens the recipe book) · Content library (each episode = a case study + 8–12 clips) · Community knowledge (Discord loops back into the kitchen) · CAC (cook show is near-zero marginal cost; SEO/social compound while competitors' CAC stays high).

Category potential expansion: Now (vibe coders, US) → Wave 2 (+~1M designers) → Wave 3 (+agencies, higher ARPU) → Wave 4 (+enterprise, multi-seat) → Pantry (+marketplace revenue share) → Endgame ("Startup Kitchen" is a budget line item, like CRM).

7. Gravity Risks + Zed Check

Zed check: Ismael (none — he defined the category). Pablo, Tamara, Carlos (alignment unconfirmed — the POV meeting hasn't happened). Action: Ismael presents the POV; each person plays it back in their own words; no feature names allowed.

Suit-fit test: Not too big (the product works bar two dependencies; the cook show proves it live; the category starts narrow and expands). Not too small (room to designers, agencies, enterprise, marketplace). Grows into it (Phase 1 = vibe coders; Phase 4 = everyone with taste).

8. Category Harvesting vs. Creation

Current mode: Creation. Stay here until the cook show is a recognized "thing" (20+ episodes), "Startup Kitchen" appears in press/analyst maps unprompted, competitors position against the term, and paid revenue is self-sustaining. As long as Ismael is on camera as the chef, he's in creation mode.

9. Personal Category Design — Ismael

• Category: The Startup Chef — cooks apps into businesses, live, on camera. Different, not better: not another tech founder or AI guru — a chef, with craft, taste, process, and the nerve to perform live.
• Personal POV: "I'm the CEO of a design studio who realized the tools we built for ourselves could turn anyone with taste into a founder. So I'm cooking apps into businesses live. 90 minutes. No edits. If it breaks, you see it break."
• Personal lightning strike: Episode 1 launches the category, Souped as king, and Ismael as the Startup Chef — three strikes in one.
• Expansion: Now (the Startup Chef on YouTube) → Year 1 (voice of the movement) → Year 2+ (the Startup Kitchen pioneer).

Summary scorecard

Souped — 30-Second Explainer (Product Capture, 16:9)

Goal: Explain what Souped is in 30 seconds — problem-led, with a sharp definition at the turn. Format: 1920×1080, 16:9. First home: site hero / YouTube / cook-show intro. Style: Kinetic text + product screen-capture, trailer-paced voiceover, music bed. VO length: ~80 words at trailer pace.

What I need to finish this: the product recordings noted in "Capture" (I can't record the product). The problem half is concept/before-state + kinetic text; the solution half is real product footage. I can generate the VO track now on request.

Locked script

Tone: calm, operator, a little weary through the problem → certain and warm after "Until now." No exclamation until the end.

Versión en español (ES) — neutro LatAm

Decisions baked in: register = neutral LatAm; "builder" kept in English (category term). ES ending diverges from EN (intentional): the Spanish closes on the positioning line "Souped: la diferencia entre una herramienta y un socio" — it does not use the canonical tagline "De crudo a curado / ¡Servicio!" The English cut keeps "From crude to seasoned. Service!" The two language versions end differently on purpose. Bookend: beat 1 "parece un negocio" → beat 8 "Tengo un negocio." Timing: Spanish runs ~35s (longer than the 30s English) — the beat-8 quote and beat-10 line are wordy. Trim a problem beat or drop "guiándote" from beat 8 if a strict 30s is needed.

Capture / visual notes

The money shots (solution half): Spark assembling the UI, the live app opening on its custom domain, a challenge card in the daily plan. Get clean takes.

Capture checklist (for whoever records)

• 1920×1080, 60fps (so the build montage can speed-ramp cleanly).
• Clean browser: hide bookmarks/extensions; full-screen; neutral wallpaper.
• Seeded demo account with believable data (the task-app from the Mateo story works) — real brand colors, populated views. No lorem ipsum, no test@test.
• Cursor: smoothing/click highlights on; move deliberately.
• Capture ~15–20s per screen so the editor can trim to the beat.
• Avoid: the Stripe/billing screen (The Check isn't shipped) and Fond (in development). "Billing" appears only as a problem idea, never as a Souped feature shot.

Music & captions

• Sparse piano/pulse under the problem → near-silence at "Until now" → warm build after. Hit the downbeat on the logo at 29s.
• Burn in open captions (most feed views are muted), short, matching the VO.
• Keep text inside 10% safe margins so it survives a later 1:1 / 9:16 re-crop.

Open items

• Recordings — needed before assembly (Capture column).
• VO — I can generate a scratch narration track (pick a voice: calm male operator / warm female).
• Companion asset — a separate, longer problem-led manifesto cut (full POV, keeps the $80K/"feel like frauds" depth) for top-of-funnel. This explainer answers "what is it"; the manifesto evangelizes the problem.

Pitch Script — Souped (v2)

Date: 2026-07-23 (supersedes outputs/14-pitch-script.md, Apr 11/15) Context: DM conversation, cook show intro, investor conversation, institutional (Kitchen X) outreach. Tone: Direct, warm, operator scar tissue. Hook and promise metaphor-free; kitchen vocabulary only at category level and in proof/product depth (v6 metaphor budget). No jargon, no feature lists. Fixed from v1: the old script used "real company" — a phrase our own cold tests killed. Gone. Pricing updated to Kitchen 0/Plus/X. Chef/brigade demoted from headlines per v6.

The DM opener — Tier A (shipped-and-stuck, found on Twitter/X)

Search: "bolt broke," "lovable scaling," "vibe code production," "my app is breaking."

"You shipped an app. It works — but it's not a business yet. Souped builds the business with you: brand, billing, and monitoring wrapped around the app you already have — no rebuild — and every morning you wake up knowing the next move. From $10/mo. Want to see yours transformed live, on camera?"

Why it works: - "You shipped an app" — enters at their exact moment; they self-select instantly - "No rebuild" — kills the migration objection in the first message - "Wake up knowing the next move" — the retention promise as a feeling, not a feature - "Live, on camera" — proof, not promises (kept from v1; it always worked)

The DM opener — idea-phase first-timer (field-signal audience)

"Got the idea but haven't shipped? Souped builds the business with you from the first decision — what to build, for whom, at what price — and then builds the thing itself: brand, code, billing, monitoring. You wake up every morning knowing the next move. From $10/mo, live in 90 minutes."

The outreach line — EIR / accelerator / business school (Kitchen X)

"Your cohort ships apps that aren't businesses — you watch them hit that wall every batch. Souped is the Startup Kitchen: each founder gets a co-builder that challenges their thinking and ships their production floor — brand, billing, monitoring, and a daily plan. Co-branded for your program. Want to see a founder go from app to business in 90 minutes?"

The conversation flow

"What do you mean?" / "How?"

"Builders like Bolt give you code that looks like a business. Slick on top — one push from collapse. And somewhere between 'it works' and revenue, you hit a wall. Not talent. Experience, tools, guidance. Nobody showed up.

The traditional fix is a team: ~$80K a month before they write a line.

Souped builds the business with you. The production floor is handled — brand, billing, monitoring, domain. And the part nobody else does: it works with you. It asks the questions you skipped, challenges your answers, and every morning tells you the next move. You stay the founder. It won't let you drift."

"What does it actually do?"

"Three things:

1. It makes you decide — who it's for, why they'd pay, what to cut. Under real constraints, before a line of code.
2. It builds and ships — brand, custom domain, billing, 12-detector monitoring. Looks like a funded team built it.
3. It stays — every morning you wake up knowing the next move. And it tests you: pitch your price to a simulated buyer built from your own answers, before a real one hears it."

"How much?"

"Starts at $10 a month. When you're earning revenue, it's $12 a month plus 1% of what you make — Stripe built in. You're probably paying $20–40 for the builder stack already and getting a fragile app back. The full comparison: a team like this costs about $80K a month."

"1%? Why the revenue share?"

"Because we only earn when you earn. The $80K team wanted salaries whether you made money or not. We'd rather be on your side of the table."

"What do I have to do?"

"Show up and answer honestly. It'll ask you real questions — who's this for, why would they pay — and it won't accept the lazy answer. Your answers become the business: the brand, the pricing, the pitch. You don't touch code. You make the calls."

"Sounds too good to be true."

"Fair. Don't trust us — watch us. Tuesdays 2PM ET we take a founder's app and make it a business, live on YouTube. No edits. If it breaks, you see it break. Or better: bring yours. Free, on camera, you keep everything."

"I'm not technical."

"Perfect. The entry requirement isn't code — it's taste. If you can say what your product should feel like and who it's for, Souped can build it. You'll be challenged on your thinking, not your syntax."

"I already tried Lovable / Base44 / another tool."

"Those are grocery stores — great ingredients, nobody cooks. You left with raw code and a recipe you couldn't read. Souped is the kitchen that comes after: we take what you built and make it a business. And unlike the builder, we don't disappear after the code works."

Cook show opening script (Episode 1)

Ismael, on camera, first 60 seconds:

"Most founders don't fail because they lack talent. They fail because nobody showed up.

They built the app. It works — kind of. But somewhere between 'it works' and revenue, they hit a wall. Not talent. Experience. Tools. Guidance. Nobody showed up.

[pause]

This is Souped. You shipped an app — Souped builds the business with you.

Today, [Guest] brought us their app. [Brief description]. [X] users. It works. It's not a business. Not yet.

In 90 minutes, we change that. Live. No edits. You watch every decision, every build, every moment — including the ones where [Guest] gets challenged on who this is actually for.

Built by operators, for founders who hit the wall between their spark and their shot.

Welcome to the world's first Startup Kitchen. Let's cook."

Cook show closing script

"[Before / after, side by side]

90 minutes ago this was a fragile app. Now it's a business — brand, monitoring running 24/7, billing, custom domain. And tomorrow morning, [Guest] wakes up knowing the next move.

[Guest], how does it feel?

[Guest reacts — this is the clip]

[to camera] Shipped something fragile? Bring it. Submit on Discord, or come watch next Tuesday, 2PM ET.

From crude to seasoned. Service!"

One-liner variants

Words to use / avoid

Follows the v6 master language rules (§1) — the working list:

Value Proposition Canvas — Souped v2

Date: 2026-07-23 (supersedes outputs/01-value-proposition-canvas.md, v1.0 of 2026-04-06) Framework: Strategyzer Value Proposition Canvas, extended with Maja Voje's 5-stage flow — ① ECP → ② Jobs → ③ Gains/Pains (Empathise/Define) → ④ Creators/Relievers + Selection (Ideate) → ⑤ Product/Service ideas (Prototype) → Next step: Verification What changed in v2: the experience-gap side added — v1 mapped only the infrastructure gap; v6 made co-creation the differentiator, so the canvas now carries both. Also: Kitchen 0/Plus/X pricing, Brain→Fond, The Counter, migration call reversed, v6 positioning anchor. Status: still pre-validation — the first-10-customers test has never run (forward plan step 5). Revise to v3 with real customer language after it does.

Profile scope: this canvas centers Mateo (Wave 1, shipped-and-stuck). The field-signal audiences map differently: the idea-phase first-timer enters through the experience-gap pains (P11–P14) before the infrastructure ones exist; the EIR buys relief for a whole cohort (Kitchen X) — that's a separate buyer canvas, not forced into this one.

Customer Profile (right side) — Mateo's world

Customer Jobs

Customer Pains

Customer Gains

Value Map (left side) — Souped's offering

Products & Services

Pain Relievers → Pain

Gain Creators → Gain

Fit Score

14/14 pains addressed, 14/14 gains enabled — 3 partial, all on unshipped mechanics (Stripe, boss fights). The experience-gap side is the differentiator and is mostly live already (games, daily plan, one voice) — the canvas finally says so.

Selection — the bets (Maja stage ④, Ideate)

Everything above is the full map. These are the selected relievers and creators — the few we lead with everywhere (hero, pitch, DMs). Selection criterion: highest-severity pain × strongest live relief × hardest for anyone else to copy.

Not selected (real but not lead-worthy): Stripe out of the box, custom domain, UAT previews, motion design — the floor. They appear as proof, never as the pitch.

Product / service ideas (Maja stage ⑤, Prototype)

What the selections imply we should build or finish — each traceable to a selected bet:

Next step: Verification

Per Maja's flow, this canvas is Prototype until verified. The verification vehicle already exists in the forward plan: step 1 (panel test — do P11/P12 rank as hair-on-fire for Mateo, EIR, and idea-phase personas?) and step 5 (the 20-founder co-creation play — do real founders' jobs/pains/gains match?). v3 of this canvas gets written in their language, not ours.

Positioning Anchor (strongest fit)

Positioning statement (v6):

You shipped an app. Souped builds the business with you. Wake up knowing the next move. The world's first Startup Kitchen. From crude to seasoned. Service!

Emotional core: from alone to accompanied. From drifting to knowing the next move. From fraud to visionary.

Bonus — Product as a Bridge (Maja's before/after exercise)

The product as the bridge from the painful now to the promised future. One bridge per persona:

Mateo (Wave 1 — the front door)

Idea-phase first-timer (field-signal audience)

EIR / accelerator (Kitchen X)

The one-line version (Mateo, for copy): Before: an app that could die any night, and no idea what tomorrow is for. After: a business that runs, watched around the clock — and every morning starts with the next move.

Watch list (updated)

• Migration path — REVERSED from v1. v1 said "not relevant, don't build escape hatches." Both readings aged badly: migration in is now the hook ("no rebuild — wraps the app you already shipped"), and migration out is canonical trust copy ("Your code is yours. Export anytime. No lock-in."). The open door is part of the pitch.
• Investor-ready analytics — Traction data (users, retention, revenue, uptime) in one screen remains a high-value Kitchen Plus surface and upgrade trigger. Still worth shipping.
• "Real company" in customer-voice research — Mateo says it; our copy never does (cold-test kill). Keep the distinction.

Next steps

• Validate: run this canvas against the first 5 co-creation founders (forward plan step 5). Do the experience-gap pains rank as high as we claim? P11/P12 severity is the key bet.
• v3 after validation, in real customer language.

Cold-Test Panel — Round 5 (v6 lines, pitch openers, three personas)

Date: 2026-07-23 Method: synthetic founder panels (same rig as rounds 1–4), adversarially calibrated. Three personas × three simulated panelists: Mateo (shipped-and-stuck), EIR/program director (Kitchen X buyer), idea-phase first-timer. Materials: v6 hero lines, sub-line candidate, CTA options, DM openers, pricing summary, bridge copy, co-creation pitch. Caveat: synthetic ≠ real. This round sharpens hypotheses; the 20-founder play (plan step 5) remains the real test.

Scoreboard

Survived (keep, promote)

Failed (change)

Verdicts

Cross-panel convergences (the round's biggest finding)

1. Artifact over claim — all three audiences independently demanded the same thing in different registers: Mateo wants a screenshot of a real morning brief; the EIR wants one boss-fight transcript + the week-8 cohort report; the idea-phase wants the first three questions free, on the page, pre-signup. The differentiated promise is 100% claimed and 0% shown, everywhere.
2. The category line doesn't belong in the 3-second zone. v6 promoted "Startup Kitchen" into the hero; two panels pushed it back out (0/3 + parsing failures). The original v5 placement rule (pills/PR/About) was correct.
3. The experience gap is confirmed as the lead pain — but only P11 self-reports. P11 carries copy; P12 gets demonstrated; P2 (silent breakage) is the anxious segment's detonator for bridge copy; P7 (dev team) is retired.

Open calls this round resolves (recommendations — Ismael confirms)

New decisions the round surfaced (open)

1. Two doors, one kitchen — keep the post-ship front door untouched (it's earning Mateo); add a visible side door: "Still carrying the idea? Start here." → page led by the heaviness bridge. Idea-phase currently converts at 0% purely because of the front door.
2. Free first three questions, pre-signup — invented independently by all three idea-phase panelists and answers Mateo's C2 condition + the subscription-guilt objection. Product work, not copy.
3. ⚠ Packaging problem (escalate to Pablo): the hero promises billing; Stripe is gated behind Kitchen Plus. Two of three Mateos flagged bait-and-switch unprompted. No copy fixes this.
4. 1% cap — decide and state it (skeptic: "at $50k MRR am I paying $500/mo for a status page?").
5. Kitchen X restructure — sell the report ("your batch at week 8: N live businesses, M with revenue events"); two-register vocabulary + defensibility kit (rubric, DPA, SSO, IP, AI-advice governance, vendor-continuity note); add per-founder tier (~$400–500, grant-language one-pager). Close UVEG first — pending = zero proof, signed = the entire proof stack.
6. Proof assets become plan step 0: morning-brief screenshot, one boss-fight transcript, a 30-second before/after clip. Cheapest, highest-leverage work in the whole plan.

Competitive Delta — July 2026 (vs. April baseline)

Date: 2026-07-23 · Method: ~25 live web searches + fetches. Refreshes the April corpus (outputs/02-*) with the v6 co-creation lens. Headline: billing fell as a differentiator; guidance got its first direct competitor; the production floor for non-technical founders and the challenge layer remain unowned — but the window narrowed.

1. Delta on the known set

2. New entrants in our category

Inconclusive/notable: no one brands "production layer for AI-built apps" as a bundle — the pain is served piecemeal (cleanup agencies, scanners); Product Hunt threads show founders still improvising post-launch stability. The pain is live and unowned.

3. The moat question — answered

Nobody combines building + production floor + founder guidance. But each edge now has an owner, and one edge fell:

• Billing = table stakes. Lovable, Replit, Bolt, Rocket all ship Stripe. Stop leading with it.
• Guidance has a direct competitor: CoFounder.AI's daily plan at $39/mo. It cannot touch the founder's real app — advice fused to execution is the counter.
• Founder-facing monitoring: unowned. Observability entrants target engineers. Our most defensible leg today.
• Nobody challenges the founder's decisions. No product pushes back on positioning/pricing/messaging; none runs constrained challenges tied to a real shipped product.

The moat = the combination + the challenge layer. The window narrowed materially since April — Lovable is one "app health" feature and one "growth advisor" agent away, with $500M ARR of distribution.

4. Pricing landscape

• Market entry anchor consolidated at $20–30/mo (Lovable/Bolt/Rocket $25, Replit ~$20–25, v0 $30, Base44 up 15–30% post-Wix). Our $10–18 now undercuts the entire field, not just Base44.
• Nobody uses %-of-revenue pricing — the 1% is still unique. Risk: Lovable/Replit advertise "we take no cut"; expect "0% fees" weaponized against us. Counter: 1% buys the floor + the cofounder, not checkout.
• Guidance-only products bracket us usefully: CoFounder.AI $39, GhostCoach $79 — Souped bundles guidance below the price of guidance alone.
• Usage-based drift (credits/tokens) is creating cost anxiety among vibe coders → flat predictable pricing is itself a wedge.

5. Strategic implications (ranked)

1. Stop leading with billing. Re-weight everything toward the two unowned claims: the 12-detector floor for non-technical founders + the decision-challenging cofounder.
2. Move fast on the co-creation narrative — CoFounder.AI is coining the category ("Software-as-a-Partner," press, $39/mo). Our line: their cofounder gives advice; ours operates your actual product. Consider positioning against them while they're 3,600 users small.
3. Lovable is the clock. The durable counter: be the layer on top of apps built anywhere (import-from-any-builder friction removal is strategic work, not polish), plus the challenge/game layer they have no DNA for. Keep the 1% alignment story loud — still one-of-a-kind.

Unresolved: Base44's exact current pricing (official page unreachable; sources conflict $16–25); whether Figma Make can publish standalone production apps outside Figma.