What a sales automation build includes, and what it should not
Six parts, two weeks, all in your own accounts. What a sales automation build should include, what to keep out, and the two things that stay manual.
By Saiful Islam Saif, Founder
· 6 min read
- Parts
- 6Data, enrichment, signals, sending, CRM, reporting
- Build time
- 2 weeksFixed scope
- Runs in
- Your accountsYou pay the tools directly
- Fee
- One-timeNo monthly fee, no markup on tools
- Kept manual
- 2 thingsWho to contact, the first message

In short
A sales automation build sets up the machine behind your outbound: where your lists come from, how they get checked and enriched, how signals reach you, how email and LinkedIn get sent safely, and how replies land in your CRM. Ours takes two weeks, runs in your own accounts, and you keep all of it.
- Sellers spend only 40% of their time selling. Automation should win back the other 60%, not replace the seller.
- A good build covers six parts: data, enrichment, signals, sending, CRM and reporting.
- It runs in your accounts. You pay the tools directly, so nothing is locked to the builder.
- Keep two things manual: choosing who to contact and writing the first message.
Why build it at all?
Because most of a seller’s week is not selling.
Salesforce, State of Sales report 2026 found the average seller spends just 40% of their time selling. Younger reps sit at 35%.
The rest goes to research, data entry, list building and admin.
- Selling40%
- Research, data entry, list building and admin60%
The rest is 100 minus 40. Younger reps: 35% selling.
Source: Salesforce, State of Sales 2026
Show the data as a table
| Activity | Share of time |
|---|---|
| Selling | 40% |
| Everything else | 60% |
Sellers expect AI agents to cut prospect research time by 34% and email drafting time by 36%, according to the same report. 54% say they have already used agents.
That is the job of a build. Take the boring hours off the table, so people spend more time talking to buyers.
What goes into the build?
Six parts. We build them with Claude Code, in your own accounts. Each one is set up, tested and written down.
- Data sources. Where accounts and people come from. Usually Sales Navigator plus one or two data tools. We match the sources to your markets, because a tool that is strong in the USA can be thin in Malaysia or Saudi Arabia.
- Enrichment and checks. Find the right person, verify the email, flag people who changed jobs, remove companies you already work with.
- Signals. Alerts for the events that matter to you: a new leader, a funding round, a hiring spike, a new office. They land in one place, not five inboxes.
- Sending. Separate sending domains, warmed inboxes, SPF, DKIM and DMARC. LinkedIn tools set to safe daily limits.
- CRM. Every contact, touch and reply logged in one place. Replies routed to the person who will answer them the same day.
- Reporting. One weekly view: who was contacted, who replied, which channel worked, what to change.
What should a build leave out?
This part matters as much as the list above.
- No AI that sends first messages on its own. AI can research and draft. A person should finish and send. We explain why in AI-written vs human-written outreach.
- No bought lists. A list you did not check is a list that burns your domain.
- No tool you will not use. Every extra tool is a bill and a login. If a step can live in a spreadsheet for now, it stays in a spreadsheet.
- No black box. If you cannot open it, read it and change it, it is not yours.
How do the two weeks run?
| Calendar days | What happens |
|---|---|
| 1 to 2 | Call on your buyers, your markets and what you use today. We agree the buyer profile and the signals. |
| 3 to 5 | Data sources, enrichment and checks set up. First 100 accounts built and reviewed by hand. |
| 6 to 8 | Sending domains, inboxes, LinkedIn tool and CRM connected. |
| 9 to 11 | Test runs on small batches. Fix what breaks. |
| 12 to 14 | Handover: written steps for every part, a recorded walk-through, and a live session with your team. |
Two weeks is enough because the scope is fixed. Most of the delay in these projects comes from scope that keeps growing.
Source: Fable InLead build plan, from the table above
Show the data as a table
| Stage | Days |
|---|---|
| Call | 1 to 2 |
| Data, enrichment, checks | 3 to 5 |
| Domains, inboxes, LinkedIn tool, CRM | 6 to 8 |
| Test runs | 9 to 11 |
| Handover | 12 to 14 |
Who pays for what?
The build lives in your own accounts. You pay the tools directly, at their normal price, in your name.
We charge a one-time build fee. No monthly fee, no markup on tools.
That split is on purpose. If the builder owns the accounts, you rent your own sales system. If you own them, you can change, grow or drop any part without asking anyone.
If you cannot open it, read it and change it, it is not yours.
Does data quality really matter that much?
Yes. It is the part people skip.
Salesforce, State of Sales report 2026 reports that 79% of high-performing teams prioritise data hygiene, against 54% of underperformers. A fast machine fed bad data just gets you to the wrong people faster.
That is why the build has a check step before anything is sent, and why the first 100 accounts are reviewed by a person.
Who is it for?
Teams that want to own their outbound and have someone to run it. A founder who sells, a small sales team, or an in-house SDR who needs better tools.
If you do not have anyone to run it yet, a managed service is the better start. A consulting firm in Malaysia with too few people left to sell got 91 high-value meetings in one year that way. A build makes sense once there is a person ready to take the wheel.
Questions people ask
How long does a sales automation build take?
Ours takes two weeks with a fixed scope. Bigger setups with several markets or a CRM move can take longer, and we say so before we start.
Do I need to buy new tools?
Usually a few, but we start from what you already pay for. You buy any new tools yourself, in your own name, at normal prices.
What happens after the handover?
You run it. You get written steps, a recorded walk-through and a live session. Support after that is optional, not a lock-in.
Can the system write and send messages by itself?
It could, but we do not set it up that way. A person reviews, approves and sends every first message. That is where replies and trust come from.
Sources
Every figure above is from these sources or from our own build plan, as the article says.



