Why Outlaw
How Outlaw Fits Together
Outlaw connects your firm two ways — in place (every part shares the same records, so you enter things once) and in time (nothing is overwritten, and each case sharpens the next).
Everything Included is about the bill: one product, one price, no feature tiers. This page is about why it’s one product in the first place, and the answer runs two ways. Outlaw connects your firm in place: every part reads and writes the same records, so you enter something once and it’s everywhere. And it connects your firm in time: nothing is ever overwritten, and what the firm does today sharpens what it does next.
The whole thing is one loop:
Read it as two arcs. The clay arc is connection in place: the same records flowing from the campaign that brings someone in to the payment that closes their case. The sand arc is connection in time: what you collect feeds back to tune the next intake. The two sections below walk each arc in turn.
Connected in Place
Most firms run on a stack: a marketing tool, a CRM for intake, a practice management app, a billing system, a payments processor. Each was built to do one job well, so the connections between them are exports, overnight syncs, and the same client’s name typed in five times. Every one of those seams is a place data goes stale or gets dropped. Outlaw was designed as one system from the start, so there are no seams to reconcile.
The Thread, Record to Record
Follow the clay arc. Each step continues the one before it rather than starting over:
- A campaign brings in a lead, and the lead remembers which campaign (or campaigns) it came from, so later you can weigh what a campaign costs against the cases it actually produced.
- When you win the lead, it becomes a case, wired back to the lead it came from, so the whole sales history stays one click away.
- Work on the case is a task, and a started task is the time entry, so the work records itself as you do it.
- Time, expenses, and earned fees roll into an invoice; the invoice collects through built-in payments; trust money is tracked as trust the whole way.
What Carries When You Win a Lead
Winning a lead doesn’t ask you to rebuild the client from scratch. The things that are genuinely the same carry straight into the case:
| When the lead becomes a case | Carried into the case? |
|---|---|
| The client(s), and who gets billed | |
| Case type, and the rate, minimum trust, and numbering it implies | |
| Participants (opposing party, co-counsel, relations) | |
| Flat-fee schedule for the case type | |
| Intake answers you mark Show in Case | you choose which, per question |
| Red flags | by design (see below) |
| Pipeline milestones | the case has its own stages |
The case opens already knowing who it’s for, how it’s billed, who’s involved, and whatever intake you chose to bring along. You’re continuing a record, not re-keying one.
Intake is opt-in on purpose: each custom question has a Show in Case switch. Leave it off and the question stays a sales-stage detail; turn it on and both the question and the client’s answer follow the case, so an address or a fact you captured at intake isn’t asked twice.
One Contact, Created Anywhere
A person is one contact, and that single record is what leads, cases, participants, expenses, payments, conflict checks, and events all point at. Type a client’s details once and every part of the firm that needs them is reading the same record. Change a phone number and it’s changed everywhere, because there’s only one copy.
What makes that practical is that you can create a contact from almost anywhere you happen to be. On a lead, a case, an expense, a payment, an event, a task: start typing a name that isn’t on file yet and choose to create it right there. The new contact is saved with the record you’re working on and lands in the same shared address book the rest of the system reads. You never have to stop, leave for the Contacts page, add someone, and come back. (Companies work the same way.)
Plan the Work Once
Most of what a task needs, the estimate, who it’s assigned to, how it’s billed, what activity it logs, can be captured ahead of time as a task template. Starting a task from a template copies all of that in, so the time tracking and billing downstream come out consistent without anyone re-deciding it each time.
Templates are reachable from wherever the work is: type part of a template’s name into a new task’s title and it fills in, or pick one from the Template chooser on the task list that’s embedded on cases, leads, contacts, and campaigns. Case types go a step further and pre-stage their own template tasks, so a new case arrives with its standard work already laid out.
Connected in Time
The forward arc would make Outlaw a tidy assembly line. The return arc is what makes it a practice that learns: because every outcome lives in the same records as the work that produced it, the firm’s past can feed the decisions that come next.
The Loop That Learns
Follow the sand arc. The reports aren’t a separate analytics product you pipe data into; they’re the same records, read across the seams that would otherwise be there. Three readings come straight out of the loop:
Which Campaigns Pay Off
Campaign spend, weighed against the leads and cases each campaign produced, all the way through to what those cases billed and collected.
Which Campaigns Bring Risk
Leads tie campaigns to the red flags raised at intake, so you can see which sources tend to send clients you end up flagging.
Which Flags Cost You
Each red flag, followed through to the invoices and payments on its cases, becomes a recovery rate: how much you actually collect when that flag is present.
That last reading can close all the way around. In Settings, Outlaw shows a suggested weight for each red flag, derived from how well cases carrying it actually pay. With Use Actuals, you apply that suggestion, and from then on the flag pulls its real, evidence-based weight in the intake risk score. The results of representing clients quietly tune how you screen the next ones.
Case types are the second dial. Open a case type’s settings and you’ll find a plot of every case of that kind, each point sized by how much it actually collected against what it billed and grouped by how it ended (open, closed, withdrawn). It’s the same payment data again, turned into a read on which kinds of work pay off, so how you price, staff, and stage that case type can follow the evidence instead of a hunch.
Nothing Is Ever Overwritten
All of that learning rests on one rule: Outlaw never overwrites your data. Every save writes a new version of the record and keeps the old one, so the history a recovery rate or a cost trend is built from is always complete and always there. Three things follow:
- Every record is a timeline you can read. The Blame Log on any record lists every change since it was created: who made it, when, and exactly what changed, field by field, with the value before and after, and a one-click restore of any past version. Even deleting is just another recorded change, which is why the Trash can bring records back. (More in Blame Log.)
- Your numbers don’t quietly drift. A figure the firm learned from a year of cases is built from versions that still exist, so the past it relies on stays exactly as it was.
- A finalized invoice is frozen in time. Once you finalize and send it, its totals are the legal document the client received. Later payments or edits never rewrite it; they belong to the next invoice. (See Invoices.)
That’s the deeper meaning of connected in time: the firm’s past is preserved exactly, so it can be trusted to shape the future.
Two Questions, One Risk Register
Red flags are the clearest case of Outlaw connecting things by keeping them apart on purpose. A lead and a case both have red flags, but they are deliberately separate sets, because they answer two different professional questions:
Lead Red Flags
Should we take this case? The flags you weigh at intake, when you’re deciding whether to sign the client at all.
Case Red Flags
Should we withdraw? The flags that matter once you’re representing the client, when the question is whether to stay in or get out.
That’s why red flags don’t ride along from the lead into the case: the things that make you hesitate to sign a client aren’t the things that make you consider leaving one. Each set is scored into a single risk number on its own record, so the intake decision and the keep-or-withdraw decision each get a clean read.
The Trust Sweep
After a billing run, the same invoices feed the Trust Sweep: the worksheet that works out, per invoice, how much earned money you may move from trust to operating, whether each client’s trust needs replenishing, and whether the invoice went out. The figures come straight from the invoices and the trust ledger you’ve already built, so the sweep is computed, not retyped into a spreadsheet where a dropped row becomes a trust-accounting problem.
See It on Every Page
You don’t have to hold this whole map in your head. Each feature’s guide ends with a short How This Connects note: what flows into that feature, what flows out of it, and which other parts depend on it. Follow those, and you’re walking the same loop this page describes, one record at a time.