Everything in this workspace hangs off one taxonomy. Build it once; the value mapper, use-case engine, comparisons, one-pagers and boundary maps all draw from it.
Every tool here moves a capability one step further along this chain — from something an engineer recognizes to something a CFO will fund. Skipping a link is where technical sales stall.
How much of your capability stack is buyer-ready. A capability without a value map is invisible to budget holders; one without boundaries invites bad-fit deals.
⌥ Capability Taxonomy
Structure what you do into Domain → Capability → Feature, with an honest maturity rating on every capability.
⇄ Value Mapper
Run each capability through the six-link translation chain — plus a jargon translator a CFO would accept.
◈ Use-Case Discovery
Generate candidate use cases by industry and function, then score them on an impact × feasibility quadrant.
▦ Stack Comparison
Weighted matrices comparing your approach against alternatives and the status quo — presented without bias.
▤ One-Pager Studio
Assemble capability one-pagers for a specific persona and industry: problem, outcomes, proof, boundaries, CTA.
⬡ Solution Boundaries
Say what you do, what you do with partners, and what you decline — and qualify out bad-fit deals early.
Three levels: Domain (a budget conversation) → Capability (a sellable promise) → Feature / asset (the proof you can keep it). Rate each capability's maturity honestly — Emerging you're building it, Established you deliver it repeatably, Differentiating you win deals because of it.
For any capability, complete all six links: technical description → what it does in plain words → the business outcome → how a CxO would say it → the KPI it moves → the proof point. A mapping with a weak link produces a pitch with a weak link.
Click edit to load a row back into the form above.
Reference library. Each technical term translated into one business sentence with no residual jargon. Use the copy button and paste straight into decks and emails.
Paste anything an engineer wrote — architecture notes, a README, a capability blurb — and get it back at three altitudes: engineer, director, CxO.
Point your capability stack at a specific industry and function, state how badly it hurts, and generate eight candidate use cases with impact × feasibility scoring — workshop-readout quality.
Track the use cases you decide to pursue. Score impact and feasibility 1–5; the quadrant below updates live.
Score = impact × feasibility. Statuses: idea → validated → in-market.
Top-right = quick wins (sell these first). Top-left = strategic bets (needs sponsorship). Bottom-right = fill-ins (bundle, don't lead). Bottom-left = deprioritize. Click a dot to edit.
Weighted, criteria-based comparisons of your approach vs alternatives vs the status quo. Honest scoring is the point — a matrix where you win every row convinces no one.
One capability, one persona, one page. Fill the fields (or pull them from your value maps and boundaries), preview the page, then export DOC / PDF or generate fully polished copy.
Load one back into the studio to iterate or export.
Per capability, three honest lists: what you deliver yourself, what you deliver with a named partner, and what you decline. Boundaries are stored on the taxonomy node, so they travel into one-pagers and generators automatically.
- Trust transfers. A vendor who names what they don't do earns belief in what they claim they do. "We don't do X — for that, we bring in a partner" is the single most credibility-building sentence in a first meeting.
- Bad-fit deals cost triple. You pay in delivery pain, in reference damage, and in the good deal you didn't staff. A boundary map is a disqualification tool as much as a sales tool.
- Scope creep starts at the pitch. Most "descope conversations" trace back to a one-pager that implied more than the team can deliver. Write the NOT-list before the outcomes list.
- Adjacency is a strategy, not an apology. The partner column is where tomorrow's capabilities incubate. Review it quarterly: what should graduate to in-scope, and what should be dropped entirely?