Docs

Use cases

Eight GTM use cases for the Amdahl learning model, from outreach to win/loss, each mapped to the calls that serve it today, what your code gets back, and where to start. Outreach needs no connected data.

The Amdahl learning model serves eight GTM use cases: outreach, positioning, ads, content, sales call prep, account-based expansion, churn risk, and deal research and win/loss. Outreach is one of them, and the only one that needs no connected data. Each row below names a job, the calls that serve it today, and what your code gets back.

Outreach

Amdahl writes and optimizes email and LinkedIn messages. Your agent sends what it knows about the recipient, and Amdahl returns the message, evaluated before anything ships.

JobCallsYou get backNeeds your dataStart with
Write one message from what you know about the recipientThe optimize call (messages.optimize)One messageNoOptimize a cold email
A whole campaign: one message per recipient, from a CSV of what you knowThe optimize call, once per recipient, or a batchOne message eachNoOptimize a campaign
The writer behind an AI SDR or any code that sendsThe optimize call between the code that knows the recipient and the send queue, with a fallbackOne message, or a fallbackNoOptimize before you send
Keep the sender's voice and house rules in every messageThe optimize call with context (facts, rules, voice_examples)One messageNoKeep your voice, rules and facts
Evaluate every claim against your customers before a message goes outThe optimize call with evidence: "workspace", which lists them in unsupported_claimsOne message and the claims nothing backsYesEvaluate claims against your customers
Grounded outbound: a first touch in your buyers' own wordsSearch (semantic, hydrate: true) for the pain, then the optimize call with evidence: "workspace", then an evaluation of the resultQuotes, then a message, then an evaluationYesOnboarding skill, use case A
Evaluate a draft: every criterion passed or failed, with a reason for eachThe optimize call with mode: "grade" and evidence: "workspace"An evaluationYesEvaluate a cold email
Optimize before it ships: evaluate what an AI SDR wrote before it sendsThe optimize call with mode: "grade", read on grade.passes_barA send or hold decisionNoOptimize before it ships
Sequence review: every step of a live sequenceOne evaluation per step, then read the criteria across stepsOne evaluation per stepNoEvaluate a cold email
Prompt tuning: improve the prompt your team or agent writes fromoptimize_prompt in improve mode, then get_prompt_run for the held-out liftA revised prompt, only when it wrote better emailNoImprove a prompt
Writing-quality trend across a teamMany evaluations, logged and aggregated by youYour own trend lineNoEvaluations as a trend

Positioning

JobCallsYou get backStart with
What closed-won accounts pushed back onSearch (filter on deals), then Search (semantic, scoped to those companies)Quotes from the accounts that boughtCohort, then voice
How customers describe the problem, in their wordsSearch, mode: "semantic" with hydrate: trueQuotes with their sourceSearch
Whether anyone named a competitor or a featureSearch with the term in double quotesEvery exact mentionSearch modes

Ads and content

Amdahl optimizes email and LinkedIn messages today. For ads and content, it gives the agent that writes them your buyers' own words.

JobCallsYou get backStart with
Buyer language for an ad or a postSearch, mode: "semantic" with hydrate: true, on the pain or the outcomeQuotes with their source, for your agent to write fromSearch
The proof points customers actually repeatSearch, filter on closed-won deals, then semantic on those accountsQuotes from customers who boughtCohort, then voice

Sales call prep

JobCallsYou get backStart with
Prep for a meeting with an accountOne research job on the accountOne cited answerResearch

Account-based expansion

JobCallsYou get backStart with
Accounts in a segment or stage, and what they saidSearch (filter on accounts or deals), then Search (semantic, scoped to those companies)A list of accounts, then their quotesCohort, then voice
Everything known about one account before you reach outOne research job on the accountOne cited answerResearch

Churn risk

JobCallsYou get backStart with
What current customers said about pricing, a competitor or a gapSearch (semantic, scoped to customer accounts), and exact terms in double quotes for namesQuotes with their sourceSearch

Deal research and win/loss

JobCallsYou get backStart with
ICP and win/loss research that needs synthesis over your own conversationsOne research job on the questionOne cited answerResearch
Funnel and pipeline questions: counts, win rates, cycle time by segmentSearch, mode: "filter" with group_by and metricsNumbers, with the SQL that produced themSearch

What every use case but outreach needs

Two limits apply to every row that reads your processed customer data. That is every row on this page except outreach evaluated without your data.

  • It needs synced conversations. A workspace with none returns empty searches, an evaluation's four evidence criteria abstain, and an optimize call with evidence: "workspace" falls back to an evaluation without your data. Check GET /search/overview first.
  • CRM presence is not a commercial relationship. CRMs create company records from inbound mail, so your data holds vendors, recruiters and press alongside buyers. For ICP, voice-of-customer and win/loss questions, scope to accounts with at least one call or deal, and say that you did.