Today's tip: find the step a person repeats only because two systems do not communicate
That is your first automation candidate. Not the flashiest workflow. Not the one a vendor demoed last quarter. The one where a human being is acting as a data cable between two pieces of software that were never introduced to each other.
It usually looks like this in a law firm: someone opens the call tracking platform, reads a number, opens a spreadsheet, types the number. Someone exports leads from the intake form and re-keys them into the case management system. Someone pulls ad spend from one tab and matter counts from another and builds the monthly marketing report by hand, from memory, under deadline. Nobody calls this work. It just happens in the gaps.
Those gaps are expensive in two directions. You pay salary for the keystrokes, and you pay again in decision quality, because data that passes through a human hand arrives late and arrives slightly wrong. A report assembled by copy-paste on the fifth of the month is a report about a decision you could have made on the first.
How to actually find it
Do not run a process audit. Ask one question in your next team meeting: "What do you open two tabs to do?"
Then listen for the tell. People describe these tasks apologetically, as if the inefficiency is their fault. "I just pull the numbers from the dashboard and drop them into the sheet." "I just check the call log against the intake list." The word just is a flag. It means the person has normalized a manual bridge between systems and stopped seeing it as a problem.
Write down every one of those bridges. Rank them by how often they run — daily beats monthly — and start with the top one. Frequency matters more than complexity here, because a five-minute task that runs every morning costs more per year than an hour-long task that runs once a quarter.
Let the attribution data tell you where the bridge should go
Once you know which handoff to automate, you need to know what it should carry. This is where most firms stop at a surface metric and lose the thread.
GA4's attribution-paths report shows which channels initiate, assist, and close key events, along with days and touchpoints to conversion. That is a materially different picture from a last-click report. A channel that never closes anything can still be the channel that starts every path — and if your manual report only captures the final touch, you have been underfunding the top of your own funnel for however long you have been running it.
The days-to-conversion and touchpoints-to-conversion dimensions matter just as much for legal. A personal injury inquiry and a complex commercial matter do not convert on the same clock. When you know the real lag, you stop panicking about a "slow" month that is actually a normal interval in a longer path, and you stop declaring victory on a campaign before its paths have finished running.
The word just is a flag. It means someone has normalized a manual bridge between two systems and stopped seeing it as a problem.
Build the drill-down, not just the number
Here is the design rule that separates a dashboard people use from a dashboard people screenshot once and ignore: let users drill from a KPI down to the actual calls, leads, and matters behind it.
A number with no path underneath it does not survive contact with a skeptical partner. The first time someone asks "where did that 38 come from?" and the answer is "the system says so," trust is gone and the spreadsheet comes back. When the same person can click the 38 and see thirty-eight named calls with timestamps, sources, and outcomes, the argument ends. That is how you retire the manual report permanently — not by publishing a prettier version of it, but by making the automated version more auditable than the hand-built one ever was.
This is the whole idea behind the ROI Dashboard workflow: the KPI is the entry point, not the destination.
Two things you keep when you automate
- Preserve approvals. Automation should remove the typing, not the judgment. If a human reviewed something before, keep the review step. Speed that removes oversight from a client-facing or compliance-adjacent process is not efficiency, it is risk with a shorter fuse.
- Create an error queue. Every automated handoff will fail sometimes — a malformed phone number, a timeout, a field that changed names upstream. Those failures must land somewhere visible with an owner attached. An automation with no error queue does not stop failing; it just fails silently, and you find out when a lead never got called.
Measure cost per signed matter, not automations built
This is where most revenue-operations projects quietly go sideways. Teams start counting workflows shipped, integrations connected, hours "saved." None of that shows up in a P&L.
Measure cost per signed matter. That single metric forces every other decision into focus. It tells you whether a channel that looks expensive per click is actually cheap per client. It tells you whether an automation that saved six hours a month also improved speed-to-contact enough to move signings. And it is the only number that lets you compare a paid campaign, an intake change, and a content investment on the same scale.
If you cannot calculate cost per signed matter today, that gap is itself a sign of a missing integration — specifically, the one between marketing spend and the case management system where matters actually get recorded. For most firms, that is the bridge a person is currently crossing by hand.
Your next step
Before the week ends, do this:
- Ask your intake and marketing people what they open two tabs to do. Write down every answer.
- Rank the list by frequency, not by how annoying each task sounds.
- Open GA4's attribution-paths report and note which channels initiate versus close, plus your real days-to-conversion. Compare that to what your current manual report claims.
- For the top item on your list, define three things before anyone builds anything: who still approves, where errors land, and what the drill-down shows.
- Write down your current cost per signed matter. If you can't, that is the project.
Firms in this situation often discover that the first automation is not a sophisticated piece of custom software at all. It is one connection, carrying clean data, ending one daily copy-paste ritual — and giving every number above it a path you can click into.
See how we approach this: the ROI Dashboard.
Next step
See how Bosseo closes this gap
Book a short call and we’ll show you exactly where the leak is.