How to forecast project profitability before work starts

There's a Reddit thread that's currently ranking for this exact topic, and the whole premise is that project profitability is "basically a guess." I get why people feel that way. But forecasting profit before you start isn't fortune-telling, it's a repeatable calculation you can run on any project in about an hour.

This guide walks through the five-step method I used in my agency days to predict a project's margin before a single hour is logged. You'll get the formula, a worked example with real numbers, the benchmarks that tell you what "good" looks like, and the mistakes that quietly wreck otherwise sound forecasts.

Forecasting profit isn't guessing, it's math you do on purpose

I've watched plenty of teams treat profitability as something you find out at the end, like opening an exam result. It doesn't have to work that way.

A project profitability forecast is a pre-work estimate of what a project will earn after costs. You take the revenue you expect to bill, subtract the cost of delivering it, subtract a fair share of overhead, and you're left with a predicted profit and margin. That's it. If you want the mechanics of the after-the-fact version, our how to calculate project profitability guide covers the calculation in depth.

It helps to be clear on what a forecast is not. A budget is a fixed plan you set once and measure against; a forecast is a living prediction you update as facts change. If that distinction matters to you, the project budgeting guide draws the line clearly. Here, I'm focused on the forecast you build before the work is confirmed.

Why "we'll figure out the margin later" is how services firms lose money

The most expensive projects I've seen weren't the ones that blew up loudly. They were the quiet ones that looked fine on the surface and bled margin the whole way through, and nobody noticed until the final numbers landed.

Here's the pattern I keep seeing. A project gets priced on gut feel, work starts, scope creeps in politely one small favor at a time, and the team is too busy delivering to check whether the math still works. By the time someone runs the profitability report, the margin is gone. You can't un-spend those hours.

That's a painful place to be right now, because margins are already under pressure across professional services. Budgets are flat, clients are scrutinizing every invoice, and utilization is slipping while salary costs climb.

Forecasting before you commit changes the whole conversation. Instead of hoping a project pays off, you know its likely margin before you sign, which means you can price with confidence, push back on scope that erodes the number, and say no to work that was never going to clear your threshold. That's not accounting for its own sake. It's the difference between growth and running fast to stand still.

The firms that win in that environment aren't the ones cutting prices. They're the ones who know their margin before they say yes, and who can walk away from work that won't pay. When SugarCRM unified projects, time tracking, and billing in one place, they landed near-perfect invoicing accuracy, crediting less than $20K on more than $10M in annual invoicing. That's what happens when the money side stops being a guess. You can read the full SugarCRM customer story for the detail.

You can't forecast what you can't see: the inputs to gather first

Before running a single number, make sure three inputs are actually in front of you. In my experience, most bad forecasts trace back to one of them being missing, stale, or half-remembered rather than to a flawed method.

The first is a real rate card, with both billable and cost rates for every role. Billable rates tell you what you charge; cost rates tell you what delivery actually costs you. If you only have one of the two, your margin is a guess with extra steps.

The second is historical data from similar past projects. Your best estimate of how long something takes is what it took last time, not what you hope it'll take this time. Even a rough log of past hours by project type beats starting from zero.

The third is a defined scope. You can't cost work you haven't described, and vague scope is where fixed-fee margins go to die. I'd rather spend an extra hour tightening the statement of work than three days absorbing unbudgeted "quick favors" later.

• Rate card: billable and cost rates per role, refreshed at least yearly.

• Historical actuals: hours and costs from comparable past projects.

• Defined scope: a clear list of deliverables and what's explicitly out of scope.

Get those three on the table and the forecast almost writes itself. Skip any one and you're back to guessing, no matter how good your formula is.

The pre-work profit forecast: a five-step method

I've run this same sequence on tiny retainers and six-figure builds, and the steps don't change. What changes is how much detail each one deserves. Below is the method I'd hand a new ops lead on day one.

Step 1: Pin down what the project will actually bill

Start with revenue, because everything downstream is measured against it. For a fixed-fee project, your revenue is the agreed price. For time and materials, it's your estimated hours multiplied by your billable rates, so your hours estimate is doing double duty as a revenue driver.

Retainers need a slightly different lens: forecast the revenue for the period, then be honest about the scope you're committing to deliver inside it. Watch out for discounts here too; a 10% "relationship discount" comes straight off the top of your margin, not off some abstract list price, so bake it into the revenue line rather than pretending it's free. If revenue estimation is where you tend to wobble, our revenue project planning breakdown goes deeper than I will here.

Step 2: Forecast the true cost of delivery, not just the obvious labor

Cost is where forecasts go to die, usually because people count salaries and stop. Your delivery cost is broader than that. It's labor at cost rate, plus subcontractors, plus billable expenses, plus any tools or licenses the project consumes.

Labor is the big one, and the trick is using cost rates, not billable rates. If a designer bills at $150 an hour but costs you $75 an hour fully loaded, the $75 is what belongs in your forecast. For a fast, defensible hours estimate, lean on historical actuals from similar past projects rather than optimism. Our project cost estimation guide has the estimation techniques worth stealing.

