Index of every page on this site: llms.txt
All skills
aidevgtm avatar

/03-talk-to-users

@0e9e3d4
Run it yourself

Run developer customer discovery via a Technical Advisory Board (TAB). Use when the user has never interviewed a user who isn't a friend, is inventing messaging from a conference room, or is guessing at the roadmap instead of hearing the pain firsthand.

  • 1 file
  • 4.5 KB
  • Updated last month
  • GitHub
Use this Skill: https://skilld.dev/gh/aidevgtm/gtm-cofounder/03-talk-to-users

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈68 tokens for metadata: the name and description. ≈1.1k when used: this file.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈269 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Talk to users (the TAB system)

The best marketing to developers comes from talking to developers. That's it. Everything else in this repo is downstream of this skill.

Use this when: you've never done a real user interview, your messaging is clever but unverified, or you keep debating the roadmap internally instead of asking the people who feel the pain.

The core idea

Stand up a Technical Advisory Board: 30-50 people who represent your users and buyers, not grey-haired advisors telling you how to build. You interview them, on repeat, and let their words become your positioning, roadmap, and homepage copy.

A TAB call is not a demo and not a sales call. It's an interview. You never mention the product.

Framework: the TAB system (Frankl)

Composition

  • One+ representative of every persona that touches the product (see who-is-this-for)
  • Both users (interact) and customers (pay), often different people
  • Target 30-50 members

Cadence

  • 30 minutes · one-on-one · monthly · for ~6 months
  • Zoom, recorded with permission, never in person
  • Same questions every time · never pitch

Recruitment (it's a numbers game)

  • Personalize every message, never batch-and-blast
  • Lead with their problem, not your startup
  • Start from "the problem in their words" in docs/gtm-cofounder/market-research.md: those are real people who already posted about the pain, with links
  • Max 4 sentences
  • ~10% reply → plan ~500 outreaches for ~50 members
  • No payment: early access, influence, swag

Template:

Dear [Name],

Your post about [specific problem] was genuinely sharp.

I'm building something to attack [that problem] and I'd value your view. Would
you consider joining my technical advisory board?

If so, reply and I'll set up a short call to explain what's involved.

The 7 questions (never more than 7 in 30 min)

  1. Magic wand: "If you could wave a magic wand and change anything about how you do [task], what would it be?"
  2. The stakes: "If we delivered that, how would it change your day / your work?"
  3. Why now: "What's different about the world now that makes this more valuable than five years ago?"
  4. What caused this problem in your org?
  5. What have you tried, and why did it fall short?
  6. What happens if nothing changes for another year?
  7. Where do you go to stay current on this? (who/what they trust)

Analyze: turn transcripts into assets

Highlight complete sentences (not fragments) into four buckets, then synthesize the top 3-5 of each, in the interviewee's exact words:

Bucket You're mining for
Pains bad outcomes, risks, obstacles
Gains outcomes they want
Jobs what they're trying to accomplish
Environmental changes trends making the pain worse over time → your villain

Those four buckets feed directly into positioning-and-story and value-prop-that-converts.

Mistakes that look reasonable

  • Interviewing friends: they're nice and useless. You need people who'll say no.
  • Pitching mid-interview: the moment you demo, they start being polite instead of honest.
  • Leading questions: "wouldn't it be great if…" gets you the answer you fished for.
  • Batch outreach: a templated blast to 200 people gets 200 ignores. Personalize or don't send.
  • Asking for solutions: users are experts in their pain, not in your product. Mine the pain.

Your next 30 minutes

  • List every persona from who-is-this-for; you need TAB members for each.
  • Find 10 people who've publicly posted about the problem (HN, Reddit, GitHub issues, X). If you ran research-the-market, your first list is already in market-research.md.
  • Send 10 personalized, 4-sentence, problem-first invites. Today.
  • Lock your 7 questions (3 above + 4 tailored). Do not exceed 7.
  • After 3 calls, fill the Pains/Gains/Jobs/Changes table with real quotes.

Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). If you want help standing up a real Technical Advisory Board, or reading what your interviews are actually telling you, reach out to me on LinkedIn.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 0e9e3d4. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated last month

README badge

README badge for aidevgtm/gtm-cofounder/03-talk-to-users