Skip to content

Instantly share code, notes, and snippets.

@tadas-subonis
Created December 31, 2025 14:03
Show Gist options
  • Select an option

  • Save tadas-subonis/7f882d46755c868cfd3aa7438c6b958a to your computer and use it in GitHub Desktop.

Select an option

Save tadas-subonis/7f882d46755c868cfd3aa7438c6b958a to your computer and use it in GitHub Desktop.

Go-to-Market example

(Below is an example I liked. I one-shot it with GPT-5.2 after I supplied it with good context.)

I am sharing the result here:

Product: "Todo-business SaaS" (team task manager) Goal: launch v1 and get first paying customers Constraint: small team, no brand, limited budget

Step 0 - Put rails in place

Before you ask the model to "make a GTM plan," give it your shape and rules.

Copy this skeleton and fill the brackets:

  • Audience: [who buys]
  • Problem: [what hurts today]
  • Why now: [what changed]
  • Differentiator: [why you]
  • Budget: [time + €]
  • Success metric: [number + date]
  • Constraints: [legal, channels you won’t use, etc.]

Now the first prompt is not "write plan." It is "build structure."

You are a B2B go-to-market lead.

Task: Propose the best GTM plan structure for launching a new B2B SaaS.

Context:
- Product: team task manager for small businesses
- Budget: €2k/month, 1 founder + 1 engineer
- Target: EU-based service companies (10–100 employees)
- Goal: 10 paying customers in 60 days
- Constraints: GDPR-sensitive, no paid search yet

Output:
- A GTM outline with headings only
- No fluff. No generic advice.

You just forced a usable template.

Step 1 - Research, then narrow the problem

Next, you do one job.

We start with pain. Not channels. Not slogans.

Feed it real inputs. Even rough ones.

Example customer notes (fake, but shaped like real ones):

Customer snippets:
1) "Tasks live in Slack, email, and people’s heads. Nothing is reliable."
2) "We miss deadlines because ownership is unclear."
3) "Asana is too heavy. People stop using it."
...
8) "Managers want visibility without nagging."
9) "We already pay for Microsoft 365."
10) "If setup takes more than 30 minutes, nobody adopts it."

Prompt:

Analyze the snippets.
Output:
- Top 3 pain points (ranked)
- Evidence: quote 2 lines per pain point
- The "job to be done" sentence for each
- A short note on what NOT to build for v1

Now you have criteria. You can say "no" with confidence.

Step 2 - Positioning, but only from the pain

Next single task.

Based on the top 3 pain points, write:
- 1 positioning statement (one sentence)
- 3 value propositions (one sentence each)
- 5 proof points we can realistically claim for v1
Constraints:
- No hype words. No "leverage," "robust," "comprehensive."
- Make it specific to EU service companies.

If it gets generic, you iterate:

Too generic.
Rewrite using:
- a concrete example (agency / accounting firm / consulting)
- a specific outcome (time saved, fewer missed deadlines)
- a clear differentiator vs Asana/Trello

Step 3 - Channels, but with tradeoffs

Don’t ask for "all channels." Ask for the best few given your limits.

Given our context (budget €2k/mo, 1 founder), pick 2 primary acquisition channels.
For each:
- Why it fits our audience
- Step-by-step weekly plan for 4 weeks
- What assets we must create
- What we will NOT do and why
Output as a table.

This is "set direction" and "say no."

Step 4 - Produce assets, one at a time

Now you use AI like a tool bench.

Cold email:

Write 2 cold emails to EU service companies (10–100 staff).
Goal: book a 15-minute call.
Constraints:
- 120 words max
- Plain text
- Mention one pain point and one proof point
- Add 3 subject lines
- No AI voice. No clichés.

Landing page draft:

Draft landing page copy with sections:
- Hero (headline + subhead + CTA)
- 3 pain bullets
- How it works (3 steps)
- Trust section (GDPR, EU hosting if true, etc.)
- FAQ (5)
Keep it short. Use simple words.

Demo script:

Write a 7-minute demo script.
Audience: operations manager at a 30-person agency.
Must show:
- Ownership and deadlines
- Client status view
- Recurring checklists
End with a clear close.

Step 5 - Adversarial review

This is where you stop lying to yourself.

Act as a skeptic buyer.
What is weak, unclear, or risky in our positioning and channel plan?
List:
- 10 hard questions we should expect
- 5 claims that need proof
- 5 ways this launch fails
Then propose fixes.

You just did a pre-mortem.

Step 6 - Turn it into a one-page execution plan

Only now do you ask for the final artifact.

Create a 1-page GTM plan.
Must include:
- ICP
- Pain points
- Positioning
- Primary channels (2)
- 4-week plan with weekly milestones
- Metrics dashboard (inputs and outputs)
- Risks and mitigations
Format: headings + bullets only.

Step 7 - Save what worked

This is the part people skip.

Create a folder like:

  • gtm/

    • 00-outline-prompt.md
    • 01-pain-analysis-prompt.md
    • 02-positioning-prompt.md
    • 03-channels-prompt.md
    • 04-assets/
    • 05-adversarial-review.md
    • README.md (what to paste each time)

Write down:

  • the prompts
  • the model used
  • what inputs mattered
  • what the model got wrong
  • the fix you used

Next time, you start at 70% quality. Not 0%.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment