Sales Automation Software for Small Business: Four Buys
One search returns four unrelated products, and on at least one vendor's published plan list the automation is gated above the tier a small team buys.

Sales automation software for a small business is four separate purchases: a CRM with a workflow engine, a sending and sequencing layer, a scheduling tool, and a connector that moves records between systems. They are not substitutes. Decide which one your bottleneck sits in before comparing products, and check whether automation is gated above your tier.
Key takeaways
- Close's pricing page carries the line Workflows not included against both its Solo and Essentials plans, so the automation begins at the third tier up.
- Pricing structure names the buyer: Close and Calendly charge per seat, Zapier charges by task volume, and Keap publishes a bundle that includes two user licences.
- Seat-priced tiers multiply by headcount while task-priced tools do not, which is why the cheaper total is frequently the one with two products in it.
- HubSpot, Pipedrive and Zoho could not be quoted here because their pages served no text, refused the fetch, or rendered another currency on 2 September 2026.
Reviewed and updated September 2, 2026
Close publishes the words "Workflows not included" against the two cheapest plans on its own pricing page, fetched on 2 September 2026. That same Close page publishes the Solo plan at $19 per user per month billed monthly or $9 billed annually, and the Essentials plan at $49 monthly or $35 annually. Workflows are the automation. A small business shopping this category on price lands on exactly the tiers where the thing it came for has been removed.
That is not a criticism of Close, which is unusually clear about it. It is the shape of the whole category, and it is the first thing worth knowing before comparing anything.
One search, four different purchases
"Sales automation software" returns products that do four unrelated jobs. They are sold as alternatives and they are not substitutes for each other. A team that buys the wrong one solves a problem it did not have and still has the one it did.
- Stores the pipeline and fires rules when a record changes
- Automation is routinely gated above the entry tiers
- Buy here when: nobody has a reliable record of who was contacted and when
- Fails when: the fields the rules read are filled in inconsistently
- Sends from mailboxes, tracks replies, manages sending reputation
- Priced around mailboxes and volume rather than around seats
- Buy here when: origination is the constraint and the list is the input
- Fails when: it is bought to fix a targeting problem
- Watches one system and writes into another on a trigger
- Priced by task volume rather than by headcount
- Buy here when: the same copy and paste happens every week
- Fails when: it becomes undocumented infrastructure nobody owns
Scheduling is the fourth and the least contested. It turns an availability exchange into a link and a confirmation, it is priced per person who needs a calendar connected, and it is worth buying when booking friction is measurably losing conversations rather than because the link looks tidy.
Most small businesses need two of these and buy one. The two are usually a CRM whose automation tier is switched on, and whichever of the other three matches the actual bottleneck.
What the published rates say about who each product is for
Pricing structure tells you what a vendor thinks it is selling, and it is more informative than a feature list.
Close prices per user per month and publishes both billing states on one page: Solo at $19 monthly or $9 annually, Essentials at $49 or $35, Growth at $109 or $99, and Scale at $149 or $139, all as published on 2 September 2026. The interesting part is not the numbers. It is that the plan feature lists for Solo and Essentials both carry the line "Workflows not included", so automation begins at Growth. A vendor charging per seat and gating workflows above the small-team tiers is telling you it sells rep productivity first and automation second.
Keap prices the opposite way. Its pricing page, fetched the same day, publishes $299 a month, billed at $2,988 a year. That page states "Keap starts you off with 2 user licenses" and that "Additional users can be purchased for only" $39 a month each. Usage beyond the plan allotment is published on the same page at $0.015 per text message and $0.01 per voice minute, and the page states that cancelling an annual contract before the end of the term incurs a $299 early termination fee. A bundle with two seats included and per-message overage is a product sold to an owner-operated business as a single line item rather than to a sales team as a seat count.
Zapier prices neither of those ways. Its pricing page publishes a free tier whose own description is "Start automating with AI" at $0 a month including 100 tasks per month, a Professional plan starting from $19.99 a month, and a Team plan starting from $69 a month, all read from that page on 2 September 2026, which renders a currency selector including US dollars. Task-based pricing scales with how much moves between your systems, which has nothing to do with how many people you employ.
Calendly's pricing page publishes Standard at $10 per seat per month and Teams at $16 per seat per month, noting on each that "Seats are required for users to connect calendars", with the billing toggle on that page defaulting to the monthly state. That page publishes its Enterprise tier as starting at $15k per year and at 50 seats, which is a useful boundary marker for a small team.
- The total multiplies by the number of people who need a login
- Upgrading a tier to unlock one feature upgrades everybody
- Cheapest at one or two people and the steepest curve after that
- Ask: how many of these logins are actually load bearing
- One line item covering several jobs, with a small seat allowance
- Overage is metered separately on messages and call minutes
- Predictable until usage moves, then the bill has a second axis
- Ask: what the annual commitment costs to leave early
- The total tracks how much data moves rather than headcount
- Adding a colleague changes nothing about the bill
- A free tier exists and stops at the point the tool becomes useful
- Ask: how many runs a month the real workflow produces
Three vendors whose figures are not in this article, and why

