New Ask Mabry drafts, edits and checks the work. Your people approve it. See it →
Home›Industries›Manufacturing and industrial tech playbook
Industry playbook · 11 of 12 · Manufacturing and industrial tech

A new plant tells you who is building pipeline.

An illustrative playbook, drawn from how the architecture behaves in this kind of motion. Not a client case study.

Demo data
Signal card
83
Industrial equipment makerExpansion · GTM reset
Ready

The company announced a new plant and hired a VP of Sales from a software company. Its go-to-market is being rebuilt this year.

Why score 83Press release · window opens this quarter · high confidence
Verified decision-makerVP of Sales · verified

The situation, and what changes.

The situation

Technical buyers, long evaluations and few public signals. A go-to-market reset, a new plant or a new-market entry tells you who is building pipeline now.

What changes

Expansions and leadership changes surface with the source attached, routed to the rep who owns the territory, with the opener drafted for a technical reader.

Signals watched

  • GTM resets and restructuring
  • Expansions and new sites
  • New-market entry
  • GTM tooling adoption

Systems deployed

  • Expansion and new-site watch by territory
  • Account plans for long, technical evaluations
  • Battlecards when a competitor shows up on a lead
  • Drafts written for technical buyers

Signal → Route → Act → Measure.

Agents watch for the events that matter (Signal), decide who should act on each one (Route), do the work with a person making every send (Act), and log what happened so results are traceable (Measure). The same framework runs every engagement.

Act now: who to call this week Scored, sourced and verified. Nothing goes out until your team decides.
The account plan keeps itself current MEDDPICC gaps, buying group, competition and the next step.
Battlecards on the lead When a lead names a competitor, the play shows up on the lead.

One agent, one job.

Every build gets the agents its failure patterns demand. Each is scoped the same way: one task, bounded permissions, its own log. The person is the only sender.

Read only · one account
HunterThe Watchman · Monitor agentWatches one account's market surface and posts findings to the account's thread. Nothing else.
Score and route only
FelixThe Fixer · Triage agentScores each finding for urgency and fit and routes it to the owning rep with context. Decides priority, never content.
One trigger per run
SloaneThe Sleuth · Research agentBuilds the context pack for one trigger: what happened, why it matters, what angle is credible.
Block or clear · no outreach
GrantThe Gatekeeper · Conflict check agentChecks the shared ledger for ownership, current-customer status, open threads and suppression, from the lists your team supplies. It never reads your CRM.
Verify or discard
VeraThe Verifier · Enrichment agentResolves one verified contact, cross-checked against more than one source. A pattern guess is a failed run, not a fallback.
Draft only · cannot send
QuinnThe Wordsmith · Draft agentWrites one email per contact in the team's voice. No invented facts, no unsourced claims.
Self-audit pass
ReedThe Red Pen · Review agentRe-reads the run's output before delivery, checks the rules held, and logs what it changed.
Final authority
YouThe person who approvesThe only sender in the system. Every draft arrives as a click-to-send package: review, edit, send or discard.

Built to pass the meeting after the demo.

01
Your workspace, your tokensAnything that touches your systems runs on your own connectors. We hold none of your credentials.
02
One engine, one interfaceFinished work arrives through one scoped connection. Your conversations never leave your workspace.
03
A person approves everythingEnforced in the system, not by policy.
04
You hold every keyAccess is granted by you and revocable by you.

The trust architecture →

Other playbooks.

Financial services

A new mandate hits hundreds of covered accounts at once.

Insurance

Renewals defended late, expansion started later.

Software and AI

Ten reps covering a market of thousands.

Fintech and data

Deals that win the business and die in procurement.

AI-native startups

Founder-led selling at full capacity.

Regulated enterprise

A board mandate meets a skeptical security team.

Credit unions

A merger resets the vendor list overnight.

Healthcare and healthtech

Wide buying committees, short windows.

Higher education

Budget cycles are fixed. The window isn't.

Public sector

The bid arrives with a clock.

Professional services

The firm that notices first earns the next engagement.

Every playbook on this site is illustrative: drawn from how the architecture behaves, not from a client engagement. Names, figures and sequences are representative.

Start here

Show us where the work piles up.

In one working session we'll show you what agents would do with it, on your accounts, before you spend anything. If we're not the right fit, we'll say so in the first reply.