Quick Answer
- Lemon law cases move faster than injury cases because liability is largely statutory, not fact-intensive in the same way fault is. Your pipeline stages need to reflect that speed.
- A working lemon law pipeline has at least six named stages: vehicle and repair history collection, manufacturer notice sent, demand letter out, settlement offer received, counter or negotiation, and signed retainer.
- Repair attempts must live in the CRM record itself, not a shared folder or email thread, so the stage is actionable and the data is portable.
- Manufacturer tagging at the record level lets you build cost per signed case by manufacturer and feed that back to the ad platform.
- Automations that flag stalled documentation keep qualified leads from going cold between intake and the demand letter stage.
Why Lemon Law Pipelines Move Faster Than Injury Pipelines
Most law firms running personal injury cases build a CRM pipeline around a long fact-gathering cycle. You are waiting on medical records, treatment to conclude, and liability investigations that can stretch months or years. A lemon law case does not work that way.
Under the Magnuson-Moss Warranty Act, a federal statute, the dispute is largely about whether the manufacturer met its warranty obligations, not about reconstructing an accident or proving who was at fault. State lemon laws add their own standards, often defining a presumption of a lemon after a specific number of repair attempts or days out of service within a warranty period. California's lemon law, codified at California Civil Code Section 1793.2, is one of the most litigated in the country, and its standards are document-driven: repair orders, mileage at each visit, the nature of the nonconformity.
That document-driven structure is what makes a lemon law case move faster once the documentation is assembled. The pipeline's job is to get the documentation assembled quickly, then move the case through notice, demand, and negotiation stages without letting any record stall.
A lemon law CRM pipeline needs at least six named stages to match how the case actually moves from intake to signed retainer to settlement offer.
Lemon law cases move faster than personal injury cases because liability is largely statutory, so the dispute is over documentation and damages, not fault.
If your CRM pipeline currently has a generic "Active" or "In Progress" bucket that covers everything from intake to resolution, you are losing visibility at the exact points where cases stall and where your intake team should be taking action.
Stage 1: Vehicle and Repair History Collection
This is the first real working stage after a lead signs the retainer. The goal is simple: get the repair orders.
In practice, this stage has a failure mode that kills more lemon law cases at the pipeline level than any other single problem. The repair orders end up in an email attachment, a shared Google Drive folder, or a text thread with the client. Nobody in the CRM record knows what has been received, what is still outstanding, or how many qualifying repair attempts are documented.
A working Stage 1 in the CRM does three things:
- Creates a checklist of required documents tied to the record: repair orders by visit, the original purchase or lease agreement, warranty documentation, and any written communications with the dealer.
- Tracks which documents have been received, with the date received attached to the record.
- Triggers a stalled-documentation automation when the record has been in this stage for more than a set number of days without the repair order checklist marked complete.
The automation is not complex. It is a time-based trigger: if a record sits in Stage 1 past a threshold you define, a task fires to the assigned intake or case coordinator with a note to follow up with the client. The threshold depends on your intake process, but the point is that the CRM enforces the follow-up rather than relying on a staff member to remember.
This is also the stage where you set the manufacturer field. Every record in your lemon law pipeline should be tagged with the manufacturer at intake. Toyota, GM, Ford, Stellantis, Hyundai, Kia. The reason for tagging at Stage 1, not later, is that you need manufacturer data to be complete when you pull reporting. If you tag it later, you will always have records where it never got filled in.
A stalled-documentation automation flags any record that sits in the repair history collection stage past a set number of days without an attached document.
Stage 2: Manufacturer Notice and Demand Letter Stage
Once repair history is confirmed and the case qualifies, the next stage covers the notice and demand process. In California and several other states, a manufacturer notice or demand letter is part of the pre-litigation process. The stage in the CRM should reflect whether the notice has been sent and what the response window is.
This stage has a date field that matters more than almost any other field in the pipeline: the date the demand letter went out. That date starts a clock. Different state statutes and the firm's own demand terms define the response window. If the CRM does not surface that date prominently, it disappears into the record.
A working Stage 2 setup:
- Records the date the demand or notice was sent.
- Calculates or displays a response-due date based on your firm's standard terms or the applicable statute.
- Flags records where the response date has passed with no manufacturer response logged.
This last automation, flagging no-response records, is the one that prompts the attorney or case manager to decide whether to proceed to filing or to follow up with the manufacturer's counsel directly.
The demand letter stage is also when manufacturer tagging proves its value for reporting. If your Toyota demand letters are consistently getting no response while your GM cases move to settlement offers within a standard window, that is a pattern worth knowing. You can only see it if the manufacturer field is clean across all records.
Stage 3: Settlement Offer Tracking and Counter Stage
This is the stage where most lemon law pipelines built for injury cases fall apart. Injury pipelines often have a single "Negotiation" stage because negotiations in those cases are long and iterative, with demand packages, adjustor responses, and months of back-and-forth. Lemon law settlement negotiations often move faster, and they often involve multiple distinct offers and counters within a short window.
A single "Negotiation" stage collapses all of that into one undifferentiated bucket. You cannot tell from a pipeline view whether a record in "Negotiation" received an offer yesterday or three weeks ago, or whether a counter has gone out, or whether the client has accepted terms pending the retainer fee calculation.
Split this into two stages:
Settlement Offer Received: The manufacturer or its counsel has put a number on the table. The record enters this stage when the offer is logged. The offer amount field on the record is filled in. A task fires to the attorney to review and advise the client.
Counter or Negotiation Active: The firm has responded to the offer and is awaiting a revised offer or a final response. The record moves here after the counter goes out.
This split gives you a pipeline view that tells you at any moment how many cases have an open offer on the table and how many are waiting on a manufacturer response to a counter. Those are different things, and they require different actions.
Automations That Flag Stalled Repair-Attempt Documentation
The automation pattern for lemon law is almost always time-based rather than event-based, because the bottleneck is documentation that comes from third parties (the dealer's service department, the client's own records) rather than from actions the firm controls.
Three automations that work in a lemon law pipeline:
1. Repair order checklist incomplete past threshold. As described in Stage 1: a time trigger on the repair history collection stage. When the record has been there past the threshold and the checklist is not marked complete, a task fires to the case coordinator.
2. No manufacturer response after demand. When a record moves to Stage 2 and the response-due date passes with no response logged, a task fires to the attorney or case manager. The CRM does not wait for someone to notice.
3. Stalled settlement offer. When a record has been in "Settlement Offer Received" past a set number of days without moving to "Counter Active" or "Signed," a task fires. Sometimes a settlement offer sits because the attorney is waiting on a client decision. The automation surfaces it rather than letting it sit.
None of these automations require a sophisticated CRM. They require that your pipeline has named stages, that your records have date fields tied to stage entry, and that your CRM supports time-based task triggers. Most major CRM platforms used by law firms support all three. The variable is whether the pipeline is set up to use them.
Tracking repair attempts inside the CRM, not a shared folder, is what lets Meta and Google learn what a qualified lemon law lead looks like.
Tagging by Manufacturer for Reporting and Ad Feedback
The manufacturer tag on each CRM record is not just an organizational convenience. It is the field that makes your lemon law ad spend make sense.
Here is the mechanism. You are running Meta ads for lemon law cases. You are also likely running Google search for branded and non-branded lemon law terms. The leads coming in are a mix of Toyota owners, GM owners, Kia owners, and every other manufacturer. Some of those cases sign at a higher rate than others. Some manufacturers have faster settlement timelines, which affects the economics of the case for the firm.
If you do not tag by manufacturer in the CRM, you have no way to pull cost per signed case by manufacturer. You know your blended cost per signed lemon law case. You do not know whether the Toyota campaigns are producing cases that sign at a different rate than the Kia campaigns.
Once you have clean manufacturer data in the CRM, two things become possible:
Budget allocation by manufacturer. If a particular manufacturer's cases sign at a higher rate from your ads, you can shift budget toward creatives and audiences that attract owners of that manufacturer's vehicles. This is a decision that requires the CRM data. The ad platform alone cannot tell you which manufacturer's cases are signing.
Signal quality back to the platform. When you send signed-retainer events from the CRM back to Meta via the Conversions API and to Google via offline conversion uploads, you are telling the platform what a real outcome looks like. If you segment those events by manufacturer, you can in some cases build manufacturer-specific signals. More practically, clean signed-retainer events, regardless of manufacturer segmentation, shift Meta's optimization from finding form-fillers to finding people who match the profile of leads that signed.
This is the mechanism behind CAPI (Conversions API) and why lemon law firms that send signed-case events back to Meta get different lead quality over time than firms that optimize only for form fills. The platform learns from the signal you give it.
Tagging each record by manufacturer lets the firm pull cost per signed case by manufacturer and decide whether a Toyota campaign and a GM campaign deserve the same budget.
Sending a signed-retainer event from the CRM back to Meta via the Conversions API tells the platform to find more people like the leads who actually signed, not just people who filled out a form.
How the Pipeline Connects to the Full Acquisition System
The CRM pipeline is the middle of the system. It receives leads from the intake-qualifying landing page, which screens leads before a staff member ever touches them. It feeds signed-case signals back to the ad platform. It is the source of truth for the firm's reporting dashboard that shows cost per signed case by ad, by case type, and, with manufacturer tagging, by manufacturer.
A lemon law firm running this system end to end is making budget decisions from signed-case data, not from form-fill counts. The pipeline stages are what make that possible, because you cannot report on what you cannot track, and you cannot track a case that lives in a generic "Active" bucket from intake to resolution.
For lemon law firms thinking about law firm SEO alongside paid media, the pipeline data also informs content decisions. If your CRM shows that a high proportion of signed cases involve a specific vehicle model or a specific type of defect, that is a signal for what qualifying content to build. The pipeline is the data source. The system uses it.
Frequently Asked Questions
How many CRM stages does a lemon law case need?
A lemon law CRM pipeline needs at least six named stages to cover the full case path: vehicle and repair history collection, manufacturer notice sent, demand letter out, settlement offer received, counter or negotiation active, and signed retainer. Some firms add a pre-intake qualification stage before repair history collection, and a closed-no-retainer or declined stage for cases that do not qualify. The specific number matters less than whether each stage maps to a distinct action and has automations that flag stalled records.
What triggers a lemon law case to move to demand stage?
A case moves to the demand stage when repair history collection is complete and the case meets the qualifying threshold under the applicable state lemon law or the Magnuson-Moss Warranty Act. In practice, that means the repair orders are documented in the CRM record, the number of qualifying repair attempts or days out of service meets the statutory standard, and the attorney has reviewed and approved the case for demand. The CRM should require the repair order checklist to be marked complete before the record can move to the demand stage, either through a hard gate or a workflow prompt. This prevents records from advancing before the documentation is in place.
How do you track repair attempts in a CRM?
Track repair attempts as individual line items on the CRM record, not as a single count. Each repair attempt should have a date, the mileage at the visit, the nature of the complaint, and the repair order number. If the CRM supports document attachments at the record level, attach the repair order itself. This structure lets you see at a glance whether a case has three repair attempts documented, or one repair attempt logged and two that the client mentioned in intake but has not yet retrieved from the dealer. A checklist tied to the repair history collection stage, with one item per documented repair attempt, is the simplest implementation that most CRM platforms support.
Can you use the same CRM pipeline for lemon law and personal injury cases?
You can use the same CRM, but you should not use the same pipeline. Injury and lemon law cases move on different timelines, involve different documentation, and stall at different points. A shared pipeline forces you to use stage names that are too generic to be actionable for either case type. Most CRM platforms used by law firms support multiple pipelines within a single account. Build a dedicated lemon law pipeline with stages that reflect the statutory and document-driven nature of these cases.
How does manufacturer tagging affect ad performance?
Manufacturer tagging at the CRM record level lets the firm pull cost per signed case by manufacturer. That data informs budget decisions across campaigns. When signed-retainer events are sent back to Meta via the Conversions API, the platform uses those events to find more people who match the profile of leads that converted. Clean signed-case signals, regardless of manufacturer segmentation, improve the quality of leads the platform delivers over time because the optimization event is aligned with the real business outcome rather than with form fills.
What CRM platforms work for a lemon law pipeline?
The specific platform matters less than whether it supports named pipeline stages, date fields tied to stage entry, time-based task automations, custom fields for manufacturer and repair attempt data, and an API or native integration for sending signed-case events back to Meta and Google. Platforms commonly used by consumer law firms include Salesforce, HubSpot, Clio Grow, and Litify. Each has different strengths for legal workflows. The pipeline structure described here can be built in any of them; the setup complexity varies by platform.
Does the intake qualifying page affect which stage a lead enters?
Yes. A lemon law intake-qualifying landing page that screens for vehicle age, manufacturer, and number of repair attempts before the lead submits a form means that a higher proportion of leads entering Stage 1 already have a documented repair history. Leads who submit without meeting the qualifying criteria can be routed to a separate pipeline stage or marked as not qualified before staff time is spent on them. The qualifying page does not replace the repair history collection stage, but it raises the baseline quality of records entering Stage 1.
RGDM builds the full case acquisition system for lemon law firms: the Meta ads, the qualifying page, the intake process, the CRM pipeline, and the signed-case signals that feed back to the platform. If you want to see what your lemon law pipeline should look like and where your current setup is leaving cases on the table, book a free Case Acquisition Review.