Professional services software requirements checklist

A professional services software evaluation should test requirements in five categories: functional capabilities (resource planning, project delivery, time tracking, financials, billing, reporting), technical and security requirements, integrations, cost and licensing, and adoption support. This checklist covers 40+ criteria with a must-have/nice-to-have scoring method your buying committee can apply consistently across every vendor on your shortlist.

Most PSA evaluations fail before the first demo. Committees drift toward whichever tool demos best, or toward the loudest stakeholder’s pet feature, because nobody wrote the requirements down. The result is predictable: in our discovery call corpus of 40+ professional services firms interviewed between March 2025 and March 2026, roughly 60% had already bought and abandoned at least one project management tool, usually one purchased without structured requirements. Gartner Digital Markets found the same pattern at scale: 60% of software buyers regret a purchase made in the last 12 to 18 months, with higher-than-expected total cost (33%) and difficult implementation (32%) as the top product-related reasons.

Use this page in three steps: skim the categories below, download the scoring spreadsheet, and assign each category to an owner on your committee.

How to use this checklist (the scoring method)

Mark each criterion as must-have, important, or nice-to-have before you watch a single demo, then score vendors 1 to 5 per criterion and let the weighted totals rank them. A vendor that fails any must-have exits the evaluation regardless of its total score.

Assign each category to its natural owner: functional requirements to the operations or delivery lead, technical and security to IT, cost and licensing to finance, adoption to the team leads who will live in the tool daily. Each owner scores only their category, which keeps one strong personality from dominating the decision.

One rule from the field: lock priorities before demos start. Vendors are good at making nice-to-haves feel like must-haves, and a committee without a frozen priority list will re-rank criteria mid-evaluation to match whatever it just saw.

Functional requirements

Functional requirements are the largest block, so they are grouped into five areas below. On this page each area lists the criteria at summary depth; the downloadable scoresheet adds the specific question to ask in a live demo for each one.

Resource planning

Resource planning is the most common gap in the tools firms are leaving. Test for:

• A single demand vs. capacity view across all projects, not per project
• Utilization tracking, billable and non-billable, at person and team level
• A hard block or visible warning on overallocation. One engineering director we interviewed put the failure plainly: his previous tool “would let you double book people… I could load somebody up with 400% of work”
• What-if forecasting: model a pipeline deal’s staffing before it closes
• Search for available people by skill or role, not just by name

SPI Research’s 2026 Professional Services Maturity Benchmark, drawn from 509 PS organizations, sets the utilization benchmark above 70%. You cannot manage to that number in a tool that hides capacity.

Project delivery

• Work breakdown structure with real hierarchy, not a flat checklist
• Project templates for repeatable engagement types
• Task dependencies, including dependencies across projects
• Milestones tied to billing or approval events
• Intake or request forms so new work enters through one door

Time and expense

• Both start/stop timers and weekly timesheet entry
• Billable vs. non-billable classification at entry, not at export
• Time approval workflows before hours reach an invoice
• Mobile time entry for field and traveling staff
• Expense capture, including mileage and subcontractor costs

Financials and billing

• Budget vs. actuals visible in real time, not after month-end
• Cost rates and bill rates held separately, so margin is visible per project
• Support for time and materials, fixed fee, and retainer billing in the same system
• Invoice generation from approved time, without re-keying

The benchmark to protect here is margin: SPI’s 2026 data puts healthy project margin above 35% and revenue leakage below 5%. Firms that assemble invoices manually from exported timesheets rarely know either number.

Reporting and portfolio

• Role-based dashboards: executives, PMs, and finance see different views
• A portfolio view across all active projects, with status and health
• Client-facing reports that do not require an analyst to build
• BI connectivity (Power BI or equivalent) for custom reporting

Technical and security requirements

Technical criteria are where IT earns its seat on the committee, and where a vendor’s answers are verifiable rather than aspirational. Require:

