The problem this solves
Call prep is the work everyone agrees matters and nobody protects time for. The meeting was booked a week ago, the calendar reminder fires fifteen minutes out, and the actual preparation happens in a frantic scan of the company homepage while joining the bridge. The rep walks in with a headline understanding, misses that the company just raised or just laid off, and burns the first ten minutes asking questions the prospect expects them to already know.
The information was never the constraint. The company's stack is visible, the hiring pattern is public, the funding is announced. The constraint is assembly: pulling five sources into one coherent read takes forty focused minutes, and forty focused minutes before every call is exactly what a busy pipeline does not allow. So prep quality tracks calendar luck rather than deal importance.
The unlock is making the assembled read as easy to get as asking for it. One message with a company name, two minutes later a brief you can absorb walking to the meeting: what they do, what they run, where they are hiring, what changed recently, the objection they will probably raise, and the one question that starts a real conversation instead of a pitch.
How the mission runs
- A company name is the entire request. You message the name or domain in the thread, exactly as it occurs to you before the call. No form, no fields. The agent treats the message as the mission trigger and starts assembling immediately, because the value of call prep decays by the minute at this point in the day.
- Four lenses assemble in parallel. Firmographics establishes who they are - size, model, market. Technographics reads the stack they run, which shapes what your product replaces or joins. Hiring Data shows where they are investing headcount, which is strategy said out loud. Web Research catches the recent moves: funding, launches, leadership changes, anything a prospect assumes you saw.
- The brief compresses to two minutes. The agent writes the read for absorption under time pressure: a tight paragraph on the company, the stack and hiring signals that matter for your pitch, likely objections given what they run today, and one opening question built from something specific and recent. Everything below that bar gets cut.
- It lands in the thread, ready to skim. The brief posts back where you asked, formatted for a phone screen because that is where pre-call reading actually happens. If a detail matters mid-read - who is the person behind the hiring spike, when exactly was the raise - you ask in the thread and the answer arrives with the brief's full context.
- The thread becomes your account memory. Prep for the same company twice and the agent knows it has seen them: the second brief leads with what changed since the last one. Over a quarter, the thread turns into a running research file on your active accounts, searchable and already in the conversation where you work.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A two-minute pre-call brief delivered in chat within minutes of your message: company overview from Firmographics, the stack via Technographics, hiring direction from Hiring Data, recent moves from Web Research, plus likely objections and one specific opening question. Ask for ten in a day and get ten. Repeat companies get a what-changed brief instead of a rerun.
Make it yours
- Wire it to your calendar rhythm: each morning, message the day's meeting list and get one thread per company, briefed in meeting order before your first call.
- Tune the lens to your sale: tell the agent once that you sell into finance teams, and every brief weights budget signals and finance-stack details over general company news.
- Add a post-call step: reply with two lines on how the call went, and the next brief on that account folds your notes into the read.
Frequently asked questions
How fresh is the information in the brief?
The brief is assembled at request time. Web Research runs live, and firmographic, technographic, and hiring reads reflect the current state of their sources rather than a cached profile. The agent timestamps recent moves so you can see at a glance whether a funding item is from last week or last year.
Can I ask follow-ups after the brief arrives?
Yes, in the same thread with full context. Questions like "who leads the team they are hiring for" or "compare their stack to the account from Tuesday" resolve against what the agent already researched, including earlier briefs in the thread. Short factual follow-ups are typically fast and cheap.
What does an average brief cost, and can I bound it?
A single brief is a small, predictable draw on the workspace meter - four data pulls and a synthesis. The same balance meters chat, email, and console work, so nothing hides. If you want a hard bound, set a per-mission threshold and the agent asks in the thread before any unusually deep dig.