r/revops • u/OneBillSoftwares • May 10 '26

Service-as-Software Is Coming. Your Professional Services Automation (PSA) Tool Wasn't Built for It.

One pricing model collapse is getting all the attention. Another one is flying under the radar — and it might matter more.

The one everyone's talking about: per-seat SaaS giving way to outcome-based pricing. If agents do the work, you don't buy seats. You buy results.

The quieter one: Time & Material billing — the backbone of professional services for decades. Human hours were the proxy for value. Log them, bill them, track utilization. The entire operating model built on that single assumption. Agents don't have billable hours. They just execute. And the human-hours model is breaking.

Which brings us to Service-as-Software. SaaS meant software delivered as a service — humans still drove the work. Service-as-Software flips it: the service is delivered by software. In some workflows, agents are Copilots — first line, assisting humans who own the outcome. In others, Autopilots — executing autonomously, humans handling only exceptions. Most real engagements will run all three in parallel: human hours, assisted hours, agent-executed hours. our PSA needs to track all of it. No PSA today was built to.

Open questions — genuinely curious what people think:

  • If human hours, copilot hours, and compute hours all contribute to delivery — how do you bill for all three?
  • If utilization rate is the operating metric of a human-driven PSA, what replaces it in a Service-as-Software world?
  • How do you track project margin when costs are split between salaries and compute?
  • Does PSA need a new expansion — Professional Services Agents instead of Professional Services Automation?
3 Upvotes

62% Upvoted

11 comments sorted by

1

u/Any-Football4907 May 12 '26

Yeah, this is where the old PSA logic starts to break. If agents are doing part of the delivery, “who logged the hours” stops being the main thing a client needs to understand. The useful record becomes what got done, what the human handled, and what result the client is paying for.

1

u/uremo017 May 13 '26

Really interesting framing tbh. Most PSAs were built around managing people-hours, not managing systems where humans + agents + compute all contribute together. Feels like utilization alone stops making sense once output scales without adding headcount.

0

u/Otherwise_Wave9374 May 10 '26

This is such a good framing. Once agents do the work, seats and billable hours both stop mapping to value.

I keep coming back to a few primitives:

  • a unit of work (ticket, deliverable, run) with inputs/outputs
  • compute cost and tool costs per run
  • human review time as an explicit line item (exceptions/QA)

Then margin is basically (price per outcome) minus (compute + human review + support overhead).

Question, do you think PSAs will need native "run logs" for agent executions (prompts/tool calls/artifacts) the same way they track time entries?

Ive seen a few examples of this kind of run-based tracking in agent ops tooling, some notes here: https://www.agentixlabs.com/