solo-founder-gtm
solo-founder-gtm helps solo founders and bootstrapped entrepreneurs design go-to-market strategies that scale without hiring. Use this skill when a founder needs to choose between self-serve and sales-led models, design AI agent workflows to handle repetitive GTM tasks, allocate their limited time effectively, or determine when to finally hire their first team member. It covers channel selection, tech stack optimization, and revenue-stage transitions specific to single-founder constraints.
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/solo-founder-gtm && cp -r /tmp/solo-founder-gtm/packages/skills-catalog/skills/(gtm)/solo-founder-gtm ~/.claude/skills/solo-founder-gtmSKILL.md
# Solo Founder GTM: The Complete Playbook for Scaling Without Hiring
You are an expert in solo founder go-to-market strategy, AI agent team design, lean operations, and founder-led distribution. You understand the 2025-2026 landscape where over one-third of new startups are solo-founded and a single person with the right stack can reach $100K+ MRR faster than a 20-person team could five years ago. You help founders choose between self-serve and sales-led motions, design AI agent workflows that replace traditional hires, allocate their most constrained resource (time), and know exactly when scaling without people stops working.
## Before Starting
Gather this context before building any solo founder GTM plan:
- What does the product do today? One paragraph, shipped features only, no roadmap.
- What is the current revenue? MRR, number of paying customers, and trend (growing, flat, declining).
- How are customers finding the product today? Organic, paid, outbound, referral, community, or a mix.
- What is the current tech stack? List every tool the founder pays for and every free tool in active use.
- How many hours per week does the founder spend on GTM vs building? Get the real split, not the aspirational one.
- What is the ACV (annual contract value) or average revenue per customer?
- Is the product self-serve today, or does every sale require a call?
- Does the founder have an existing audience? X followers, LinkedIn connections, newsletter subscribers, community members.
- What has the founder tried for GTM that did not work? Failed channels are as informative as successful ones.
- What is the founder's biggest constraint right now? Time, money, technical skill, distribution, or something else.
---
## 1. Taste as Moat: Why Judgment Beats Headcount
AI handles execution at scale. Writing 100 cold emails, researching 500 prospects, generating 50 ad variations. All of that is commodity work now. The moat for a solo founder is judgment: knowing which market to enter, which messaging resonates, which customers to prioritize, and which signals to act on.
```
DELEGATE TO AI AGENTS OWN PERSONALLY
+----------------------------+ +----------------------------+
| Research and data gathering| | Strategic decisions |
| First-draft writing | | Customer conversations |
| Lead scoring and routing | | Pricing and packaging |
| Email personalization | | Product direction |
| Social media scheduling | | Partner relationships |
| Competitive monitoring | | Brand voice and values |
| Analytics and reporting | | Which market to enter next |
| Data enrichment | | When to say no |
| Basic customer support | | High-stakes sales calls |
+----------------------------+ +----------------------------+
```
The rule: if a task requires taste, market context, or relationship capital, you do it. If a task requires throughput, pattern matching, or repetitive execution, an AI agent does it.
---
## 2. The One-Person Startup Stack
| Function | Recommended Tool | Monthly Cost | Why This One |
|---|---|---|---|
| CRM | Attio or Folk | $0-30 | Lightweight, API-friendly, no enterprise bloat |
| Email outreach | Instantly or Smartlead | $30-97 | Multi-inbox rotation, warmup included |
| Enrichment | Clay (Starter) or Apollo Free | $0-149 | Clay for waterfall enrichment, Apollo for basic lookups |
| AI personalization | Claude API or GPT API | $20-50 | Per-message personalization at scale |
| Landing pages | Framer or Carrd | $0-24 | Ship in hours, not weeks |
| Analytics | PostHog or Plausible | $0 | PostHog for product analytics, Plausible for web |
| Scheduling | Cal.com or Calendly Free | $0 | Cal.com is open-source and self-hostable |
| Payments | Stripe | 2.9% + $0.30/txn | Standard, reliable, great API |
| Support | Crisp Free or Intercom Starter | $0-39 | Crisp for chat widget, Intercom if you need AI bot |
| Automation | n8n (self-hosted) or Make | $0-30 | n8n for full control, Make for visual workflows |
| AI coding | Cursor or Claude Code | $20-40 | Ship features without a dev team |
| Content | Claude or Notion AI | $0-20 | Long-form drafts, repurposing, research |
| Social scheduling | Buffer or Typefully | $0-15 | Typefully for X-native scheduling |
| Email marketing | Loops or Resend | $0-25 | Developer-friendly transactional + marketing |
| **Total** | | **$50-450/mo** | |
### Stack Selection by GTM Motion
```
Product-Led (self-serve) --> Analytics (PostHog), Landing page (Framer),
Email marketing (Loops), Support (Crisp)
Outbound-Led (sales calls) --> Enrichment (Clay), Outreach (Instantly),
CRM (Attio), Scheduling (Cal.com)
Content-Led (audience-first) --> Content AI (Claude), Social (Typefully),
Email marketing (Loops), Analytics (Plausible)
Community-Led --> Community platform (Discord/Circle),
Content AI (Claude), Email (Loops), CRM (Folk)
```
### Stack Anti-Patterns
| Anti-Pattern | Why It Hurts | What to Do Instead |
|---|---|---|
| Salesforce or HubSpot Enterprise | $150+/mo, 80% features unused, weeks to configure | Attio or Folk at $0-30/mo |
| Building internal tools pre-PMF | Engineering time that should go to the product | Off-the-shelf tools until $50K+ MRR |
| Buying annual contracts early | Locks in spend before you know what works | Stay monthly until a tool proves critical |
| Using 15+ tools at once | Context-switching tax exceeds the tool's value | Cap at 8-10 core tools |
---
## 3. Revenue Stage Playbook
GTM strategy shifts at every revenue milestone. What works at $0 MRR actively hurts at $50K MRR.
### Stage 1: $0-1K MRR (Validation)
**Goal**: Find 10 people who will pay. Nothing else matters.
**Time split**: 40% customer conversations, 40% building, 20% content.
- DM 20 people per day on X or LinkedIn who matFinds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis).
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or analyzing why namespaces have misplaced code. Do NOT use for dependency analysis (use coupling-analysis) or domain grouping (use domain-identification-grouping).
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices strategy", or tracking decomposition progress. Do NOT use for domain analysis (use domain-analysis) or component sizing (use component-identification-sizing).
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).
AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity. Use when the user asks to build, design, create, or improve any frontend interface — websites, landing pages, dashboards, components, apps, emails, forms, modals, or any UI element. Also triggers on "build me a UI", "design a page", "create a component", "improve this layout", "make this look better", "frontend", "interface", "redesign", or when the user provides mockups, screenshots, or design references. Do NOT use for backend logic, API design, database schemas, or non-visual code tasks.