The same data, typed three times

On October 9, Cloudflare announced that the team behind Deno, a developer tool many programmers build on, is joining the company (Cloudflare). Anyone who built on Deno now has a new question to watch: what changes when the people behind your tool move to another company.

I am not telling you this because you use Deno. You probably do not. I am telling you because it is a clean example of something every business owner lives with: the tools you rent can change under you. Prices move, features disappear, a company gets bought. Your business has to keep running anyway.

That matters for the bottleneck I want to talk about, because it is the one that rented tools create most often.

A common bottleneck: the same data, typed again

A customer fills out a form. Someone copies the details into the scheduling tool. Someone copies them again into the invoicing tool. Someone copies them a third time into a spreadsheet so the owner can see what is going on.

Each step takes two minutes, so nobody counts it. But it happens every time, it invites typos, and it means your numbers are only as current as the last person who had time to update them.

The bottleneck is not the typing. It is that your tools do not talk to each other, so a person has become the connection.

How to spot it

Do you have a spreadsheet whose only job is to hold information that already exists somewhere else?
Do two people ever give a customer different answers because they looked in different places?
Is there a step in your process that starts with "copy this over to..."?
Do you avoid changing a tool because too many things are wired to it by hand?

The last one is the quiet warning sign. When a process is held together by people copying data, you are stuck with whatever the tools do today, even when they change.

How it gets automated, and stays fixed

There are two honest answers, and which one fits depends on your situation.

First, use what already connects. Many tools can pass data to each other without anyone writing code. If the two systems you use have a standard connection, turn it on, test it with a few real records, and you are done. That costs little and I will tell you to do it.

Second, build the missing piece. If your process is specific to you, for example a quote that depends on how you really price, or a schedule with rules no off-the-shelf tool knows, then a small piece of software built for your business can be the one place the data lives. The other tools read from it instead of being retyped into. That is what custom software for small business should mean: one small piece that fixes one bottleneck, not a giant system.

What makes the fix last is the same in both cases:

One source of truth. Pick the place where a fact is entered once. Everything else reads from it.
Plain rules. Write down what should happen when the data changes, in words, before anything is built.
No locked doors. You should be able to export your data and change tools without losing years of history. That is the lesson of any tool that gets bought or shut down: plan the exit before you move in.
Someone can change it. A system nobody can edit is just another bottleneck with a nicer name.

I build my own products, so I have been on both sides of this: choosing a tool, and being the one responsible when a service I depended on changed. The trade-off is real. Building costs more up front. Renting costs you control. The right answer is usually a mix, with building reserved for the part that is truly yours.

What a lasting fix looks like in practice

Picture a simple version. A customer fills out one form. That entry creates the job, drives the schedule, and feeds the invoice, so nobody types it again. If a field changes, it changes everywhere. If the invoicing tool is replaced next year, the job record is still yours and the new tool reads from it. That is the difference between a patch and a fix: the patch saves two minutes this month, and the fix keeps saving them after the tools change.

It also changes who you depend on. When data is retyped by hand, you depend on whoever has time. When it is entered once, you depend on a rule, and a rule can be checked.

What I would do on Monday

Pick one customer record, one order or one job, and follow it from the first time anyone types it to the last. Write down every place it gets typed again. Circle the ones that are pure copying. That list is your map, and the top item is where I would start.

Show me yours

If you would like a second set of eyes, that is the free call. Tell me how a job moves through your business, and I will help you find where it gets retyped and what would fix it for good. Fixed quote before any work, no obligation, and I reply myself.

Show me yours. Text (512) 337-9530, email josh@joshdlange.com, or book the free AI assessment.

Source: Cloudflare, Deno joins Cloudflare.