market-scan
Refresh the user's competitive and market context. Re-scan named rivals and the category for what changed since the brief was written (rebrands, repositioning, new entrants, pricing shifts, renamed categories) and update docs/gtm-cofounder/founder-brief.md and the roadmap with anything that moves positioning. Use on a cadence, or whenever a competitor rebrands, a new tool appears, or the user senses the market has shifted under them.
git clone --depth 1 https://github.com/AIDevGTM/gtm-cofounder /tmp/market-scan && cp -r /tmp/market-scan/skills/16-market-scan ~/.claude/skills/market-scanSKILL.md
# Market scan (keep your read current)
> Positioning rots. The competitor you sized up six months ago has since rebranded, raised, repriced, or renamed the category. This is the habit that keeps your brief honest about the world outside it.
**Use this when:** a rival just rebranded or repositioned, a new tool is getting attention in your space, your `docs/gtm-cofounder/founder-brief.md` competitor answers are more than a quarter old, or you just have the feeling the ground moved and your messaging is answering last year's market.
## The core idea
Your `docs/gtm-cofounder/founder-brief.md` captured the market as it was the day you wrote it. Markets don't hold still. A scan re-checks the outside world against your brief and surfaces the deltas: what changed, and which changes actually threaten or help your positioning. Most don't matter. The scan's job is to find the two or three that do, not to produce a competitor spreadsheet.
## Before you start: can your agent see the web?
- **If your agent can browse or search the web**, it runs the scan for real: competitor homepages, changelogs, pricing pages, launch posts, and recent discussion.
- **If it can't**, it runs the scan as an interview: it asks what you've noticed and where, and you paste in the pages. Same output, you're the browser. Say which mode you're in up front.
## How to run this (for the agent)
- **Start from the brief.** Read `docs/gtm-cofounder/founder-brief.md`: the rivals ("what do they use instead"), the "why you", the villain, and the current positioning line. That's your baseline to compare against.
- **Scan the named rivals first, then the category.** For each competitor in the brief, check: homepage headline and positioning, pricing, any rebrand or renamed category, funding or acquisition, and new capabilities that erase the founder's wedge. Then scan for new entrants and category-level shifts (a term everyone suddenly uses, a platform move, an AI or agent shift).
- **Report deltas, not descriptions.** Do not summarize each competitor. Say what *changed* since the brief, and for each change, whether it strengthens, threatens, or is irrelevant to the founder's positioning. Rank by "does this move our position."
- **Tie every real change to an action.** A rival adopting the founder's language means the wedge is eroding: route to `positioning-and-story`. A new pricing norm means revisit `market-to-devs-sell-to-buyers`. A dead competitor means an opening. No action, no reason to flag it.
- **Update the brief and roadmap.** Rewrite the affected lines in `docs/gtm-cofounder/founder-brief.md` (rivals, why-you, villain, positioning) with today's reality and the date, and add any positioning move it triggers to `docs/gtm-cofounder/gtm-roadmap.md`. Keep the tags honest: a competitor's public claim is `[assumption]` until you have checked it is real.
## What actually matters (and what doesn't)
Changes worth acting on:
- A rival **repositions onto your wedge** or adopts your vocabulary. Your differentiation is eroding. Highest priority.
- A **new entrant** is getting real traction in your exact lane.
- The **category gets renamed** (buyers now search a different term than your copy uses).
- A **pricing norm** shifts (a free tier appears or disappears, seat pricing becomes standard).
Noise to ignore:
- Cosmetic rebrands, new logos, homepage redesigns with the same substance.
- Feature announcements that don't touch your wedge.
- Funding rounds that don't change what the product is or who it is for.
## Mistakes that look reasonable
- **Reacting to a competitor's launch by copying it.** Their move fits their strategy, not yours. Ask what it means for your wedge, not how to match it.
- **Scanning everything, changing nothing.** A scan that doesn't update the brief or the roadmap was just anxiety with extra steps.
- **Treating a rival's marketing claim as fact.** "Now with X" on a homepage is a positioning bet, not proof it works. Tag it `[assumption]`.
- **Doing it constantly.** Monthly, or on a real trigger (a rebrand, a new entrant), is plenty. Daily competitor-watching is procrastination dressed as diligence.
## Your next 30 minutes
- [ ] Tell your agent which mode you're in (it browses, or you paste).
- [ ] List the rivals from your `docs/gtm-cofounder/founder-brief.md`. Scan each for a rebrand, repricing, or repositioning since you wrote it.
- [ ] Write down only the changes that touch your wedge. Ignore the cosmetic ones.
- [ ] For each real change, mark it strengthens / threatens / irrelevant, and the one action it triggers.
- [ ] Update the affected lines in `docs/gtm-cofounder/founder-brief.md` (with the date) and add any positioning move to `docs/gtm-cofounder/gtm-roadmap.md`.
---
Built from real dev-tool GTM experience, with frameworks from Adam Frankl (*The Developer-Facing Startup*) and Jakub Czakon (*markepear.dev*).
When a framework can't make the call, that's what a human is for: [The DevTool GTM Company](https://thedevtoolgtmcompany.com).Interview the user once and write a docs/gtm-cofounder/founder-brief.md that every other skill reads first, so the advice is about their real business, not a textbook. Use this before anything else, or whenever the agent lacks context on the user's product, ICP, market, or stage, or is giving generic GTM advice.
After the founder brief, turn it into an honest diagnosis and a prioritized, stage-aware GTM roadmap saved as docs/gtm-cofounder/gtm-roadmap.md. This is the hub the user returns to every session to see where they are and the single next move. Use right after start-here, whenever the user doesn't know what to work on next, wants a plan instead of a one-off task, or is drowning in disconnected tactics.
Define a real ICP and the developer personas in the sale. Use when the user says the product is \"for developers,\" can't name who would say no, or is marketing to whoever holds the budget instead of who actually adopts.
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.
Build a positioning and narrative where the developer is the hero and a real trend is the villain. Use when the messaging describes the product instead of the problem, sounds like every competitor, or has no urgency because nothing is at stake.
Position an AI product when everyone claims AI and skeptics call it \"just a wrapper.\" Find the real wedge (data, workflow, trust, domain), make reliability the differentiator, answer \"won't the big labs just build this,\" and stop leading with \"AI-powered.\" Use when your AI or dev tool blends into a sea of similar demos, buyers doubt the accuracy, or you can't say why you win when the model is a commodity.
Write a developer value proposition that is specific, provable, and free of puffery. Use when the messaging leans on \"powerful,\" \"better,\" \"seamless,\" or \"best-in-class,\" when claims have no proof, or when the same line is supposed to reach both the developer and the buyer.
Structure a dev-tool homepage that converts developers into champions. Use when the landing page is written for the buyer instead of the developer, reads as salesy, buries what the product does, or makes it hard to start. Pairs with the ShipReady homepage audit.