← Back to Notes
Data & Reliability · Oct 2026

Why Your Customers Stop Trusting Your Numbers

Your finance product doesn't have to crash to lose a customer. It just has to show one number they know is wrong.

A payment counted twice. A refund that never appears. Last month's income landing in this month. A bank connection that stopped updating days ago without anyone noticing.

Each one feels small to your team. To your customer, it's proof the app can't be trusted with their money. They don't file a bug report. They export their data and leave.

These problems are rarely random. They come from a few early decisions about how data comes in.

How records are recognised. If the app can't reliably tell that a transaction is one it has already seen, every re-import creates duplicates. Records should be matched using the bank's or platform's own reference, not their position in a file.

How imports finish. An import that fails halfway can leave data half-changed. Imports should show a preview, then save everything or nothing.

How refunds are handled. Refunds and reversals are real money. Quietly ignoring them makes totals look better than reality, until a customer checks.

How dates are handled. Banks and platforms report times in their own time zones. Handled carelessly, entries land on the wrong day, or in the wrong month.

How problems are shown. A sync that fails silently is worse than one that fails loudly. Customers should always be able to see when their data was last updated.

Get these right and something quietly changes: people stop double-checking the numbers and start relying on them.

Have something
worth solving?

Hiring an engineer, building a product, or dealing with a problem you haven't figured out yet — start with the problem.

Tell me what you're trying to make happen.