Imagine a finance director at a 200-person logistics business who has been told its employment contracts may be out of date. The company has no regular employment adviser, so the director compares several firms.

One site offers a generic explanation of employment law, gives no clue which lawyer handles businesses like theirs and ends at an unowned contact form. Two days later, a junior colleague calls and asks for the same context again.

Another site describes contract reviews for mid-sized employers, names the responsible lawyer, shows relevant experience and explains what an initial conversation covers. The enquiry reaches that person with the context attached. The first response acknowledges the problem instead of restarting the journey.

The difference does not require futuristic technology. It requires the firm to design the handoffs between discovery, instruction, delivery and relationship development.

Before instruction: help the buyer recognise fit

Legal service pages often describe a discipline from the firm's perspective. Buyers need to recognise their situation, judge relevant experience and decide what to do next.

Specificity can include:

  • The client types and situations the team regularly handles
  • Relevant sectors, jurisdictions and scale
  • Named lawyers with clear roles
  • Properly approved experience evidence
  • Guidance written for the buyer's decision
  • A contact route with a realistic response expectation

The source's example contrasts “we advise on employment law” with advice for owner-managed businesses of a particular size dealing with contract disputes, TUPE and senior exits. That sharper language is valuable when it reflects the team's real market. Specificity should reveal fit, rather than manufacture a niche the practice cannot support.

Useful content demonstrates how the firm frames a problem. A guide to settlement agreements written for employees has a different audience and purpose from a technical note for in-house counsel. The author, review date, next action and legal limitations should be clear.

The source reports a top-50 firm increasing qualified enquiries by 67% after restructuring its site. Without analytics, the change set and client permission, that number is too strong to republish. The operational lesson remains: connect relevant pages to owned enquiry routes and measure suitable demand through to instruction.

Onboarding: turn individual habits into a service promise

After the engagement letter, many firms rely on each lawyer's personal communication habits. Some clients receive clear expectations and regular updates; others wait without knowing who is involved or when they will hear next.

Map the first weeks of a matter. A proportionate onboarding sequence might cover:

  • The team, roles and contact routes
  • The intended process and immediate next steps
  • Information or decisions needed from the client
  • Update cadence and escalation route
  • Document exchange and security expectations
  • Billing format and who can answer a query
  • Accessibility or communication preferences

Templates can create consistency, while the responsible lawyer adapts the content to the matter. A high-risk, distressed or unusual instruction may need a direct conversation instead of a sequence designed for routine work.

The source remembers a head of client services saying, “We've just never written it down before.” That is one of the article's strongest observations. The firm did not lack caring lawyers. It lacked a shared process that could survive workload, absence and variation between partners.

Good onboarding also creates evidence. If clients repeatedly ask the same question in week two, the process is missing something. If the first invoice produces confusion, explain the format and assumptions earlier rather than treating each query as an isolated event.

Any statement about professional or regulatory requirements should be checked by the firm's qualified owners against the current SRA rules and the circumstances of its services. Better communication can support demonstrable practice, while a generic digital sequence cannot establish compliance.

During a matter: design visibility around client need

Clients should understand what has happened, what comes next, what the firm needs from them and where uncertainty remains. That may be delivered through a structured update, a call, a portal or a combination.

A portal is valuable when it makes important tasks easier and safer. A document repository with confusing navigation can increase calls. Before buying technology, identify the client tasks:

  • Check matter status
  • Find or provide a document
  • See decisions and actions
  • Understand fees and billing history
  • Contact the right person securely

Then test whether users can complete them. Feature lists do not establish client value.

Regular updates can use a consistent structure without sounding automated. Matter context, professional judgement and difficult news remain the lawyer's responsibility. AI or templating may assist a draft only within approved confidentiality, security and review controls.

Billing deserves the same design attention. Time-recording structure may not match how a client understands value. Clear scope, useful narrative, early explanation and an owned query route can prevent confusion. The objective is not merely fewer calls; it is a client able to understand what it is paying for and raise a concern promptly.

Between matters: make the relationship less dependent on memory

Long-term client development often sits in a partner's head. It works until workload changes, the partner is absent or the relationship moves.

A shared client plan can record relevant services, communication preferences, significant dates and agreed follow-up. CRM prompts may help a relationship owner remember an appropriate conversation. They should never turn regulatory change or client data into indiscriminate marketing.

The source describes a 60-lawyer East Midlands firm whose simple workflow flagged clients with no recent matter and connected that view with relevant sector changes. The senior partner's observation is memorable: “We used to lose clients and not notice for a year. Now we notice before they've decided to leave.” Verify the firm, process, quotation and permission before publishing it as a case. Preserve the principle: client retention can be managed as a shared system while judgement stays with the relationship owner.

Adjacent-service discovery should begin with client need. A timely alert about a change affecting a client's business can be valuable. A generic cross-sell sequence weakens trust. Use permissions and relationship knowledge to determine who receives what, why and from whom.

Technology follows the service design

The technical estate may include a CMS, CRM, matter-management system, secure portal, analytics and communication tools. Buying all of them does not create a coherent experience.

The CMS should allow authorised teams to keep service, people and insight content current without unsafe workarounds. CRM and matter systems need sufficient, governed data to preserve context through handoffs. A portal must support defined client tasks. Communication tools should make timely review easier and preserve appropriate records.

Integration is usually both technical and organisational. Owners need common definitions, clean enough data, permissions, exception handling and accountability when a connection fails. The source is right to warn that data and operating effort can exceed the apparent difficulty of connecting systems.

Start with a small number of consequential journeys. Improve the prospect-to-first-response handoff, one onboarding pattern or one matter-update process. Measure it before adding a large platform programme.

A phased investment without invented promises

The source proposes three to six months for an initial phase and 12 to 18 months for portal, CRM and automation, alongside claims about partner capacity and competitive performance. Those figures depend too heavily on the starting estate to function as general guidance.

A credible roadmap sequences work by client value, risk and dependency:

  1. Establish baseline journeys, evidence and ownership.
  2. Repair harmful friction and stale information.
  3. Define service patterns for onboarding, updates and billing.
  4. Improve the content and data models that support them.
  5. Introduce or change technology where the current estate cannot deliver.
  6. Measure client, operational and commercial effects.

Early work should produce a visible client or staff improvement without creating a throwaway solution. Larger investments then have evidence behind them.

Modern means deliberately managed

The main gap is not access to technology. It is the decision to treat client experience as an operating system that can be described, owned, measured and improved.

Clients may never request a portal or a particular update format. They will notice whether they can find the right expertise, understand what happens next and receive useful communication without chasing. The firm should learn those needs directly rather than importing expectations from consumer apps or competitors.

If you want to map your firm's current client experience against the standard described here - and identify specifically where the gaps are and what addressing them would require - book a client experience mapping session. We've also put together a modern law firm client experience checklist - a three-stage self-assessment covering prospect, engagement, and ongoing relationship - that you can walk through internally before any external conversation. It's designed for managing partners and innovation directors, and it takes about thirty minutes to complete honestly.