_image7d2.webp)
The story every burned operator tells
Most operations leaders who have been through a painful ERP tell it the same way. They did the diligence, sat through the demos, and signed with a name everyone in the category knew. A year later the real work is running in QuickBooks and spreadsheets beside the system they paid for, and they are wondering how something this expensive ended up running so little of the business. The instinct is to conclude they bought bad software. Usually they didn’t. They bought a system built for a different company than theirs.
Fit, not features, is where it breaks
Legacy ERPs rarely lose on the feature list. On paper, NetSuite and Microsoft Dynamics 365 can do almost anything. They lose on fit: each is built around a fixed model of how a business should operate, and it expects yours to conform. That assumption holds up if you look like the enterprise the software was designed for. Growing consumer-goods operators rarely do. They run lean teams, add channels and SKUs constantly, and need to change a workflow this week, not next quarter.
When the system can’t bend, you bend around it. You close the gap with configuration, then customization, then a consultant or a partner, and every workaround becomes something you now own and maintain. Two failure modes show up again and again. One company hit both.
When the pricing model punishes growth (NetSuite)
Snackwise , a Bay Area food and beverage distributor, started on NetSuite and got priced out. The problem wasn’t capability. It was that the cost scaled against them.
“We have 2,300 invoices with lines of data going through the roof, and NetSuite was charging us per line of data. Our bill quadrupled overnight and they just expected us to eat it.”
— Steve Toves, Owner
For a distributor whose entire business is volume, thousands of orders consolidating into one invoice per customer each month, a meter on data turns success into a penalty. This is the ERP tax: enterprise capability priced for an enterprise, plus the consulting overhead it takes to keep running.
When every change goes through a middleman (Dynamics)
Microsoft Dynamics 365 came next, and as a small business Snackwise was routed to third-party implementation support. In a high-volume, time-sensitive operation, every small change became a slow, billed ticket.
“Any simple change took time, effort, and cost. One client wanted their invoice to say ‘United States’ where our system said ‘USA.’ We had to reach out to our Microsoft Solutions Partner to fix it. That would take weeks, an invoice, and additional fees.”
— Roger Hechema, Operations & Purchasing Manager
“I wanted to move our logo from one side of the page to the other and they had to code it, costing $1,500 and taking one week. I could do that in QuickBooks in thirty seconds.”
— Steve Toves, Owner
Dynamics is powerful, but its power lives behind the Power Platform and a partner. The people who ran the business had no way to touch the system themselves.
The compounding cost of inflexibility
Inflexibility does not just slow a team down; it multiplies mistakes, because so much of the work recurs. Snackwise restocks the same customers on a standing schedule, so a single setup error repeats on every delivery. If a recurring order was built to send Coke instead of Diet Coke, that mistake could go out 40 times a day for a month before anyone caught it, leaving Roger to correct 800 identical orders by hand at billing time. The system sold as leverage was manufacturing manual work.
DOSS vs NetSuite vs Dynamics, side by side
On paper the enterprise systems win the feature war. What a growing operator actually feels, month to month, is who controls the system. Here is how the three compare on that.
The pattern is consistent. NetSuite and Dynamics deliver enterprise depth, but access to it runs through developers, consultants, and partners. DOSS puts the controls in the operator’s hands.
A different design: adapt the software to the business
The fix is not a better-configured version of the same thing. It is a system that adapts to how the business already runs, and that the operator can change without a middleman. That is the principle behind DOSS, the Modern Operations Platform built for the real world: your applications should serve your strategy, not cap it. The changes that used to be billable requests, schemas, approvals, routing, automation, become clicks your own team makes, and Dossbot, the AI copilot, runs analysis, actions, and bulk changes across workflows through chat.
“We’re not a technology company, we’re a food company. What mattered to us was finding someone who understood our business and could solve problems quickly.”
— Steve Toves, Owner
Approachability mattered as much as capability. Roger, who calls himself a business person rather than a technologist, runs it day to day. “It wasn’t too complicated. With help from Joyce and the DOSS team, I figured it out. It felt easy.”
What changes when the system fits
Today Snackwise runs ordering and consolidated invoicing on DOSS. Month-end invoicing that once took a week now takes a couple of hours, 95% faster, with bulk fixes handled in one form instead of hundreds of manual edits.
“Steve and I would be here until midnight making little edits. Now I do it in a couple of hours.”
— Roger Hechema, Operations & Purchasing Manager
And when something needs attention, it is handled in the moment: “We’d be on a call with DOSS, have an issue, and by the time we got off the call it was fixed.”
Fit is the whole game
Snackwise isn’t done. Purchasing, inventory, and accounting are next. As Steve puts it, the better DOSS makes them, “the easier it is for us to grow, and for me to sleep well at night.”
If the ERP you bought never fit, the question isn’t whether it was good software. It’s whether it was ever built for a business like yours, and whether you can change it yourself when the business changes. NetSuite and Dynamics ask you to conform. DOSS adapts. That is the whole game.
See how Snackwise made the switch
Compare in detail: DOSS vs NetSuite | DOSS vs Microsoft Dynamics
