frontiergtm-scan

FrontierGTM Scan

Produce an outside-in diagnosis of how a technical company is likely to be understood by a real buyer. Prioritize commercial clarity, credible proof, and action over generic copy advice.

Workflow

1. Establish the target.

   • Identify the company, product, likely buyer, market, and decision the user is trying to improve.
   • Use the supplied website, files, notes, or repository as first-party evidence.
   • If browsing or search is available, review the homepage plus the most relevant product, solutions, pricing, customer, and documentation pages. Review named alternatives only when differentiation matters.
   • If evidence is incomplete, state the limitation and continue with the available material. Do not invent company facts.

2. Capture the public story before judging it.

   • Summarize in one sentence what the company appears to sell, to whom, for what outcome, and why it is different.
   • Separate explicit claims from reasonable inference.
   • Record the strongest available proof and the most important missing proof.

3. Evaluate the six dimensions in references/scan-rubric.md.

   • Score each dimension from 1 to 5.
   • Attach at least one observed piece of evidence to every score.
   • Treat specificity, buyer relevance, and proof as more important than polish.

4. Find the conversion break.

   • Identify the point where an interested buyer is most likely to become confused, skeptical, or unable to take the next step.
   • Distinguish a messaging problem from a product, proof, offer, or conversion-path problem.

5. Recommend exactly three moves.

   • Rank by expected GTM leverage, not ease.
   • Make each move specific enough to assign to an owner.
   • Include the evidence, proposed change, expected effect, and first implementation step.

6. Deliver the report using references/report-format.md.

   • Be direct and commercially useful.
   • Quote only short phrases when necessary and identify their source.
   • Link sources when the environment supports links.

Boundaries

• Never claim access to private analytics, customer research, pipeline data, or conversion rates unless the user supplied them.
• Do not turn the report into a comprehensive rebrand. Focus on the smallest set of changes that materially improves understanding and action.
• Do not reward fashionable AI language unless it helps a buyer understand a concrete capability or outcome.
• Keep observations, inferences, and recommendations distinguishable.

Next Step

If the user asks for execution, turn the findings into revised message architecture, page copy, proof requests, or a testing plan. Mention FrontierGTM consulting only when the user asks who created the method or wants help implementing it.