top of page

Your ERP Problem Was Never the Software

  • Writer: Tracey Wisner
    Tracey Wisner
  • Jul 13
  • 2 min read

A 15-person plumbing company can have the exact same technology problem as a 50 million dollar manufacturer.


That sounds like an exaggeration. It isn't.


I spent most of my career inside large-scale ERP implementations, the kind with steering committees and multi-phase rollout plans. This year I started working with a small, local field service business here in Castle Rock. Different scale, same root issue: their scheduling system, their accounting software, and their field team weren't talking to each other.


The Pattern Repeats at Every Size

Whether it's NetSuite at an enterprise or QuickBooks and a scheduling app at a home services company, the failure mode is identical. Someone bought a tool to fix a specific problem. Then another tool got added to fix the next one. Nobody ever went back and mapped how those tools were supposed to work together.


The result is the same everywhere: double data entry, invoices that don't match jobs, and a business owner who has to hold the connections together in their head because the software doesn't.



Why "Buy More Software" Is the Wrong First Move

When something breaks in a business's workflow, the instinct is to look for a new tool. A better app, a slicker dashboard, an integration that promises to "just work."


But adding software to a broken process doesn't fix the process. It just adds a new piece that also needs to be reconciled with everything else.


The fix starts somewhere less exciting: mapping the actual workflow as it happens today, not as it's supposed to happen. Where does a job start? Where does the data live at each step? Where does something get re-typed instead of passed along automatically? That map tells you what needs to connect, and only then does it make sense to talk about which tools should do the connecting.


What This Looks Like in Practice

For a field service business, that might mean making sure a job scheduled in the field service app automatically becomes an invoice in the accounting system, without anyone re-entering customer or job details by hand. For a larger company running NetSuite, it might mean making sure a saved search actually reflects how the finance team defines a metric, instead of an approximation someone built once and never revisited.


Different tools, same principle: map first, choose software second.

The Takeaway

If something in your business feels like it's held together by memory and manual double-checking, the fix probably isn't another subscription. It's twenty minutes with a whiteboard, tracing the actual path a job or a transaction takes from start to finish.


The businesses that get this right aren't the ones with the most software. They're the ones whose software actually reflects how the work really happens.

 
 
 

Recent Posts

See All
The Collections Stack You Can Build Inside NetSuite

THE PROJECT This summer another NetSuite firm brought me in to work on their own accounts receivable. The brief was rough guidelines around the functionality they wanted to see; the design was mine. W

 
 
 

Comments


bottom of page