CRM for professional services firms: proposals, retainers and utilisation

Professional services do not sell units; they sell capacity and trust. A CRM built for product sales will misrepresent both.

Two pipelines, not one

Run a New business pipeline and a Renewal/expansion pipeline. New business stages follow qualification, scoping, proposal, negotiation. Renewals follow usage review, scope change, approval. The metrics that matter differ: win rate for the first, retained revenue for the second.

Model the engagement, not just the deal

Create a custom object for the engagement or matter: start date, end date, fee model (fixed, retainer, time and materials), rate card, responsible partner and delivery team. Associate it to the company and to invoices so revenue and delivery live in the same view.

Make referrals a first-class source

Most professional services revenue comes from relationships. Track the referring contact on every deal, report on referral sources by revenue, and automate a thank-you and update cadence. A referral network you cannot report on is a network you will lose.

Proposals as structured data

Store scope, deliverables, fee and assumptions as properties and line items, not only inside a PDF. This lets you analyse win rate by fee model, by service line and by partner — the three most useful cuts in this business.

Connect capacity to pipeline

Add expected start date and required roles to each deal. A weighted pipeline view against team availability prevents the classic failure: winning three projects that all start the same week.

Reporting the partners will use

Pipeline by service line, average fee, win rate by referral source, realisation rate, and renewal rate by client. Add cycle time from first meeting to signed engagement letter — it usually hides weeks of avoidable delay.

Confidentiality and access

Client confidentiality requires real permission design: team-based access, restricted properties for sensitive matters, and documented offboarding. Under ISO 27001 practice, access control is reviewed, not assumed.