A new client signs on. They fill out an intake form. Someone copies their details into a spreadsheet the owner likes to look at. Then someone sets them up in the project management tool, typing the same name, address, contact and service details. Then someone sets them up in the accounting software, typing it all again.
Three entries. Sometimes four. And by the third one, the phone number has a typo, the billing contact is different, and nobody’s sure which version is right.
What the owner thinks
Often nothing, at first. It’s just admin. It’s how setup works. When it starts to bother someone, the next thought is usually, “We need an integration.”
Maybe. But an integration moves information from one place to another. If you haven’t decided where the information should start, you can end up automating the confusion.
Tracing the trip
Here’s the typical path for a new client’s information:
- Intake form. Client enters their own details. Usually the most accurate version, because they typed it.
- Spreadsheet. Someone copies it in, maybe adding notes. Now there are two versions.
- Project tool. Someone types it again to set up the client and their work. Three versions. The project tool might also get extra details the others don’t have.
- Accounting software. Typed again for invoicing. Four versions. Billing contact, payment terms and rates often live only here.
- A change happens. The client moves or switches contacts. Someone updates one place. Maybe two. Now they disagree.
Every retype is a chance for an error, and every update is a chance for the systems to drift apart.
What I’d investigate
I’d make a simple map. List every piece of information that gets collected about a new client: name, contacts, address, billing contact, services, rates, terms, start date. Then for each one, mark where it’s first captured and every place it gets entered again.
That map usually makes the problem obvious. You’ll see fields typed four times, fields that only exist in one person’s spreadsheet, and fields that are collected but never used.
What’s underneath it
Nobody decided where each piece of information is born and which system you trust for it. So every system collects a little bit of everything, and people fill the gaps by hand.
What I’d change
- Decide where each field originates. Contact details might start at the intake form. Rates and terms might start in the signed agreement. Project details might start in the project tool.
- Collect it once. Expand the intake form so it captures what downstream systems need, instead of chasing it later by email.
- Decide which system you trust for each field. If two systems disagree on the billing contact, everyone knows which one wins.
- Then move it. By integration if one exists and is reliable, or by one clean export or setup step. Even a single, well-defined copy step is better than three improvised ones.
For a contractor, the same pattern shows up with a new job: the estimate, the scheduling board, the job management app and accounting each get the customer and the job typed in fresh. For a service firm, it’s the engagement letter, the CRM, the project tool and billing. The fix is the same either way: one place where each fact starts.
What I’d leave alone
Systems that already do their job. I’m not trying to collapse everything into one tool. I’m trying to stop the retyping and the drift.
The tradeoff
Integrations need upkeep. They break when software updates, and someone has to notice. Sometimes a perfectly connected setup costs more to maintain than a little retyping. The goal is to make that call on purpose, not by default.
The pattern
Decide where information is born before you decide how it travels. Most double entry isn’t a technology problem. It’s a missing decision about which system owns which fact.
So try the map. One new client, every field, every place it gets typed. You’ll know in twenty minutes whether you have a small annoyance or a real problem.
If the map gets messy, that’s a good thing to bring to a Systems Fit Call.
