A solo operator moves between prospecting, selling, content, and reporting in the same afternoon. The cost is often the restart: finding the notes, remembering the last decision, and rebuilding the brief before useful work begins. Pick one repeated handoff and make it dependable.
This page collects plays across the funnel because you own work across the funnel. Begin with a task you understand well enough to review, using the tools you already have. The goal is one useful result you can produce again next week, with enough context saved that you do not have to reconstruct the process.
One prospect, one conversation, one clear next step
Understand the account
Use the company URL and your target-customer definition. Verify the brief and choose a reason to contact the person.
Open the account-brief prompt →Draft a specific message
Connect the account evidence to the problem you solve. Review the claim and the ask before sending it yourself.
Open the cold-email prompt →Follow through on the conversation
Turn checked meeting notes into agreed actions and open questions. Keep the next step explicit for both you and the prospect.
Open the follow-up prompt →
Start with the job that keeps slipping
List the tasks you postpone even though the inputs are available: account research, follow-ups, repurposing a useful explanation, or checking a campaign file. Choose one whose finished output you can describe. A specific definition of done is more useful than a plan to automate sales.
Borrow the workflow for the seat you are covering. Use the SDR material for research and outreach, the AE material for discovery and follow-up, and the marketing material for content. Keep the inputs and review criteria with the chosen play so you can return to it after a week spent elsewhere.
Use the tool setup that fits the actual job. A prompt may be enough for a draft. A repeatable file operation or connected workflow needs its own instructions, dependencies, and checks. The Claude, ChatGPT, and Codex guides explain those tools separately; each playbook names what its implementation requires.
Make the workflow easy to pause and resume
Save the source brief, the instruction, and one reviewed example together. Write down what must be checked every time, especially facts, customer commitments, and destinations for an output. Future you should be able to tell what the workflow does without rereading a long conversation.
Keep publication, sending, and changes to live systems visible. A small team has fewer people to notice an incorrect campaign or a broken data job. Start with drafts and proposed actions, and follow the approval steps in the selected playbook when you connect more tools.
Review the maintenance cost as well as the time saved. A workflow that needs constant repair may be a poor trade for a task you do twice a month. Expand the dependable pieces and remove the ones you no longer use.
Use cases for Founder / Solo GTM
Complete workflows with their implementation tools listed below. Follow each playbook's setup and review steps.
Account Research: Turn Any Company URL Into a First-Call Brief
Run the account research for a first call from a single company URL: a structured, cited, talking-point-ready brief before every first call, in minutes instead of an hour.
Tools: Claude web search, Claude, HubSpot / SheetsCold Email Personalization at Scale, From Real Research
Cold email personalization at volume: research each prospect automatically and generate one genuinely personalized email per person, then send at scale without sounding like a mail merge.
Tools: Clay, Apollo.io, Claude, SmartleadGenerate LinkedIn Ad Angles, Hooks, and Creative Concepts
Turn your positioning and real customer language into a slate of genuinely distinct LinkedIn ad angles, hooks, and creative concepts ready to test.
Tools: Claude, Claude web search, Google SheetsVideo Prospecting at Scale Without Capping at 20 a Day
Scale video prospecting past the 20-a-day ceiling: record one base video and have AI personalize the opening and on-screen details per prospect, so each recipient gets a video that feels made for them.
Tools: Sendspark, HeyGen, Clay, SmartleadTurn Discovery Into a Business Case and Mutual Action Plan Template
Turn raw discovery notes into a tailored business case and a mutual action plan template your champion can use to sell internally without you in the room.
Tools: Claude, Gong, Fathom, Google DriveSecurity Questionnaire Template and AI First-Draft Answers
Start from a security questionnaire template, then use AI over your own approved documents to first-draft the answers, turning a multi-day deal-blocking slog into a few hours of focused human review.
Tools: Claude, Google Drive, Google SheetsWeekly Competitor Intel Digest, Run by a Claude Routine
You know the competitive-intel chore: someone is supposed to track what competitors shipped this week, and that someone is slammed. This hands the whole job to a Claude Routine that researches with web search, keeps only the moves that change a deal, and drops a cited digest in Slack every week. Nobody owns the chore, and there is no glue to keep alive.
Tools: Claude web search, Claude Routines, Slack (via MCP)Turn One Webinar Into 15+ Content Assets
Turn a single webinar transcript into 15+ ready-to-edit assets: a blog post, social posts, emails, clip scripts, and a FAQ, from one reviewed outline.
Tools: Fathom, Claude, Google DriveAutomate Google Ads Management with AI
Most Google Ads accounts run on a human exporting a report, then clicking. Wire yours to a Claude agent instead: it reads the account through the Google Ads API, writes its own weekly diagnosis, mines the search-terms report for wasted spend, and executes only the changes you approve by ticking a checkbox, negatives, bids, budgets, and pauses, the same week, not next month.
Tools: Google Ads API (GAQL), Google Analytics 4, Claude Code, Claude Code Routines, Google Ads (mutate API)Automate LinkedIn Ads Management with AI
Most LinkedIn ad accounts run on a human reading a dashboard, then clicking. Wire yours to a Claude agent on a weekly routine instead: every Monday it ranks the changes worth making, and executes the ones you approve, bids, budgets, pauses, launches, and audience edits, the same day you approve them, not days later.
Tools: LinkedIn Marketing API, Claude Code, Claude Code Routines, LinkedIn Campaign ManagerRun Your GTM Automations as Claude Agents with MCP
Most GTM automations are a pile of Zapier zaps and n8n flows nobody maintains. Move the logic onto one Claude agent with MCP connectors to your stack: it reads the context, reasons, decides, and writes, all in a brief you can actually read.
Tools: Trigger (webhook or schedule), Claude Code + MCP, HubSpot / Slack / DrivePut Recurring GTM Work on Autopilot with Claude Routines
Every GTM team has a list of recurring chores that quietly slip: the Monday pipeline-risk read, the competitor check, the CRM-hygiene sweep. A Claude Routine runs each one on a schedule as a cloud agent, so the work shows up whether or not anyone remembered it.
Tools: Claude web search / MCP, Claude Routines, Slack / your CRMTurn Your Best GTM Plays into Claude Skills the Whole Team Runs
Your best account brief, battlecard, and follow-up live in one person's head and one clever prompt nobody else can reproduce. Package them as Claude Skills: the play, the format, and the guardrails, versioned and shared, so every rep runs it at the same quality.
Tools: Your best prompts + docs, Claude Skills, Every rep's ClaudePipeline Review on Autopilot: A Monday Digest from a Claude Routine
The Monday pipeline review is the most expensive meeting in sales, and most of it is spent establishing facts that were sitting in the CRM the whole time. This play hands the facts to a Claude Routine: every Monday at 7am it reads the pipeline over MCP, works out what moved, what went stale, what has no next step, and where coverage sits against quota, and posts a written digest to Slack. The meeting starts at the decisions.
Tools: HubSpot or Salesforce (via MCP), Claude Routines, Claude Code (optional), Slack (via MCP)CRM Data Cleanup on a Schedule: A Claude Agent That Proposes, You Approve
CRM data cleanup is the job every RevOps team owns and nobody schedules, so it happens as a panicked spreadsheet purge the week before the board deck. This play makes it a weekly run: a Claude agent reads the CRM over MCP, finds duplicates, non-standard values, empty fields, orphan records, and dead deals, proposes every fix as a line in a change list with the evidence beside it, and writes only the lines you tick. The database gets cleaner every week, and nothing merges without a human looking at it.
Tools: HubSpot or Salesforce (via MCP), Claude Code, FullEnrich or Clay, Slack (via MCP)AI RFP Response with Provenance: A Claude Answer Library That Cites Its Sources
An RFP lands with 180 questions and a deadline in nine days, and the first thing an AE does is open the last RFP and start copying. Half those answers were written for a different buyer, a few are a year stale, and nobody remembers which. This play puts Claude over your approved sources instead: it drafts every answer from the security docs, the product docs, and the answer library, tags each with the source it came from and when that source was last verified, flags anything it could not source as 'needs a human', and exports in the buyer's numbering. The AE spends the nine days on the twenty answers that need a person.
Tools: Notion or Google Drive (via MCP), The buyer's RFP file, Claude Projects, Claude Code, The answer librarySales Forecasting with AI: A Weekly Claude Agent That Builds the Bottoms-Up Forecast Brief
The Monday forecast call spends its first forty minutes reconciling: the CRM says one number, the rep's spreadsheet says another, the manager's gut says a third. This play hands the reconciliation to a Claude agent. Every Monday at 6am it reads every open deal in the quarter, checks each committed deal against a written evidence checklist (a dated next step, a named champion, a paper process that has started, activity in the last ten days), flags deals whose stage disagrees with their evidence, rolls it up by rep against quota and against last week, and writes the forecast call brief. The call starts at the deals worth arguing about. The number stays the human's.
Tools: HubSpot or Salesforce (via MCP), Gong (via MCP), Quota + snapshot files, Claude Code, Slack (via MCP)How I’d take a cold email draft through QA to a Smartlead import
A finished email draft still needs evidence review, suppression checks and a reliable handoff. I built a small offline workflow for that last mile, with a fictional batch you can reproduce before using your own prospects.
Tools: Python, SmartleadSkills for Founder / Solo GTM
Reusable procedures for the tool or runtime named on each card. Check the setup before adding one to your workflow.
LinkedIn Ads Optimization Skill for Claude
Reads a LinkedIn ad account by layer and format, flags what moved week over week, and returns a ranked, evidence-backed list of changes to approve. It classifies before it counts and proposes, never executes.
Google Ads Optimization Skill for Claude
Reads a Google Ads account through the API, writes a dated diagnosis, mines the search-terms report for negatives, and returns a ranked, evidence-backed list of typed changes to approve. It categorizes before it counts and proposes, never executes.
ICP Framework Builder: Turn Your Wins and Losses Into a Scoring Rubric
Feeds Claude what you sell plus a dozen recent won and lost deals and gets back an ICP framework a new hire could apply without judgment: measurable disqualifiers, weighted attributes that sum to 100, tier cut-offs, and a back-test against the deals you gave it.
Competitor Monitoring Skill: Diff a Competitor's Public Surface Every Week
Turns competitor monitoring into a weekly diff: the skill reads one competitor's public pages, compares them with the snapshot it saved last run, and returns each change classified, rated for deal impact, and translated into what it means for your reps. Run it by hand, in a Project, or as the brain of a scheduled Routine.
Cold email campaign QA: the skill I’d run before importing leads
I want to know exactly why a prospect and a message are ready before either reaches a sender. This skill produces a review queue, ties decisions to the final copy, and exports approved records to a Smartlead import CSV.
Prompts for Founder / Solo GTM
Individual tasks with required inputs and example outputs. Each prompt lists the assistants it supports.
Turn a Company URL Into a First-Call Brief
Turn a company URL into a sourced, opinionated first-call brief that maps your offer to your buyer's real pressures and earns the next meeting.
Works with: Claude, ChatGPT, Gemini, PerplexityDefine Your ICP and Buyer Personas
Distill real win/loss evidence into an ICP, a buying-committee map, and a scoring model your whole team can act on, built on disqualifiers, not aspiration.
Works with: Claude, ChatGPT, GeminiWrite a Cold Email That Earns a Reply
Produce a tight, relevance-first cold email with one clear ask, built around the prospect's trigger not your pitch, sub-90 words, no fluff, no fabrication.
Works with: Claude, ChatGPT, GeminiLinkedIn Post Generator: Turn a Point of View Into a Post
A LinkedIn post generator that turns a raw opinion or experience into a post with a real hook, one sharp idea, and a concrete moment, in your voice, with the cringe stripped out.
Works with: Claude, ChatGPT, GeminiSales Discovery Questions, Tailored to the Deal
Build deal-specific, open-ended sales discovery questions mapped to pain, quantified impact, process, and competition, with the must-answer for each.
Works with: Claude, ChatGPT, GeminiObjection Handling Script for Tough Objections
Turn a specific objection into an objection handling script: the clarifying question to ask first, the likely root causes, and three honest, non-defensive responses that advance the deal.
Works with: Claude, ChatGPT, GeminiTurn Call Notes Into a Follow-Up and Action Plan
Convert raw call notes into a tight recap email, a mutual action plan with owners and dates, and the risk flags that predict whether the deal will drift.
Works with: Claude, ChatGPT, GeminiBattlecard: Build a Rep-Ready One vs Any Competitor
A prompt that builds a rep-ready, no-spin battlecard against a named competitor: where you win, where you honestly lose, the traps to set, and the landmines to avoid.
Works with: Claude, ChatGPT, Gemini, PerplexityAI Content Repurposing: One Transcript Into a Content Engine
AI content repurposing that turns one transcript into a blog post, social posts, an email, pull-quotes, and clip ideas, keeping the original point of view and grounded in the source.
Works with: Claude, ChatGPT, GeminiReply Fast to an Inbound Lead
Draft a fast, intent-matched reply to an inbound lead that keeps momentum, qualifies with one smart question, and makes the next step one click.
Works with: Claude, ChatGPT, GeminiGuides for your chosen assistant
Follow the guide for the tool you use. A shared workflow directory does not change the setup requirements of an individual playbook.
Claude
- Which Claude should I use? App vs Claude Code vs API →Use Claude apps for conversation, finished documents and supported multi-step cloud tasks.
- Claude Code: install and your first agent run →Claude Code is an agentic tool that runs in your terminal, your editor, a desktop app, or the web, and does multi-step work against your real files and tools.
- Claude Routines: scheduled cloud agents, explained →Claude Routines are scheduled jobs that run in the cloud on a cadence you set, without you or your machine involved.
- What is an AI agent? The agentic loop, explained →An AI agent is a model you give a goal, a set of tools, and permission to loop: it looks at the situation, picks a next action, takes it with a tool, reads the result, and goes again until the job is done or it hits a stop you set.
- Claude vs AI SDR tools: build the agent or rent the rep →Buy an AI SDR tool (11x, Artisan, AiSDR) when you have no builder on staff and need outbound volume running in weeks: you get data, writing, sending, deliverability, and reply handling behind one login and one invoice, at a price that starts around $900 a month for the cheapest published plan and climbs fast.
- Claude cost control for a GTM org: seats, Code, and routines on one ledger →AI cost control for a GTM org means putting three different bills on one ledger: app seats (a fixed price per person, standard or premium), Claude Code (usage that scales with how much reps and builders run it), and API routines (tokens, priced per model).
- Rolling Claude out to a sales team: the adoption playbook →AI adoption on a sales team is a rollout problem, not a tooling problem.
ChatGPT & Codex
- Getting started with ChatGPT: your first useful workflow →Start with one small task, supply the relevant sources, specify the output and review the result.
- ChatGPT and Codex plans, pricing and usage limits →Choose a plan by the work, required controls and actual usage.
- ChatGPT for teams: access, privacy and a practical rollout →A team rollout needs separate decisions about workspace access, connected-service permissions, local execution and API projects.
- What is Codex? A practical guide for GTM operators →Codex is OpenAI’s developer-facing agent experience for working with code, files and tools.
Frequently asked questions
Where should a solo founder start?
Choose one task that repeatedly delays useful work and has an output you can judge. Account research and follow-ups are concrete starting points. Finish one small workflow before adding another.
Do I need several AI subscriptions?
Start with a tool you already use and a prompt that lists it as supported. Check the prerequisites of a full playbook before choosing it. Add another tool only when a specific workflow makes the need clear.
How much of GTM can I hand over?
Use the workflows for research, drafts, preparation, and repeatable operations. Keep ownership of customer relationships, positioning, commitments, and decisions about what should happen next. Review the work at the points where it reaches other people or changes a live system.
How do I avoid a pile of half-finished automations?
Keep one source of instructions, a reviewed example, and a short checklist for each workflow. Name its inputs and outputs, make failures visible, and remove workflows whose maintenance costs more than the work they save.