• SOC 2 (or equivalent) attestation, current, not “in progress”
• Data residency options. In our corpus, roughly 35% of firms treated hosting location (Canada or US) as a hard requirement, driven by healthcare, government, and financial services compliance
• Single sign-on via Entra ID or SAML
• Granular permissions: contractors and clients see only their projects
• A documented API for custom needs
• A published uptime SLA
• Full data export rights on exit, in a usable format

Integration requirements

Accounting comes first. A two-way QuickBooks or Xero sync was the single most requested integration across our corpus, and the failure mode is specific: one operations lead described running the business with “two different aging ARs” because time lived in one system and invoices in another. Then:

• CRM integration (HubSpot or Salesforce) that creates a project automatically from a closed-won deal, so the sales-to-delivery handoff stops depending on someone remembering
• Calendar and email sync
• Jira coexistence for firms with development teams, since Jira stays for dev work
• Payroll export from approved timesheets

Force one distinction in your criterion wording: “native two-way sync” and “CSV export” are not the same answer, and vendors will blur them if the checklist lets them.

Cost and licensing requirements

Cost criteria protect you from the number one regret driver, unexpected total cost. Require:

• Transparent per-user pricing, published or quoted in writing before the demo
• License tiers that match real usage. A typical PS firm runs 20 to 60 full users plus 50 to 200 collaborators or guests; paying full-user rates for light users is the most common overspend we see
• Implementation and onboarding cost quoted upfront, not discovered at contract
• No forced modules you will not use
• Contract flexibility: annual terms, seat adjustments at renewal

For budgeting context, mid-market PSA spend typically lands between $5K and $25K per year depending on user counts and modules.

Adoption and vendor requirements

Feature gaps get firms shopping; support failures make them switch. Poor vendor support was one of the most common switching triggers in our corpus, ahead of most functional complaints. Evaluate:

• Structured onboarding or professional services, weighted higher if your team has no spare operations capacity to self-implement
• Support responsiveness with a named SLA and named channel, not “great support”
• Training resources your team leads can reuse for new hires
• A client or guest portal, so external stakeholders see status without full licenses
• A mobile app for field teams
• Roadmap transparency and reference customers in your vertical

Requirements summary table

Who this checklist is for

This checklist fits professional services firms of roughly 20 to 400 employees running a formal evaluation or RFP with a buying committee of two to five people across operations, finance, and IT. That includes consulting firms, engineering services, agencies, and internal PMOs formalizing tool selection. If you are a solo evaluator at a firm under 10 people, weighted committee scoring is more process than you need.

One honesty note: no vendor, including Birdview, scores 5 on every row. A checklist that produces a perfect score for one tool is a rigged checklist, and your committee will notice.

Get the scoring checklist

The download turns this page into a working evaluation kit: the full criteria set as a weighted scoring spreadsheet (score up to three vendors side by side), a demo script with the exact question to ask for each must-have, a stakeholder sign-off sheet, and a TCO worksheet. It works with any vendor, which is the point; circulate it to your committee as-is.

[Download the PSA requirements scoresheet]

If your must-haves are already clear, the faster path is to test them in a live demo and score as you go.

FAQ

What requirements matter most in professional services software?

Across the 40+ firm evaluations in our corpus, three requirements decided most deals: a real capacity and utilization view (the top pain in about 80% of calls), an unbroken flow from tracked time to approved invoice, and a two-way accounting sync. Firms that anchored their must-haves there avoided re-buying within two years.

How do you run a PSA software evaluation?

Freeze your prioritized checklist first, then shortlist two to three vendors. Assign each requirement category to a committee owner, run scripted demos against your must-haves, and score independently before comparing. Expect two to three calls per vendor (discovery, demo, trial or negotiation), so a disciplined evaluation typically runs four to eight weeks end to end.

What is the difference between a requirements checklist and an RFP?

The checklist is the internal working document: prioritized criteria your committee scores vendors against. An RFP is the formal external version of the same list, sent to vendors for written responses. Most firms under 400 employees can skip the formal RFP and evaluate directly from the checklist; the RFP earns its overhead mainly in government, healthcare, and enterprise procurement.