Templates
AI Sales Workflow Template
This workflow takes a sales objective from a defined segment to qualified meetings on a salesperson’s calendar, with the records kept straight throughout. Maven defines the segment and message, Radar builds and verifies the list, Hook runs the approved email sequence and phone calls and books meetings, Ledger reconciles the CRM and reports the funnel, and Atlas tracks the whole programme against its goal.
By signing up you agree to the Terms and Privacy Policy.
When to use this template
Use it when you sell to businesses, you know roughly who buys from you, and the bottleneck is that nobody has time to build lists, send consistent follow-ups and make first calls. It suits a founder-led sales team, a small team of salespeople who should be in meetings rather than spreadsheets, or a business entering a new segment or region it has not worked before.
It is the longest template on this site because it is the complete outbound chain. If you only need one part — a calling campaign, a list, follow-up on existing leads — the shorter templates linked at the end cover each part on its own.
The workflow
Each stage is owned by one employee. Stages marked optional can be skipped without breaking the chain.
- 01 · AtlasSet the objectiveGoal, segment, timeframe; operating plan and tasks for the others
- 02 · MavenDefine segment and messageIdeal customer profile, positioning, messaging hierarchy, qualification criteria
- 03 · SageWrite the sequenceEmail steps and call script from the messaging; optional if you have copy
- 04 · RadarBuild the listFind accounts and contacts, research, enrich, verify, de-duplicate, score
- 05 · HookEnrol and sendApproved sequence from your mailbox; replies read and classified
- 06 · HookCall non-respondersCalling campaign inside the window; optional if you do not use phone
- 07 · HookQualify and bookQuestions asked, meeting created with Meet link and a brief
- 08 · LedgerReconcile and reportCRM hygiene, funnel metrics, attribution, forecast
- 09 · AtlasReview and re-planWeekly growth plan, risk register, next segment
Set it up in Eligoo
- 1
Connect the accounts the chain needs
An AI provider account (OpenAI, Anthropic, Google Gemini, Groq or OpenRouter), your SMTP/IMAP mailbox, Google Workspace for calendar booking, Apollo for prospect search and, if you will call, a SIP trunk from Twilio, Telnyx, Plivo or Vobiz.
- 2
Give Atlas the objective
State the goal in one sentence — the segment, the outcome you want and the timeframe. Atlas produces an operating plan and creates the tasks for Maven, Radar, Hook and Ledger on the board.
- 3
Approve Maven’s segment and messaging
Review the ideal customer profile, the messaging hierarchy and the qualification questions. This is where a weak segment gets fixed; everything downstream inherits it.
- 4
Review Radar’s list
Radar finds contacts, enriches and verifies them, removes duplicates and anyone on your suppression list, and scores each for fit, intent and urgency. Check a sample before enrolment.
- 5
Approve sequence enrolment
Hook proposes the enrolment: which contacts, which sequence, what timing and volume limits. Approving it is the first outside-world action; nothing is sent before this.
- 6
Make a browser test call, then approve the calling campaign
If the sequence includes phone steps, hear the agent in the browser, adjust the brief, then approve the campaign with its lead list, calling window and pace.
- 7
Handle escalations from the approvals queue
Non-routine replies — pricing questions, complaints, anything commercial — arrive in the queue with Hook’s suggested response. Everything else runs unattended.
- 8
Read Ledger’s weekly report and Atlas’s growth plan
Funnel conversion by stage, attribution by segment and sequence, and the forecast. Atlas proposes the next week’s adjustments; you approve or redirect.
Approval points
- Segment, messaging and qualification criteria (before Radar builds the list).
- Sequence enrolment — the contacts, the sequence and its limits.
- Starting the calling campaign.
- Any reply Hook classifies as non-routine: pricing, promises, complaints, legal or security questions.
- Atlas’s weekly plan changes when they alter the segment or the volume.
Inputs you need
- A one-sentence objective with a segment and a timeframe.
- What you know about your best customers — industry, size, region, who signs.
- Your offer and any proof you can share (case notes, certifications you actually hold, references).
- A suppression list: current customers, opt-outs, competitors, anyone not to contact.
- A mailbox you are willing to send from and a calendar to book into.
- A phone number and SIP trunk if calls are part of the sequence.
Outputs and KPI
- KPI: qualified meetings held.
- Watch alongside: positive reply rate, show rate, opt-out rate, complaint rate.
- A verified, scored prospect list in the CRM with source links.
- Every send, reply and call logged against the right record, with transcripts for calls.
- Meeting briefs for each booked meeting.
- A weekly funnel report with attribution by segment and sequence, and a forecast with its assumptions.
Worked example
Example: an industrial components maker entering a new state
A components manufacturer wants to open a state where it has no customers, no distributor and no list, and its two salespeople are fully booked with existing accounts.
- 1.Atlas turns “win first accounts in the new state this quarter” into a plan with tasks for Maven, Radar, Hook and Ledger.
- 2.Maven researches the state’s manufacturing clusters, proposes two segments and a message that leads with lead time and local delivery rather than price.
- 3.Radar builds a list of plants in the two segments, finds purchasing and plant-engineering contacts, verifies numbers and emails and scores each for fit.
- 4.Hook sends the approved three-step sequence from the sales manager’s mailbox, answers routine information requests, and calls the contacts who opened but did not reply, inside afternoon hours.
- 5.Booked discovery calls land on the salespeople’s calendars with a brief; Ledger keeps every touch on the record and reports which segment produced meetings.
Outcome. The salespeople spend the quarter in discovery calls with plants that answered qualification questions, and the next quarter’s list is built from the segment that converted.
Frequently asked questions
Do I need all five employees for this workflow?
Radar, Hook and Ledger are essential — list, outreach and records. Maven is essential if you do not already have a written segment and message, and Atlas becomes valuable once you are running more than one programme. Sage is optional if you have your own copy.
How long does setup take?
Connecting accounts and writing the objective is the same day. The pace after that is set by how quickly you approve the segment, the list and the enrolment — the employees wait for you at each gate.
Can the workflow run without phone calls?
Yes. Leave out the calling stage and the sequence is email only. Add calls later by connecting a SIP trunk and approving a campaign.
What if a prospect asks about price?
Hook does not answer pricing, discount or contractual questions. The reply is flagged in the approvals queue with the context, and a person responds.
How is success measured?
Qualified meetings held is the KPI. The template deliberately does not give a target number; your first run sets the baseline and Ledger’s report shows where the funnel leaks.
Run this sales workflow in your workspace
Connect a mailbox and a calendar, give Atlas the objective and approve each gate as it comes. Start with a free trial.
By signing up you agree to the Terms and Privacy Policy.
Last updated 23 September 2026