Paid Is Not the Same as Profitable

When a project wraps up, the focus typically moves toward the client settling the final invoice. When the invoice clears, the project feels like a win.

However, the invoice only confirms the revenue that came in. It says nothing about the actual costs incurred while the work was being delivered: the extra days, the additional revision rounds, and the hours you personally spent stepping in to keep the project on track.

So while a project can be paid in full, it might still have cost the business more than it brought in. Nothing on the invoice will show you that.

What the Usual Checks Miss

Most owner-led businesses rely on one of three signals to judge if work is profitable. Each answers a different question.

• The bank balance shows cash on a given day. However, since deposits from one project can cover the costs of another, a healthy balance can hide a project that lost money.
• The profit and loss statement shows the whole business, usually after the month or year has closed. Although it can split revenue by service line, it doesn't show which project made money and which didn't, because overheads and the owner's time are rarely split per project.
• A happy client shows the work was good. But over-delivery often produces the happiest clients and the thinnest margins.

These are useful measures, but none of them sets what a project was priced to recover against what it actually cost to deliver.

Until you make that comparison, profitability is an assumption.

Worked Example:
A Video Production Company

Take a corporate video production company quoting a brand film. Before the client signed, the studio spent six days on pitches and proposals.

The fee is $40,000, and the plan is 20 working days from pre-production to final delivery, with two rounds of revisions.

The studio runs several projects and service lines at once, and each one carries its share of the cost of keeping the business open: salaries, rent, equipment, software.

For this film, that share comes to about $900 for every working day the team spends on it. That cost does not stop when a project runs long.

Midway through, the client asks for a third round of changes, which brings a half-day reshoot and four more days in the edit suite. Then final approval sits with the client's leadership team for a week.

It is easy to assume the wait costs nothing, especially when the team has other projects to work on. But the business is losing money that week.

The running costs don't pause when a project stalls, but that project's contribution to them does. The profit from the other active jobs covers the gap, subsidizing a project stuck in limbo.

In total, the film takes 27 working days instead of 20. The client loves it and pays in full. But at what cost?

Figures are illustrative, not drawn from a specific company.

A $4,900 loss, absorbed by the business, on a project that was meant to earn $8,000.

Across 10 projects a year makes it an avoidable loss of $49,000.

How to Check If a Project Made Money

The scorecard above came from seven steps. Here is how to run them on your own projects. Most of the numbers are already in your records.

1. Start with what the client actually paid, and when.
   Use the final amount received, not the quote, after discounts, write-offs and extra work you absorbed. If it arrived 60 days after delivery, the business funded the project in the meantime. That is how a business ends up making money but short of cash.
2. Subtract the direct costs.
   These exist only because of this project: freelancers, subcontractors, materials, travel, equipment hire.
3. Count the days the project actually ran.
   Count from kickoff to final delivery, including revision rounds, reshoots and the days it sat waiting for approval. Overruns are common. In the Project Management Institute's 2018 Pulse of the Profession survey, 52% of completed projects experienced scope creep.
4. Charge the project its share of running costs for every one of those days.
   Rent, salaries, software and insurance don't stop while a project runs long. Multiply your daily running cost for that service line by the actual days, not the planned ones.
5. Add the time no invoice covered.
   This means pitching, proposals and scoping calls before the work was won. It also means the hours the founder spent stepping in to rescue it (more on this in Why Your Business Cannot Run Without You). Count those days at the same daily running cost.
6. Pull out the figures behind your original quote.
   These are the days you planned, the direct costs you estimated and the profit you built in. Note anything from steps 2 to 5 that the quote never included. Those are gaps in the quote, not just in the delivery.
7. Compare the two.
   The difference shows exactly where the margin and cash went: more days, higher costs, or costs the quote never priced. That difference is what your next quote has to cover.

Why This Matters Before the Next Quote

If you never measure whether a project made money, the next price is built on the same assumptions as the last one.

The extra days, the unpriced pitching and the owner's hours repeat on every project, and revenue grows while the margin does not. This is one of the patterns behind a business that is busy but not profitable.

Knowing the real result of past projects is what makes the next price defensible. It turns pricing from guesswork with an invoice attached into a decision you can stand behind.

What to Settle Before the Next Project Starts

The loss in the example was decided before the first day of work. Four questions, answered before you quote, close most of that gap:

• What does this work cost you to deliver, not just to produce? Include the cost of keeping the business running while the project is live.
• How long will it really take? Price the timeline you expect, not the one you hope for.
• What is included, in writing? The number of revision rounds, the approval timeline, and what happens when either runs over.
• What did it cost to win? If pitching and proposals take weeks, that time belongs in the price.

A price that answers these four questions doesn't depend on delivery going perfectly.

Frequently Asked Questions

How do I know if a project actually made money?

Compare what the project was priced to recover with what delivery actually cost. That includes direct costs, the cost of running the business for every day the project ran, and the time spent winning it. If the price does not cover all of that, the project lost money, even if the invoice was paid in full.

What numbers do I need to check if a project made money?

What the client paid, the direct costs, the actual days the project ran, the running costs for those days, any unbilled time, and the figures behind your original quote to compare against.

Why does a fully paid project still lose money?

Because the price was fixed before delivery began, and delivery took more than the price allowed for. Extra revision rounds, delays and owner involvement add days and costs that no one invoices. The client pays the agreed fee, and the business absorbs the difference.

Isn't my profit and loss statement enough to tell me?

A profit and loss statement shows how the whole business performed over a period, usually after it has closed. It can split revenue by service line, but it rarely shows which projects made money and which lost it, because overheads and the owner's time are seldom split per project. Profitable work can hide unprofitable work until the overall numbers start to slip.

What costs do project prices usually leave out?

The most common gaps are the cost of running the business while the work is delivered, the days a project runs beyond its plan, the time spent pitching and preparing proposals before a client signs, and the owner's own hours spent keeping projects on track.

How often should I check whether projects are profitable?

At the close of every project, and before the next quote goes out. Checking once a year shows the damage after it has happened. Checking per project shows which prices need to change while there is still time to change them.