FORGE BUILDS DEFINITIVE GTM PLAN 2026-04-03

Forge Builds — Complete GTM Plan

Every stage from first impression to community member. Every message. Every mechanic. Every extraction layer.

Payment Structure

20%
DEPOSIT
Holds spot. Jason starts building. Refundable if not selected.
50%
DELIVERY
Forge is running. Health green. Day-one items work. Puppy is alive.
30%
ONE WEEK CHECK-IN
Client has lived with it. Satisfaction confirmed. Relationship strongest.

Round 1 Timeline

Now
Content + Source
Derek sourcing, Jason posting
Apr 7-10
Qualify + Deposit
Derek vets, deposits collected
Apr 10-14
Finalist Calls
Jason talks to top 3-5
Apr 15
Build #1 Starts
Factory runs, Jason supervises
May ~5
Handoff
Puppy delivered
May ~12
Check-in + Final 30%
Satisfaction, payment, community

The Full Arc — 11 Stages

0
ATTRACT
Before they know we exist

What Happens

Content goes out on Jason's channels. No selling. Just showing what Forge does. Curiosity is the only call to action.

Channels

Content Pieces (Fixed Templates)

PostHookGoal
"What My AI Did Last Night"Real screenshots of morning brief, completed tasks, content published while sleepingProof. No explanation of how — just results.
"The Puppy Theory"AI agents are like puppies — useful day one, real value comes from trainingReframe expectations. Set up the metaphor before we sell.
"Why I Don't Use [Popular Tool]"Forge vs OpenClaw, ChatGPT. Not attacking — explaining chatbot vs OSCategory creation. "This is different."
"I'm Building 3 More"The announcement. Short. Direct. Link.Open the funnel. Let DMs and comments do the work.
"The Venture Studio Thesis"Why building businesses WITH AI agents, not just tools FOR humansAttract cascade thinkers. Filter out feature shoppers.

Timing

Round 1: Derek sources from warm network in parallel. Content builds background demand for Round 2.

Round 2+: Content is the primary top-of-funnel. 2-3 weeks of content before applications open.

Two lanes (A/B test): Derek runs the consultative outreach lane. Jason runs the self-selection/anti-sell lane on jasondmacdonald.com. Both feed the same funnel. We learn which converts better.
1
LAND
They hit the page

What They See

A sales/boarding page (vibe-coded app). Not a traditional landing page — it's an experience that filters and impresses simultaneously.

Page Sections (All Fixed Template)

  1. The Line: "I built an AI that runs my business while I sleep. I'm building 3 more. If you want one, tell me why."
  2. What a Forge IS: Not a chatbot. An operating system. Proactive. Autonomous. Gets smarter over time. (Video of real Forge in action preferred.)
  3. The Puppy Metaphor: What you get, what you grow. Day one vs month three.
  4. What's Included / Not Included: The MVP table from Product Scope.
  5. Your Costs: $220-240/mo ongoing (Claude Max + VPS + domain). Transparent.
  6. Selection Criteria: What gets you picked. What gets you redirected. Published so they self-filter.
  7. The Bigger Game: Venture studio vision. Board model. "This isn't transactional — it's relational."
  8. FAQ: "Is this OpenClaw?" / "Do I need to code?" / "What about support?" / "What if I'm not satisfied?"
  9. CTA: "Start Your Application" → enters the boarding flow.
No pricing on this page. Price is discussed after qualification. The page sells the concept, not the number. "Investment details are covered during the alignment call."
2
BOARD
AI-driven intake questionnaire

What Happens

Not a static form. A guided, conversational questionnaire that adapts based on answers. The AI probes for depth. This is the first extraction layer.

The Boarding Flow

Step 1 — Who Are You? (Identity + Context)
Name, business, role, website "Describe your business in 2 sentences" AI follow-up: "What's the one thing that takes most of your time that shouldn't?"

→ Auto-tags: industry, company size, pain category

Step 2 — What Do You Want? (Use Cases)
"Describe your ideal Monday morning if an AI agent handled everything it could" "What 3 tasks would you hand off first?" AI follow-up: probes specificity — "When you say 'handle my email,' do you mean draft? Triage? Auto-respond to certain types?"

→ Auto-tags: use cases, complexity tier (simple/moderate/complex)

Step 3 — Second-Order Effects (The Cascade Filter)
"If your Forge worked perfectly for 6 months, what changes in your business?" "What becomes possible that isn't possible today?"

→ AI scores cascade thinking: shallow / moderate / deep. This is THE filter. People who can't answer this are self-selecting toward a different silo.

Step 4 — Workflow Mapping (Layer 1 Extraction)
"Walk me through your typical Tuesday, hour by hour" "What tools do you open first thing in the morning?" "Where do you lose time between tasks?"

