Running a web agency without a dashboard is like flying a plane without instruments. You're moving forward, sure. You feel the turbulence. But you don't know what altitude you're flying at, how much fuel is left, or whether you're heading in the right direction. And when you find out, it's often too late to correct course.
Most agency directors know this. They've even started tracking indicators -- monthly revenue, number of projects in progress, the team's "sense" of workload. The problem is that these indicators are either too vague, consulted too rarely, or both. Growing revenue can mask collapsing profitability. A full order book can hide a team on the edge of burnout.
What you need isn't more indicators. It's the right indicators, measured with the right formulas, compared to the right benchmarks, and consulted at the right frequency. Here are the six that truly matter.
Team utilization rate
What it is
The utilization rate measures the percentage of available working time that your team actually spends on billable projects. It's the most fundamental indicator of a service agency's productivity.
The formula
Utilization rate = (Billable hours / Available hours) x 100
Available hours correspond to working hours minus holidays, public holidays, and absences. For a full-time employee in France, the standard is approximately 1,610 hours per year, or about 214 days or 7.5 hours per business day.
Billable hours are hours devoted to client projects, whether the billing model is fixed-price or time-and-materials. Internal hours (training, pre-sales, administration, agency meetings) are not billable.
Benchmarks
| Level | Utilization rate | Interpretation |
|---|---|---|
| Excellent | 75-85% | Team is well-utilized with time for training and internal projects |
| Adequate | 65-75% | Room for improvement, but the agency is functioning |
| Insufficient | < 65% | Resource underutilization, prospecting or planning problem |
| Danger | > 85% | Overload, burnout risk, no buffer for emergencies |
Measurement frequency
Weekly, with monthly consolidation. The utilization rate naturally varies from week to week (project gaps, vacation periods). It's the trend over 4 to 8 weeks that's meaningful, not a single week's value.
Common pitfalls
Confusing attendance with billable. A team member present 40 hours per week but spending 15 hours in internal meetings, pre-sales, and admin has only 25 billable hours, a 62% utilization rate. If you count all 40 hours as billable, you're severely overestimating your production capacity.
Targeting 100%. A 100% utilization rate is a toxic goal. It means zero training time, zero breathing room between projects, zero capacity to absorb emergencies. The best agencies target 75-80% and use the remaining 20-25% to invest in skills, tools, and pre-sales.
Ignoring individual gaps. An average utilization rate of 75% can mask a senior developer at 95% (overloaded) and a junior developer at 55% (underutilized). Track the indicator individually to detect workload imbalances within the team.
Key takeaway: The utilization rate is the baseline indicator, but it says nothing about profitability. You can have an 80% utilization rate and lose money if your projects aren't profitable. That's why it must be read alongside the next indicator.
Average project profitability
What it is
Per-project profitability measures the margin your agency generates on each project, after accounting for the actual cost of production. It's the indicator that answers the most important question: "Are we making money on this project?"
The formula
Project profitability = ((Amount invoiced - Production cost) / Amount invoiced) x 100
Production cost is calculated by multiplying the hours actually consumed by each team member's loaded hourly cost. The loaded hourly cost includes gross salary, employer contributions, pro-rated overhead (rent, licenses, equipment), and a share of non-billable costs (administration, management).
Example loaded hourly cost calculation:
| Component | Annual amount | Calculation |
|---|---|---|
| Annual gross salary | 42,000 euros | |
| Employer contributions (45%) | 18,900 euros | |
| Pro-rated overhead | 8,000 euros | |
| Share of non-billable costs | 5,000 euros | |
| Total annual cost | 73,900 euros | |
| Annual billable hours (75%) | 1,208 hours | 1,610 x 0.75 |
| Loaded hourly cost | 61.20 euros | 73,900 / 1,208 |
If this team member works 80 hours on a project billed at 8,000 euros, the production cost is 80 x 61.20 = 4,896 euros, and the project profitability is (8,000 - 4,896) / 8,000 = 38.8%.
Benchmarks
| Level | Project profitability | Interpretation |
|---|---|---|
| Excellent | > 40% | Project is very profitable, quote was well-calibrated |
| Adequate | 25-40% | Healthy margin covering overhead and generating profit |
| Insufficient | 15-25% | Margin barely covers overhead, near-zero profit |
| Danger | < 15% | Project is losing money or not earning enough to cover costs |
Measurement frequency
At the close of each project, with a monthly consolidation of average profitability across all projects delivered that month. For long projects (over 3 months), do a mid-project profitability estimate based on hours already consumed.
Common pitfalls
Calculating profitability from the quote, not from actuals. A quote's "theoretical" profitability only serves to make the signing decision. The profitability that matters is calculated after delivery, based on actual hours. It's the only one that reflects reality.
Forgetting untracked hours. If a project manager spends 10 hours in meetings and client exchanges without logging them to the project, the displayed profitability is artificially high. All hours devoted to a project must be accounted for, including project management and post-delivery support.
Not differentiating profiles. An hour from a senior developer at 75 euros/hour loaded and an hour from a junior at 45 euros/hour loaded don't have the same impact on profitability. Use individual hourly costs, not a generic average cost.
Key figure: According to industry data, the average project profitability in web agencies ranges between 20 and 35%. The highest-performing agencies reach 35 to 45% thanks to better project scoping, rigorous time tracking, and proactive overrun management. Identifying which clients are actually profitable is often the first step toward improvement.
Quote-to-actual time ratio
What it is
This ratio measures the accuracy of your estimates. It compares the time planned in the quote to the time actually consumed. It's the indicator that tells you whether your quoting process is reliable or needs recalibration.
The formula
Quote/actual ratio = Actual time / Quoted time
A ratio of 1.0 means a perfect estimate. A ratio of 1.3 means the project consumed 30% more than planned. A ratio of 0.85 means the project was delivered with 15% of hours unconsumed.
Benchmarks
| Level | Ratio | Interpretation |
|---|---|---|
| Excellent | 0.95 - 1.10 | Accurate estimate, reliable quoting process |
| Adequate | 1.10 - 1.25 | Moderate overrun, acceptable with sufficient margin in the quote |
| Insufficient | 1.25 - 1.50 | Chronic underestimation, margin is systematically eroded |
| Danger | > 1.50 | Estimation failure, quoting process overhaul needed |
Measurement frequency
At the close of each project, with quarterly overall tracking to identify trends. Break down the ratio by project type (brochure site, e-commerce, web application) and by item (design, front-end dev, back-end dev, project management) to identify overrun sources.
Common pitfalls
Analyzing the overall ratio without breaking it down. An overall ratio of 1.20 can mask a perfectly estimated back-end (ratio 1.05) and systematically blown project management (ratio 1.60). It's the breakdown that reveals the real problems.
Blaming the team instead of the process. If 80% of your projects overrun, the problem isn't in execution but in estimation. Review your margin coefficients, your time reference framework, and your scoping process.
Key takeaway: This ratio is the best indicator of organizational learning. If it improves quarter over quarter, your agency is learning from its mistakes. If it stagnates or worsens, you're repeating the same mistakes without correcting them.
Revenue per employee
What it is
Revenue per employee measures your team's economic productivity. It's a macro indicator for comparing with other agencies and detecting underlying trends.
The formula
Revenue per employee = Annual revenue excl. tax / Number of FTE employees
The number of employees must be expressed in FTE (Full-Time Equivalent) to account for part-timers and regular freelancers. A freelancer working half-time for you counts as 0.5 FTE.
Benchmarks
| Level | Revenue per employee | Interpretation |
|---|---|---|
| Excellent | > 100,000 euros | Well-positioned agency with high daily rates and good utilization |
| Adequate | 70,000 - 100,000 euros | Standard market level for web agencies |
| Insufficient | 50,000 - 70,000 euros | Daily rates too low, underutilization, or too many non-billable profiles |
| Danger | < 50,000 euros | Business model needs fundamental review |
Measurement frequency
Monthly with a rolling 12-month view to smooth seasonality. Revenue per employee is a trend indicator, not an operational one. It should be read over 6 to 12 months.
Common pitfalls
Ignoring freelancers in the calculation. If you use 3 regular freelancers representing the equivalent of 1.5 FTE, not counting them artificially inflates your revenue per employee. Include all regular production contributors.
Confusing revenue with value created. A high revenue per employee can result from high rates (positive) or work overload (negative). Always cross-reference this indicator with the utilization rate and profitability for a complete reading.
Quote conversion rate
What it is
The conversion rate measures the percentage of issued quotes that turn into signed orders. It's a commercial indicator that directly impacts the workload plan and cash flow.
The formula
Conversion rate = (Number of signed quotes / Number of issued quotes) x 100
Also calculate the conversion rate by value to complement the analysis:
Value conversion rate = (Amount of signed quotes / Total amount of issued quotes) x 100
A 30% conversion rate by volume with a 45% conversion rate by value means you convert larger projects better than smaller ones -- a strategic insight.
Benchmarks
| Level | Conversion rate | Interpretation |
|---|---|---|
| Excellent | > 40% | Strong demand, good positioning, clear value proposition |
| Adequate | 25-40% | Standard level, room for improvement on targeting or proposition |
| Insufficient | 15-25% | Too many untargeted quotes, positioning or pricing problem |
| Danger | < 15% | Time spent on pre-sales isn't being recouped |
Measurement frequency
Monthly, with a quarterly analysis of rejection reasons. Systematically ask prospects why they didn't sign: price too high, timelines too long, unsuitable proposal, chose a competitor? This feedback is more valuable than the rate itself.
Common pitfalls
Only counting formal quotes. If your salesperson spends 4 hours preparing a proposal that doesn't convert, this pre-sales cost must be considered. A 25% conversion rate means 75% of pre-sales time is "lost" -- the remaining 25% must more than compensate.
Targeting too high a rate. An 80% conversion rate may seem excellent, but it probably indicates you're only quoting near-certain projects. You're not taking enough commercial risks and missing opportunities.
Key figure: The average cost of producing a quote in a web agency is estimated between 500 and 2,000 euros (brief time, analysis, costing, drafting, presentation). With a 25% conversion rate, each signed project "carries" the cost of 3 unconverted quotes. This cost must be integrated into your overall profitability calculation.
Average invoicing delay
What it is
The average invoicing delay measures the time between delivering a milestone (or completing the project) and issuing the corresponding invoice. It's a cash flow indicator often overlooked that has a direct impact on your working capital requirement.
The formula
Average invoicing delay = Sum (Invoice date - Delivery date) / Number of invoices
Complete with the payment delay for the full cycle view:
Total collection delay = Invoicing delay + Client payment delay
Benchmarks
| Level | Invoicing delay | Interpretation |
|---|---|---|
| Excellent | < 3 days | Invoice issued immediately after delivery |
| Adequate | 3-7 days | Slight lag, acceptable if systematic |
| Insufficient | 7-15 days | Significant delay, measurable cash flow impact |
| Danger | > 15 days | Every day of delay costs money, process needs urgent review |
Measurement frequency
Monthly. Analyze invoices issued in the month and calculate the average delay. Identify "overdue" invoices -- those that should have been issued but haven't yet.
Common pitfalls
Waiting until the end of the project to invoice. On a 4-month project, invoicing at final delivery means 4 months of advanced cash. Milestone-based invoicing (30% at kickoff, 40% at mockup approval, 30% at delivery) reduces working capital requirement considerably.
Underestimating the financial impact. An agency billing 60,000 euros per month with a 10-day average invoicing delay and a 30-day payment delay has a permanent outstanding amount of 80,000 euros. Reducing the invoicing delay to 2 days frees up 16,000 euros in cash.
Not following up on unpaid invoices. The invoicing delay is useless if invoices aren't paid. Combine this indicator with a collections tracker and a structured follow-up process.
Key takeaway: Every day of invoicing delay is a day of lost cash flow. Over a year, the difference between invoicing at D+2 and D+12 can represent the equivalent of one month of payroll costs in immobilized cash.
The summary dashboard: see everything at a glance
To be useful, your dashboard must fit on one screen. Here's a summary model grouping the 6 indicators with their targets and tracking frequency.
| Indicator | Formula | Target | Alert | Frequency |
|---|---|---|---|---|
| Utilization rate | Billable hours / Available hours | 75-80% | < 65% or > 85% | Weekly |
| Project profitability | (Invoiced - Cost) / Invoiced | > 30% | < 20% | Per project + monthly |
| Quote/actual ratio | Actual time / Quoted time | 0.95 - 1.10 | > 1.25 | Per project + quarterly |
| Revenue per employee | Annual revenue / FTE | > 80,000 euros | < 60,000 euros | Monthly (rolling 12 months) |
| Quote conversion rate | Signed quotes / Issued quotes | > 30% | < 20% | Monthly |
| Invoicing delay | Days between delivery and invoice | < 3 days | > 7 days | Monthly |
How to read the dashboard
The six indicators are read together, not in isolation. Here are the most revealing combinations:
High utilization rate + low profitability = your daily rates are too low or your projects systematically overrun. The team works a lot but the agency doesn't earn enough.
Low utilization rate + low conversion rate = commercial problem. You're not signing enough projects to keep the team busy. Work on prospecting or positioning.
High quote/actual ratio + low profitability = your quotes are underestimated. Each overrun eats into the margin. Recalibrate your estimation coefficients.
High revenue per employee + utilization rate > 85% = your team is overloaded. Revenue is good short-term but the risk of turnover and quality decline is real.
High conversion rate + long invoicing delay = you sign well but are slow to collect. Cash flow is under pressure despite a healthy order book.
Setting up the dashboard: where to start
If you're tracking none of these indicators today, don't try to implement everything in one week. Proceed in stages.
Week 1-2: Utilization rate. Start by having the team log their hours, even in simplified form. Billable project or internal time -- that's enough to calculate the utilization rate.
Week 3-4: Project profitability. Calculate each team member's loaded hourly cost and start comparing hours consumed against the amount invoiced on delivered projects.
Month 2: Quote/actual ratio. At the close of each project, compare planned and actual time. Store this data in a simple table.
Month 3: Commercial and financial indicators. Add the quote conversion rate and invoicing delay. This data is generally easier to collect (it comes from your CRM and invoicing tool).
Key takeaway: The perfect dashboard is the one you actually look at. Three indicators tracked every week are better than 15 indicators in a file nobody opens. Start simple, stay disciplined, and enrich over time.
Turning indicators into decisions
A dashboard that remains contemplative is useless. Each indicator must lead to a concrete action.
If the utilization rate drops below 65% for 3 weeks, it's the signal to intensify commercial prospecting or accelerate the kickoff of signed but unlaunched projects.
If the average project profitability drops below 25% for a quarter, it's the signal to audit the last 3 months' quotes, identify overrun sources, and recalibrate estimates.
If the quote/actual ratio exceeds 1.25 on a specific project type, it's the signal to increase the margin coefficient for that service type or review the scoping process.
If the conversion rate drops below 20%, it's the signal to review prospect targeting, proposal quality, or pricing positioning.
If the invoicing delay exceeds 7 days, it's the signal to automate invoice issuance upon milestone validation or appoint someone responsible for invoicing.
Modern time tracking and management tools calculate these indicators automatically. But the tool is just the vehicle. The discipline of weekly review, gap analysis, and resulting decision-making -- that's the agency director's job. And that's what makes the difference between an agency that endures its results and one that steers them.