DEV Community: Tolmete

Your Project Is on Time. So Why Is It Losing Money?

Denis Salatin — Mon, 09 Nov 2026 09:32:22 +0000

A fixed-price project ships on the agreed date. The client signs off, the delivery lead closes the board, and the status report stays green from week one to week twelve. Then finance runs the numbers: the project closed at 32% margin against a 45% plan. Nobody missed a deadline, yet the money is gone.
This gap between schedule health and margin health is where most revenue leakage in service companies hides. Tolmete, an AI Early Warning System for Service Companies, uses AI delivery intelligence to bring project activity, budget figures, and contract terms into one view. This helps teams spot margin risks before a project is closed. A common source of trouble is scope creep in project management, when teams take on small, unplanned additions to keep the original release date.
The previous post on this blog explored why dashboards tend to show problems only after they happen. This article takes the discussion further, looking at what happens when a project stays on schedule but starts losing money — and how AI can uncover margin risks before the deadline.

Why On-Time Projects Hide Revenue Leakage

Time is tracked throughout a project. Cost is often tracked in retrospect. Teams know exactly how many days remain before delivery, but may not realize how much extra effort the work is consuming. By the time finance reviews the numbers, the margin damage may already be done.
The project began with a $120,000 fixed fee and an estimate of 1,200 hours at $55 per hour. With planned costs of $66,000, the expected professional services gross margin was 45%. Actual delivery required 1,480 hours and $81,400, cutting the margin to 32%. That's below the 37.7% average project margin reported in SPI Research's 2026 benchmark. The team delivered on time, but the extra 280 hours came at a cost. They came from three sources.

Scope Creep Absorbed to Protect the Date

Around 110 hours were spent on client requests that came in through chats and calls: an additional export format, a redesigned onboarding screen, and two extra user roles. Each request seemed minor on its own. None resulted in a formal change request because the team didn't want to put the release date at risk. Instead, they agreed to the changes, put in extra hours, and delivered on time.

Hours That Never Reach an Invoice

A requirement change in week six led to another 90 hours of rework. On fixed-price projects, those hours cut into the margin. On time-and-materials projects, they can become unbilled hours if no billable task or time entry captures the work. This is revenue leakage: costs the company absorbs but never passes on to the client.

A Cost Overrun Hidden in Senior Hours

Another 80 hours went into getting a stalled payment integration back on track. With only three weeks left, two senior engineers had to step in and resolve the issue. But the cost calculation above treats every hour equally. In reality, senior engineering time comes at a higher rate than the mid-level effort budgeted initially. This made the cost overrun larger in financial terms than the 80-hour increase suggests, likely pushing the actual margin below 32%. The release stayed on schedule because the team brought in its most expensive people.

High Resource Utilization Can Fund a Losing Project

During those twelve weeks, the team looked excellent on paper. Resource utilization stayed above 90%, while the billable utilization rate also looked healthy because most of the extra hours were logged against the client project. Both metrics show how much of the team’s time went into project work. Neither reveals whether that time was actually priced into the contract.
This is the trap for small and mid-sized service companies. A full team can signal strong demand. A full team can also signal absorbed overage. Utilization reports cannot tell the two apart without the budget and the agreed scope next to them.
Curious how much margin your own on-time projects lose? The ROI calculator gives a quick estimate based on team size and revenue.

Budget Variance Is the Earlier Signal

Schedule progress and budget burn move at different speeds, and the distance between them is the earliest warning a project gives. Budget variance compares the share of budget consumed with the share of work completed. Here is how it looked on the same project:

By week four, the project had burned five points more budget than progress justified. That was the moment to ask whether the extra export format belonged in the contract. By week eight, the gap had reached 13 points, and the remaining options were cutting scope or absorbing the cost. The schedule column stayed on plan the entire time.

Where Professional Services Automation Software Stops

Most service companies already collect the data needed to see this. Professional services automation software, project accounting software, and time tracking for professional services hold the hours, rates, budgets, and invoices. The problem comes down to timing and disconnected data. Approved timesheets arrive days after the work is done. The project scope is documented in a signed SOW, while ticket activity is tracked in Jira. Each system provides accurate information, but none checks a new ticket against the contract as soon as it appears.
Delivery leads end up doing that comparison by hand, usually in a Friday review and often with partial data. For a company running fifteen or twenty projects in parallel, the manual version fails first on the projects that look healthiest, because nobody has a reason to open them.

How AI Turns Project Data Into Margin Decisions

AI is becoming increasingly common across professional services. SPI Research reports that 43.6% of projects used AI in 2026, compared with 23.1% in 2025. However, stronger delivery performance hasn't led to the same level of improvement in profitability. Most AI tools help teams get tasks done faster. They don't necessarily show whether projects are becoming more profitable.
AI revenue intelligence gives service teams a way to see how delivery decisions affect project finances. It brings together estimates, approved hours, task updates, and agreed scope, then checks them against the budget throughout the project. A delivery lead can use this information in three ways:

A margin forecast. Based on the current burn rate, what margin is the project likely to deliver? A 34% forecast in week four gives the team time to respond. The same figure on the final invoice only explains what went wrong.
A likely cause. The delivery lead can see what is driving the variance, from unapproved scope additions and underestimated tasks to hours that don't correspond to any recorded project activity.
A next step. Draft a change request, re-sequence the backlog, or return a senior engineer to the critical path, with the expected margin impact of each option shown. AI won’t replace the conversation between a delivery lead and a client. It can, however, bring it forward — before small issues turn into costly problems — and give both sides real project data to work with. That’s the practical side of delivery risk management: fewer financial surprises and more room to act before the contract is closed.