→ Produces workflow graph: tools, transitions, bottlenecks, automation candidates

Step 5 — Communication Topology (Layer 3 Extraction)
"Who do you communicate with daily? How? (Slack, email, text, calls)" "Which communications could be templated? Which need your voice?"

→ Configures Commander channels, draft-vs-auto rules, notification priority

Step 6 — Rhythm + Preferences (Layer 5 Extraction)
"When do you start work? When do you stop?" "Morning person or night owl?" "How do you want to be nudged — aggressive or gentle?"

→ Configures daily rituals, quiet hours, notification tone. Puppy matches owner.

Step 7 — The Network Question (Adjacency + Viral)
"What other ventures or projects are you involved in?" "Is there anyone in your network who should know about this?"

→ Jason's adjacency filter. Also: soft referral prompt = viral seed.

Step 8 — Timeline, Budget, Deposit
"When do you need this running?" "What budget range are you working with?" "Attach a refundable deposit to secure your spot" [Deposit link — 20%]

→ Hard data. Deposit = strongest signal of seriousness.

What's fixed: Question structure, AI follow-up logic, scoring rubric, auto-tags.
What's customized by AI: Follow-up questions adapt to answers. A coach gets different probes than a SaaS founder.

Where This Data Goes

3
TRIAGE
Route to the right silo — no dead ends

The Principle

Nobody gets rejected. Everyone gets routed. The boarding app is a triage engine, not a filter. Every person who enters the funnel lands somewhere useful.

SignalRouteWhat They Get
High signal (finalist)Alignment call pipelineFull Forge Builds experience. Pre-call page published for them.
Medium signalWaitlist + Forge University"You're close. Join the community, learn the thinking, reapply next round."
Low signal, has budgetIntelligence Brief ($497)"A Forge might be premature. Start here — we'll map what's agentifiable."
Low signal, low budgetFree content funnel"Here's how to start: Forge U public content, Lobster U model."
Wrong product, right personAthio / MasteryOS / Labs"What you described sounds like [X]. Here's where it lives."

Messaging by Route

High Signal → Finalist
To: Applicant | Trigger: Auto after scoring | When: Within 24h of application
"[Name] — your application stood out. We've published a preliminary page for you at [link] based on what you shared. Jason will review this week and reach out to schedule a 30-minute alignment call. In the meantime, you can add notes directly on your page."
Medium Signal → Waitlist
To: Applicant | Trigger: Auto after scoring | When: Within 24h
"[Name] — thanks for applying. You're in the pool for Round [N]. We had strong applications and can only take a few calls this round. You're automatically in for Round [N+1] unless you opt out. Meanwhile, join Forge University where we share the thinking behind how these systems work: [link]. The deeper you go, the stronger your next application."
Low Signal + Budget → Intelligence Brief
To: Applicant | Trigger: Auto after scoring | When: Within 24h
"[Name] — based on what you described, a full Forge build might be ahead of where you are right now. That's not a bad thing — it means there's groundwork to lay first. Our Intelligence Brief ($497) maps your business through an AI lens and shows you what's agentifiable. It's often the best first step before a Forge: [link]. If the brief reveals a strong Forge case, you'll jump to the front of the next round."
Wrong Product → Ecosystem Redirect
To: Applicant | Trigger: Manual or AI-detected | When: Within 48h
"[Name] — what you described sounds like it fits better in our [MasteryOS / Athio / Labs] ecosystem than a Forge build. Here's where that lives: [link]. If you explore that and still want a Forge, you're welcome to reapply with that context."
Every route leads somewhere. Waitlist → Forge U → reapply. Brief → map → Forge-ready. Free content → educate → apply later. Wrong silo → redirect → still in our world. Zero dead ends.
4
DEPOSIT
20% to hold spot — before anything else

When

After triage routes them as a finalist (or they can attach deposit during boarding to jump the queue). Nothing happens without deposit. No calls, no pages, no build.

Mechanics

Deposit Confirmation
To: Applicant | Trigger: Payment received | When: Immediate
"[Name] — deposit received. Your spot is held for Forge Build Round [N]. We're publishing your preliminary page now at [link]. Jason will reach out within [X days] to schedule your alignment call. You can add notes and context to your page anytime — the more we know going in, the better the call."
5
PRE-CALL PAGE
Published for them before Jason says a word

What Gets Published

A NowPage at jasondmacdonald.com/forge/[their-name] — Pulse-enabled, built from their application data.

Page Sections

