The Hidden Revenue Signal in Your Project Data

On the first of every month, someone at your firm pulls a report. Total invoiced last month. Total collected. Outstanding balance. Maybe a chart showing the last twelve months side by side.

That report tells you what happened. It doesn't tell you what's happening right now, or what's about to happen next. For a firm billing monthly across projects that run six to eighteen months, the difference between backward-looking totals and forward-looking signals is the difference between managing your practice and reacting to it.

The signals are already in your data. You're just not looking at them the right way.

The business-day problem

May has 22 business days. April has 22. February has 20. January has 22 but realistically 19, because the first week after the holidays is always slow. When you pull "May invoiced" versus "April invoiced" on the 14th of May, you're stacking 10 business days of activity against 22 days of final totals. The comparison is meaningless. May will always look behind.

Business-day normalization fixes this. Instead of comparing May's running total to April's final total, you compare May through business day 10 to April through business day 10. Same window, same lens. If May is $18,000 behind April at that point, that's a real signal. If May is $3,000 ahead, that's also a real signal, one your month-end report won't surface for another three weeks.

The math is simple. The problem is that no ERP does it automatically. They all report calendar-month totals. The business-day comparison, the one that actually tells you whether you're on pace, ends up as a manual spreadsheet that someone builds and then stops updating by week two.

Client-specific invoice timing

Every firm has clients with patterns. The developer who pays in 15 days, reliably. The institutional client whose AP department only runs on the 1st and 15th. The government agency that takes exactly 45 days regardless of your due date. Three years of payment data contains enough signal to predict, within a few days, when each client will pay each invoice. Not because anyone programmed their AP process into your system. Because the pattern is visible in the data.

More importantly, deviations from the pattern mean something. A client who has paid in 22 days for two straight years suddenly taking 38 days is a signal. It might mean a process change, a merger, a new accounting system. It might mean financial strain. It might mean your invoice is sitting in someone's spam folder. The right response depends entirely on the cause. Escalating a relationship over what turns out to be a process change is counterproductive. Letting a legitimate credit risk slide because the number didn't look alarming enough is expensive.

Your ERP shows you the 38-day number. It doesn't tell you that 38 is anomalous for this client, doesn't surface a likely cause, and doesn't recommend a next step. That's the gap.

The unbilled work blind spot

Every A/E firm has unbilled work. Time logged, work performed, invoice not yet sent. For T&M contracts, it's straightforward: billable hours times rate, minus what's been invoiced. That delta is money sitting in your timesheets waiting to become revenue. Fixed-fee is different but equally important. Say a project's contract value is $76,000. You've invoiced $63,800. The project is at 84% completion. You have $12,200 left on the contract. Whether that's profit or loss depends on whether your team can close the remaining 16% of work within the remaining budget.

Most firms track this project by project in a spreadsheet. A principal or PM reviews budget consumption against completion percentage and makes a call. At a firm with 40 active projects, that review takes two to three hours, and it happens, optimistically, once a month. The data to run this calculation already exists in your project management tools. Every time entry, every invoice, every budget. What's missing is the aggregation: a single view of total unbilled T&M across the firm, plus fixed-fee remaining value by project.

When you see that number, it changes how you think about the month. If invoiced revenue is $66,000 but unbilled work is $42,000, your projected month is $108,000, not $66,000. The invoicing isn't behind. The invoices just haven't been sent yet. Different problem. Different response.

Invoice velocity as a leading indicator

Here's a signal almost no firm tracks: invoice velocity. Not when invoices are paid, but when they're sent. If your firm typically sends 11 invoices per month and you've sent 4 by business day 10, you're behind pace. Filter to clients who received invoices in at least two of the last three months and you can identify exactly which expected invoices haven't gone out yet.

This is a leading indicator for cash flow. Late invoicing leads to late payment leads to cash flow pressure leads to line-of-credit draws leads to interest expense. The whole cascade starts with a PM who was too slammed to get an invoice out on time. Client-specific patterns add precision. If you typically invoice Meridian Development by the 5th and it's the 10th, that's a flag. Not a fire. A flag. Someone should check whether the PM is behind or whether there's a project issue holding up billing.

Track this across the firm and patterns emerge fast. Certain PMs invoice late consistently. Certain clients get invoices earlier because their projects are simpler to bill. September and December have systemic delays because of coverage gaps. These patterns have been in your data for years. Nobody looks at them because no tool presents them. Most PSA dashboards are expensive screenshots, not intelligence.

From signals to decisions

Revenue intelligence doesn't require new data. It doesn't require a new ERP, a new accounting system, or a new process. It requires connecting the data you already have in ways that surface actionable signals.

Business-day pacing tells you whether you're on track right now, not three weeks from now. Client payment patterns tell you what to expect and when to worry. Unbilled work tells you how much revenue is waiting to be invoiced. Invoice velocity tells you whether your billing process is keeping up with your project load. Each of these signals is a question your data can answer today.

ProLens reads your project management data and surfaces this layer of revenue intelligence. It's not a replacement for your financial systems. It's a lens on top of them that shows you what the monthly report can't. The question is whether you want to wait until month-end to find out, or whether you'd rather know now.