Three automations people buy, and how to sell them
Automation as a subject gets 7% hot posts against an 11.6% baseline — below average, and the cause is the framing: people write about it as technology. Below are three things people genuinely buy, and the key to selling them: all three are about what does not get done at all rather than about doing things faster.
Automation as a subject gets 7% hot posts against an 11.6% baseline — below average, and the cause is the framing: people write about it as technology. Below are three things people genuinely buy, and the key to selling them: all three are about what does not get done at all rather than about doing things faster.
---
Automation gets written about as technology
I went through 6 502 posts from eleven channels in the niche over 19 months. Automation as a subject appears 42 times — respectable enough.
But its share of hot posts is 7% against an 11.6% baseline. So the subject performs noticeably below average.
The cause is visible if you look at how it gets written about. Almost always as technology: here are the blocks, here is the flow, here is how to connect a service.
To a reader who wants to earn, that answers not one question: who buys this, for how much, and what exactly gets delivered.
Below are the three automations most often commissioned. Not by how interesting they are but by demand.
---
1. Enquiries in one place
What gets bought. A business receives enquiries from four or five sources: a website form, email, a messenger, social media, sometimes the phone. Each lives in its own place and some get lost.
The automation brings it all into one spreadsheet or system, with a notification for each new one.
Why this comes first. An owner knows their revenue and does not know their losses. An enquiry that arrived in the wrong place exists in no report — it can neither be counted nor recalled.
How to approach a client. Not with an offer of automation. With a question: how many enquiries arrive outside working hours and what happens to them.
That one figure settles the question of necessity faster than any presentation.
What gets delivered: the sources consolidated, notifications, a simple dashboard with a counter, instructions.
The catch: the client often does not know all their own sources. The first step is not building but an inventory: where can people actually write to you.
---
2. Winning back existing clients
What gets bought. A reminder to people who have not been in touch for a while, with the ability to book or order in one tap.
Why this is the fastest payback in the set. Those people have already bought. They need no convincing, no advertising to bring them in, no explanation of who you are.
The typical situation in an offline business: once a year the owner remembers the base, asks somebody to ring round, and it dies within a week. Or they hire somebody remote who works an hour a day.
How to work out the value with the client. Take their base, estimate how many people have not been in touch for six months, and multiply by the average sale. Even at a few per cent returning, the sum usually covers the cost of the work several times over.
What gets delivered: the selection rule — who to remind and when, the message copy, the sending mechanic, tracking the responses.
The catch: the copy. A reminder that reads as a mass mailout works against you. It has to be about a specific occasion and a specific timing rather than "we have an offer on".
---
3. Regular reporting
What gets bought. Collecting data from several sources on a schedule, consolidating and sending it.
Why people commission this. Not to save an hour. So the report starts existing at all. Most small companies have no regular reporting whatsoever — not because they do not want it but because every time somebody has to be chased.
How to approach it. Ask which figures the manager would like to see every week and why they do not. The answer is almost always "nobody ever gets round to compiling it".
What gets delivered: the sources, the consolidation rules, the schedule, the output format, a failure notification.
An important catch: first you have to agree which figures exactly are needed. A client usually names ten and actually looks at three. A report of ten indicators does not get read at all.
---
What all three share
Not one of them is about complex technology. All three are about what does not get done at all rather than about speeding up something that does.
That is the key to selling. Automation that speeds up something already being done sells badly: the client counts the hours saved and sees no value. Automation that creates something that did not exist sells easily.
Frame it through absence: "at the moment overnight enquiries get lost", "at the moment nobody works the old base", "at the moment there is no report".
How to price it
Not by your hours. The client is buying not your work but a hole closed.
The quote as items rather than one sum:
- The inventory: where the sources are, what sits where
- Building the flows
- Copy and rules, where needed
- Failure notifications
- Instructions and training
- What the client pays for themselves afterwards — services, subscriptions
- Support: included or separate
A quote of seven lines defends itself. People argue with the items rather than the total.
The price range. By my scrape of 848 listings: a system or pipeline — $490–1 460, against a $30–75 median for one-off work. A caveat: an explicit budget appears in 6% of listings, with between two and fifteen observations per category.
Where the main money is
Not in the first build.
In support. Services change their interfaces, flows break silently, the client's processes get rearranged. Automation with no owner survives until the first failure. That is a recurring payment and an honest one.
In expansion. The first flow works — a request arrives for a second. Then for reporting, then for integration with their system of record.
In my dataset 21.9% of clients are explicitly looking for somebody long-term and 20.3% mention a flow. Almost half the market does not fit into one-off work — and automation is exactly the type of service that lands in it naturally.
Three mistakes when selling
Selling a platform. The client does not care what it was built on. The conversation is about the result.
Automating before describing. If a process gets done differently every time, you will cement chaos. Describe first, build second — a rule with no exceptions.
Promising headcount cuts. Even if it is true. One mention turns the client's staff into opponents at every step where their honesty in supplying information is needed.
The right framing: the time freed up goes to what nobody got round to before.
What is available on the platform
Automation templates — more than 3 000 ready flows: handling enquiries, mailings, reports, integrations. Do not build from scratch; most tasks are standard.
The descriptions are open to everyone, the ordinary templates come with the Plus plan, advanced ones with Full.
AI Workflow — if the task needs understanding rather than a rule: chains with chat models, conditions and an iterator. Scheduled and webhook-triggered runs — the Full plan.
More than 140 AI assistants across 14 categories — from Basic. Analytics for the reporting, marketing for the win-back copy, sales for the conversation with the client.
The ten-lesson sales module — how to shape an offer around demand and handle objections. Included in Basic.
Registration is free and opens three days of full Basic access.
Where to start today
One action. Take a business you know — your own or somebody else's — and ask the owner one question: how many enquiries arrive in the evening and at weekends, and what happens to them.
They almost certainly do not know the exact answer. That not knowing is your sale: you are offering not automation but the chance to find out and stop losing.
That conversation is where the first of the three begins.
---
How this looks ready-made
The three automations above are what gets bought. All three exist already built.
Receiving and qualifying enquiries → a 24/7 AI manager. It advises, holds a conversation, sells, takes payment, integrates with a CRM. $480.
Analysing conversations → the conversation analyst. Text gets broken down into script errors and client pains, voice messages get transcribed automatically. The summary arrives as "the client doubts the price, the salesperson did not address the discount". Deployment $360–1 200.
Regular reporting → automated advertising reports. It pulls data for 7 and 14 days, compares them, and the model writes a report with concrete advice: which combinations to scale, which to switch off. Setup $200–500.
Plus from the Legacy library: CRM integration — by its own description the most in-demand service, an integrator's fee from $1 200 · call transcription attached to the deal · management dashboards on Google Sheets.
What that changes in your economics. Every solution comes with a blueprint file: load it, enter credentials, and five minutes later it works. You are not spending a month building — you are selling something that already works and adapting it to the client.
The archives — Make, N8N and Full.
---
What to read next
[Make or n8n: which to choose](/en/blog/make-or-n8n) — what to build this on.
[Digitising an offline business](/en/blog/offline-business-digitization) — where these three hurt most.
[A company knowledge base as a service](/en/blog/company-knowledge-base) — the next service up by fee.
[A process audit](/en/blog/processes-and-automation-audit) — what gets done before automating.
[n8n and Make automation templates](/en/blog/n8n-automation-templates-guide) — the full guide to automations.