SectionSourceEditable?
About [Name]AI summary from boarding Steps 1-2Client can add notes via Pulse
What Your Forge Could DoAI-mapped from their use cases + workflowClient can react / correct
Your Workflow MapFrom boarding Step 4 (tools, transitions, bottlenecks)Client can annotate
Communication ChannelsFrom boarding Step 5Client can add channels
Your RhythmFrom boarding Step 6Client can adjust
Alignment Brief (empty)Template — filled live on callFilled by Jason on call
What Happens NextFixed template — process explanationNo
Why this matters: The client opens this page and sees their business reflected back with AI precision — before Jason has said a word. It impresses. It demonstrates capability. It starts the extraction before the call. And they'll share it: "Look what they built for me just from an application."

Viral Mechanics

6
ALIGNMENT CALL
Jason's first real conversation — 30-45 min

Jason's Prep (Auto-Generated)

On the Call — Two Jobs

Job 1: Validate Fit (Jason's exit ramp)

Job 2: Deep Extraction (Layers 2, 4, 6 — the ones AI can't get from a form)

Layer 2 — Decision Patterns
"What decisions do you make daily that follow a pattern?" "What decisions require your gut — no rules could capture them?"

→ Maps off-rails vs on-rails boundary. Determines what Ralph handles vs what needs human gates.

Layer 4 — Knowledge Audit
"What documents define how your business runs?" "What's in your head that's nowhere written down?"

→ Seeds KFS knowledge graph. More context on day one = smarter Forge.

Layer 6 — Success Metrics
"How will you know in 30 days this was worth it?" "What number changes if this works?"

→ Measurable satisfaction criteria beyond the 5-7 brief items. Feeds the check-in conversation.

Building the Brief Live

Jason fills the Alignment Brief section on their pre-call page in real time using Pulse. Client watches and reacts. By end of call:

What They Name It

On the call: "What do you want to name your Forge?" Personal. Makes it theirs from minute one.

Post-Call (Winner)
To: Selected finalist | Trigger: Jason decides | When: Within 24h of call
"[Name] — you're in. Your alignment brief is live at [page link]. The 5 items we agreed on are your day-one deliverables. To lock in your build slot starting [date], here's the payment link for 50%: [link]. Your 20% deposit applies. And here's your setup checklist — complete this before [date] so we can hit the ground running: [HC walkthrough link]."
Post-Call (Not Selected, Had Call)
To: Non-selected finalist | Trigger: Jason decides | When: Within 24h
"[Name] — great call. Your page and brief are yours to keep and share. This round's builds were a closer match to the problems we're solving right now, but you're first in line for Round [N+1]. Your deposit will be refunded within [X days]. Meanwhile, you're welcome in the Forge community: [link]."
7
PAYMENT — 50%
Build commitment — Forge starts

Trigger

Client selected, brief approved. 50% payment due before build starts.

Payment Math

Build Fee20% Deposit (Paid)50% Due Now30% at Check-in
$15,000 example$3,000 ✓$7,500$4,500
$20,000 example$4,000 ✓$10,000$6,000

Deadline

48-72 hours to pay. After that, slot offered to next finalist. No chasing.

8
PRE-BUILD SETUP
Client homework — accounts + keys

Published HC Walkthrough

A step-by-step setup page at jasondmacdonald.com/forge/[name]/setup. Paint-by-numbers. Every step has screenshots.

#TaskCostTime
1Create Hetzner account → provision CAX21 VPS~$10-20/mo15 min
2Create Supabase account → create project → copy keysFree tier10 min
3Create Telegram bot via @BotFatherFree5 min
4Subscribe to Claude Max ($200/mo)$200/mo5 min
5Register domain for dashboard~$10/yr10 min
6Save all keys/tokens to secure form5 min

Total client time: ~50 minutes. Total ongoing cost: ~$220-240/mo.

Setup Reminder
To: Client | Trigger: 3 days before build start | When: Automated
"[Name] — your Forge build starts [date]. Make sure your setup checklist is complete: [link]. If you get stuck, reply here — or ask your soon-to-be Forge for help (it already knows how)."
9
BUILD
The factory runs — 3-4 weeks

Process Factory Pipeline (forge-factory.json)

PhaseBlocksWhoTime
ConfigureGenerate CLAUDE.md, skills, rituals from extraction dataAgentic (Ralph)1-2 days
Human GateJason reviews generated configJason30 min
DeployVPS provisioning, service install, migrations, health checksAgentic (factory script)1-2 hours
Human GateJason verifies deployment, all services greenJason15 min
CustomizeWrite custom skills, configure dashboard, set up integrationsAgentic (Ralph) + Jason3-5 days
Human GateJason + client review on Pulse-enabled pageBoth30 min
TestSimulate daily rituals, execute test tasks, verify CommanderAgentic1 day
GenerateCreate HC walkthrough page, prep handoff materialsAgentic2 hours

Jason's total time during build: ~2-3 hours (human gates + custom skill review). The factory handles the rest.

Client Visibility During Build

Their page at jasondmacdonald.com/forge/[name] updates as phases complete. They see progress. They can add notes via Pulse.

Messaging During Build

Week 1
"Your Forge '[name]' is being configured. We've generated your CLAUDE.md and 4 custom skills based on your workflow. Preview on your page: [link]."
Week 2
"[Name] is deployed and running. Health checks: all green. Your Commander bot is active — say hi: [Telegram link]. Next: custom integrations."
Week 3
"Custom skills installed. Here's what [name] can do on day one: [list]. We're scheduling your handoff session: [calendar link]."
Build teasers = marketing. With client permission, each progress update becomes content for the next round. "Here's what I'm building this week for Forge Build #1."
10
HANDOFF + 50% PAYMENT
The puppy moment — 1-2 hours

Handoff Session Agenda (Fixed Template)

  1. Tour: Walk through Commander bot, dashboard, Ralph queue live
  2. Talk to it: Show them how to give their Forge instructions
  3. Self-teaching: Demonstrate the Forge helping them extend it ("Ask your Forge how to add a new skill")
  4. Homework: "Your first task: ask [name] to write you a skill for [something from their workflow]"
  5. Brief verification: Walk through 5-7 items. Client marks each "done" on Pulse.
  6. What's next: One-week check-in scheduled. After that, you and [name] are a team.

50% Payment Trigger

All 5-7 brief items verified working. Client has seen the Forge in action. 50% invoice sent at end of handoff or within 24 hours.

Post-Handoff
To: Client | Trigger: After handoff session | When: Same day
"[Name]'s Forge is live. Your walkthrough page: [link]. Remember your homework — ask [name] to write you a new skill before our check-in on [date]. One week from now, you'll be surprised what you and [name] have figured out together."
11
ONE WEEK CHECK-IN + FINAL 30%
30 min — last scheduled touchpoint

Check-in Agenda

Final 30% Payment

After check-in, final invoice. This is the natural moment — client has lived with the Forge, relationship is strongest, referral energy is highest.

Post Check-in
To: Client | Trigger: After check-in | When: Same day
"You and [name] are officially on your own. Welcome to the Forge Owners community: [link]. Your Forge knows how to help you grow from here — just ask it. And if you know someone who should have their own, we're opening Round [N+1] soon: [referral link]."
COMMUNITY
Ongoing — zero Jason time

What They Join

Forge U Topics (Fixed Content)

Automated Messaging

Weekly — Forge U
"This week in Forge U: [topic]. [HC page link]"
Monthly — Next Round
"Forge Builds Round [N] applications open [date]. Know someone? [referral link]"
As-Needed — Updates
"New Forge capability shipped: [feature]. Ask your Forge to pull the latest."

Complete Template vs Custom Map

StageFixed TemplateCustomized
0. AttractContent calendar, page designNothing
1. LandSales page, FAQ, criteriaNothing
2. BoardQuestion flow, AI logic, scoringAI adapts follow-ups to answers
3. TriageRubric, routing rules, all messagingPersonalized redirect reasons
4. DepositPayment flow, Stripe, messagingAmount (bid or proposal)
5. Pre-Call PagePage template, section structureEverything — their data, their map
6. Alignment CallPrep doc, extraction framework, brief templateEverything discussed + extracted
7. Payment 50%Invoice, deadline, messagingAmount
8. Pre-Build SetupHC walkthrough (paint-by-numbers)Forge name, domain
9. BuildFactory template, block types, gatesCLAUDE.md, skills, rituals, dashboard
10. HandoffAgenda, homework, brief verificationDemo is their Forge, their workflows
11. Check-inAgenda, success metric checkTheir specific issues + metrics
∞. CommunityForge U content, messaging cadenceNothing

Jason's Time Per Build

ActivityHours
Review applications (dashboard, not calls)0.5
Alignment call0.75
Human gates during build (3 gates × 20 min)1.0
Handoff session1.5
One-week check-in0.5
Total~4-5 hours
At $20K per build and 5 hours of Jason's time, the effective rate is $4,000/hr. At $15K it's $3,000/hr. This works because the factory does the building. Jason does the thinking.

Cascade

Build #1 (April 15) → Proves the factory pipeline works → Content from build feeds Round 2 marketing → Round 2 has inbound (not just Derek outreach) → Client joins Forge Owners community → Peer support reduces Jason's post-delivery time to zero → Community content feeds Forge U → Build process reveals what's universal vs bespoke → Universal parts become productized template → Aaron can run Round 3+ with minimal Jason If 10+ deposits after Round 1 → Aaron productizes delivery → Jason curates problems, doesn't build → Effective rate goes up, hours go down If 2+ builds reveal venture-worthy businesses → Venture studio model activates → Board seats, equity, rev-share → Portfolio of agent-run startups → Forge Builds was the proving ground all along
]]>