Sold hours get agreed in a CPQ tool or a signed SOW, then handed off to your PSA, Certinia, OpenAir, or Kantata, through a manual step. When that step breaks, nothing alerts anyone. The PSA just keeps showing whatever was entered last. Picklii compares both sides and matches every project and role, so you see exactly where the two stopped agreeing.
| Project | Role | Burn | Exposure |
|---|---|---|---|
| PRJ-1004 | PM | absent | $14,850.00 |
| PRJ-1002 | Senior Consultant | 91% | $11,100.00 |
Revenue leakage figure: SPI Research, Professional Services Maturity Benchmark, as summarized by multiple PSA vendors. Waste figure: PMI, Pulse of the Profession, 2018 (9.9% of every dollar invested in projects, industry-wide), the most recent PMI report with this measure; newer editions report overrun rates instead (see the third figure). Budget overrun figure: PMI, Pulse of the Profession, 2026. Industry averages, not a guarantee for any specific business.
The handoff between the system that sells the hours and the system that tracks them has no failure mode anyone can see. That's a visibility problem, not a carelessness one.
Sold hours are supposed to flow into the PSA as the budget baseline every timesheet and margin calculation gets measured against. In practice, that flow is a report and an import, run by a person, on a schedule nobody owns.
When the import fails partially or entirely, there's no error state. The PSA shows the last figure that landed correctly, which may be stale, wrong, or missing entirely. A broken sync looks exactly like a normal report.
Across dozens of concurrent engagements, checking by hand isn't a plan. Issues surface reactively: from a client, from a PM mid-project, or from finance at quarter close, which is the most expensive time to find them.
Switching PSA platforms doesn't fix it either. That changes the tool, not the process, and the manual step survives the migration unless someone redesigns it on purpose.
No integration project, no IT ticket, and no access to your PSA required. Two exports you can already produce today.
A project 90% through a budget that's wrong is a five-alarm fire. A brand-new project with a small variance is a background item. Picklii puts them in that order.
| Project | Role | Sold | Budgeted | Burn | Exposure | Severity |
|---|---|---|---|---|---|---|
| PRJ-1004 | PM | 90 | absent | — | $14,850.00 | High |
| PRJ-1002 | Senior Consultant | 400 | 340 | 91% | $11,100.00 | High |
| PRJ-1001 | Senior Consultant | 200 | 200 | 23% | — | Unscored |
Illustrative, computed from the sample files Picklii ships with, not customer data.
A role sold on the SOW and absent from the PSA entirely is the failure this exists to catch, so it's never buried. It ranks as High no matter how modest its computed exposure looks.
Every gap carries an exposure figure at the role's rate, so the conversation with finance starts at the number rather than at the discrepancy. Where a rate has to be estimated, we say so.
Severity weights exposure by how much of the questionable budget has been consumed, because the cost of a wrong budget rises with every hour delivered against it.
At portfolio scale, with dozens of engagements running at once, spot-checking one reconciliation at a time doesn't scale. The Dashboard is every active project, ranked by what needs attention first, not just the one you happened to just run.
PRJ-1004
Live since Jun 1, 2026
$14,850.00No budget to burn against
PRJ-1002
Live since May 1, 2026
$11,100.00PRJ-1001
Live since Mar 15, 2026
No scored exposureNo budget to burn against
Illustrative, computed from the sample files Picklii ships with, not customer data.
Picklii is still early, and we're upfront about that. What it needs next is a services organization running a real PSA, willing to point it at real portfolios and tell us plainly where it falls short. Not another feature.
Interested in being a design partner? Email support@picklii.com.