In the gym, the approach to the bar is not incidental — it is deliberate.
You know your opener. You know your second and your third. You have studied
the competition. You walk up already inside the lift.
The Approach does the same thing before a sales call. Give it a company
name and a line of context. It researches the target across nine concurrent
source categories — company snapshot, leadership, financials, industry
context, social signal, tech stack, security events, demo prep, and discovery
— then renders a structured field brief. Two acts in one document: business
intelligence for the AE above the fold, technical depth for the SE below.
Brief structure
Two acts. One document.
Both halves travel together. Both get read before the call.
Act 01
The AE Half
Account executives
Business intelligence above the fold. Company snapshot, leadership and the buyer, financial posture, industry context, and recent signal — everything you need to open the call with authority and ask the right questions.
Sections
Company snapshot
Leadership & the buyer
Financial posture
Industry context
Recent signal
Act 02
The SE Half
Sales engineers
Technical depth below the fold. Stack and integrations, public security events, demo prep, and an opener with discovery questions grounded in real public signals — so the SE walks in with a plan, not a script.
Sections
Stack & integrations
Public security events
Demo prep
Opener & discovery
Who it's for.
Account executives
Company intel, leadership profiles, financial posture, and competitive context — before the deck, before the discovery script.
Sales engineers
Tech stack, public security events, and a demo prep section tied to what is already in their environment.
Founders doing outbound
Research and discovery questions without a full sales team. Walk into the first conversation already inside the lift.
Anyone in an important meeting
Not just sales. QBRs, executive sponsors, partner calls — any time walking in cold is not an option.
Built from public intel
MEDDPICC. Before the first call.
Every brief includes a MEDDPICC scorecard built entirely from public signals.
Each of the eight qualification dimensions gets a verdict — Confirmed, Partial,
or Unknown — with a specific next action attached. You walk in knowing what
you know, what you are guessing, and what you still need to find out.
MMetricsConfirmed
EEconomic BuyerPartial
DDecision CriteriaPartial
DDecision ProcessUnknown
PPaper ProcessUnknown
IIdentify PainConfirmed
CChampionPartial
CCompetitionConfirmed
Sample scorecard. Your actual brief reflects real public intel on the target company.
See it in action
The brief, before the call.
The Approach renders as a live HTML artifact in the Mission Built editorial
style — cream paper, oxblood accents, Oswald display type, Merriweather
body, JetBrains Mono for labels. No rounded corners. No drop shadows.
Reads like a field document, not a CRM screen.
Live demo · Example brief · Use ← → or the panel to step through
The Approach — interactive demo
How to use it
One connection. Every skill.
The Approach is part of the Loadout MCP server. One connection gives you every skill in the kit. Tested on Claude.
Server URLhttps://mcp.missionbuilt.io/sse
✓ Verified on Claude
Claude Code · CLI
If you have Claude Code installed, run this in your terminal:
claude mcp add loadout https://mcp.missionbuilt.io/sse
Claude · No CLI
Open Claude, then go to Settings → Connections → Add MCP Server. Paste the server URL above and save.
After you connect
Say this to get started.
Give it a company name and a line of context. The brief runs automatically.
Full brief"run the approach on [company]"
With context"approach for Acme — AE at Elastic, meeting VP of IT Friday"
Quick form"brief me on [company]"
Questions
Common questions.
Is any data stored?
No. Your brief is generated in memory and discarded after the artifact is built. Your seller config in APPROACH.md stays on your machine and is never committed.
What do I need to provide?
Just a company name and a line of context — who you are, who you're meeting, and when. The skill handles the rest across nine concurrent research batches.
Do I need to sign in?
Yes. The server uses Google OAuth. You authenticate once when you connect — no separate account creation required.
The Approach ships under MIT. Use it commercially, adapt it for your team,
embed it in your product. Source for both the skill and the MCP server lives in
github.com/missionbuilt/loadout.
Save your seller context once in APPROACH.md at your project
root. The skill reads it on startup and skips those intake questions on
every repeat run.
Know your opener. Walk up already inside the lift.