Skip to content
Agentmart
Submit a tool

gtm-readiness

Go-to-market audit for a B2B startup: which fit it has (find, sell, serve, retain), which GTM phase it is in, whether the segment is real, and the mistakes in…

Skill by renzobianchi

IndexedMIT★ 2
Write a review

Chalk Labs

Need help deploying gtm-readiness?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code. Read the repository before you give any tool access to your data.

npx agentmarket install skill/renzobianchi-gtm-readiness

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Go-to-market audit for a B2B startup: which fit it has (find, sell, serve, retain), which GTM phase it is in, whether the segment is real, and the mistakes in play, each with the correction.

Use cases: security

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Nov 2, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/gtm-readiness

Tools it pre-approves 6

From allowed-tools in SKILL.md: the agent may use these without asking you each time.

  • Read,
  • Write,
  • WebFetch,
  • AskUserQuestion,
  • Bash(curl
  • *)

What's inside

Skill name
gtm-readiness
Description
Go-to-market audit for a B2B startup: which fit it has (find, sell, serve, retain), which GTM phase it is in, whether the segment is real, and the mistakes in play, each with the correction.
License
MIT
Allowed tools
Read,, Write,, WebFetch,, AskUserQuestion,, Bash(curl, *)
Instructions
82 lines in SKILL.md · view on GitHub

Before installing

  • Pre-approves some shell commands

Files (6)

  • README.md
  • SKILL.md
  • frameworks.md · references/
  • interview.md · references/
  • mistakes.md · references/
  • sources.md · references/

SKILL.md (first lines)

# GTM readiness

You audit whether a startup is ready to scale what it is doing, and if not, which phase it is really in. Founders arrive claiming product-market fit from a handful of customers and a platform roadmap; the audit tests four pillars for repeatability, places the company in one of three GTM phases, checks the segment is a marketable one, and names the mistakes from a catalogue of thirty with the correction for each.

Vocabulary: **fit** is repeatability, measured per pillar; **segment** is workflow plus competitive alternative plus problem; **phase** is experimentation, beachhead, or expansion. A revenue number is evidence for a pillar, never fit itself, and firmographics alone are a mailing list, never a segment. Definitions and procedures in [references/frameworks.md](references/frameworks.md); read it before the interview.

Output: a **readiness report** with a verdict per pillar, the phase, the segment check, the mistakes in play, and the one next move.

## Phases

Open a todo list with one entry per phase.

1. Reconnaissance
2. Interview (three rounds)
3. Placement
4. Mistakes in play
5. Report

`quick`: reconnaissance plus round 1, placement, report. Say so in the header.

## 1. Reconnaissance

Fetch the homepage, pricing, and one customer or case-study page. Record: the growth model the CTAs imply (trial, demo, contact sales), the number of personas and use cases the site claims, whether the hero leads with an outcome, a capability, a category or a vision, whether a platform or suite is claimed, and which industries or segments are named. Each one is a hypothesis the interview confirms or drops.

Closed when the five observations are written down with the line that supports each.

## 2. Interview

Two or three questions per call to the ask-user tool. Wording and follow-ups in [references/interview.md](references/interview.md).

**Round 1, the four pillars.** Can you consistently get in front of your ideal customers? Consistently close deals with them? Consistently get them to value? Do they stick around? For each, the follow-up is the number: how many of the last ten, and were they the same kind of customer. "Consistently" with no number is a no.

**Round 2, the segment.** Company type, champion, the workflow they buy for, what they used before, and the problem in the champion's framing. Then: who was easiest to close, who gets the most joy from the product, who shares it, and who churned. Any customer using an alternative with no complaint about it is outside the ICP.

**Round 3, the plan.** What are you building toward: one feature with fit, a product, a platform? How many segments are you selling to now, and with how many people? Distribution advantage (community, audience, virality, a large raise)? Time to value: minutes, weeks, quarters?

Closed when each pillar has a number, the segment has all five dimensions or an explicit blank, and the plan questions are answered.

## 3. Placement

From the interview, decide and justify with the founder's own numbers:

- **Fit**: which pillars repeat. Retain course-corrects the others: strong find and sell with weak retain means the wrong customers were found and sold, which is a segment problem.
- **Phase**: experimentation (still learning who cares most), beachhead (one use case for one group, building the plumbing, aiming at repeatability), or expansion (adding a segment or a use case). The exit signal from experimentation is a gut feeling that you could sell a lot to one specific market; the exit from beachhead is repeatability and predictability; ARR is evidence of it, never the criterion.
- **Market maturity**: immature, emerging, or mature, from what the customers used before.
- **Segment**: marketable or not, on the four prioritization questions (sticks, reachable, sellable, onboardable; size is not one of them).

Closed when the four placements each cite an interview number or quote.

## 4. Mistakes in play

Walk [references/mistakes.md](references/mistakes.md) top to bottom against the placement and the reconnaissance. List every mistake that holds, with the evidence line and the prescribed correction. Keep only those with evidence; a padded list buries the one that matters.

Closed when every entry in the catalogue has been checked and the list carries only those with evidence.

## 5. Report

Write `gtm-readiness-<slug>.md`:

1. Verdict in one line: the phase, and whether the current motion is ready to scale.
2. Pillars table: pillar, repeatable yes/no, the number.
3. Segment: the five dimensions and the prioritization answers.
4. Mistakes in play, ordered by cost, each with correction.
5. The one next move (a segment to commit to, a phase to finish, a positioning sprint to run) and which skill runs it: `startup-positioning` when the segment or the alternative is undefined, `homepage-messaging` when the site does not support the growth model.
6. What could not be verified and where the answer lives.

Closed when the founder can say which phase they are in without hedging.

## Guardrails

- **Grade fit pillar by pillar with the founder's numbers.** A million in ARR from five segments is initial traction toward five different fits.
- **Score segments on sticks, reachable, sellable, onboardable, and leave size out.** The biggest segment attracts the worst-fit customers, who pull the product apart.
- **Audit the wedge the company sells today, and treat the platform as a sequence.** Fit is found one feature at a time.
- **Read weak retain as a segment problem before a marketing problem.** Churn means the wrong customers were found and sold.
- **Take the wedge as the market's story and the vision as the investors'.** Customers are told the wedge; investors are told everything.
- **List three mistakes with evidence over fifteen that might apply.** The one that matters gets buried in a padded list.

## Credits

Method distilled from Fletch PMM (Robert Kaminski, Anthony Pierri): the Product Fit Model, the three phases of startup GTM, the segment prioritization questions, the minimal viable market segment, the market maturity stages, and their mistakes posts. Names kept on purpose; [references/sources.md](references/sources.md) maps each part to its post.

From renzobianchi/skills, MIT.

More from renzobianchi/skills

Signals

Stars
2
Forks
2
Open issues
0
Last commit (this folder)
Sep 2, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from renzobianchi

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get gtm-readiness running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying gtm-readiness?

CallGet help
Cite this page

gtm-readiness skill. Agent Mart. https://agentmart.dev/skills/renzobianchi-gtm-readiness (last updated 2026-10-24)