Absence here is a property of the fetch rather than of the vendor, so it is worth stating precisely.
HubSpot's sales pricing page returned almost no visible text to a plain browser-agent fetch on 2 September 2026, so no figure could be read off the bytes it served. Pipedrive's pricing path refused that same fetch with an HTTP 403 while its other paths have served in the past, which is a property of that one path on that day. Zoho's CRM pricing page arrived in full and served its four CRM plan tiers in Indian rupees on a page carrying a currency selector, so the dollar rate a US buyer sees was not in the bytes this fetch returned.
None of that means those products are unsuitable, and all three appear on every competing list for this term. It means their current rates have to be read from the page in your own browser, in your own currency, which is where you should read any rate before signing anything.
The arithmetic that usually decides it
The comparison people expect to be about features is almost always about how many people need a login.
The following arithmetic is invented for illustration, uses the vendor rates attributed above, and covers no real purchase. In that invented example a four-person team on Close Essentials at $35 per user per month billed annually pays $140 a month and has no workflows. Moving all four to Growth at $99 in the same invented example costs $396 a month, because a seat-priced tier applies to everybody. Leaving them on Essentials and buying the connector layer separately on Zapier Professional from $19.99 a month costs about $160 a month in that invented comparison, because task pricing does not multiply by headcount.
Those two paths point in opposite directions, and which one is right depends entirely on whether the automation you need lives inside the CRM's own records. Rules that move a deal stage, assign an owner or create a task belong in the CRM and cannot be replicated by a connector without making the CRM the second copy of the truth. Work that crosses systems, such as writing a form submission into the pipeline, is what the connector layer is built for and what a CRM workflow engine is worst at. The trap in a CRM's own automation is a rule firing on a change another rule made, which is worked through in workflow automation in a CRM.
- Yes: Write down the specific task being automated, in the form of what happens now and who does it
- Yes: Check whether the tier you already pay for includes automation nobody has switched on
- Yes: Count the people who need a login, which is what decides seat-priced totals
- Yes: Decide whether the work happens inside one system's records or crosses two systems
- Yes: Read the current rate on the vendor's own page, in your own currency, before signing
- No: Buying a tool because a task feels repetitive, without counting how often it happens
- No: Automating the message before the list it goes to has been decided
What none of it does

Three things get expected of this category and are in none of it.
A decision about who to contact. Every product here acts on records it is given. The choice of which companies and which people belong in the list is upstream of all of them, and a tool bought to compensate for a vague target market will send a vague message faster.
Data that is worth acting on. Rules read fields. A record whose owner, stage or contact address is stale produces a confident wrong action, which is worse than no action because nobody reviews it. Cleaning first is unglamorous and it is the whole foundation.
Time you have not budgeted. Configuration is the real cost at this size, not licence fees. A small business has no administrator, so the person setting up the automation is the person who was doing the work manually, and they are doing both for a while. Which stack that adds up to across a whole small-business programme is priced out in lead generation tools for small businesses.
Where we differ from standard practice
Much of the writing in this category assumes outbound is run the common way, and since this page sits on our site it is worth naming where ours differs and what it costs.
The standard automation recommendation for outreach is a sequence: several messages to each contact over some weeks, often landing in the same thread, with later steps going only to people who did not answer. We run one message per campaign, with no bumps and no thread replies, and an audience that did not respond becomes a new campaign built on a different premise rather than a reminder. The reasoning is mechanical. A repeat message is delivered to the population that already saw the first one and chose not to answer, which is the population most likely to complain, and the reputation cost of that lands on the sending domain across everything else it sends.
The consequence for a buyer reading this page is concrete. The sequencing depth that dominates feature comparisons in this category is a feature we do not use, and the automation that matters to us is the part that keeps records accurate and gets a reply in front of a person quickly. We also send from dedicated mailboxes on separate sending domains rather than through a CRM's own sending, for reasons set out in sending cold email from the CRM you already pay for, and we agree what counts as a qualified meeting in writing before a campaign launches. The cost of running it this way is that each contact hears from us less often, and we accept that.
There is a related boundary worth stating for any team automating outreach at this size. Automating the delivery is safe. Automating the judgment about whether a person should be contacted at all is where small programmes get themselves into deliverability trouble, and no tier of any product on this page protects you from it. Why we run campaigns as single messages rather than chains is set out in email sequence software.
The short version

