Home / Problems solved
Problems solved · written from your side of the desk

Start with the problem, not the service.

Nobody wakes up wanting "systems integration." They wake up to a month-end that won't close, a feed that failed silently, an application only one person understands. Each page below starts with how the problem sounds in your plant, explains what's usually underneath it, shows how it gets fixed, and points at the ledger entry that proves it.

THE APP NOBODY CAN MAINTAIN

The system that runs the business — and the one person who understands it is retiring.

It's FoxPro, or Access, or something written in-house in 1999. It works, mostly. Nobody wants to touch it, the vendor is long gone, and every ERP salesperson who hears…

Read how it gets fixed →
TWO SYSTEMS THAT WON'T TALK

Two systems that are supposed to talk — and the people who re-key between them.

Engineering releases a change in PLM and someone types it into the ERP. Sales quotes from the CRM and operations ships from a different number. The EDI feed failed on…

Read how it gets fixed →
MONTH-END THAT WON'T CLOSE

The close takes nine days, and nobody can explain why the numbers move.

Every month it's the same: the GL and the subledger disagree by an amount that changes, PPV on the report doesn't match PPV in the GL, two reports of the same thing give…

Read how it gets fixed →
THE OUTAGE NOBODY SAW COMING

It failed at 2 a.m. on Tuesday. You found out Thursday. From accounting.

The nightly ERP processing quietly exited with an error and every downstream number was wrong for two days. The disk filled and the plant floor found out at the 6 a.m.…

Read how it gets fixed →
THE MIGRATION NOBODY PREPARED FOR

The new ERP is signed. The partner's plan assumes your data is clean. It isn't.

The vendor said the old system is end-of-life. The board approved the move. The implementation partner's project plan has a line called "data migration" that assumes…

Read how it gets fixed →
Let's talk

Your problem isn't on the list?

It probably rhymes with one of them. Tell us what's broken in your own words — the symptom, not the diagnosis — and you'll get a straight read on what's underneath it.

You'll get a straight answer and a tight scope. If we can't help, we'll tell you that too — and usually who can.

No newsletter. No drip sequence. Just a reply from us.

Got it — thanks.

We read every one of these ourselves. Expect a reply within one business day. If it's urgent, email us directly at dan.mindlin@mindlinconsulting.com.