A custom system is useful when the business keeps paying people to bridge the same gap by hand.

1. Trace one repeated job. 2. Mark every copy, wait, and workaround. 3. Check whether a current tool can be configured or connected. 4. Price the smallest useful change.

Do not build a custom app to replace a tool people already use successfully. That is expensive pride in a tiny tuxedo.

Each step usually asks for more money and more change than the one before. Stop at the first one that fixes the broken outcome. Name the outcome, not the tool you dislike.

• Keep: the tool is clunky, but staff use it and customers aren’t hurt. Write the workaround down and move on.
• Connect: two tools hold the same facts and someone retypes them. The link may already exist. Google Forms, for example, can store responses in a linked Google Sheet: open Responses, then More, then Select destination for responses. Pick one place as the record, so two copies never disagree.
• Replace: the current tool blocks a must-have job. Download a copy of your data and open it before you sign anything new.
• Build: the gap is specific, it happens every week, and the first three didn’t fix it. A problem that shows up twice a year rarely earns custom software.

Count one repeated job for a week. Then estimate its yearly cost with your own numbers:

• Minutes per repeat × repeats per week × 52 ÷ 60 = hours a year spent bridging the gap.
• Hours × the hourly cost you choose, including what that person’s time is really worth to the business.
• Plus the yearly cost of every subscription that touches the job.

Set that against the full cost of building: the build, upkeep, moving data in, and moving it out later. It is an estimate, not a promised saving. If the numbers are close, keep renting.

Paper counts too. A clipboard can beat a login when one person uses it, in one place, and nobody needs a report. It starts costing time when the same fact gets copied into a calendar, a spreadsheet, and an invoice, or staff wait on one notebook. Fix the worst handoff with the smallest reliable tool, like the form-to-sheet link above.

• Accounts: when we build, the accounts stay in the business’s name.
• Code: the U.S. Copyright Office says copyright “initially belongs to the author(s) who created that work,” with exceptions such as an employee’s regular work. Owning a copy of the files does not give you the copyright. A transfer “generally must be made in writing and signed.” Put ownership in the written agreement and have a lawyer read it. This is not legal advice.
• Upkeep: who fixes it when a phone update or vendor change breaks something, and how is that billed?
• Exit: how does your data come out if you stop? See how to make sure you own your domain, website, and accounts.

Start with a Tech Audit and decide whether to keep, connect, replace, or build.

No. Useful tools should stay.

One real process, the tools involved, and the point where it breaks.

Want it handled? Software You Own — Tools no longer fit? We can map the handoffs before deciding whether to connect or build.

Product features and rules can change. Use the linked source as the current word.

• Google Docs Editors Help: Choose where to save form responses — Google Forms can send every response into a linked Google Sheet; menu path included. Checked October 19, 2026.
• U.S. Copyright Office: Circular 1, Copyright Basics — Who owns copyright at the start, the work-made-for-hire exception, and how ownership is transferred. Checked October 19, 2026.