Sales automation software is four purchases wearing one label: a CRM with a workflow engine, a sending and sequencing layer, a scheduling tool, and a connector that moves records between systems. Decide which of the four your bottleneck is in before comparing any two products, because they are not alternatives.
Read the pricing structure as a statement of who the product is for. Seat pricing scales with headcount, task pricing scales with how much data moves, and a bundle with seats included is sold to an owner rather than to a team.
Check whether the automation is gated above the tier you were going to buy, because on at least one vendor's published plan list it is, and that single fact changes the arithmetic more than any feature comparison will.
None of these products decides who to contact or fixes the records they read. Where the constraint is that not enough of the right conversations are starting at all, see what a first campaign produces against your market before adding another tool to the stack.
Rates and plan contents verified against each vendor's own pricing page on 2 September 2026, with dated snapshots retained. Vendor pricing pages carry monthly and annual states and render regional currencies, so confirm the current terms in your own browser before relying on them.
Sources: Close pricing, Keap pricing, Zapier pricing, Calendly pricing
Frequently asked questions.
Frequently asked questions- What is the best sales automation software for a small business?
- There is no single answer because the term covers four unrelated products. A CRM workflow engine automates rules over your own records. A sending tool automates outbound contact. A scheduler removes booking friction. A connector moves data between systems. Work out which of those four your bottleneck sits in, then compare only the products that do that job.
- Is sales automation included in the cheap CRM plans?
- Often not, and this is the single most useful thing to check before comparing anything. Close publishes the words Workflows not included in the feature lists of its two lowest plans, as read on its pricing page on 2 September 2026. Other vendors gate automation similarly. Read the plan feature list rather than the plan name.
- How much should a small business expect to pay?
- It depends on which of the four purchases you are making and how many people need a login. Published entry rates on 2 September 2026 ranged from a free task-based tier to a bundle at $299 a month including two user licences. Seat-priced products multiply by team size, so count the logins before comparing any two totals.
- Can one tool replace all four?
- Some vendors sell bundles that cover several, and for an owner-operated business that can be the right shape. The trade is that the bundle prices the whole thing as one line item, so you pay for the parts you do not use and you cannot swap one component out. Most small teams need two of the four and should buy two.
About the author.
B2B cold email experts helping companies generate qualified leads through done-for-you outreach campaigns.
RevenueFlow Team
Explore more.
Ready to scale your outreach?
We build GTM engines that book real meetings. See the receipts.
Related articles.
Sybill: The Credit Meter Is the Number to Model
Sybill meters by credits per week rather than by seat, and its pricing page carries three different figures for the same two plans. Both facts change the model.
Pipedrive Pricing: Half the Numbers Online Are Retired
Pipedrive renamed every plan in 2025, so most pricing write-ups quote a retired rate card. The five inputs that actually decide your bill, from the vendor's own docs.
Pipedrive Calling: Native Surfaces, Marketplace Dialers
Pipedrive's knowledge base says it has no built-in calling integration. What ships natively is a set of shortcuts to your phone, and the dialer is a second subscription.
Avoma Pricing: Recorder Seats, Free Viewers, and the Add-Ons
Avoma charges only for people whose meetings get recorded and makes viewers free, so the seat count to price is smaller than the team and the add-ons are larger.
Calendly Pricing: Every Plan and What Changes With Seats
Calendly's published rates read as annual by default. What each tier unlocks, why the same page shows three currencies, and where the non-profit discount lives.
Salesforce Einstein AI for Sales: The Agentforce Rename
Four products still carry the Einstein name on Salesforce's rate card. The pricing page's own data says which editions include them, and contradicts its footnote.