Almost every small claims operation starts the same way. You win a few files, you track them in a spreadsheet, you keep the carrier correspondence in Gmail, you save the photos to a phone or a shared drive, and you keep the deadlines in your head or on a sticky note. It works — right up until it doesn’t. The question isn’t whether the patchwork stack breaks. It’s how much it’s quietly costing you before it does.
The real cost of the patchwork stack
The spreadsheet-and-Gmail setup feels free because you’re not paying for it. But you’re paying in other currencies.
Lost context. A property claim is a conversation that runs for weeks or months. When the record of that conversation is scattered — some in email threads, some in spreadsheet cells, some in a folder of PDFs, some in nobody’s notes — reconstructing “where does this claim stand?” becomes a small research project every time someone asks. Multiply that by your active caseload and it’s a real tax on every day.
Missed follow-ups. Carriers respond on their timeline. Supplements sit. Deadlines for proof of loss, appraisal demands, or statutory response windows arrive whether or not anyone’s watching. In a spreadsheet, the clock isn’t anyone’s job — it’s a column someone has to remember to look at. Things slip not because anyone’s careless but because nothing is surfacing the slip.
Version chaos. The moment two people touch the same spreadsheet, you have a versioning problem. “Final_v3_REAL.xlsx” is a punchline because it’s true. Financial numbers in particular — RCV, ACV, depreciation, deductible, supplements, fees — are exactly the kind of data you do not want living in a file that can fork.
No visibility. You can’t manage what you can’t see. A spreadsheet doesn’t show you a pipeline. It doesn’t tell you which stage has a logjam, which adjuster is overloaded, or which claims have gone quiet. You find out when something’s already on fire.
Onboarding friction. When the system is “ask the person who knows,” every new hire is slow for months, and the business doesn’t really scale past the founder’s memory.
None of this means you did something wrong. It means you outgrew the tool.
What changes when every claim has one record
The fix isn’t a fancier spreadsheet. It’s a different model: one record per claim, with everything attached to it.
When that’s true:
- The pipeline is real. Every claim sits in a stage. You can see the board, spot the logjams, and rebalance work.
- The correspondence is on the claim. Carrier emails sync in, so the thread lives where the claim lives — not in one person’s inbox.
- The documents are on the claim. The policy, the estimate, the supplements, the signed agreements, the photos — one place, versioned, searchable.
- The financials are on the claim. A worksheet, not a side file: RCV, ACV, depreciation, deductible, supplements, contractor payouts, your fee — computed, attached, current.
- The deadlines are on the claim, and the system surfaces them instead of waiting for you to check.
The difference in day-to-day feel is hard to overstate. “Where does this claim stand?” becomes a five-second look instead of a five-minute hunt. Handoffs stop dropping context. New hires get productive because the system is the institutional knowledge.
A practical migration path
Migrating off the patchwork stack sounds heavier than it is. Done in order, it’s a week or two of low-drama work — not a big-bang cutover.
1. Audit your active claims
You’re not migrating history; you’re migrating what’s live. Pull your active caseload into a clean list: claim name or number, the insured, the carrier, the date of loss, the current status, the amount in play, and the key upcoming date. That list is your migration scope. Closed and dead claims can stay archived where they are.
2. Pick your stages
Before you import anything, decide what your pipeline actually is. Most claims operations have somewhere between four and seven real stages — something like New / Documenting / Submitted / Negotiation / Settled with maybe a Litigation or On hold lane. Don’t copy someone else’s. Name the stages the way your team already talks. Configurable terminology matters here: if your team says “matters” not “claims,” or “documenting” not “scoping,” the tool should bend to you.
3. Import via CSV
Take that audited list and import it. A clean CSV — one row per claim, columns mapped to the fields above — gets your whole active book into the system in one move. Map your old status values to your new stages during the import. This is the moment your spreadsheet stops being the source of truth.
4. Connect Gmail
Turn on the email sync so carrier correspondence flows onto the claim record going forward. This is the step that ends “which inbox is that thread in?” From here, the conversation lives with the claim.
5. Train the team — briefly
The training that sticks is short and concrete: here’s how you find a claim, here’s how you move it a stage, here’s where the documents go, here’s where the financials live, here’s how you log a call. Twenty minutes and a one-pager. Don’t over-produce it.
6. Sunset the spreadsheet
This is the step people skip, and skipping it is fatal. If the spreadsheet still exists, half the team will keep updating it “just in case,” and you’ll have two sources of truth — which is worse than one bad one. Pick a date. After that date, the spreadsheet is read-only history. Everything new happens in the system.
What you should expect afterward
- Status questions answered at a glance instead of by archaeology.
- Fewer slipped deadlines, because the clock is the system’s job now.
- One set of financial numbers per claim, not a fork.
- A pipeline view that actually tells you something about your business.
- New hires productive in days, not months.
The patchwork stack got you here. It won’t get you further. The good news is that getting off it is mostly a matter of doing six unglamorous steps in order.
If you want to see what “one record per claim” looks like in practice, take a look at everything Clatus does, or — if you run a public adjusting firm — how Clatus fits a PA shop. You can bring a few active files and we’ll walk through the migration with you.