Example project
Meridian Legal Group
Connect consultation requests with the campaign that started them.
Large project. Typically three to six months, billed by milestone. Custom software with a real database behind it, designed with the people who will use it every day. The figures are illustrative.
The problem
worth solving.
The intake team can count inquiries but cannot reliably follow each source through consultation and engagement.
Try a related working exampleThe system behind the solution
Trace advertising to accepted engagements
Reconcile campaign IDs with intake milestones and approved billing totals while keeping confidential matter details in the firm’s own system.
A proposed system. The working example covers part of it.
Bring the information together
- Campaign costs and source identifiers
- Staff-approved intake milestones
- Engagement and collected-fee summaries
The decision it supports
Count an engagement once, using a documented attribution window and a verified link to the originating inquiry.
When a person steps in
Unmatched records enter a reconciliation queue; attorneys retain conflict, suitability and case decisions.
What happens next
An authorized reviewer approves aggregate reporting and any proposed campaign change.
How to measure the improvement
Compare cost per accepted engagement and collected fees after ad spend; keep case outcomes outside the marketing model.
Build it in stages
- Give each practice-area campaign a focused request page.
- Collect basic contact and matter-category details, not confidential case files.
- Let the intake team review conflicts and suitability.
- Link consultation and engagement status back to the originating campaign.
Example numbers
What improvement
could look like.
These are example figures, not results or guarantees.
- Consultation requests
- +76%
- Cost per consultation request
- −32%
- Inquiry-to-engagement rate
- +61%
- Cost per retained client
- −27%
From example
to your business.
Start with the actual workflow
Confirm how your team works today, which systems contain the records and how you measure the result. Test the idea against your real constraints before agreeing the scope.
Build, connect and test
Start with one complete workflow. Connect approved systems, test permissions and failures, and review the result with the people who will use it. The examples on this site do not connect to business accounts.
Keep the system useful
Agree who owns access, monitoring and day-to-day changes. Document the handover and define the maintenance and improvement work that fits the engagement.