A short history of professional services software

From time-tracking spreadsheets to PSA suites to the emerging Professional Services OS category. How services firms got the tools they have, and why the next category exists.

Professional services software has evolved through four distinct generations since the 1990s: spreadsheets, first-generation PSAs, cloud PSA suites, and the emerging Professional Services OS category. Each generation solved the pain of the previous one and inherited its assumptions. Understanding the progression is the fastest way to see why services firms still run on a patchwork of disconnected tools. And why a single connected system is the obvious next step.

Generation 0: Spreadsheets and time sheets (1990s–early 2000s)

Before dedicated tools, services firms tracked engagements in Excel. A partner kept the pricing spreadsheet. An ops lead kept the utilization spreadsheet. A senior consultant kept the scoping template. When someone left, the spreadsheet went with them.

This era produced the habits that still haunt services firms: pricing by gut, scoping from the nearest similar proposal someone could find, and no feedback loop between what was sold and what was delivered.

Generation 1: First-generation PSAs (2000s)

OpenAir, Changepoint, and Kimble emerged to solve one specific problem: partners could not see utilization across the firm. The first-generation PSA was essentially a timesheet with reporting on top.

These tools shipped with a hard assumption: the engagement already exists when it enters the system. Scoping and pricing were someone else’s problem. Typically a scoping doc and a rate card spreadsheet. The PSA’s job started the day the project kicked off.

Generation 2: Cloud PSA suites (2010s)

Mavenlink, Kantata (formerly Mavenlink + Kimble), FinancialForce PSA, and others moved PSAs to the cloud and bolted on resource planning, revenue recognition, and invoicing. They became systems of record for the delivery phase of services firms.

But the core assumption from Generation 1 never moved: scoping and pricing still happened outside the system. By the mid-2010s, services firms commonly used a CRM for pipeline, a CPQ for some pricing (if any), a PSA for delivery, a finance system for revenue rec, and a knowledge base for anything learned. Five tools, five databases, zero feedback.

Generation 3: Productised services and CPQ pressure (late 2010s)

As SaaS companies built services arms, pressure to “productise” services grew. CPQs (Salesforce CPQ, Apttus, Oracle CPQ) tried to absorb services pricing, but CPQs assume configurable SKUs, not bespoke engagements. The result: either artificially standardised services, or a CPQ that was bypassed in favour of spreadsheets.

This is where most mid-market services firms still are today. A PSA for delivery, a CPQ or spreadsheet for pricing, a CRM for pipeline, a knowledge base nobody updates, and a set of rituals (Monday ops review, quarterly retro) to paper over the gaps.

Generation 4: The Professional Services OS (2025+)

The emerging Professional Services OS category treats all four stages: scoping, pricing, delivery, learning. As parts of a single connected system. Scopes are structured objects. Pricing generates from the scope against a live catalog. Delivery writes back to the catalog. The next engagement starts from the closest completed one.

This is not a rebranded PSA. It is a recognition that services firms are in a 25-year local maximum of disconnected tools, and that the path out is not better integrations between categories, but a single category that does not need the integrations in the first place.