Float

Most agencies price work before they know whether they have the hours to deliver it, so margin leaks at the scheduling layer rather than the sales layer. As autonomous agents absorb repeatable production tasks, the scarce input shifts to senior human judgment, and the firms that can see real capacity against incoming demand will reallocate people weekly instead of quarterly. Resource planning is therefore a margin discipline, not an admin chore.

The Utilization Ceiling Trap is the point where an agency's billable utilization rate climbs so high that any new client request, sick day, or scope change triggers a cascade of missed deadlines. The framework holds that utilization above roughly 80% looks healthy on a dashboard but converts your delivery team into a single point of failure, because there is no slack to absorb variance. Agencies feel this as burnout, rushed work, and client churn that arrives months after the utilization number peaks. The practical move is to treat 15 to 20% of capacity as a deliberate buffer, not waste, and to track it as a named line item in resource planning. A concrete example: when Anthropic released Claude Haiku 5.5 at $0.10 per million input tokens with a 1M context window, agencies could route high-volume content processing through it and reclaim senior hours, but only if those hours were not already booked at 95% utilization. The buffer is what lets you redeploy capacity when a model or workflow shift makes it available.

Capacity Truth Lag is the gap between when a resource plan is set and when it reflects what is actually happening on client work. Agencies that schedule from stale data overbook senior specialists and underbook juniors, then discover the mismatch only when a retainer deliverable slips. The lag compounds: a two-week-old heatmap in Float or Resource Guru hides the fact that a designer has already been pulled onto an unplanned client request. Closing the lag means treating timesheet and booking data as a live input, not a monthly report. Toggl and Everhour feed actual hours back into the plan, while Runn and Tempo surface forecast-versus-actual variance before it becomes a margin problem. The framework matters because a plan that is 80% accurate today beats a perfect plan that is three weeks old.

Billable Ratio Decay is the framework that separates two numbers agencies routinely conflate: utilization (hours booked against available hours) and billable ratio (hours actually invoiced against hours worked). A team can sit at 85% utilization while its billable ratio slides from 72% to 61%, because internal reviews, rework, and non-billable coordination absorb the difference. The decay is invisible on a capacity heatmap and shows up two months later as retainer margin compression. Tracking the gap between booked and invoiced hours per client gives agency operators an early warning that no scheduling view provides. The same discipline applies to AI-assisted delivery: Anthropic's Claude Haiku 5.5, priced at $0.10 per million input tokens with a 1M context window, makes automated document processing cheap enough that agencies must decide whether saved hours get rebilled or quietly absorbed into fixed-fee retainers. Tools such as Toggl, Everhour, and Hubstaff surface the invoiced side of the ratio; Float, Runn, and Resource Guru surface the booked side. Neither alone closes the loop.

Book the work only against named people with verified open hours, and treat every unstaffed commitment as a delivery risk rather than a revenue win.

Build a defensible demand forecast from signed and probable work before buying scheduling software, because a capacity tool pointed at an unknown pipeline just renders the guesswork in a nicer interface.

IF client demand shifts inside a 30-day window more often than your staffing plan can absorb, THEN run a live capacity ledger where bookings, time entries, and utilization update weekly and drive assignment calls. IF your delivery mix is stable across two or more quarters and scope changes arrive with 30 days notice, THEN a quarterly staffing plan with monthly reconciliation is cheaper to operate and easier for account leads to defend.

These three solve different halves of the same agency problem: Float and Runn look forward at whether the team can take the work, while Everhour looks backward at whether the work was billed and stayed inside budget. Most agencies under 60 people do not need all three, and the honest test is which failure hurts more right now, a burned-out senior who was double-booked or a retainer that quietly ran 20 percent over scope. Pick the tool that closes your worst leak first, then revisit the other half once utilization data is trustworthy.

A fixed-scope engagement that maps an agency's real delivery capacity against booked and pipeline demand, then installs a scheduling cadence that lifts billable utilization without adding headcount. Built for shops running 8 to 60 delivery staff across retainer and project work.