solo-founder-gtm

# solo-founder-gtm

solo-founder-gtm

Overview
Improve solo-founder-gtm with a repeatable operator workflow instead of ad hoc execution.

This matters because solo operators need revenue systems that remove negotiation drag, keep follow-up moving, and protect margin.

External marketplace demand already exists, so this is not just an internal naming exercise.

When to Use This Skill
- You need a practical playbook for solo-founder-gtm instead of scattered notes.
- You want one operator-friendly workflow that can be reused every week.
- You want a page that can rank, be cited, and turn into a repeatable operating habit.

What This Skill Does
- turns solo-founder-gtm into a repeatable operating sequence
- clarifies the decisions, checkpoints, and outputs that matter
- keeps the workflow useful for a solo operator instead of a large team

How to Use
1. Start by defining the exact job solo-founder-gtm is supposed to improve.
2. Strip the workflow down to one narrow operator loop with a clear trigger and output.
3. Write the checklist, prompt, or operating policy in plain language.
4. Run it on one live task, capture the result, and refine the workflow around what actually helped.

Output / Result
- a reusable solo-founder-gtm playbook
- clear steps a solo operator can run without extra context
- a better base for future proof blocks, examples, and public distribution

Common Mistakes to Avoid
- making it a vague GTM page instead of a workflow that affects pipeline or revenue
- copying marketplace wording without translating it into an operator job
- trying to cover too many workflows in one page
- skipping the proof step and publishing a page that still reads like a concept

## Direct Answer
Use this skill when you need a weekly founder-led GTM loop, not random execution. Pick one GTM bottleneck, set one baseline metric, ship one concrete change, and log proof so the next cycle compounds what worked.

## Weekly Solo Founder GTM Loop

1. Pick the constraint. Choose one GTM bottleneck for the week: message-market fit, lead generation, conversion flow, follow-up speed, or distribution consistency.
2. Record the baseline. Capture the pre-change metric before touching anything: qualified replies, booked calls, close rate, CAC proxy, or revenue per lead.
3. Ship one GTM move. Improve one high-intent page, one outreach sequence, one offer frame, or one distribution message.
4. Define measurement. Tie the move to a measurable path: GA4 key event, UTM-tagged source, CRM stage, or manual conversion count.
5. Save evidence. Store links, screenshots, and before/after snapshots in a short GTM run report.
6. Roll the next sprint. Keep the winning move, remove dead work, and pick the next constraint.

## Evidence To Collect
- the baseline metric before the GTM change
- the exact page, sequence, or offer that changed
- before/after conversion or response data
- the key event, tagged link, or manual proof count tied to the change
- the next action for win, mixed, or loss outcomes

## Source Links To Cite
- market and competitive analysis source used to prioritize the GTM bottleneck
- analytics source defining event measurement and source attribution
- search performance source used to validate page discoverability gains
- disclosure/trust source used when publishing testimonials or partner mentions

## Freshness Reinforcement (2026-04-08)

- Added a fixed weekly GTM evidence review cadence with baseline-versus-current metric tracking.
- Added explicit measurement requirements covering GA4 key events, Search Console checks, and UTM attribution.
- Added compliance guidance for social proof, testimonial use, and partner amplification.
- Added a source-backed comparison grid so weekly GTM reviews compare page, channel, and offer changes using the same evidence window.

## Authority and Citations Table

