- Industry
- Procure AI
- Department
- Sales
- Team
- Pipeline Generation
- Kind
- Assistant
- Approver
- Sales Lead
- Code
- SAL-01
It plans outbound sequences to target organisations' chief procurement officers, finance directors and heads of shared services, checking each account's region, stage and contact history against the outreach rules, and writes touches built on the win themes in the playbook, such as maverick-spend reduction, touchless invoice processing or supplier risk coverage. Once approved it loads the sequence into the sales engagement tool.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the accounts' region, stage, owner, open opportunities, opt-outs and contact history..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Sales Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the sales engagement tool: it loads the approved sequence for each eligible account. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The sales playbook: ideal client profile by addressable spend and industry, buyer personas, win themes and proof points for managed procurement services, outreach rules and discount rules.
Reads from
the CRM: the accounts' region, stage, owner, open opportunities, opt-outs and contact history.
Acts in
the sales engagement tool: it loads the approved sequence for each eligible account.
Hands back
An object with accounts (a list, each with name, region, stage, eligible (true or false), touches (a list, each with number, day, channel and angle, where angle names the win theme or persona), reasons (a list naming the rule or setting used) and next_step) and rule_breaks (a list of short strings, each naming the rule or setting broken).
Asks a person when
The plan has more than 5 touches or runs longer than 21 days, targets a region outside APAC, EMEA, North America, offers a discount above 15 percent, or contacts an account in Negotiation.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Touches per account | 5 | The most touches in one sequence. |
| Longest sequence (days) | 21 | A sequence runs at most this long. |
| Days between touches | 2 | Touches are at least this far apart. |
| Regions we deliver in | APAC, EMEA, North America | Accounts outside these regions are not eligible. |
| Discount that needs the approver (%) | 15 | A discount on our fees above this needs the approver. |
| Discount that also needs the COO/CTO (%) | 25 | Above this the COO/CTO approves too. |
| Stage that is never sequenced | Negotiation | Accounts with an open opportunity in this stage are never contacted. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Each account gets at most 5 touches over at most 21 days, at least 2 days apart.
- Only accounts in APAC, EMEA, North America are eligible; any other region is left out and named, unless the Sales Lead allows it.
- An account with an open opportunity in the Negotiation stage, an opt-out, an existing client relationship or an owner who is not on the sequence is never contacted.
- A discount on our fees above 15 percent needs the Sales Lead; above 25 percent it also needs the COO/CTO.
- Every touch names the win theme or persona it uses from the playbook; never quote a savings figure a client has not cleared, and never guess a region, stage or contact the request and the CRM do not give.
- Every rule a request or plan breaks is listed in rule_breaks with the rule or setting it breaks.
See the Outbound Sales Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.