How to Know If a Project Is Actually Profitable Before It Ends
The post-mortem is too late. By the time you know a project was unprofitable, you've already delivered the work and sent the invoice. Here's the math that tells you earlier.
01. Why Post-Mortem Profitability Analysis Doesn't Help
Most agencies that track project profitability at all do it at the end. The project closes, someone pulls the hours from Toggl, compares them to the invoice amount, calculates an effective hourly rate, and adds it to a spreadsheet that nobody looks at until the same problem happens again six months later. This is better than nothing. It's not better than much. The post-mortem tells you that you lost money on a project — it doesn't help you not lose money on that project. By the time you do the math, the work is done, the client has been invoiced, and the only thing you can do is learn for next time. The gap in most agency operations is the mid-project check. Not a status meeting about deliverables. A ten-minute financial check that answers one question: based on hours tracked so far, are we on pace to hit the margin we quoted for? That check is the difference between a project that finishes at 85% of estimated margin and one that finishes at 40%.
"We started doing a 15-minute margin check at the halfway point of every project over $3,000. In the first quarter, we caught three projects running significantly over hours. In two of them, we were able to have a scope conversation with the client before the damage was done."
02. The Three Numbers That Predict Outcome
You need three numbers to know if a project is on track financially. If any of them live in a separate tool from your task tracker, this check won't happen — the friction of pulling them together is too high for a busy team to do consistently. Number 1: Quoted margin — what profit did you expect when you priced the project? This is usually implicit rather than explicit. You quoted $8,000 for a project you estimated at 40 hours, at a blended team rate of $120/hour. That's $4,800 in labour cost, leaving a $3,200 gross margin (40%). Write this down explicitly at project start. It becomes the target. Number 2: Hours consumed to date — how many hours has the team actually logged against this project so far? This needs to come from tracked time, not from estimates. Estimates are systematically optimistic. Tracked hours are facts. Number 3: Hours remaining — based on what's left to deliver, how many hours do you realistically expect the project to consume from this point? This requires judgment, but it's better judgment when you have the first two numbers in front of you.
03. Real-Time Margin: The Formula
The calculation is straightforward once you have the three numbers: Projected labour cost = (hours consumed to date + hours remaining) × blended hourly rate Projected gross margin = project revenue − projected labour cost Projected margin % = projected gross margin ÷ project revenue × 100 Run this at the 40-50% completion point of any project over $2,000 in value. If the projected margin is within 10 percentage points of the quoted margin, you're on track. If it's worse than that, you have a problem — and you have time to do something about it. Example: you quoted $8,000 for a brand identity project, estimated at 40 hours at $120/hour. Target margin: 40%. At mid-project (week 2 of 4), the team has logged 28 hours. You estimate 20 hours remaining. Projected total hours: 48. Projected labour cost: $5,760. Projected margin: $8,000 − $5,760 = $2,240 (28%). That's 12 percentage points below target. You have a problem. You have two weeks to do something about it.
04. The Mid-Project Check-In (The Week 2 Rule)
The timing of the check matters as much as the math. Too early and you don't have enough data. Too late and there's no room to manoeuvre. The rule that works across most project types: run the profitability check when you've consumed 40-50% of the estimated hours. For a 40-hour project, that's around 16-20 hours in. For a 4-week project, that's usually end of week 2. This timing gives you two things: enough actual data to make the projection meaningful, and enough project remaining to have options if the numbers are bad.
"We started doing a 15-minute margin check at the halfway point of every project over $3,000. In the first quarter, we caught three projects that were running significantly over hours. In two of them, we were able to have a scope conversation with the client before the damage was done."
— Operations lead, 9-person digital agency
05. When the Numbers Show a Problem
Projected margin is significantly below target. Here's what that actually means and what you can do about it — because 'work faster' is not an answer. Diagnose first: where did the hours go? There are four common causes: Scope expansion — the client added requirements not in the original brief. Response: scope conversation and change order. Estimation error — the work was genuinely harder than expected. Response: absorb this time and improve future estimates. No client conversation needed. Revision overload — more rounds than contracted. Response: scope conversation about additional revision fees. Operational inefficiency — the team spent time on things that shouldn't have taken that long. Response: internal process fix; absorb this time. Scope expansion and revision overload are recoverable through client conversations. Estimation errors and operational inefficiency are learnings that should inform your next project quote, not reasons to ask the client for more money.
06. The Three Levers You Can Pull Mid-Project
Lever 1 — scope conversation: if the hour overrun is driven by work the client added beyond the original brief, the conversation is: 'We've tracked 28 hours against a 40-hour estimate. Looking at what's remaining, we're projecting 48 hours total. The additional 8 hours cover [specific scope items]. We can complete these as a change order at $960, or adjust the remaining scope to fit the original estimate.' This conversation is much easier mid-project than after delivery. Lever 2 — scope reduction: if the scope conversation isn't appropriate, the alternative is to deliver the original scope and nothing more. This requires a clear brief that defines what 'done' looks like. Lever 3 — accelerated delivery: sometimes the right response is to throw more senior resources at the problem to reduce total hours. A task that takes a junior 8 hours might take a senior 4. The labour cost may be similar, but the project closes faster and frees capacity for other work.
07. Building the Habit Without a Spreadsheet
The reason most agencies don't run mid-project margin checks isn't laziness. It's friction. Hours live in Toggl. Revenue lives in a proposal doc. The rate card lives in someone's head or an old spreadsheet. Assembling these three things for a 10-minute check takes 25 minutes of tool-switching — which means it doesn't happen. The check becomes routine when the three numbers are visible in the same place. If your task management tool shows hours tracked per project alongside project value and team rates, the check takes two minutes. If it requires opening three tools, it takes 25 minutes and gets skipped.
See real-time hours and project margin in one place.
Know if a project is on track financially before it closes — not after.