Let me make it concrete. Say you're quoting a $60,000 fixed-fee website build. You estimate 400 hours at a blended cost rate of $75, so labor costs $30,000. Add a $5,000 subcontractor for motion design and $2,000 in stock assets and hosting. Your direct cost is $37,000.

That leaves a gross profit of $23,000, or a 38% gross margin. Looks healthy. Hold that thought, because we're not done. If you want a repeatable method for the cost half specifically, cost forecasting methods covers trend and historical approaches.

Step 3: Load in overhead so the margin is honest

Overhead is the step most people skip, and it's the one that turns a "great" project into a break-even one. Your rent, software, admin salaries, and non-billable time all have to be paid for, and every billable project carries a share.

The simplest approach is an overhead rate: total your annual overhead, divide by total billable revenue, and apply that percentage to each project. Say your firm runs at 20% overhead; on our $60,000 build, that's $12,000 coming off the top. You can allocate on a different base if revenue skews things, like per billable hour or per head, which is often fairer when project sizes vary. Whatever base you pick, apply it consistently across projects, because a forecast that treats overhead differently on every job can't tell you which work is actually your most profitable.

Now the real picture: $23,000 gross profit minus $12,000 overhead leaves $11,000 net profit, a net margin of about 18%. Still fine, but a lot slimmer than the 38% that would have gone into a pitch deck if you'd stopped at Step 2. That gap is exactly why margins slip on paper-healthy projects. For the fuller treatment, our financial planning for projects margin playbook connects estimates, allocation, and targets.

Step 4: Calculate the forecast margin and pressure-test it

Now put it together. Your forecast margin is the profit that survives revenue, cost, and overhead, expressed as a percentage:

$$\text{Forecast margin (\%)} = \frac{\text{Estimated revenue} - \text{Estimated cost} - \text{Allocated overhead}}{\text{Estimated revenue}} \times 100$$

One number is never enough, though. Run three versions: an expected case, a best case, and a worst case where hours run over. If those same 400 hours become 460, your labor cost climbs by $4,500 and that 18% net margin drops to around 11%. Knowing that before you sign tells you how much cushion you actually have. Benchmarking your billable rates against a target is easier with a tool like the billable utilization rate calculator.

Step 5: Set your go / no-go line before you talk price

Decide your minimum acceptable margin now, while you're calm and the client isn't on the phone, then hold the line: if the forecast comes in below it, you either renegotiate scope, adjust the price, or pass. Say your floor is 15% net; our example build forecasts at 18%, so it clears, but only just, which tells you there's almost no room for overruns. That single number turns a gut-feel "sure, we can do that" into a decision you can defend to a partner or a CFO.

Every project cost hides in one of these buckets

When a forecast misses on the cost side, it's almost never because someone fabricated a number. In my experience it's because a whole category got left out entirely. I use a simple checklist of buckets so nothing slips through.

The pattern is clear: the buckets people forget are the indirect ones. Get all five on the table before you price, and your forecast stops springing leaks.

I add one more habit on top of the checklist: a small contingency line, usually 5% to 10% of estimated cost, depending on how well I know the client and the work. New client, fuzzy scope? Lean toward 10%. Repeat client, tight brief? You can trim it. The point isn't to inflate the number, it's to price in the reality that estimates are estimates, and to protect the margin when the inevitable surprise shows up.

What a healthy forecast margin looks like by services model

People always want a single "good margin" number, and I understand why, but it depends entirely on how you sell the work. In my experience the target that keeps a fixed-fee project safe would be reckless for a thin-margin retainer.

Professional services firms typically target net margins in the 20% to 35% range, though gross margins on delivery run higher. Here's how I think about it by engagement model.

Notice how the biggest forecast risk shifts with the model. On fixed fee, the danger is scope creep, because your revenue is locked while your costs can wander. On time and materials, the risk flips to unbilled hours, since every hour someone forgets to log is revenue you'll never see. Retainers hide their risk in over-servicing, where the team quietly does more than the monthly scope and nobody adjusts the number. Knowing which risk your model carries tells you exactly what to watch once the work starts.

Use these as starting points, not gospel; your real targets should reflect your own overhead and market. If you want the metrics that sit underneath these numbers, our project profitability metrics agencies should track guide is the companion piece. And once you know your target margin, the revenue gain calculator helps you see what protecting it is worth over a year.

Keeping the forecast honest once the work starts

A forecast is only useful if it keeps up with reality, and here's where I see the most value left on the table. Teams do the hard work up front, then never look at the number again until the project closes. By then it's a post-mortem, not a forecast.

The fix is a re-forecast rhythm. I compare planned hours and costs against actuals on a set cadence, so the gap between "what we thought" and "what's happening" never gets a chance to hide. On a fast project that's a weekly check; on a longer build, I do it at every milestone.

What you're watching for is variance, and specifically the direction of travel. If a project is 40% through its hours but only 25% through its deliverables, that's an early margin warning, and you still have time to act. Catch it at 40% and you can rescope or reset expectations. Catch it at 95% and you're just writing down the loss.

