Funnel and CTA Teardown
Product Frame
The gstack/gbrain system is open-source product marketing, founder education, recruiting, and YC brand reinforcement in one surface. The CTAs are not random. They move from "try this tool" to "build this way" to "work at YC."
CTA Inventory
| Surface | CTA | Job |
|---|---|---|
| gstack README opening | "Fork it. Improve it. Make it yours." | Convert criticism or curiosity into hands-on adoption |
| Quick start | Install, run /office-hours, /plan-ceo-review, /review, /qa | Get first value in minutes |
| Team mode | commit gstack into a repo for teammates | Turn individual usage into team/process adoption |
| OpenClaw section | install gstack and route coding tasks through Claude Code sessions | Connect into multi-agent workflows |
| Native OpenClaw skills | install office-hours, ceo-review, investigate, retro via ClawHub | Let OpenClaw users sample the methodology without Claude Code |
| Other AI agents | setup supports Codex, OpenCode, Cursor, Factory, Slate, Kiro, Hermes, GBrain | Make gstack a portable workflow standard |
| License/footer | "Free, MIT licensed, open source. No premium tier, no waitlist." | Remove buyer friction and maximize distribution |
| Hiring block | "Come work at YC" with ycombinator.com/software | Convert inspired builders into candidates |
Funnel Stages
1. Belief Shift
Claim: one person with the right tooling can ship like a team.
Evidence used:
- Karpathy quote about not typing code.
- Peter Steinberger/OpenClaw example.
- Garry's own contribution/productivity claim.
- Screenshots of GitHub contribution acceleration.
User state: skeptical but curious.
Conversion target: accept that the workflow might be real enough to try.
2. Fast Trial
CTA: clone and run setup, then run /office-hours or /qa.
Why it works: the user does not need to understand the whole system. The fastest magical moment is a skill that pushes back on a product idea or tests a real URL.
User state: wants proof without commitment.
Conversion target: first meaningful agent output.
3. Workflow Adoption
CTA: team mode, repo bootstrap, auto-update, CLAUDE.md guidance.
Why it works: after individual value, the product asks for process adoption. This is where gstack becomes team infrastructure, not a personal prompt pack.
User state: "this helped me; how do I make it standard?"
Conversion target: repo-level install.
4. Ecosystem Expansion
CTA: use with OpenClaw, native ClawHub skills, other coding agents, GBrain.
Why it works: gstack positions itself as a workflow layer above model/client choice. That increases surface area and reduces lock-in objections.
User state: "I already use another agent."
Conversion target: methodology adoption, even if host differs.
5. Recruiting and YC Affinity
CTA: "Come work at YC" and the YC software page.
Why it works: the tool is the proof. A builder who wants to harden this way of working is already self-selecting for YC software's desired persona.
User state: "I want to work on this frontier."
Conversion target: YC software lead or applicant.
YC Layer
The YC software page asks interested builders to get in touch at software@ycombinator.com with a brief note about themselves and what they would want to build. The broader YC application page frames YC as full access to YC, $500k investment, San Francisco in-person batch, late applications considered, interviews, and ongoing alumni support.
Product implication: the OSS funnel has two exits:
- Builder/user exit: fork and use gstack/gbrain.
- Talent/founder exit: join YC software or apply to YC.
Messaging Strategy
The voice has four traits:
- Proof-heavy: concrete repos, numbers, commands, screenshots, benchmarks.
- Founder-coded: speed, shipping, taste, product judgment, leverage.
- Open-source generous: free, MIT, no waitlist, no premium tier.
- Recruiting-coded: if this excites you, come build it at YC.
What Ren/OpenClaw Should Learn
- Make the public artifact the proof, not a pitch deck.
- Put the install path close to the strongest belief-shift claim.
- Let users sample one high-value workflow before asking for system adoption.
- Expose methodology as native skills for adjacent agents.
- Tie contribution opportunities to a bigger story of how software work is changing.
Exact CTA Inventory, Deep Pass
| Surface | Exact CTA / Copy | Funnel Job |
|---|---|---|
| gstack opening proof | "How does one person ship like a team of twenty?" | Establish the category problem: individual leverage through agents. |
| Founder credibility | "I'm Garry Tan, President & CEO of Y Combinator..." | Borrow YC authority and personal builder credibility. |
| Proof claim | "In the last 60 days: 3 production services, 40+ shipped features..." | Turn the repo from prompt pack into proof-of-work. |
| Main OSS CTA | "Fork it. Improve it. Make it yours." | Convert curiosity or criticism into hands-on adoption. |
| Try-first CTA | "I'd rather you just try it first." | Lower ideological resistance; do not debate AI coding, run the workflow. |
| Audience CTA | "Founders and CEOs", "First-time Claude Code users", "Tech leads and staff engineers" | Segment the reader by job, not by tool preference. |
| Quick start | Install gstack, run /office-hours, /plan-ceo-review, /review, /qa, then "Stop there. You'll know if this is for you." | Force a short path to first value. |
| Install CTA | "Open Claude Code and paste this. Claude does the rest." | Make install feel agent-native, not developer toil. |
| Team adoption | "Team mode - auto-update for shared repos (recommended)" | Convert personal workflow into org standard. |
| OpenClaw CTA | "Paste this to your OpenClaw agent" | Make OpenClaw a distribution surface for gstack methodology. |
| Native OpenClaw CTA | clawhub install gstack-openclaw-office-hours... | Let users sample gstack without Claude Code. |
| Other agents | "gstack works on 10 AI coding agents, not just Claude" | Reframe gstack as workflow standard, not Claude dependency. |
| Host expansion | "Want to add support for another agent?" | Recruit contributors into adapter growth. |
| See it work | Daily briefing app transcript ending in shipped PR | Demonstrate end-to-end sprint, not a feature list. |
| Competitive redirect | "If you already use Karpathy-style CLAUDE.md rules, gstack is the workflow enforcement layer..." | Absorb adjacent practice into gstack. |
| Parallel sprint claim | "10-15 parallel sprints" | Sell the next-level operating model after one sprint works. |
| Reversibility | Full uninstall section | Reduce install fear; mature OSS posture. |
| Trust footer | "Free, MIT licensed, open source. No premium tier, no waitlist." | Remove buyer/sales friction. |
| Hiring CTA | "We're hiring. Want to ship real products at AI-coding speed and help harden gstack? Come work at YC" | Convert strongest-fit builders into candidates. |
| gbrain upgrade | "GBrain - persistent knowledge for your coding agent" and /setup-gbrain | Move user from process to continuity. |
| gbrain install | "Your AI agent is smart but forgetful. GBrain gives it a brain." | Name the memory pain sharply. |
| gbrain agent install | "Paste this into your agent" | Position install as delegated work. |
| gbrain eval CTA | BrainBench scorecards and sibling gbrain-evals repo | Route skeptics to proof. |
| YC software page | "Build the software that runs YC"; email software@ycombinator.com with a brief note about yourself and what you want to build | Talent capture for engineers attracted by the system. |
| YC apply page | submit the application online; apply as soon as ready | Founder capture for builders who want the broader YC path. |
Expanded Funnel
- Belief shift: "Same person. Different era. The difference is the tooling." Proof stack: Karpathy quote, OpenClaw example, Garry's YC/software background, contribution graphs, LOC caveats.
- First value: install, run
/office-hours,/plan-ceo-review,/review,/qa. The first experience is not generate-code; it is product judgment, review, and browser QA. - Workflow standardization: team mode, repo bootstrap, auto-update,
CLAUDE.md/AGENTS.mdintegration. - Agent ecosystem expansion: OpenClaw, Codex, Cursor, OpenCode, Factory, Slate, Kiro, Hermes, GBrain.
- Memory upgrade:
/setup-gbrain,/sync-gbrain, MCP registration. - Proof layer: gbrain-evals, LongMemEval, BrainBench, scorecards.
- YC capture: work at YC, apply to YC, contribute, or join the YC-aligned audience.
Message Architecture
The strongest pattern is a four-part stack:
- Status proof: "I am YC's CEO and I use this myself."
- Behavior proof: shipped products, shipped features, contribution graphs.
- Mechanism proof: commands, skills, browser tools, memory tools, evals.
- Invitation: fork it, install it, use it with your agent, work at YC.
This avoids a classic SaaS funnel. There is no pricing page, demo request, or waitlist. The conversion asset is the repo itself.
Funnel Risks
- The productivity claim invites scrutiny; the LOC caveat helps, but proof must stay credible.
- The CTA surface is dense; users can hit "too many commands" before the magical moment.
- The hiring CTA and OSS CTA are aligned now, but YC recruiting could make the project feel less neutral if overdone.
- gbrain setup has higher cognitive load than gstack; the memory upgrade needs a tighter first-win path.
- Benchmarks can backfire if they feel self-serving or mismatched to real workflows.