Agency productivity techniques that protect margin, starting with the proposal

A full calendar feels productive. Every designer is booked, the project board is crowded and nobody has time for lunch. Then the month closes and the numbers are flat. The team worked hard, but a lot of that work was never billed, or was billed at a price set before anyone knew how long it would take.

That is why the useful definition of agency productivity is narrow: the margin each project hour keeps. Output per hour, not effort per week. A studio can raise it without anyone working longer, simply by losing fewer hours between the moment a project is sold and the moment it is invoiced.

Personal productivity rules still have a place. The so-called rule of threes for productivity asks you to spend a focused block on your most important project, then clear three short tasks and three maintenance tasks. It is a sensible way to plan a day. It does nothing about a fixed fee that was quoted too low or a revision round nobody charged for.

Read utilization and realization together

A pair of measures does the heavy lifting. Utilization is the share of available hours your team spends on billable client work. Realization is how much of the value of those hours you actually bill and collect. Utilization tells you whether people are busy on the right things. Realization tells you whether that busyness turns into money.

A studio with high utilization and low realization is the classic overworked shop: everyone is on client work, but discounts, write-offs and unbilled revisions eat the value. A studio with low utilization and high realization is selling well but carrying too much internal time. Track both, and look at project margin on every engagement, not only at the end of the year.

The last row is the row many studios skip, and it is often the largest unbilled cost in the business.

New research found that the average agency undertakes 27 pitches to win new contracts every year, with 62 hours spent on average per pitch.

None of those hours shows up on a timesheet as billable work, yet they decide which projects arrive and at what price. Treat pitching as part of production, and measure it like production.

Every project passes through the same chain. It is sold in a pitch or proposal, scoped into deliverables, scheduled against the team's capacity, delivered and finally billed. Each handoff is a place where hours can slip out unnoticed.

At the sale, the leak is the pitch itself: time spent on work you do not win. At scoping, it is vague deliverables that leave room for interpretation. At scheduling, it is a deadline promised before anyone checked who is free. During delivery, it is the extra revision round, the quick favour and the waiting time while a client approves. At billing, it is everything above that never makes it onto the invoice.

Based on responses from 412 agencies, EACA found that the average agency now spends 650.937 € annually on pitching to win new business.

Even a healthy win rate means a large share of pitch hours buys nothing. That makes the cost of pitching worth knowing in money, not only in hours.

Pitching is only the first leak. The rest tend to sit inside projects the studio has already won, and they are easier to fix because you control them.

Illustrative example: a small studio, Field Office, wins a brand identity project for a fictional bakery chain at a fixed fee of $24,000. The studio estimates 112 hours and plans with a delivery cost of $90 per hour, so it expects to keep $13,920 after delivery costs.

The project ships on time and the client is happy. The timesheets tell a different story: the team logged 166 hours, and the studio kept $9,060. Nobody worked badly. The hours leaked at the handoffs.

For example, run the same project again with the fixes in place. Reusable proposal blocks cut the proposal to 10 hours. The extra workshop turns into a priced add-on worth $1,800. Revisions stop at 2 rounds, with round 3 quoted as a change request, which brings revisions back to 26 hours. Approval inside the document cuts admin to 8 hours, and a handover list in the scope holds handover at 12 hours.

The rerun lands at 128 hours. At $90 per hour of delivery cost, Field Office keeps $12,480 on the base fee, plus the $1,800 add-on. The work, the team and the client are the same. The difference sits almost entirely in decisions made before the first concept was drawn.

Scope creep rarely arrives as a big request. It arrives as a small one, in a friendly tone, a few weeks into the project. "Could you just try it in green?" If the proposal never said how many rounds were included, saying no feels petty, so the studio says yes and the hours disappear.

The fix is to make the limits part of what the client agreed to. When the proposal lists each deliverable, states the number of revision rounds and explains what happens beyond them, the conversation changes. Extra work becomes a quote, not a confrontation.

How many revision rounds should a proposal include? There is no universal number, but many studios settle on a small, fixed count per deliverable and price anything beyond it. What matters is that the number is written down and visible next to the price.

The proposal is also where pitching hours can be cut. A studio that rebuilds every proposal from an old file spends hours on layout before it writes a word about the client. A library of finished, reusable sections, such as approach, case studies, terms and pricing structure, turns each new proposal into assembly plus a short stretch of fresh thinking. Pitches are often unpaid, so every hour saved on assembling a proposal is an hour returned to paid work.

Fixes only last if they become habits. The most valuable habit is the closeout review: when a project ends, compare estimated and actual hours by phase, note where the hours went and update your estimates. After a handful of projects, you have an estimating library built from your own work, which beats any rule of thumb when you price a project you have not done before.

Standardize what has become predictable. Proposal sections, onboarding emails, kickoff agendas, handover checklists and invoice reminders are the same every time, so template them and automate the sending where you can. Keep the variable work, the thinking and the design, for the people who are best at it.

Protect focus time as well. Client coverage matters, but a designer pulled into every call never finishes anything. Rotate who covers client messages, block shared focus hours and keep all project decisions in a single system of record so nobody has to ask twice.

This is where Formlio fits. Formlio proposals are built from blocks you save to a library and reuse, so a new proposal starts already assembled. Deliverables, revision rounds and exclusions sit in the document the client approves. The interactive quote lists optional add-ons the client can toggle on, so extras are priced before work starts rather than argued about later.

After you hit send, you get a notification when the client opens the proposal, and section-level analytics show how long they spent on scope and pricing, so follow-ups land at the right moment. A PDF goes into a black box. A Formlio document reports back: who opened it, what they read, when they signed. Clients approve with slide-to-approve or an e-signature inside the document, which gives the whole team the same approval trail.