Map a referral partner agreement from lead handoff to fee record

Freeze the referral package and growth brief

Begin by inventorying the proposed referral agreement, partner schedule, qualification or lead form, service descriptions, pricing or fee schedule, introduction procedure, CRM or reporting instructions, customer handoff checklist, confidentiality or security instructions, and every addendum or policy included with the package. Record the filename, version, sender, received date, and internal owner for each item. Preserve the originals rather than replacing them with one blended pipeline summary.

Add a short growth brief written by the provider. Record the services and customer types in scope, the lead path the team currently uses, the people who qualify opportunities and approve pricing, the delivery owner for a new customer, the records expected after an introduction, and the person authorized to approve a business change. Keep this brief labeled as context so it cannot be mistaken for referral language.

• Name the exact agreement, partner, service, pricing, and reporting versions under review.
• List every lead, qualification, handoff, or security instruction the package incorporates.
• Record the growth, sales, delivery, finance, partner, and approval owners.
• Keep pipeline forecasts and partner conversations separate from source-backed terms.

Trace one lead from source through customer handoff

Draw the lead sequence the provider and partner can actually verify: lead source, intake, qualification, duplicate check, partner introduction, provider response, discovery or proposal, customer acceptance, onboarding handoff, service start, and the record used for follow-through. For each stage, name the person and record involved and attach the proposed language that appears to describe it.

Leave a stage open when the package does not answer it. An expectation about lead ownership, response timing, qualification, customer status, or onboarding should remain visibly separate from the proposed documents. The lead-path map is an operating fact record for counsel, not a conclusion about when a fee is earned or a relationship is formed.

• Use the provider's real intake and onboarding sequence rather than a generic funnel.
• Identify the document and exact source location behind every agreement-derived note.
• Name who can verify each lead, introduction, customer, and service-start record.
• Preserve an unclear lead assignment or missing record as an open item.

Pair attribution, fees, and reports with source events

Create one source-linked table for every lead category, attribution event, amount, formula, date, customer status, invoice, fee record, adjustment, report, and other partner event the package describes. Useful rows may include accepted referral, duplicate or existing account, qualified opportunity, introduction, proposal, customer start, invoice, fee statement, correction, and end-of-relationship work. Keep each entry tied to its source language and label any internal estimate separately.

Place the provider's pipeline forecast beside the source rather than inside it. Growth can identify expected opportunity activity, delivery can verify customer-start records, and finance can confirm fee administration. Counsel can then inspect the proposed language without receiving an internal forecast or practice as though it were an agreed term.

• Keep a stated fee, formula, or account definition separate from the provider's forecast.
• Record the event, source location, evidence owner, and business owner for each row.
• Mark a missing lead definition, statement, adjustment record, or report procedure explicitly.
• Do not turn an incomplete event or formula into a confident fee conclusion.

Test duplicate, delayed, and transition scenarios

Test the package with concrete partner scenarios: an existing customer is referred again, two partners identify the same lead, qualification takes longer than expected, a customer pauses before onboarding, a service scope changes, a fee report needs correction, or the provider and partner are preparing to stop new referrals. For each scenario, place the expected business response beside the source sections and procedures that appear relevant.

Route each unknown to the right lane. Growth can verify lead history and communication, sales can confirm proposal records, delivery can confirm onboarding facts, finance can confirm statements and fees, leadership can own commercial choices, and counsel can address interpretation, drafting, and legal risk. Keep the question open when the source or business record is incomplete.

• What lead, customer, service, payment, report, or transition event is being tested?
• Which source passage or procedure appears to address it?
• Who can verify the record or approve a business change?
• What interpretation or drafting judgment remains for counsel?

Give counsel one lead-to-fee packet

The handoff should include the frozen document inventory, growth brief, source-linked lead path, attribution-and-fee table, duplicate and transition scenarios, missing materials, and the owner of every open decision. Keep superseded schedules, pipeline exports, and informal explanations available but distinguish them from the package counsel is being asked to review.

For each uploaded contract document, CounselOS can preserve source-linked clause extracts, surface playbook deviations, capture questions beside the relevant finding, and export selected material in a review packet. The lead path and CRM records remain human-reviewed operating artifacts; CounselOS provides traceable contract evidence for the provider and attorney making the next decisions.