The 10-question Professional Services OS test
A ten-question checklist to determine whether a tool is a true Professional Services OS or just a PSA, CPQ, or project management suite with a new label.
The phrase “Professional Services OS” is new enough that vendors will start borrowing it. A true Professional Services OS connects scoping, pricing, delivery, and learning in one data model and closes the feedback loop between them. This ten-question test separates a PS OS from a PSA, CPQ, or project management suite with a rebrand. If a tool cannot answer yes to at least eight of these ten, it is not a PS OS.
The 10 questions
1. Is the scope a structured object, not a document?
A PS OS models scopes as first-class records with deliverables, assumptions, risks, and dependencies. A Word or Google Doc is not a structured object.
2. Does pricing generate from the scope, or is it typed in separately?
A PS OS derives price from effort estimates against a live catalog. If pricing happens in a separate spreadsheet, the tool is not closing the loop.
3. Is the pricing catalog updated from delivery actuals?
When engagements overrun, the catalog should learn. If the rate card is static, the tool cannot reflect reality.
4. Can a new scope start from the closest historical engagement?
A PS OS pre-populates new scopes from the most similar completed ones. If every scope starts blank, institutional memory is leaking.
5. Do approvals see delivery risk, not just discount %?
Approval routing should consider historical overrun rates, team capacity, and client risk. Not just discount thresholds.
6. Is time tracked against the scope object, not an abstract project code?
Hours should write back to the deliverable they served, so variance is visible at the scope-line level.
7. Does the tool surface institutional memory at the moment of scoping?
When a new scope is opened, the PS OS should surface related past engagements, reusable assumptions, and relevant risks. Automatically.
8. Is learning a first-class stage, not an afterthought?
A PS OS treats post-engagement review as structured data (captured lessons, updated catalogs) not a retrospective doc that nobody reads.
9. Can one data model answer “what did we scope, sell, deliver, and learn”?
If answering that question requires exports from three tools and a spreadsheet, the system is not integrated.
10. Does the next engagement materially benefit from the last one?
This is the single most important question. If each engagement starts from zero, the firm has a PSA, not a PS OS.
Scoring
- 8–10 yes: You are looking at a true Professional Services OS.
- 5–7 yes: Promising, but likely a PSA or CPQ being repositioned.
- 0–4 yes: It is a project management or time-tracking tool.
Related
Need more help?
Our support team is available to assist you.
Contact Support