sales-skills/sales-miskmap

MiskMap Platform Help

MiskMap (miskmap.app) is a Claude-powered SaaS-idea validator built to be a skeptic, not a cheerleader. It returns a 60-second 0-100 viability score and a BUILD/VALIDATE-MORE/PIVOT/DON'T-BUILD verdict, then — on the paid tier — a technical architecture + Claude Code / Cursor-ready code prompts to build the MVP. Its whole point is finding "The Fatal Flaw" before you spend a weekend building.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask only what you can't infer from the user's prompt:

1. Where are you? (a) about to run an idea through MiskMap, (b) staring at a score/verdict and unsure what to do with it, (c) deciding free tier vs the paid Builder Pass, (d) want to use its code prompts / tech-stack to actually build, (e) asking whether it has an API/export.
2. What's the idea, in one sentence? (helps you interpret the four-pillar score).
3. What have you got so far — just a hunch, an AI score, a landing page, a waitlist, or someone offered to pay?

Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.

Step 2 — Route or answer directly

MiskMap is one AI validator. Most of the thinking a founder needs is tool-agnostic — route it:

| The user's real question | Route to | |---|---| | Should I trust this score? How do I actually validate? The evidence ladder, comparing validators | /sales-idea-validation | | Build the smoke-test / fake-door landing page the demand test runs on | /sales-funnel | | Grow a pre-launch waitlist and capture signups | /sales-audience-growth | | Reddit-based real-demand signal to cross-check the score | /sales-trendseeker |

When routing, give the exact command: "This is a validation-method question — run: /sales-idea-validation {the user's original question}"

Answer directly only for MiskMap-specific mechanics (the four pillars, the score bands, Stages 1-4, the Builder Pass gate, the code prompts, "does it have an API").

Step 3 — MiskMap platform reference

Read references/platform-guide.md for the full reference — the four-pillar methodology, score bands, the Stage 1-4 flow, pricing/plan gates, what's free vs Builder-Pass-gated, the (absent) automation surface, and how to get data out.

Answer using only the relevant section — don't dump the whole guide.

Step 4 — Actionable guidance

• The viability score and every market number are an AI opinion, NOT demand. MiskMap runs on Claude and is deliberately skeptical, which makes its structured output (the competitor teardown, the "Fatal Flaw", the risks, the four-pillar reasoning) genuinely useful to sharpen the pitch — but a BUILD verdict still isn't a stranger paying. Keep the structured parts, discard the verdict, and take the go/no-go from a real behavior test (smoke test / pre-sale). Route that test to /sales-funnel + /sales-audience-growth.
• Treat the "Fatal Flaw" as the deliverable, not the score. Its edge over cheerleader validators is that it names the one assumption that kills the business — read it as your top thing to go disprove with real customers, not as a reason to feel bad or good.
• Interpret the verdict band, then connect a low score to the weak pillar. The 0-100 score bands to BUILD (80-100), VALIDATE MORE (60-79), PIVOT (40-59), or DON'T BUILD (0-39) — so a mid-range score (e.g. a PIVOT) means the idea as framed has a weak dimension, not that it's dead or ready. When the score is low, tell the user which pillar likely dragged it down (usually weak Market Urgency — a vitamin, not a painkiller — or weak Competitive Defensibility — a thin wrapper with no moat) and turn the Fatal Flaw into the concrete next thing to fix or re-frame.
• Cross-check any verdict with a second source and a sharper re-run. Before a founder accepts a MiskMap number as final, have them re-run with a more specific customer + painkiller problem (thin input → generic output) and cross-check against a second validator or a real-demand signal (/sales-trendseeker) — disagreement between sources is the useful information.
• Feed it a specific customer + painkiller problem; thin input → generic output. The five setup questions (target customer, pain, how they find solutions today, goal, timeline) are what the score is built on — answer them concretely, especially the "painkiller vs vitamin / credit card at 2 AM" framing behind the Market Urgency pillar.
• Don't let the code prompts pull you into building before you've validated. The Builder-Pass technical architecture + Claude Code / Cursor-ready prompts are a real head-start once you've decided to build — but generating them is not permission to skip the demand test. Building is cheap now; demand evidence is the scarce thing.
• Present all pricing as best-effort and unsettled. The Builder Pass price and model differ across MiskMap's own pages (one-time vs monthly) — confirm at miskmap.app/pricing before quoting, and note the free tier covers Stages 1-2 (full validation) with paid gating Stages 3-4.
• There's no API — point automation at the demand test, not the report. MiskMap is UI-only (no public API, webhooks, Zapier/Make, or MCP); to get data out you download the PDF or share the link. Don't plan an integration around it — and since the score isn't demand anyway, put any real pipeline on the demand side (landing-page analytics, waitlist capture, pre-sale checkout events), or reconstruct scriptable signals from source (a keyword-volume API, Google Trends, Reddit).

If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.

Gotchas

Best-effort from research (2026-07) — the AI-validator tool set churns fast; verify tiers, the pillar set, and the Builder Pass price at miskmap.app.