- GTM prioritization evidence: Select the weekly GTM lane using documented market and competitive analysis before changing messaging or channels. Source: U.S. SBA market research and competitive analysis - https://www.sba.gov/business-guide/plan-your-business/market-research-competitive-analysis
- Operating plan baseline: Founder-led GTM still needs explicit assumptions around value proposition, customer segments, channels, costs, and revenue model. Source: U.S. SBA write your business plan - https://www.sba.gov/business-guide/plan-your-business/write-your-business-plan
- Measurement discipline: GTM conversion actions should be tracked as GA4 key events, not inferred from generic traffic movement. Source: Google Analytics key events report - https://support.google.com/analytics/answer/12571843
- Search visibility checkpoint: Weekly page-level GTM reviews should track clicks, impressions, CTR, and average position for changed assets. Source: Google Search Console performance report - https://support.google.com/webmasters/answer/7042828
- Attribution consistency: Distribution and outbound channel comparisons should use UTM-tagged links for source-level decision quality. Source: Google Analytics URL builders - https://support.google.com/analytics/answer/10917952
- Compliance guardrail: Testimonials, endorsements, and incentivized partner claims require clear material-connection disclosure. Source: FTC endorsement guides FAQ - https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking

## Source-Backed Comparison Grid

- Search page upgrade: compare the edited page's Search Console clicks, impressions, CTR, and average position across the same pre/post date window before you keep the new framing.
- Conversion page upgrade: compare the page's GA4 key-event count or conversion rate before and after the GTM change instead of relying on session growth alone.
- Channel test: compare UTM-tagged source or medium results for the same offer, landing page, and review window so you know whether distribution or messaging produced the lift.
- Offer or proof update: compare conversion movement only after adding compliant testimonials, partner mentions, or case-study proof, and save the exact source links that justify the trust claim.
- Outbound follow-up change: compare qualified-reply rate or meeting rate for one sequence version at a time, then record the winning variant in the weekly evidence pack.

## Solo Founder GTM Scorecard

- primary GTM bottleneck this week
- baseline metric and current metric
- one shipped GTM move
- comparison window used for the review
- key event count or stage progression signal
- source/campaign attribution labels
- winning page, message, or channel variant
- proof asset created: report, screenshot, or CRM excerpt
- next GTM bottleneck after review

## Evidence Pack Template

- Review date (UTC): `YYYY-MM-DD`
- GTM bottleneck: `messaging | lead gen | conversion | follow-up | distribution`
- Baseline metric: `name + value`
- Shipped move: `page | sequence | offer | channel message`
- Comparison window: `pre window -> post window`
- Proof links: `page URL`, `report path`, `screenshot path`, `conversation link`
- Measurement path: `GA4 key event`, `UTM`, `CRM stage`, `manual count`
- Search checkpoint: `GSC clicks`, `impressions`, `CTR`, `average position`
- Winning variant or source: `page version | message variant | campaign label`
- Result after review window: `win | mixed | loss | unresolved`
- Next move: `double down | revise | stop`

## What Good Looks Like
- The GTM change is specific and measurable.
- The page includes evidence, not only advice.
- The next action is obvious for a solo founder.
- One operator can run the loop in under an hour.

## Named Examples

- A solo founder sees low booked calls, rewrites one high-intent service page, tracks the CTA submit event in GA4, and logs a before/after conversion delta in the weekly report.
- A productized-service operator gets inbound leads but poor attribution, adds UTM tags to newsletter and partner links, and compares close-rate by source for the next sprint.
- A founder with high outbound volume but weak replies tightens one outreach sequence and compares qualified-reply rate before expanding channel spend.
- A founder testing two offer angles keeps the landing page constant, changes only the headline and CTA frame, compares Search Console CTR plus GA4 key-event rate across the same window, and keeps the variant that wins on both discoverability and conversion.

## Frequently Asked Questions

### What is the fastest way to start solo-founder-gtm?
Start with one bottleneck and one baseline metric. Ship one concrete GTM change and decide how it will be measured before publishing it.

### How often should this GTM loop run?
Run it weekly on a fixed review day. Weekly cadence is frequent enough to keep momentum and long enough for real response and conversion signals.

### What counts as proof for solo-founder-gtm?
Proof is any artifact that allows later verification: analytics exports, tagged links, before/after page copies, CRM movement, or a short run report with links.

### How should I compare GTM changes without fooling myself?
Use the same review window, keep one major variable under test, and compare search, conversion, and attribution evidence together before declaring a winner.