When is a custom app just three spreadsheets in a nicer shirt?

A custom tool is worth it when one repeated job is costing you more than the build. Not before.

Owners ask for an app when they are drowning in tabs. Sometimes they need software. Sometimes they need one spreadsheet with rules, or to stop asking the same three people to copy-paste between tools. Building the mess in custom code makes it harder to unwind.

Name the job before you name the product

Write the repeated task: “Every Friday we retype orders from email into a sheet, then into QuickBooks.” If you cannot name the job in one sentence, you are not ready to build.

Then check whether a simpler path works: one air-tight spreadsheet, an existing tool you already pay for, or a Zap that moves the data once. Custom is for the leftover part that still hurts.

• A task that happens often enough to measure.
• The people who would use it, named.
• A first version you could test in weeks, not a platform vision.

Pay for discovery so you do not pay twice

A short mapping phase is cheaper than a rebuild. It shows which steps are human, which are already solved, and which one slice is worth a prototype.

If the honest answer is “three cleaner spreadsheets,” that is a win. You can always build later, with a smaller target and a real budget.