INT/CTG-06
INT/CTG-06
Cartiga
Cartiga
LegalTech
LegalTech
Litigation Funding Intake
Litigation funding runs on qualification. Before anyone gets money, somebody has to establish whether the case is fundable, and that means a long list of questions that exist for legal reasons rather than product ones. Here is the part that matters, and it took me a while to build the flow around it. The person filling this out is usually having the worst month of their life. They are hurt, or they are in a lawsuit, or they need money by Friday. Sometimes all three. The old intake asked everything, of everyone, up front. People stopped partway through. Attorneys chased the rest by phone, which is the most expensive way to collect a form field ever invented.
Litigation funding runs on qualification. Before anyone gets money, somebody has to establish whether the case is fundable, and that means a long list of questions that exist for legal reasons rather than product ones. Here is the part that matters, and it took me a while to build the flow around it. The person filling this out is usually having the worst month of their life. They are hurt, or they are in a lawsuit, or they need money by Friday. Sometimes all three. The old intake asked everything, of everyone, up front. People stopped partway through. Attorneys chased the rest by phone, which is the most expensive way to collect a form field ever invented.
You can’t delete a question the law requires. You can decide when to ask it, and who has to face it.
You can’t delete a question the law requires. You can decide when to ask it, and who has to face it.
Progressive disclosure
Progressive disclosure
Underwriting
Underwriting
INT/CTG-06
INT/CTG-06
Role
Role
Senior Product Designer, Creative Director
Senior Product Designer, Creative Director
Deployed
Deployed
2022 to 2023
2022 to 2023
Scope
Scope
Consumer intake, attorney CRM, brand
Consumer intake, attorney CRM, brand
Team
Team
Two direct reports
Two direct reports
Constraint
Constraint
Compliance questions that could not be removed
Compliance questions that could not be removed
Tools
Figma
20%
20%
20%
20%
20%
more qualified leads
more qualified leads
35%
35%
35%
35%
35%
less drop-off
less drop-off
01
01
Handed something over-designed, with a name that was a problem
Litigation funding runs on qualification. Before anyone gets money, somebody has to establish whether the case is fundable, and that means a long list of questions that exist for legal reasons rather than product ones.
Cartiga is two products and a lending business, connected by design. LegalWizard is a consumer attorney finder for low-impact injury claims. An attorney group CRM takes a submitted claim as a warm lead, and the group accepts or passes. And Cartiga funds those groups against the cases on a percentage, which requires case status tracking and the ability to request updates.
So the intake is not a form. It is the origination point for a loan. What a claimant types determines whether a case is fundable, which is why qualification mattered more here than it does on a normal signup.
I was handed LegalWizard over-designed, and the first work was cutting it back.
Here is the part that matters, and it took me a while to build the flow around it. The person filling this out is usually having the worst month of their life. They are hurt, or they are in a lawsuit, or they need money by Friday. Sometimes all three.
And the name was already there, and it was not going away quietly. Which meant the brand had to hold two things at once: a wizard, and the worst day of somebody’s year.
02
02
The rebrand, and it was my call
The existing brand was yellow and blue and looked like Windows 95. That is not a taste problem, it is a trust problem, because somebody deciding whether to hand over the details of their injury is reading the interface for whether these people are real.
I argued for the rebrand rather than being asked for it. Earth tones and purple, leaning into the name rather than pretending it was not there.
The tricky part was tone. Lean too far into the wizard and you are making light of somebody’s injury, which is both wrong and commercially stupid, because the person filling in that form is not in a playful mood. Lean away from it entirely and you have a name your brand is embarrassed by, which reads as its own kind of untrustworthy.
Warm rather than whimsical. Approachable without being light about it.
LEGALWIZARD AFTER
After the rebrand. The previous identity was yellow and blue in a late nineties register, which reads as untrustworthy to somebody deciding whether to hand over the details of their injury.
03
03
Qualification, not friction
The old intake asked everything, of everyone, up front. People stopped partway through. Attorneys chased the rest by phone, which is the most expensive way to collect a form field ever invented.
You can’t delete a question the law requires. You can decide when to ask it, and who has to face it.
Intake became a dynamic form with conditional logic. You answer what applies to you and nothing else. Questions that do not apply never render, so the form gets shorter as the system learns more about the case instead of longer.
When somebody said a question was mandatory, I checked it. Every time, against the objective, the end goal, and the actual compliance requirement. Not because I doubted anyone. Because “we need this” and “the law requires this” get said in the same tone of voice, and only one of them is immovable.
That verification is what bought the room to design for the emotional state. You cannot lower cognitive load on a flow where every question is untouchable. You can lower it a lot on one where six of them turn out to be preferences.
I had two designers on this. Which changed what my job was: less drawing, more deciding what got drawn and why, and making sure the reasoning behind a screen survived being handed to somebody else.
The hardest part was cognitive load, not compliance. A required question is a fixed cost. What you control is how many of them somebody has to hold in their head at once, and whether the next one arrives before they have recovered from the last.
So the flow got built for somebody with about forty percent of their usual attention. One decision per screen where the decision is heavy. No question that requires reading a previous answer to make sense. Nothing that punishes you for stopping and coming back an hour later.
The worst screen was choosing an attorney. We could not pick one for you, legally, and that is not a rule anybody was going to bend. But the alternative as originally scoped was handing somebody in the middle of a bad month a list and asking them to rank lawyers.
What shipped was the top three near you, sortable. Three is small enough to hold. Nearby is a reason you can understand without explanation. And sortable means the people who do want to compare can, without making everyone else do it.
Qualified leads went up 20% and drop-off fell 35%, in the first three months after launch. Those two normally trade against each other: take friction out, get more completions and worse leads. Moving both the right way means the form did not get shorter so much as it started asking for different things.
THE INTAKE CUT
Not a shorter form. A form that asks for what makes a case fundable and stops asking for everything else.
04
04
The other side of the marketplace
The attorney CRM sits on the other end. A submitted claim arrives as a warm lead. The group accepts or passes. Case detail accumulates as the matter progresses, and status tracking and update requests keep the loan against it visible.
Lead status, case tracking and funding requests in one view instead of scattered across email and spreadsheets. Document upload feeds the same pipeline, so a funding request and its supporting files arrive together rather than needing to be matched up by hand later.
Design on this side is not persuasion. The group either takes the case or does not, and the job is to give them enough to decide quickly and enough afterwards to keep the lending side honest.
Then paralegal onboarding, which was the surface I expected to be easy and was not. Paralegals are the people actually moving cases through this thing all day. They are trained, they are fast, and they have almost no patience for a system that makes them think. Designing for somebody in distress and designing for somebody doing this four hundred times a week pull in opposite directions, and both flows feed the same records.
ACCEPT OR PASS
The other side of the marketplace. Enough to decide quickly, and enough afterwards to keep the lending side honest.
05
05
What it cost
I never got to test with a broad enough range of people.
It was the attorney groups. They are the side of the marketplace whose behaviour the whole product is designed against, and they are also the side that is hardest to get an hour from.
The four review gates came out of that. UAT, product, stakeholder, compliance, five checks each. I have described that as process discipline before and it was, but it was also a substitute. When you cannot get the user, you build something that catches what the user would have caught. It is a worse instrument and it is better than nothing, and I would rather say that than pretend the gates were the plan all along.
The order is not decorative either. Compliance last means the legal review is looking at something real people have already used. Compliance first means every usability decision downstream gets made inside a box somebody drew before anyone tested anything. ADA sits in the same checklist because in this product both are legal requirements, and neither survives being the thing you get to later.
The four gates. What I built because I could not get the user. It is a worse instrument than talking to them and it is better than nothing.
Gate | Check |
|---|---|
UAT | Usability |
UAT | Responsive logic |
UAT | Integration front to back, not just in the mockup |
UAT | Compliance |
UAT | ADA |
Product | Usability |
Product | Responsive logic |
Product | Integration front to back, not just in the mockup |
Product | Compliance |
Product | ADA |
Stakeholder | Usability |
Stakeholder | Responsive logic |
Stakeholder | Integration front to back, not just in the mockup |
Stakeholder | Compliance |
Stakeholder | ADA |
Compliance | Usability |
Compliance | Responsive logic |
Compliance | Integration front to back, not just in the mockup |
Compliance | Compliance |
Compliance | ADA |
It stuck, which is the part I did not plan for. The CRM dashboard went through it, and so did paralegal onboarding. UAT being one of the gates means every feature after this one gets in front of somebody before compliance signs it. That does not fix the range problem. It does mean nobody ships this flow again without a real person touching it first.
The cognitive-load decisions are reasoned rather than proven. I still think they are right. I would rather know.
What I’d do differently: trace every requirement to its source before designing against it, not partway through. Most of the room I found came from asking where a rule originated, and I was doing that reactively. Start there and the flow gets built once instead of twice.
I designed for somebody I never got enough of in a room.
06
What I wanted to show you
Regulated products are where most design advice stops working. You can’t delete the question, you can’t reword it into something friendlier, and the person insisting on it is usually right.
What’s left is sequencing, and who has to carry the weight of it. On a product where the user is already having a bad month, that turns out to be most of the job.
ケビン・チャップマン
No. 26 / Lot 01 / SS26