Tools that don’t talk
to each other

Your booking tool, invoices, office spreadsheet and website form each work. The cost, when there is one, sits in between: the same customer typed in again by someone with other things to do.

Start with one ordinary job and a simple list.

1. Follow one real customer

Pick an ordinary job you finished recently, not your best or worst.

Write down every place that customer’s details were entered, from first contact to final payment. For each, note:

• Where it was entered: the website form, a text, the scheduling tool, the invoice, a notebook.
• Who entered it.
• Where they got it from: the customer, or another of your tools.

Don’t tidy it up. If the address was read off a text and typed into the schedule, write exactly that.

2. Mark the retypes

Mark every line where “where they got it from” is another tool, paper or someone’s memory. Those are your retypes: information you already had, entered again by hand.

Count them. Your real number beats any average you’ll read online.

Did any retype go wrong? A wrong address, an old price, a note that never reached the person doing the work. Mark those twice.

3. Ask four questions

Take each retype and ask:

1. Does a tool I already pay for do this? Check the receiving tool’s settings and help pages for a feature you never switched on. Confirm whether the feature is included in your plan and what setup or ongoing work it needs.
2. Can these two tools connect? Check both vendors’ connection lists for the plan you have. Until you’ve checked both, it’s a hope, not a plan.
3. Are two tools doing the same job? If your scheduler can also send the reminder, you may not need the reminder app.
4. Is this one fine as it is? A two-minute weekly retype that never goes wrong may not be worth touching.

Use these questions to identify options. Compare their full costs, reliability and effect on the work before choosing.

4. Configure, connect, replace, or leave

Configure when an existing feature meets the need at a sensible setup and ongoing cost.

Connect when a supported transfer has enough benefit to justify setup, monitoring and recovery when it fails. Connections can break, so know who will notice.

Replace when a tool can’t do a job you now need, or two tools overlap and one does both. Count the cost of moving records and retraining, not only the subscription.

Leave it when the retype is rare, quick and reliable. Not every gap needs closing.

If no tool does what you now need, a custom tool or a rebuilt website with a way for your team to manage jobs and requests can be right, once requirements, costs and dependencies have been checked.

5. The checklist

1. For one ordinary job, how many times were the customer’s details entered by hand?
2. Which of those were copied from another tool you already have?
3. Did any copy go wrong on that job?
4. For each tool: who holds the login, and is the account in the business’s name?
5. What does each tool cost a month, and which plan features don’t you use?
6. Can you export your customer list and job history from each one?
7. If one tool stopped working tomorrow, what would stop with it?

Few retypes, none going wrong: leave it. Otherwise, list the options that fit (configure, connect, replace or build) and compare their full costs, reliability and effect on the work. Check requirements, costs and dependencies before replacing a tool or building one.

A manageable next step

Bring that list to a free First Look: a 15-minute call, one real observation and a straight answer on whether more work is worth it, with no obligation. If it is, Diagnose follows one journey through your tools and ranks up to three improvements. A Build starts with the tools you already use. Website the question? See patch it, rebuild it or leave it alone. Too much runs through you? See can your business run without you for five days?

What a tool can connect to depends on the vendor and your plan, and both change. Check before you commit.