Data Analysis in Professional Life: A Worked Pricing Example
Work out an hourly floor, a fee with a buffer and a value check for a data analysis job, in sample money. An outline, not advice.
In this lesson you will
- Work out an hourly floor
- Estimate hours with a buffer
- Price a job and check its value
- Know what to hand over and not to promise
About 28 minutes
Turning a skill into a living
A local charity hears about Leila’s workshop report and asks Dev, a freelance analyst who has been helping, to do something similar for them: tidy a year of donation records and report what they show. Dev has the skills. What he does not have is a price. This lesson works through one example of how to turn your skills into a fee that is fair to you and to the client. Everything here uses sample money and invented numbers. It is a worked outline and not business, tax or legal advice, and your own costs and rules will differ.
Step one: your hourly floor
Your floor is the lowest hourly rate that lets you live and keep working. You build it from three numbers: the pay you want in a year, your business costs for the year, and the hours you can really bill. The last number is the one people get wrong. A year has far more working hours than you can sell, because time goes on finding clients, writing proposals, learning, tidying and being ill. Many freelancers can bill only a part of their working time.
pay, costs, hours = 30000, 4200, 700
floor = (pay + costs) / hours
print("hourly floor:", round(floor, 2))
tasks = {"agree the question": 3, "clean and check": 6, "analyse": 8, "report": 5, "review": 3}
base = sum(tasks.values())
padded = base * 1.25
print("task hours:", base, "| with 25 percent buffer:", padded)
fee = padded * floor
print("fee at the floor:", round(fee, 2))
actual = 31
print("if it takes", actual, "hours, pay per hour:", round(fee / actual, 2))
print("fee per task hour, before buffer:", round(fee / base, 2))
gain = 3600
print("client gain a year:", gain, "| fee share:", round(fee / gain * 100), "percent")
print("payback in months:", round(fee / (gain / 12), 1))
half = gain / 2
print("if the gain is half, payback:", round(fee / (half / 12), 1), "months")
extra = 4
print("a change of", extra, "hours costs", round(extra * floor, 2))
hourly floor: 48.86
task hours: 25 | with 25 percent buffer: 31.25
fee at the floor: 1526.79
if it takes 31 hours, pay per hour: 49.25
fee per task hour, before buffer: 61.07
client gain a year: 3600 | fee share: 42 percent
payback in months: 5.1
if the gain is half, payback: 10.2 months
a change of 4 hours costs 195.43
With sample pay of 30,000, costs of 4,200 and 700 billable hours, the floor is 48.86 an hour. That number is a minimum, not a target. At the floor you earn exactly what you planned and not a penny more, so a quiet month would put you behind.
Step two: estimate the hours honestly
Dev breaks the charity job into five tasks: agree the question (3 hours), clean and check (6), analyse (8), report (5) and review (3). That is 25 hours of work. But estimates are almost always too low, because tasks have surprises. Dev adds a buffer of 25 percent, and uses 31.25 hours. The buffer is not padding or dishonesty. It is a fair share of the risk that the job will grow, and it protects both sides from an awkward argument later.
Step three: the fee, and what happens if you are wrong
The fee at the floor is the padded hours times the floor rate: 1526.79. If the job really takes 31 hours, Dev earns 49.25 an hour, almost exactly the floor. If it takes the unpadded 25 hours, he earns more. If it takes 40, he earns less, and a good contract has a way to deal with that, such as a clear scope and a price for changes. The program also shows that a change of 4 hours costs 195.43. Stating the price of a change in advance turns an argument into a menu.
Step four: the value check
Now ask the client’s question: is it worth it? Suppose the charity believes the report could help it save or raise about 3,600 a year, a made-up figure that the client would have to confirm. The fee would be 42 percent of one year’s gain, and the fee would be paid back in 5.1 months. If the gain turned out to be half as large, the payback would stretch to 10.2 months. A value check like this helps both of you. If the fee looks too large compared with the gain, the project may be the wrong size, or the price too high. If it looks small, Dev might be undercharging.
What to hand over
- The answer in plain words, with the doubt stated, as in the project of lesson 20.
- The clean data and a data dictionary, so the client can use them again.
- The pipeline and the tests, so that next year’s analysis costs less.
- A note of assumptions and choices: what was removed or filled, and why.
What not to promise
- A particular result. You are selling honest analysis, not an answer. A client who wants a pre-decided result wants a different service.
- Certainty from small data. If the data cannot answer the question, say so.
- Fast and cheap and thorough. Pick two, and say which.
Before you take on work, check what you need for your own situation, such as how to record income, whether you need a written agreement, and how to handle other people’s data. Those rules differ from place to place, and this lesson cannot cover them.
Pricing from the hours of the task alone. Without a floor built from real costs and billable hours, you may work a full week and earn less than you planned.
All amounts are sample money and the charity job is invented. The 25 percent buffer and the 3,600 gain are teaching choices. This is not business, tax or legal 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 your hourly floor?
- The rate your client likes
- A rate set by law
- The rate of the last job
- The lowest rate that covers your planned pay and costs over your billable hours
It is a minimum, not a target.
Why can you not bill every working hour?
- Billing is illegal
- Time also goes on finding clients, proposals and learning
- Clients pay by the day
- Hours cannot be counted
Billable hours are only part of your working time.
What is the purpose of the 25 percent buffer?
- To pad the invoice dishonestly
- To pay tax
- To reduce the fee
- To share the risk that the job grows
Estimates are almost always too low.
What does a value check compare?
- The fee with the gain the client expects
- The fee with the floor only
- Two clients
- Hours with days
It tells both sides whether the project is the right size.
Why state the price of a change in advance?
- It raises the fee
- It removes the buffer
- It turns an argument into a menu
- It is required by law
The client can choose before the work happens.
Summary
- The floor comes from pay, costs and billable hours.
- Estimate honestly and add a buffer for risk.
- Check the fee against the gain the client expects.
- Hand over the answer, the data, the code and the assumptions.
Questions
Should I charge by the hour or by the project?
Either can work. A fixed fee suits a clear scope and gives the client certainty. Hourly work suits unclear scope. Whichever you use, the floor and the estimate tell you whether the price is sensible.
Where does the gain figure come from?
From the client, as their own estimate. You can help them think it through, but it is theirs, and you should say that it is uncertain. A rough figure is enough to see if the fee is in proportion.
Is this tax or legal advice?
No. It is a worked example in sample money. Tax, contracts and insurance depend on where you are and how you work, so get advice for your own situation.
