b2b-account-mapslisted

*[日本語](SKILL.ja.md)* # B2B Account Maps Two maps, one purpose: knowing whether this deal can actually close, and what to do next. The influence map answers **who**; the discovery map answers **what we still do not know**. Run all commands from the slide-forge repository root. Use `.venv/bin/python`. ## Boundaries | Request | Route | |---|---| | Who decides / who blocks / approval path | this skill | | What is confirmed vs assumed, what to ask next | this skill | | The customer-facing proposal deck | `scalar-proposal-slides` / `google-slides-template` | | A new reusable one-slide template | `slide-template-creator` | | Visual check of a generated deck | `slide-qa` | These maps are **internal working artifacts**. They record judgements about named individuals at a customer, so do not hand them to the customer and do not paste them into a proposal deck. ## The eight pages All live in the `b2b-sales` pack (`slide-templates/b2b-sales/`). | Template | Answers | |---|---| | `influence-map` | Who has to be moved for this to get decided (two axes: influence × for/against) | | `buying-committee` | Who is involved, and how far have we gotten access to them | | `decision-structure` | In what order does approval move up, and where does it stall | | `discovery-map` | What is confirmed, and what is still a hypothesis | | `pain-chain` | Which executive-level number does the frontline problem actually move | | `discovery-gaps` | Who to confirm what with next | | `influence-map-org` |