Freelance data analysts are often underpriced because clients see the output (a dashboard, a report) and not the work behind it (data cleaning, modelling, validation). This calculator helps you find a rate that reflects what you actually do, not just what you deliver.
// frequently asked questions
How do I price a dashboard build project?
Dashboard projects have two distinct phases: data preparation (connecting sources, cleaning, modelling) and visualisation (building the actual views). The first phase is almost always harder and takes longer. Estimate them separately, quote them together, and make sure the client understands that 60-70% of the cost is usually in the data work, not the charts. A dashboard that looks simple to the client often has weeks of pipeline work behind it.
When does a reporting retainer make sense?
A retainer works when a client needs recurring analysis: monthly performance reports, weekly KPI updates, or ongoing campaign measurement. Define exactly what is included (which reports, which cadence, how many ad hoc requests) before quoting. Retainers without scope definitions become full time jobs. With clear scope, they are the most stable income a data analyst can have.
Does SQL depth affect my rate significantly?
Yes. Basic SQL (SELECT, JOIN, GROUP BY) is table stakes and does not command a premium. Advanced SQL (window functions, CTEs, query optimisation on large datasets) is meaningfully rarer and justifies a higher rate. If you can work directly in a data warehouse (BigQuery, Snowflake, Redshift) without hand-holding, price yourself as a technical analyst, not a reporting analyst.
What billable percentage should I plan for?
Data analysts typically bill 55-65% of working hours. Data quality issues, source system changes, and stakeholder alignment take real time that does not appear on a deliverable. Account for it in your rate rather than absorbing it as unpaid work.
// how does data analyst pricing compare to DevOps engineer?
Both are technical roles with strong freelance markets, but
DevOps engineers typically command higher rates because infrastructure failure has immediate operational consequences. Data analyst work is high-value but the consequences of errors are usually slower to surface. At the senior level, analysts who work on revenue attribution, financial modelling, or real-time operational data close this gap considerably.