Professional Life: Selling Automation Work Honestly
Work out a floor rate, price a project with a buffer, show the client's payback including the weak case and write an offer that promises only what you control.
In this lesson you will
- Work out a floor rate from pay, costs and billable hours
- Estimate with a buffer
- Show a client’s payback honestly
- Write an offer that promises only what you control
About 25 minutes
“Can you automate my office for me?”
A friend of Ravi’s, who runs a small accountancy, asks whether he can automate her enquiries the way he did his own. Ravi realises that he now has a skill other businesses would pay for, and that he has no idea what to charge, what to promise or how to avoid being on call forever. He is entering the territory of professional life, and this lesson applies the same honest sums that earlier courses used for freelancers, adapted to automation work. Every figure here is made up, and no market prices are quoted.
Start with your floor
Your floor rate is the lowest hourly figure that covers the pay you need and your costs, spread over the hours you can really bill. Not every working hour is billable, because finding clients, learning and admin take time. In the program below, a made-up target of 24000 a year in pay, 3600 in costs and 720 billable hours gives a floor rate of 38.33 an hour, found by dividing 27600 by 720. Always quote at or above your floor. A fee below it is a gift.
Estimate honestly, then add a buffer
Automation projects take longer than they seem to, because there are always cases nobody thought of. Estimate each part, add them up and then add a buffer, an agreed extra for the unknown. The program uses 25 per cent, which is made up. Be clear with the client about what the buffer covers. If you do not need it, you can say so, and the trust you gain is worth more than the hours.
from fractions import Fraction as F
import math
# MADE-UP planning numbers in sample money
pay, costs, billable = 24000, 3600, 720
floor = F(pay + costs, billable)
print(f"floor rate: {float(floor):.2f} an hour")
tasks = {"map the process": 6, "build the workflow": 14, "test on saved examples": 6, "hand over": 4}
hours = sum(tasks.values())
buffer = F(1, 4)
planned = hours * (1 + buffer)
fee = planned * floor
print("estimated hours:", hours)
print("with a 25% buffer:", float(planned))
print(f"fee at the floor: {float(fee):.2f}")
# the client's side (the client's own estimate)
hours_saved, their_rate, care = 12, 15, 40
monthly_gain = hours_saved * their_rate
net = monthly_gain - care
print("client gain a month:", monthly_gain)
print("after the care plan:", net)
print("months to pay back:", math.ceil(fee / net))
print(f"if the gain is half as big: {math.ceil(fee / (monthly_gain / 2 - care))} months")
floor rate: 38.33 an hour
estimated hours: 30
with a 25% buffer: 37.5
fee at the floor: 1437.50
client gain a month: 180
after the care plan: 140
months to pay back: 11
if the gain is half as big: 29 months
The four parts add up to 30 hours, and with the buffer to 37.5 hours. At the floor rate, that gives a fee of 1437.50. Now look at the client’s side, which is how you should explain the price. If her own estimate is right, the automation saves her 12 hours a month at a value of 15 an hour, which is 180 a month. She also needs a care plan, a small monthly fee to keep the workflow working, and after paying 40 for it, her net gain is 140 a month. The fee pays back in 11 months. The last line is the important one for honesty. If the gain is only half as big as she hopes, the payback stretches to 29 months, and she may decide not to go ahead. Showing her that number yourself, before she asks, is a mark of a trustworthy professional.
What to put in the offer
- Scope. What the automation does and does not do, in plain sentences.
- What you need from the client. Examples, access and a person to answer questions.
- Testing. How you will check it, using saved examples, and what counts as done.
- Human checks. Which actions always wait for a person, as in earlier lessons.
- Care plan. What is covered after hand-over, how problems are reported and how quickly you will reply.
- Data. Which personal data the workflow touches, who sees it and how long it is kept.
What not to promise
- A saving or a payback period. These are the client’s estimates, not your guarantee.
- That the automation will never be wrong. Say what checks exist and what a person handles.
- Features of third-party tools or plans, which change and are outside your control.
- That nothing can go wrong with private data. Say what you do, and what the client must do.
Put the agreement in writing, with a short contract or a clear email that both sides accept. The terms that matter most are the scope, the changes process, payment dates, who owns the work and what happens if either side stops. This is an outline, and anything with serious consequences deserves proper legal and insurance advice for your country.
Quoting from the hours you hope to take. Projects have surprises. Estimate each part, add a buffer, and agree in advance how changes will be priced.
The pay, costs, hours, savings and fees are made up, in sample money. No real prices are quoted, and no income or saving is promised. Contract, tax, insurance and data protection points are outlines, not legal, tax or financial advice.
Practice for this lesson
Check what you learned
Five quick questions. Pick an answer and you will see straight away whether it is right and why.
What is a floor rate?
- The average market price
- The client’s budget
- A tax rate
- The lowest hourly figure covering your pay and costs over billable hours
Dividing 27600 by 720 hours gave 38.33.
Why add a buffer to an estimate?
- To raise the price secretly
- Automation projects hide unexpected cases
- Because tools charge it
- It is always required
Be clear with the client about what the buffer covers.
Why show the half-gain payback?
- To scare her off
- To raise your fee
- To avoid a contract
- It tells the client the fair worst case before she asks
Honesty about the weaker case builds trust.
Which should you NOT promise?
- A specific saving or payback period
- To test with saved examples
- A written scope
- A care plan
Savings are the client’s estimate, not your guarantee.
What does a care plan cover?
- The first build only
- Prices of other tools
- What happens after hand-over, such as reporting problems and reply times
- Nothing in writing
It says how the workflow is kept working.
Summary
- Quote at or above your floor rate.
- Estimate by part and add a stated buffer.
- Show the client’s payback, including the weak case.
- Promise your work, not their savings.
Questions
Should I charge by the hour or by the project?
Either can work. A project fee needs a clear scope and a way to price changes. An hourly fee suits work that is hard to define. Start from your floor in both cases.
What is a care plan?
A small recurring fee for looking after a workflow after hand-over, with clear terms about what is covered and how fast you reply.
Are these figures real?
No. All pay, costs, hours and savings are made up, in sample money.
