Your systems disagree about the same numbers, and you're not sure what kind of engineer fixes that.

• The accounting system, the POS and the CRM each have a number for last month, and they're three different numbers.
• Someone reconciles the systems by hand before anyone will trust a report.
• The real process lives in a spreadsheet, and the software is where the data goes afterwards.
• Every tool was bought to fix one problem, and nobody decided how they fit together.
• You've asked a developer, an IT company and a SaaS vendor, and each one offered to sell you the thing they sell.

With what's true. Software that grew together by accident usually disagrees for a small number of reasons: the same thing has three names in three systems, one system is quietly dropping rows, a feed was patched once years ago and nobody remembers why. Those are findable, and finding them comes before anyone should build anything.

That's what the audit is. I read the database your reporting runs on, with read-only access, and you get a written report of what disagrees and why, with the queries I ran and what came back.

From there, the honest outcomes are:

• Fix how data comes in, so the systems you have start agreeing. That's the reporting and data platform work.
• Replace the one part that hurts, usually a workflow living in a spreadsheet. That's operational software.
• Build nothing. Sometimes the fix is configuring a tool you already pay for, and I'll say so.

Read access to a replica of the database your reports come from. If your business has one, even an old one someone set up years ago, that's enough to start. The systems I usually find feeding it are point of sale, accounting, payroll, scheduling, reservations and a CRM.

If there's no database anywhere, and your numbers live only inside SaaS tools and spreadsheets, the audit as it stands doesn't fit. Write to me anyway and describe what you have. I'll tell you plainly whether I'm the right person, and if I'm not, what kind of person is.