Sales automation ROI calculator: prove the business case in 5 minutes

Before you release money for sales automation or ask your fellow shareholders for it, you want to know whether it can pay off. This sales automation ROI calculator isn't an online tool but a five-line worksheet you can fill in within a few minutes. It doesn't deliver proof, but it does give you a solid plausibility check and the question a pilot then has to answer.

What a five-minute business case can and can't do

A quick business case answers a single question: under which assumptions does the investment pay for itself? It doesn't say that those assumptions will come true. That is exactly its value. Instead of arguing over an uncertain forecast, you agree on the conditions that need to be met and test them in a pilot.

So the real proof doesn't come from the table but from four to eight weeks of live operation with properly recorded baseline figures. The table helps you decide whether such a pilot makes sense at all. Our article on the AI pilot project in sales describes how to set one up.

The ROI calculator: five lines for your sales automation

Line	Question	Where the figure comes from
1. Monthly costs	What does the solution cost per month, including a share of the setup?	Vendor's quote, setup spread over 12 or 24 months
2. Internal time	How many hours a month do you need for maintenance and review?	Estimate, on the generous side
3. Time saved	Which enquiries does the automation handle completely, and how long did they take you until now?	Tally sheet over one week
4. Gap	Line 1 plus line 2 minus line 3	Calculation
5. Break-even	How many additional deals per year close the gap?	Gap times twelve, divided by contribution margin per deal

Line 5 is the core. You don't have to predict how many deals the automation will bring. You only have to judge whether the number required is plausible. That is a question you and your team can answer from experience.

Worked example for an estate agency

All figures in this section are assumptions for illustration. They don't come from customer data and are not a promise. Use your own numbers.

Suppose an estate agency with three agents receives lots of enquiries about property listings via portals and its own website, plus calls in the evening and at weekends. A digital assistant is to answer enquiries, pre-qualify prospects and arrange viewings.

• Line 1: Neurobots Pro at €599 a month, plus €1,299 setup, spread over 12 months that is about €108 a month. Together roughly €707.
• Line 2: assume three hours a month for maintenance and review at an internal rate of €45 an hour, so €135.
• Line 3: assume the assistant fully handles 60 standard enquiries a month that previously took ten minutes each. That is ten hours at €45, so €450.
• Line 4: €707 plus €135 minus €450 gives a monthly gap of €392, or €4,704 a year.
• Line 5: assume one additional sale brings the agency a contribution margin of €5,000. Then, on paper, one additional sale a year is enough to close the gap.

The discussion in the office is then no longer “Will this do anything?” but “Is it plausible that faster replies and being reachable in the evening will win us at least one extra deal a year?” You can test this question in the pilot, for example by marking which prospects came in via the assistant outside office hours.

The cautious scenario

Run the same table again with lower expectations. Suppose the assistant fully handles only 30 enquiries instead of 60, because many prospects have questions about the floor plan or financing that an agent has to answer. Then the time saved in line 3 falls to five hours, or €225. The monthly gap rises to €617, or €7,404 a year. With an assumed contribution margin of €5,000 per sale, the agency would need two additional sales a year on paper. This figure, too, is something the team can answer honestly. If even that still looks achievable, the business case rests on a much more solid footing than any single optimistic forecast.

Typical mistakes in the business case

• Revenue instead of contribution margin. Calculate with what is left after direct costs, not with the gross amount.
• Counting every enquiry as saved. Only enquiries handled completely save time. If an enquiry is passed on, there is still work to do.
• Forgetting internal time. Even a well set-up system needs maintenance when properties, prices or contacts change.
• No baseline. Without a week of tallying before the start, you have nothing to compare against.
• Only calculating the best case. Also calculate a cautious scenario with half the time savings. If the investment still pays off, the decision is easier.

Our pricing guide to AI sales automation goes into more detail on cost types and pricing models. The article Measuring and communicating AI ROI shows how to present the result to shareholders or the bank.

When the numbers don't add up

In some cases the five lines alone show that you are better off waiting. If you get few enquiries and answer them all promptly, line 3 is small and line 5 unrealistically high. If your contribution margin per deal is low, for example with small one-off orders, you need a great many additional deals. And if your capacity is already fully used, more prospects won't help much. In these cases, better organising your existing process is often the cheaper solution. Further levers are described in where AI can cut your sales costs.

Frequently asked questions

Why calculate break-even instead of an ROI percentage?

Because a percentage suggests a precision that a business case can't have before you start. The question of how many additional deals you need, on the other hand, can be judged from experience and checked later in the pilot.

What time period should I use?

Twelve months for the first calculation. Spread one-off costs over this period. If you plan further ahead, you can spread the setup over 24 months, but then stay consistent.

What if my team has no time for a tally sheet?

Then look at the phone system and the inbox for a typical week: how many calls came in, how many went unanswered, how many enquiries arrived outside office hours? It is less precise, but better than a gut-feeling estimate.

How reliable is the result?

As reliable as your assumptions. That is why every business case needs a cautious scenario and a short pilot that tests the most important assumption.

Conclusion

A good business case for sales automation doesn't need elaborate software, just five honest lines and the willingness to test the key assumption in a pilot. If you work this way, your decision rests on a basis others can follow. The page Digital assistant for estate agents shows how a digital assistant handles enquiries, pre-qualification and viewing appointments for agents.