A quick way to read the gap is to compare the percentage of budget spent against the percentage of work delivered. If you've burned 60% of the hours to produce 45% of the deliverables, your effective cost per deliverable is climbing, and your forecast margin is already lower than the version you signed. Spotting that at the halfway mark gives you real choices; spotting it at delivery gives you a lesson.

Change orders deserve their own discipline. Every scope change should trigger a forecast update, not a mental note. When a client adds "one more round of revisions," I want that reflected in the numbers the same day, with a decision about whether it's billable or absorbed. That's the difference between a margin you manage and a margin that manages you.

Five ways profit forecasts quietly fall apart

I've built and reviewed a lot of these forecasts, and the failures rarely come from bad math. They come from the same handful of habits, and once you know them, they're easy to catch.

• Optimism bias on hours: I've seen teams forecast the version of the project where nothing goes wrong. It never happens, so pad your hours toward your historical average, not your best day.

• Ignoring overhead: A gross margin with no overhead line is a fantasy number. I've watched "profitable" projects turn out to barely cover the rent once the real share went in.

• Stale rate cards: Salaries rose, your cost rates didn't, and now every forecast quietly understates cost. Refresh rates at least once a year.

• No re-forecast cadence: A forecast you set once and never revisit is a budget in disguise. Update it as real hours land so surprises surface early, not at the final account.

• Treating scope creep as free: Every "quick favor" has a cost. If it isn't tracked and, where appropriate, billed, it comes straight out of margin.

How I forecast profitability in Teamwork.com before the work is confirmed

I'll be honest about where I land after years of doing this by spreadsheet: the method works, but it's fragile when the inputs live in five different places. Your rate card is in one file, actual hours in a timer app, budgets in a finance sheet, and by the time you've stitched them together, the forecast is already out of date. The reason we built the profitability tools the way we did at Teamwork.com is to make the forecast a live number instead of a Friday-afternoon reconstruction, with the rates, hours, budgets, and margins all sitting in one connected system.

AI Forecaster Predict revenue, cost, and profit in one click by turning your historical data into a forward-looking forecast, so you can decide whether a project is worth taking before you commit the team.

Budget tracking with threshold alerts Set fixed-fee, time and materials, or retainer budgets and get alerted before you cross a threshold, so an overrun surfaces at 80% spent, not at the final invoice.

Time tracking with billable and cost rates Capture real hours against billable and cost rates as the work happens, so the labor side of every forecast is grounded in what delivery actually costs, not what you hoped it would.

Resource Scheduler Forecast who's delivering the work and whether you have the capacity to say yes, so your cost and timeline estimates rest on real availability instead of wishful staffing.

Profitability report Watch forecast margin against actuals in real time, so the moment a project drifts from its plan you can course-correct while there's still margin left to protect.

If you'd rather start from a structure than a blank page, the project profitability tracking template gives you the budget, expense, and margin fields already wired up.

FAQ

How do you forecast project profitability before work starts?

You forecast project profitability by estimating the revenue a project will bill, subtracting the full cost of delivering it, and subtracting a fair share of overhead. Build the estimate from historical actuals rather than optimism, then run best, expected, and worst-case versions. Compare the resulting margin against a go/no-go threshold you set in advance, so you know whether to accept, rescope, or pass. The whole process takes about an hour once your rate card and past project data are in place.

What's the formula for forecast profit and forecast margin?

Forecast profit equals estimated revenue minus estimated delivery cost minus allocated overhead. To get forecast margin, divide that profit by estimated revenue and multiply by 100. Delivery cost must include labor at cost rate, subcontractors, and expenses, not just salaries.

What's the difference between a project budget and a forecast?

A budget is a fixed plan you set once and measure performance against, while a forecast is a living prediction you update as the project's facts change. You approve a budget at kickoff; you revise a forecast throughout delivery. Think of the budget as the target and the forecast as the GPS that tells you whether you're still on course. Both matter, but only the forecast tells you where the project is actually heading.

Is a profit forecast the same as a cash-flow forecast?

No. A profit forecast predicts whether a project will earn more than it costs, while a cash-flow forecast predicts the timing of money in and out. A project can be profitable on paper yet still create a cash gap if a client pays late. You need both views to run client work safely.

What's a good profit margin for an agency or services project?

A healthy services project typically targets a gross margin between 40% and 50% on fixed-fee work, with net margins landing lower after overhead. The right number depends on your overhead structure and engagement model, so treat industry ranges as a starting point. Time and materials work often runs slightly lower on gross margin but carries less scope risk, while retainers can hold higher margins if you protect against over-servicing. What matters most is setting a target and forecasting against it before you price.

How often should I re-forecast a project's profitability?

Re-forecast on a fixed cadence: weekly for fast-moving projects and at each milestone for longer engagements. Update the forecast as real hours and costs land so variances surface early enough to act on. Any significant scope change should also trigger an immediate update, rather than waiting for the next scheduled review. A forecast you set once and never revisit is just a budget wearing a disguise.