A project that hits its deadline by burning extra senior hours has already made a pricing decision. The team simply made it without seeing the numbers.
— Denis Salatin, CEO of Lumitech and founder of Tolmete

Scope Creep Has a Price Before It Has a Deadline

The problem with scope creep isn’t just the extra work. It’s the delay between accepting that work and seeing its financial impact. A project can stay on schedule while its margin steadily declines. By tracking professional services profitability throughout delivery, companies can address the trade-off in time: bill for additional work, defer it, or accept the cost with a clear understanding of its impact.
On-time delivery remains a useful metric. It answers one question well, and margin needs a question of its own.
To see this on live project data, start a free trial and connect Jira, Git, or your time logs.

Dashboards Tell You What Happened. Tolmete Tries to Tell You What’s Going Wrong Now

Denis Salatin — Tue, 20 Oct 2026 13:14:55 +0000

Think of a delivery lead at a mid-sized software development agency with 50 employees. Every Monday, they open the same business intelligence dashboard. With utilization at 85% and revenue on track, there are no obvious signs of trouble. Three weeks later, finance closes the month, and one fixed-price project is 30% over budget. The dashboard was accurate the whole time. It simply reported what had already happened.
Tolmete focuses on the gap between spotting a problem and seeing its financial impact. Its AI early warning system helps service companies monitor delivery, time, utilization, and financial data while projects are underway. It identifies patterns linked to agency margin leakage early enough for teams to respond before the impact appears in the P&L.
Below is a practical look at why classic reporting misses these problems and what changes when predictive analytics works on live delivery data.

Why a Business Intelligence Dashboard Always Arrives Late

A business intelligence dashboard runs on closed data such as approved timesheets, posted invoices, and finished sprints. That design makes it reliable for profitability analysis and board reporting. It also makes it slow. By the time hours are approved and costs are allocated, the decision that caused an overrun is usually two or three weeks old.
Industry data highlights the operational risks of identifying problems too late. Deltek’s 2026 SPI Professional Services Maturity Benchmark summary puts billable utilization at 66.4% in 2025, the lowest level in the study’s history. Average project overruns stood at 10.7%, above the 10% threshold linked to growing pressure on margins and client relationships. Dashboards provide visibility into performance, but teams also need actionable alerts early enough to prevent small deviations from becoming costly problems.

The Real Cost That Utilization Management Can Miss

Traditional utilization management measures how busy people are. With 90% resource utilization, employees may look highly efficient on a dashboard. But the fact that they are busy doesn’t mean their work brings profit to your business. Here are four ways a busy team can quietly lose money:

Unplanned work. What starts as a client’s “small tweak” expands into 30 hours of extra work, with no change request in place.
Rework loops. The same module is rewritten three times with little net progress.
Stalled tasks. An 8-hour estimate turns into 28 hours on the critical path, often before the team realizes how much time has been lost.
Unverified hours. Logged time has no matching commits or ticket movement. These patterns all push utilization rates upward. Revenue leakage in service companies rarely shows up as idle time. More often, it hides behind a full project board. Capacity planning and resource planning tools help managers see which team members will have spare capacity next month. Mature utilization management also checks whether the work done this month still aligns with the scope agreed with the client.

Tolmete as a Revenue Intelligence Platform for Service Teams

Sales teams use revenue intelligence to spot deals at risk before the quarter closes. Tolmete works as a revenue intelligence platform for signed work. It connects to the tools where delivery already happens (Jira, Git repositories, calendars, time logs, and communication tools) and links those signals to budget and contract data.

Predictive Analytics for Better Delivery, Time, and Cost Forecasts

With predictive analytics tools, teams can spot delivery risks before they escalate. By analyzing tickets, commit metadata, time logs, and calendar events, they uncover stalled tasks with rising hours, unplanned work outside the agreed scope, and estimates that repeatedly fall short of actual effort.
A single source rarely confirms a problem. However, when three sources reveal the same issue, the signal is much more reliable.
The outcome is real-time analytics that brings operational intelligence to delivery and finance, helping both teams make decisions based on the same data.

Project Risk Management That Quantifies Financial Exposure

Every risk comes with a dollar estimate, a straightforward explanation, and a mitigation plan teams can adapt. Project risk management is no longer about a simple discussion in a status meeting. Instead, it includes a specific action like submitting a change request, splitting a task, or re-planning the sprint. Tolmete can analyze metadata only, with no screen recording, keystroke monitoring, or individual performance scoring.

Most margin problems in a service company are visible on day three. Nobody looks at them until day thirty, because the report that would show them doesn’t exist yet.
— Denis Salatin, CEO of Lumitech and founder of Tolmete

Predictive Analytics in Practice: Day 3 or Day 10

A 200-hour sprint hits trouble on day three: an unapproved filter request pulls a senior engineer away from a critical-path API task. Hours climb, but high utilization keeps the dashboard looking healthy.
By day 10, all money is spent, but the team completed less than 50% of the tasks. Real-time predictive analytics can flag Scope Creep and Execution Delay much earlier, giving the delivery lead time to bill for extra work, defer it, or get the task back on track.

Project Risk Management Begins With Early Warning Signals

Dashboards aren’t going anywhere. Every service company needs a reliable record of what happened, with month-end profitability analysis depending on it. Project risk management, though, depends on timing. Tolmete’s own benchmark puts average leak detection at under one week with signals, compared with 6 to 8 weeks through standard reporting.
Packed boards don’t guarantee healthy margins. The real losses may be building up in the weeks your reports overlook