Workspace 05 · Capability Explorer
Your engineers built the capability. Now translate it into what a buyer will fund.
Capability Explorer is the pre-sales translation layer: structure what you actually do into a taxonomy, map every capability to a business outcome and KPI a CFO would sign off, and ship one-pagers that say exactly what you deliver — and, just as deliberately, what you don't.
3-level capability taxonomy
12-term jargon translator
2×2 impact × feasibility scoring
6 pre-sales tools, one workspace
The problem
Engineers speak features. Buyers buy outcomes. The gap is where deals stall.
Pre-sales lives or dies on translation. When the story on the page is a spec sheet, the economic buyer can't do the math — and "we'll circle back" quietly becomes no-decision.
✕
The jargon buries the value
Your deck says "RAG over a vector DB with an agentic workflow." The CFO hears noise, can't tie it to a P&L line, and mentally files you under "science project." The value was real — the framing killed it.
✕
No two people tell the same story
The founder pitches one thing, the SE another, the one-pager a third. Positioning drifts across every call and deck, so the buyer never hears a crisp, repeatable claim — and discounts to compensate for the confusion.
✕
You pitch everything, so you win nothing
With no explicit NOT-list, every one-pager implies you do it all. That wins the bad-fit deal, then bleeds it back in delivery pain, reference damage, and scope creep that starts at the pitch.
What's inside
Six tools that turn raw capability into buyer-ready narrative.
Everything hangs off one taxonomy — build it once, and the value mapper, use-case engine, comparisons, one-pagers and boundary maps all draw from the same source of truth.
🗂️
3-level capability taxonomy
Structure what you do into Domain → Capability → Feature, with an honest maturity rating on every capability. One tree the whole team can point at.
🔤
Value mapper + jargon translator
Run each capability through the translation chain — technical → plain English → business outcome → CxO phrasing → KPI — backed by a 12-term jargon translator (RAG, vector DB, agentic workflow, MLOps, zero-trust, digital twin…).
🎯
Use-case discovery
Generate candidate use cases by industry and function, then score each one on an impact × feasibility 2×2 quadrant so you chase the deals worth the calendar time.
⚖️
Weighted stack-comparison matrices
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-pager studio
Assemble capability one-pagers for a specific persona and industry: the problem, plain-English explainer, outcomes with a KPI, proof, and a clear call to action.
🧭
Solution-boundary maps
Per capability, three honest lists: in-scope (you deliver it), adjacent (with a named partner), and out-of-scope (you decline). Boundaries travel into every one-pager automatically.
How it works
Structure it, translate it, prioritize it, ship it.
Manual mode is free and needs no API key. Turn on assisted mode with your own key when you want the translation chain and use-case ideas drafted for you.
Structure
Build your capability taxonomy — Domain → Capability → Feature — and rate the maturity of each capability honestly. This becomes the spine everything else reads from.
Translate
Push each capability through the value chain to a business outcome, CxO phrasing and a KPI. The jargon translator swaps every technical term for one clean business sentence. Manual, or assisted with your key.
Prioritize
Discover use cases by industry and function, score them on the impact × feasibility quadrant, and build weighted comparison matrices so the shortlist defends itself.
Ship
Generate the one-pager and boundary map for a named persona, then export. What you deliver — and what you decline — reads the same in every deck and email.
Sample output
A capability one-pager the CFO can actually read.
This is the money shot — a real artifact the one-pager studio produces. Note how the same capability is stated in plain English, tied to a KPI, and fenced with an explicit NOT-list.
rag-regulatory-intelligence · one-pager.md
Capability one-pager · For: Chief Compliance Officer, mid-cap financial services
RAG-based Regulatory Intelligence
Always-current answers to "what does this rule require of us?" — sourced only from your own regulatory corpus, with a citation on every line.
The problem
Regulations move faster than your analysts can re-read them. Circulars, consultation papers and amended handbooks land weekly across jurisdictions. Teams answer new obligations from memory or from a PDF that was current two quarters ago — and a single missed clause becomes a remediation program, a fine, or a headline.
What it is, in plain English
A private assistant that reads your regulatory library and answers questions in your own policy language. Ask "does the new circular change our client-onboarding checks?" and it replies with the specific obligation, the source document, the effective date, and the paragraph it came from. It never answers from anything outside your approved corpus.
How it works — in 3 steps
1. Ingest — your circulars, handbooks and internal policies are indexed into a searchable, access-controlled library. Nothing leaves your tenancy.
2. Retrieve — every question pulls the exact passages that apply, filtered by jurisdiction and effective date, so the answer is grounded in real text, not a guess.
3. Answer with citations — a plain-language response with a source link on every claim, ready to paste into a memo or an audit trail.
Business outcomes
• Analysts answer obligation questions in minutes, not days — research load down materially per query.
• Every answer is audit-defensible: source, clause and date attached by default.
• New regulations are triaged the week they publish, not the quarter they bite.
Headline KPI → Time-to-answer on a regulatory query: from ~2 days to under 10 minutes.
What it is NOT
✕ Not legal advice — it surfaces and cites the source; a qualified human still signs off.
✕ Not a public chatbot — it answers only from your approved corpus, never the open web.
✕ Not a rip-and-replace of your GRC platform — it plugs alongside it as the read-and-explain layer.
Next step → 30-minute working session on your top 3 regulatory pain points. Reply to book.
Who it's for
Anyone whose job is to make technical capability legible to a buyer.
Pre-sales & solution engineers
Walk into every call with one taxonomy, one story and one honest boundary map — so the SE, the AE and the deck all say the same thing.
Product marketers
Turn a roadmap of features into outcome-led narrative, complete with the KPI and CxO phrasing a buyer's finance team will accept.
Solution consultants
Score use cases on impact × feasibility and defend the shortlist with weighted comparisons instead of hand-waving.
Technical founders
Stop pitching the architecture. Say what you do in a sentence a CFO funds — and get explicit about what you decline, before it becomes scope creep.
Pricing
Start free. Upgrade when the workspace is doing real pre-sales lifting.
Manual mode is free forever and runs entirely in your browser. Paid tiers add assisted drafting, a done-with-you pre-sales package, and white-label for teams who resell it.
Subscription
Practitioner
Free / manual mode
Then from $19/mo for assisted mode with your own key
- Full 3-level taxonomy builder
- Value mapper + 12-term jargon translator
- Impact × feasibility use-case quadrant
- One-pager studio & boundary maps
- Runs locally — your data stays in your browser
Open the workspace →
Pre-sales package
Pre-sales Team
from $2,500 / engagement
Done-with-you setup, indicative
- Everything in Practitioner
- We build your taxonomy & value maps with you
- Persona-specific one-pager set, drafted together
- Comparison matrices vs your real competitors
- Boundary maps to stop scope creep at the pitch
- Team walkthrough so the story stays consistent
Book a working session →
White-label
White-label
Let's talk
For agencies & platforms reselling it
- Your brand, your domain
- Deploy the workspace to your clients
- Pre-loaded taxonomy templates by vertical
- Priority support & roadmap input
- Commercial terms set per partnership
Enquire →
Figures are indicative starting points, not final quotes. Actual pricing is set by the owner per engagement — the numbers above frame the model, not a contract.
FAQ
The questions pre-sales teams ask first.
Do I need an API key to use it?
No. Manual mode is completely free and needs no key — you build taxonomies, value maps, one-pagers and boundary maps yourself. Assisted mode, which drafts the translation chain and use-case ideas for you, uses your own AI key so you stay in control of cost and provider.
Where does my data live?
In your browser, on your machine. The workspace runs client-side and stores your taxonomy, mappings and one-pagers locally — nothing is uploaded to a server we run. Your capability data and competitive comparisons never leave your device.
Can my team use it together?
Yes. The point of the taxonomy is a single source of truth the whole team reads from, so the SE, the founder and the deck all tell the same story. The Pre-sales Team package includes a walkthrough to get everyone aligned, and white-label lets you deploy it across an org under your own brand.
Is it hosted, or do I run it myself?
Today it runs in your browser with no backend to manage — open the page and go. A hosted, multi-seat option with shared team libraries is on the roadmap; white-label partners get early access as it lands.
How do I start?
Open the workspace and load the starter data — a boutique AI & Quality Engineering team modelled with domains, capabilities, scored use cases and a comparison matrix. It merges by name and never overwrites your work, so you can replace it with your real capability stack as you go.
Say what you do in a sentence a CFO funds.
Structure your capabilities, translate them into outcomes and KPIs, and ship one-pagers that draw the line between in-scope and out. Free to start, in your browser.
Open the workspace →
The platform
Part of a five-workspace platform
Capability Explorer is one workspace in the GTM Intelligence Platform. Each sells and delivers a different slice of go-to-market — and they share the same taxonomy of who you are and what you do.