Services firms: projects, people and cash flow on one system.

A service contract rarely goes into the red through one big mistake; it bleeds out through hours nobody could attach to anything. But when people’s time, work progress, and finance sit in three different places, you usually only learn a contract lost money after it already has. This article analyzes why these three pieces of data must read from one source, and the conditions for unification to actually give you decisions in time.

In services, profit and loss live at the project level

Unlike manufacturing or retail, a services firm’s product is mostly people’s time. A company can have a positive overall margin yet still be negative on many contracts — the profitable ones are just carrying the loss-making ones, and no one sees it until final settlement. To manage profit, you have to see it where it actually forms: each project, each contract, as close to real time as possible.

Time is a cost — tie it to the project

The biggest cost in services is labor hours. When time entries are recorded tied directly to a project and contract — rather than an aggregate timesheet at month end — you see the real cost of goods of each project while it’s running. A fixed-price contract that starts eating more hours than planned shows up the moment hours cross the threshold, not two months later when accounting finishes adding them up. The condition for this is concrete: hours must be recorded by project, and finance must read that exact data rather than a re-keyed copy.

Revenue recognized by real progress

Many services contracts recognize revenue by percentage of completion. If progress lives in the project manager’s head and finance only learns of it through a status email, the recognized revenue number is always a guess. When progress and finance read the same data, recognized revenue tracks the real work done, and the per-contract profit report stays current instead of being rebuilt each period end. This is also the foundation for a trustworthy cash-flow forecast, because you know which work has qualified to be invoiced.

• Labor cost of goods consumed against each project’s budget.
• Actual percentage of completion against the portion already invoiced.
• Estimated remaining margin of each contract at the current rate of hours consumed.
• Billable hours against total hours, by person and by project.
• Payment milestones that are due but not yet invoiced or collected.

Decide while there’s still time

The real value of unification isn’t a prettier report — it’s an earlier warning. A project sliding on margin should signal while it’s still running, when you can still adjust scope, renegotiate with the client, swap in more suitable people, or rein in the extras. When that signal only arrives at settlement, every option has closed and all you can do is record a loss. On one system, the gap between what’s happening and what you know shrinks to the point where the decision still means something.

Unification only works on real timesheets and honest estimates

Be honest: a unified system is only as accurate as its inputs. If staff log time in a lump at week’s end from memory, or assign hours to a project for convenience rather than accuracy, the per-project profit report will look smooth but be wrong. Likewise, a percentage of completion self-assessed by the manager can be overly optimistic. Unifying data makes these distortions easier to see and easier to trace, but it doesn’t replace a culture of honest, timely recording. This is as much a habit change as a tool change.

Where to look to see your project data split three ways

A few signs that your project data is split three ways:

• You only learn whether a contract profited or lost after it ends.
• Timekeeping, progress, and finance live on three tools that don’t talk to each other.
• The per-project profit report has to be built by hand each period and is always late.
• Recognized revenue is based on estimated progress, not the real work recorded.
• You can’t say right now which project is consuming hours over budget.

Connect timekeeping to the project first

You don’t need to roll out everything at once. The first step is almost always connecting timekeeping to the project, because that’s where cost forms and also the data that’s most often kept separate. Pick a group of running projects, require hours to be logged by project daily, and tie that data to the contract budget. Just being able to see labor cost of goods in real time is enough to change how you decide. From that foundation, expand to progress-based revenue recognition and cash-flow forecasting. The invariant principle: in services, learning a contract lost money at settlement is learning too late — the goal of unification is to pull the moment you know forward, ahead of the moment you can still do something about it.

Related articles