You've outgrown the spreadsheet, and the SaaS you'd replace it with doesn't fit either.

• The business runs on a spreadsheet three people are afraid to touch.
• You pay for four SaaS tools, and someone exports between them every week.
• The ERP quote was written for a company five times your size.
• Every workaround has an owner, and one of them is about to leave.

The part that hurts, not the whole stack. Usually that's one workflow (ordering, scheduling, inventory, approvals) that lives in a spreadsheet because no product did it the way the business actually works. It becomes a small application on the same database your reporting reads, with the tools you keep connected to it rather than replaced.

Sometimes the honest answer is that nothing custom should be built, and the right move is configuring something you already pay for. If that's what the audit shows, that's what I'll tell you, and it's a finished piece of work.

What changes: the spreadsheet stops being a single point of failure, and the numbers it used to produce land in the same place as everything else.

PostgreSQL. A small web application, deliberately boring, that the next engineer can read without me. Connections to the systems you keep, over their APIs where they have one and their scheduled exports where they don't. Nothing you have to license from me.

If you need a certified off-the-shelf ERP, for regulated accounting or audited financial controls, buy one. And if the business has no data yet, there's nothing for software to sit on.