D'Alessio Law Group: Speed-to-Lead Architecture
A mid-sized law firm was losing cases to a 14 hour intake queue. 200+ leads a week arrived by email and were keyed in by hand, 6 to 48 hours later. The rebuilt pipeline captures, qualifies, routes and syncs every lead in seconds, and it checks for conflicts before a matter is ever created.
Quote this
D'Alessio Law Group: 10s lead to CRM sync, under 1% routing error rate, on 200+ leads a week, with 22 hours per week of paralegal time freed for high-value client work.
01 The problem
Legacy manual intake was bleeding high-value leads.
D'Alessio Law Group was running high-cost digital marketing campaigns generating 200+ leads per week. But the intake process relied on email forwarding and manual data entry by paralegals. A prospective client would submit a form at 9 AM. An intake specialist would read the email at 11:30 AM. They would open Clio Grow, create a Contact, create a Matter, assign it to an attorney, and send a follow-up SMS. By the time the lead entered the system, 6 to 48 hours had passed.
Conversion rates for leads contacted after 5 minutes were 10x higher than leads contacted after 5 hours. The firm was hemorrhaging cases to faster competitors.
02 The three bottlenecks
- Parallel Processing Limit: One paralegal could only process about 15 leads per hour manually. During campaign surges, 200+ leads would queue up creating a backlog lasting days.
- Error Cascade: Manual form transposition caused wrong attorney assignments (criminal cases to family law attorneys) requiring rework and client confusion.
- No Conflict Checking: The firm had no automated system to detect if a potential client was already represented by the firm or was an adverse party in an existing matter, creating ethical risk exposure.
03 The architecture
Modular decision-tree pipeline with semantic routing.
The system runs four stages and one gate: inbound capture via webhook, cognitive qualification via Claude API, attorney routing logic based on complexity and damages, a conflict check against every existing matter, and dual-CRM sync to both Lawmatics and MyCase. The intake half, form fill to case record with no manual entry, is the same build as my Typeform to MyCase automation guide.
Figure 1. The intake pipeline. Every arrow is an event with an owner, a failure path and a log.
Before a matter is created, the system queries the MyCase API to check whether that email or phone already exists in any opposing party role across active matters. A match routes to the managing partner for ethical review instead of auto-assignment. 47 potential ethical violations prevented in the first six months.
04 Before / after
Before
Response Time: 6-48 hours
Manual Work: 15 min/lead
Conversion Rate: 10% qualified
Errors: 3-4 misroutes/week
Capacity: ~15 leads/paralegal/day
Conflict Checks: Manual, often missed
After
Response Time: 10 seconds
Manual Work: 0 min/lead (except review)
Errors: <1% routing error rate
Capacity: Unlimited automated
Conflict Checks: 100% automated
05 Results, 90 days and 6,000+ leads
- Speed-to-Lead: Reduced from average 14.2 hours to 10 seconds (5,112x faster)
- Qualified Conversion Rate: Increased from 10% to 55% (4.5x improvement)
- Routing Accuracy: 99.2% correct attorney assignment (vs 87% manual)
- Paralegal Time Savings: 22 hours per week freed for high-value client work
- Conflict Detection: 47 potential ethical violations prevented in first 6 months
- Cost per Lead Processing: Reduced from $18.50 to $0.42
06 What broke
Every build had a failure that only showed up under load. All three were found in production, not in review.
- Webhook Flood on Campaign Launch: First major campaign triggered 847 leads in 4 hours. Make.com rate limits hit 429 errors. Fix: Google Cloud Functions as buffer layer with exponential backoff and queue-based rate limiting.
- Claude Token Overflow: Rich text intake forms with pasted legal documents exceeded context window, causing silent truncation. Fix: Pre-processing step to truncate and summarize long-form context before API call.
- MyCase API Field Mismatch: Custom Lawmatics fields did not map 1:1 to MyCase, causing data loss. Fix: Field translation dictionary with fallback logic to store unmapped data in Lawmatics custom fields.
07 The stack
08 Related case studies
| Operational dimension | Legacy baseline | Production system |
|---|---|---|
| Lead response time | 6 to 48 hours via manual email forwarding | 10 seconds from form submit to CRM assignment and SMS |
| Qualified conversion rate | 10% baseline on delayed follow-up | 55% qualified conversion rate (+45 percentage points) |
| Conflict checking | Manual spreadsheet and memory checks | 100% automated opposing-party scan before matter creation |
| Processing cost per lead | $18.50 in manual paralegal time | $0.42 in compute and API calls (22 hrs/wk freed) |
FAQ Frequently asked questions
How does the system prevent ethical conflicts before creating a matter?
Before creating a matter record, the workflow queries the MyCase API to check whether the prospect's email or phone number appears as an opposing or adverse party on any existing matter. Matches pause automatic assignment and route to the managing partner.
What happens if Make.com hits rate limits during an ad campaign surge?
A serverless webhook buffer with exponential backoff queues burst traffic so zero form submissions are dropped when campaign volume spikes.
How long did the D'Alessio Law Group intake rebuild take?
The initial speed-to-lead and dual-CRM synchronization pipeline shipped in four weeks, with 90-day production metrics verified across more than 6,000 inbound leads.
Have a similar intake problem?
Paste your broken workflow, describe the bottleneck, or share the error. I will tell you exactly what is wrong and how to fix it.
Run Free DiagnosticStay in the loop.
Technical breakdowns, new system builds, and lessons from deploying autonomous AI. One email a week, direct to your inbox.
One email a week. Leave with one click.
The intake queue was 14.2 hours and it is now 10 seconds. The Implementation Review is $1,500 and a one-workflow build is $4,000, paid 50% at kickoff and 50% on handover. The Multi-Workflow Program starts at $9,000 when more than one workflow shares a source.