A referral partner introduces a prospect. The prospect reads an attorney guide, searches the lawyer's name, and calls a tracked number. Business development remembers the relationship, marketing sees the visit, and intake sees the call. If each team replaces the others' context with its own label, the firm loses the journey and still cannot decide what to do next.
Growth operations connects the teams through responsibility transfers, shared definitions, and preserved evidence. It does not require one team to own the whole relationship or one field to explain every influence.
Give each team a different job
Marketing helps a defined audience discover, understand, and evaluate the firm. It owns the public promise, channel context, destination, acquisition cost, and the evidence created before contact.
Intake responds to a request through the firm's approved process. It owns contact events, operational status, preliminary business criteria, next action, coverage, and escalation. Authorized attorneys own legal evaluation and representation decisions.
Business development builds and maintains professional, referral, and existing-client relationships. It owns relationship context, agreed follow-up, and internal stewardship.
Growth operations sets the shared handoff requirements, identity rules, system responsibilities, exception review, and decision record. It helps the functions learn from the same outcome while preserving their distinct roles.
Jeff Homer said of his music-school role in episode 8 of Juris Digital's Non-Billable Hour, “my job is to support the teachers.” The nonlegal-business analogy is useful here: coordination should reduce avoidable work for attorneys and staff serving clients. It should not add fields and meetings that have no next action.
Define a completed handoff
A handoff contains five elements:
- Trigger: what happened and what expectation was created.
- Minimum context: what the recipient needs to act.
- Recipient: named role and backup.
- Required action: the next observable step and period.
- Acceptance: evidence the recipient owns the record or returned the decision.
A sent email is a trigger. A created task is a routing event. Neither proves the receiving person accepted responsibility.
Use a handoff card:
Scroll sideways to review every column.Each row is shown as a labeled card.
| Field | Example |
|---|---|
| Trigger | Accountant makes an approved introduction |
| Context | Person, organization, stated question, permission and relationship owner |
| Recipient | Intake specialist; intake lead as backup |
| Required action | Review request, contact through approved route, record next status |
| Acceptance | Named owner, timestamp, next action |
| Return | Outcome and relationship-safe update to the internal owner |
Collect only the context required for the action. A relationship note does not authorize broad distribution of private or prospective-client information.
Preserve three kinds of source evidence
Keep separate:
- observed path: campaign, landing page, tracked call, search, or event registration;
- reported influence: the person's neutral answer about what helped them find or evaluate the firm; and
- relationship context: referral, introduction, existing-client connection, or event relationship recorded by the appropriate owner.
One person can have all three. They remain one person. A reporting rule may choose a primary source for a particular view, but it should not destroy the other observations or present the rule as the full causal history.
The law firm marketing analytics guide develops this source-to-outcome discipline.
Connect promises to response
Marketing and business development create expectations before intake responds. Record the requested action and stated next step:
Scroll sideways to review every column.Each row is shown as a labeled card.
| Trigger | Prospect expectation | Intake or relationship response |
|---|---|---|
| Consultation request | Firm will evaluate the request through its stated process | Prompt operational response and appropriate review |
| Guide download | Resource delivery | Do not turn access into an unexpected legal sales call |
| Professional introduction | Follow the introduction's permission and context | Confirm ownership and preserve the relationship owner |
| Event question | Answer or follow-up within the promised scope | Route matter-specific facts through the approved process |
A 2020 Juris Digital podcast conversation with Gyi Tsakalakis discussed offering a scheduling link with a reply alternative when no listed time worked. Use that attributed historical example as a design principle, not current product documentation: an automated path needs an appropriate exception route.
Return outcomes that each team can use
“Bad lead” is not useful feedback. Agree on operational reason codes such as wrong service, unsupported location, duplicate contact, no established contact, attorney decline, conflict route, pending review, signed agreement, and opened matter. Preserve unknown rather than converting it into unqualified.
Then return only the context needed for action:
- Marketing may need the promise, campaign, practice category, and aggregate or appropriately limited disposition evidence.
- Intake may need updated service boundaries, coverage decisions, and script or workflow changes.
- Business development may need relationship-safe confirmation that an introduction was received and handled.
- Practice leaders need review queues, capacity, and unresolved decisions.
Growth operations should keep detailed legal narratives out of broad marketing reports when categories and outcomes are sufficient.
Work one relationship through every handoff
The following case is fictional. A regional business firm wants more succession-planning relationships with accountants. A partner sends an approved briefing to 30 accountants. One accountant introduces an owner and copies the partner. The owner later reads the firm's guide, searches the partner's name, and calls through the website number.
The relationship owner records the accountant, introduction date, stated question, and permission to contact. The website preserves the guide visit and tracked call. Intake recognizes the person as the same inquiry, keeps both contact events, and accepts ownership. The first intake specialist is absent, so the backup accepts the task under the coverage rule.
Intake confirms that the request meets preliminary business criteria and routes a defined scope question to the attorney. The partner reviews it, requests more information, and returns the next step to the record. The prospect signs an agreement; the matter opens five days later. Finance has not yet recorded collected fees.
The outcome record contains one eligible distinct inquiry, one qualified inquiry, one attorney-reviewed opportunity, one signed agreement, one opened matter, and zero collected fees at the review date. It also contains three influence flags: accountant introduction, observed guide path, and reported attorney-name search. Three flags remain one person and one opened matter.
The first operational defect appears after opening: the automated matter connection overwrites the relationship owner with the tracked-call source. The reporting owner restores separate fields, the systems owner changes the transfer rule, and staff retest a referred visitor who later calls.
At the monthly meeting, the firm does not award the matter to one channel. It chooses three actions:
- Business development: thank the accountant within the agreed relationship boundary and keep the introduction history.
- Marketing: continue the succession guide because it supported evaluation, while making no causation claim.
- Intake/operations: retain the backup-acceptance rule and repair the overwrite before expanding the briefing.
The firm has capacity for two more succession matters this quarter, so it continues the 30-person relationship cycle rather than scaling to a broad list. The decision follows preserved context, staff ownership, and practice capacity.
Run a decision meeting, not a reporting contest
Review exceptions that need more than one function:
- public promise and service-boundary mismatch;
- repeated reason code with supporting examples;
- aging attorney-review queue;
- duplicate or overwritten relationship evidence;
- capacity change requiring investment adjustment; and
- failed source-to-matter transfer.
For each, record evidence, decision, owner, authority, due date, and retest. The meeting is complete when the next owner accepts the work.
Configure systems after the agreement
Once responsibilities are clear, configure fields, tasks, transfers, access, and exceptions to support them. Test owner absence, duplicate contact, changed status, referred-plus-tracked journeys, attorney-review return, signed-pending-opening, and matter connection. The law firm technology-stack guide helps inspect those transfers.
Juris Digital's current JurisOS page is a public commercial route for discussing coordinated growth work. Bring one journey, the handoff cards, source fields, exception examples, staff authority, and capacity. Ask for a written scope of responsibilities, access, work, fees, deliverables, and handoff. The page does not establish an integration, CRM, workflow feature, staffing model, response time, price, or result.