• A high viability score is not validated demand. MiskMap is a skeptic among LLM validators, but it's still an LLM — a BUILD (80+) verdict reflects the model, not the market. Always follow with a real-behavior test.
• The scoring factors have shifted across versions. The methodology page describes four "Red Team" pillars (Market Urgency, Competitive Defensibility, Monetization Clarity, Distribution Ease); older/other pages list five factors (Market Demand, Competitive Position, Monetization Potential, Customer Access, Founder Fit). Read whichever the app actually shows and don't over-index on exact pillar names.
• Pricing is inconsistent across its own pages. The paid Builder Pass appears as a one-time charge on some pages and a monthly subscription on others; a "$9.99 Single Blueprint" also shows up. Treat every figure as best-effort and confirm before quoting.
• Free tier gates you to one active plan at a time. Full validation (Stages 1-2) is free but you archive/replace to run another idea; the technical architecture and code prompts (Stages 3-4) are Builder-Pass-only.
• SaaS/digital only. It's built for pre-launch SaaS, mobile apps, and online marketplaces — not physical goods, brick-and-mortar, or long-cycle enterprise sales.
• No API, webhooks, Zapier, or MCP. UI-only; export is PDF + shareable link. Don't build automation on it.

Related skills

• /sales-idea-validation — the tool-agnostic validate-before-building method and the full idea-validator comparison (start here to decide whether to trust any score)
• /sales-funnel — build the smoke-test / fake-door landing page the real demand test runs on
• /sales-audience-growth — grow a pre-launch waitlist and capture signups once you're testing demand
• /sales-trendseeker — Reddit-based real-demand signal to cross-check MiskMap's verdict
• /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code

Examples

Example 1: "MiskMap scored my idea 84 and said BUILD — am I good to go?"

User says: "MiskMap gave my idea an 84/100 with a BUILD verdict. Should I start building?" Skill does: Reframes the 84/BUILD as a skeptical AI opinion, not demand — keeps the useful structured parts (the competitor teardown, the named "Fatal Flaw", the four-pillar reasoning, the risks) to sharpen the pitch, and prescribes the real test: a smoke-test landing page with a pre-committed conversion threshold, then a pre-sale, routing the build to /sales-funnel and signups to /sales-audience-growth. Result: The founder goes and disproves the Fatal Flaw with real behavior before betting the build on a number.

Example 2: "It says PIVOT — what do I actually do with that?"

User says: "My score came back 48, PIVOT. Now what?" Skill does: Explains the band (40-59 = PIVOT) as "the idea as framed has a weak pillar", points the user at which pillar dragged it down (usually Market Urgency — a vitamin, not a painkiller — or Competitive Defensibility — a thin wrapper), and turns the "Fatal Flaw" into the pivot brief; suggests cross-checking with a second source (/sales-trendseeker) and re-running with a sharper customer/problem before concluding. Result: The user gets a concrete pivot direction instead of a discouraging number.

Example 3 (automation): "Can I pull MiskMap reports into my dashboard via API?"

User says: "I want to auto-export my MiskMap validation reports into Notion/my CRM — is there an API or webhook?" Skill does: States plainly that MiskMap is UI-only — no public API, no webhooks, no Zapier/Make, no MCP; the only export is PDF + a shareable link (Builder Pass). Offers the realistic paths: download/parse the PDF manually, or — since the score isn't demand anyway — reconstruct the signals you'd actually automate on from source (a keyword-volume API, Google Trends, Reddit) and put the real pipeline on the demand test, not the AI report. Result: The user stops trying to integrate a UI-only tool and points automation at real signals.

Troubleshooting

The score feels too high / too low to trust

Symptom: A glowing BUILD or a harsh DON'T BUILD the founder doesn't believe. Cause: It's a Claude-generated opinion off five short answers; the four pillars amplify how you framed the customer and the problem, and the factor set differs between MiskMap's pages. Solution: Keep the structured outputs (competitor teardown, Fatal Flaw, risks), discard the verdict, re-run with a sharper customer + painkiller problem, cross-check with a second validator or /sales-trendseeker, and earn the real verdict with a smoke test / pre-sale.

"I paid but can't tell what the Builder Pass unlocked / what it cost"

Symptom: Confusion over free vs paid and whether the charge was one-time or monthly. Cause: Pricing and the Builder Pass model are presented inconsistently across MiskMap's own pages. Solution: Confirm the current price/model at miskmap.app/pricing. Free = Stages 1-2 (full market analysis + validation, 1 active plan). Builder Pass = Stages 3-4 (technical architecture, 3 tech-stack options, dev timeline & cost, AI code prompts) + unlimited plans + PDF export + shareable links.

The generated code prompts / tech stack don't fit my idea

Symptom: The Builder-Pass architecture or Claude Code / Cursor prompts feel generic or off. Cause: Like the score, they're generated from your short setup answers — thin input yields a generic stack. Solution: Treat them as an editable first draft: re-run with a concrete feature set and constraints, pick the tech-stack tier (Beginner/Intermediate/Advanced) that matches your skill, and — most importantly — validate demand before you spend the weekend building from them.