Ksenia Kartamysheva A PSA readiness assessment is a structured review that tells you whether your firm can absorb professional services automation software without breaking. It scores your people, processes, data, technology, budget, and governance against what a PSA platform actually demands. The output is a go/no-go decision and a short list of fixes before you sign a contract.
Most failed PSA rollouts do not fail because the software is wrong. They fail because the firm was not ready. A readiness assessment is the cheapest insurance against that failure. This article walks through what to assess, how to run the assessment, and how to score the result.
What a PSA readiness assessment covers
A readiness assessment covers five domains. Skip one and you get a blind spot that shows up mid-implementation, usually as a change order.
1. People and process readiness
Does someone own resource management today? Is there a named services operations lead? Can your project managers describe the intake, staffing, and closeout process the same way? If three PMs give three different answers, you have a process problem, not a software problem. PMI’s research has consistently linked standardized delivery practices to higher project success rates [2].
2. Data readiness
PSA runs on clean records: employees, skills, rates, clients, projects, tasks, time entries. If your rate card lives in a spreadsheet that only one finance person edits, that is a blocker. Audit what exists, where it lives, and how consistent it is.
3. Technology readiness
What does the PSA need to talk to? Typically your CRM, accounting system, HRIS, and identity provider. List every integration point and confirm each source system has an API or a supported connector.
4. Financial readiness
Budget for licenses is the easy part. Also budget for implementation, internal time, data cleanup, and a year-two optimization pass. For a realistic view of how to build the financial case, see the business case for PSA software.
5. Governance readiness
Who signs off on configuration decisions? Who arbitrates when sales wants one workflow and delivery wants another? Without a steering group, every design choice becomes a debate.
How to run a PSA readiness assessment
Plan for three to five weeks of work. One person can run it, but they need executive air cover.
People to interview
Talk to eight to twelve people: the services lead, finance controller, two or three PMs, a resource manager, sales ops, IT, and HR. Ask the same questions to each. What breaks today? What takes too long? What number do you not trust? Record answers verbatim.
Process mapping
Map the complete opportunity-to-cash flow. Sales handoff, project setup, staffing, time capture, approvals, invoicing, revenue recognition, closeout. Use a swim-lane diagram. Mark every manual step, every spreadsheet, every rekeying moment. Those are the spots PSA either fixes or exposes.
Data audit
Pull samples. Take last quarter’s time entries and check them for completeness. Pull the active project list and see how many have a budget, a plan, and an owner. Pull the employee master and check whether skills and cost rates are populated. Count the gaps. Put a number on it.
Tooling inventory
List every system involved in services delivery. For each, note the owner, the data it holds, and how it currently exchanges data with anything else. Attachments and email do not count as integration.
Scoring framework
Score each domain 1 to 5 using consistent criteria. Do not average feelings, score against evidence from the interviews, maps, and audit.
| Domain | 1 (Not ready) | 3 (Partial) | 5 (Ready) |
|---|---|---|---|
| People & process | No named owner, ad-hoc delivery | Owner exists, process varies by team | Standard process, trained PMs, clear RACI |
| Data | Spreadsheets, no master records | Some master data, known gaps | Clean masters, defined stewards |
| Technology | No API access, unknown integrations | Some connectors, manual bridges | Documented integrations, IDP in place |
| Financial | No budget beyond license | License + partial implementation | Full multi-year budget approved |
| Governance | No steering group | Ad-hoc decisions | Steering committee, decision log |
For a deeper view of what to evaluate during the maturity stage before PSA rollout, see PSA implementation success metrics.
Readiness score and what it means
Add the five domain scores for a total out of 25. Then apply a traffic-light band and act on it.
| Total score | Band | Meaning | Next step |
|---|---|---|---|
| 20–25 | Green | Ready to select and implement | Start vendor shortlist, plan phased rollout |
| 13–19 | Yellow | Ready in parts, gaps in others | Fix bottom two domains first, reassess in 60–90 days |
| 5–12 | Red | Not ready | Do not buy PSA yet, invest in process and data first |
A green firm can move to vendor evaluation. Build a shortlist of three, run scripted demos against your process map, and pilot with one service line. For help building that shortlist, see the mid-market PSA buyer’s guide.
A yellow firm should not stall the whole program. Pick the two lowest-scoring domains and assign a fix owner with a deadline. Common yellow patterns: strong process but dirty data, or strong data but no governance. Both are fixable in a quarter.
A red firm needs to slow down. Buying PSA into a red environment usually produces a system that mirrors the chaos in higher resolution. Spend two quarters standardizing delivery and cleaning masters, then reassess. Firms rushing implementation without foundational work see weaker margin improvement post-go-live than those that prepare [1].
Common gaps that block PSA adoption
Four gaps show up in almost every yellow and red assessment.
Unclear ownership
Nobody owns the complete services operations cycle. Finance owns billing, delivery owns projects, HR owns capacity, and nobody owns the seams. PSA touches all three, so the seams become fights. Name a services operations lead before you sign anything.
Dirty data
Duplicate clients. Employees with no cost rate. Projects with no end date. Time entries coded to a catch-all project. A PSA will not clean this for you, it will inherit it and make the mess visible to executives, which is worse. Clean the top three masters (clients, employees, projects) before migration.
No process standardization
Every PM runs their engagements their own way. That works at 20 people. It falls apart at 80. PSA assumes one intake, one staffing model, one time approval flow. If you cannot describe those in one page, you are not ready. For more on how the pieces fit together, see the professional services operations guide.
Resistance to change
Consultants who like their spreadsheets. Partners who see time tracking as surveillance. Finance leads who trust their own reports over any system. Ignore this and adoption stalls. Address it with a named executive sponsor, honest communication about what changes, and training tied to real work.
PSA Readiness Assessment checklist
Use this as a working checklist. Mark each item Yes, Partial, or No. Anything not Yes is a gap to fix or accept.
People and process
- Named services operations lead
- Documented opportunity-to-cash process
- Standard project intake form
- Defined resource request workflow
- Time entry policy communicated
Data
- Client master deduplicated
- Employee master with cost rates and skills
- Rate card in a single source
- Project list with owners and budgets
- Time entries at task level for last two quarters
Technology
- CRM with API access
- Accounting system with supported connector
- HRIS as the main employee record
- Single sign-on / identity provider
- Integration owner named in IT
Financial
- License budget approved
- Implementation budget approved
- Internal time allocated (PM, data, IT)
- Year-two optimization budget reserved
- Executive sponsor confirmed
Governance
- Steering group named
- Decision log template ready
- Configuration owner per module
- Change management plan drafted
- Training budget and owner confirmed
FAQ
What is a PSA readiness assessment?
A PSA readiness assessment is a structured review that scores a professional services firm across people, process, data, technology, finance, and governance to decide whether it is ready to adopt PSA software. The output is a go/no-go decision and a short list of fixes.
How long does a PSA readiness assessment take?
Typically three to five weeks. One person can run it if they have access to the right people and executive support.
Who should be involved in a PSA readiness assessment?
The services lead, finance controller, project managers, resource manager, sales ops, IT, and HR. Eight to twelve people is usually enough.
What is the most common reason a PSA rollout fails?
The firm was not ready. The software is usually capable, but the organization lacks standard processes, clean data, or clear ownership.
What score means we are ready for PSA?
A total of 20–25 out of 25 is green. 13–19 is yellow, fix the bottom two domains first. 5–12 is red, do not buy yet.
Do we need clean data before buying PSA?
Yes. PSA will not clean your data. It will make your current data problems visible to more people. Clean the top three masters, clients, employees, projects, before migration.
What is the single most common blocker?
Unclear ownership of services operations. Firms buy PSA to fix a coordination problem, then discover no one has authority to make the coordination decisions the software forces.
Sources
- SPI Research, “2026 PSA End-User Survey,” Service Performance Insight, 2026. https://spiresearch.com/reports/2026-psa-end-user-survey/
- Project Management Institute, “Organizational Project Management Maturity Model,” PMI.org, 2024. https://www.pmi.org/learning/library/pmi-organizational-maturity-model-7666
