Why platform implementations ask you to change your process

Somewhere around week three of a platform rollout, a consultant says the line. "We recommend adopting the standard workflow here." Translation: the software can't do what you do, so you're going to stop doing it. That sentence has quietly reshaped more mid-sized businesses than any strategy deck ever has. And most owners nod along because they assume the platform knows better.

Sometimes it does. Often it doesn't. The trick is telling the difference before you've spent a year retraining your team around someone else's assumptions.

Platform vendors sell one product to thousands of companies. That's the whole business model. Every feature they build has to be useful to a large slice of the customer base, or it doesn't get built. So the product becomes an average of what everyone needs.

Your process isn't average. It grew out of your customers, your margins, your state regulations, and the specific way your ops manager solved a problem in 2016. Some of that is accumulated wisdom. Some of it is scar tissue nobody's questioned. The platform can't tell those apart, and neither can a consultant who's been onsite for three weeks.

Implementation partners get paid to finish the implementation. That is the honest version. A partner who bends the software into unusual shapes creates something fragile that breaks at the next update, and then owns the support burden. A partner who talks you into the standard workflow ships on time and moves on. Their incentives point toward changing you, not the software. This isn't a conspiracy. It's just how the contract is written.

Plenty of business processes deserve to die. We've walked into shops where three people manually reconcile the same numbers because a spreadsheet broke in 2019 and nobody fixed it. We've seen approval chains with five signatures for a $400 purchase. We've seen a company track jobs in a system, then re-track them in a whiteboard, then re-track them in a group text.

None of that is competitive advantage. It's habit. When a platform pushes back on that kind of process, take the win. You get a cleaner workflow, and you get it without paying anyone to build it.

Here's a decent test. Ask whether a customer would notice if the process disappeared. If a step exists only to make an internal system happy, it's overhead. If a step exists because your customers expect something your competitors don't provide, that's the business. Protect it.

Standard accounting rules, tax handling, and payroll structure fall in the first bucket almost every time. Nobody wins on a custom general ledger. Use the platform. Follow the standard. Move on to something that matters.

A distributor we worked with had a pricing rule that made no sense on paper. Certain accounts got a rebate calculated after the fact, based on volume across product families, applied as a credit on the next order. The ERP couldn't model it. The recommendation was to switch those accounts to flat tiered pricing.

That rebate was why those accounts stayed. It was thirty percent of revenue. Changing it wasn't a process change. It was a strategy change, dressed up as a configuration decision, made in a room where nobody from sales was sitting.

That's the real risk. Process decisions get made during implementation by people who understand the software and don't understand the business. The finance lead is in the room. The person who actually knows why the odd step exists is on a job site. By the time anyone notices, the workaround is already live and there's a spreadsheet keeping the real business running alongside the system you just bought.

Most companies compare the license fee to a build quote and stop there. That comparison is wrong, because it leaves out the cost of the process change itself.

Put real numbers on it. Say a platform requires your team to add two manual steps per order because the standard workflow doesn't match how you quote. Two steps, four minutes total, on 120 orders a day. That's eight hours of labor a day. Roughly one full-time person, forever, whose entire job is compensating for software that doesn't fit.

Now add the seat licenses. Add the annual increase, which is real and usually somewhere between five and fifteen percent depending on your renewal terms. Add the implementation fee. Add the integration middleware you'll need because the platform doesn't talk to your other systems natively. Add the partner retainer for changes after go-live.

Then compare that to a system you own. A custom build is a one-time capital cost, plus hosting, plus whatever maintenance you choose to buy. The subscription line goes away. The per-seat penalty for hiring goes away, which matters a lot if you're growing.

The honest version is that the custom system usually costs more in year one. Sometimes more in year two. The crossover comes later, and it comes faster the more seats you have and the more workarounds the platform forces. If you've got twelve users and a straightforward process, buy the platform. If you've got ninety users and four spreadsheets holding the real process together, run the numbers again.

Don't make this decision at the system level. Make it at the workflow level. Almost every mid-sized company ends up with a mix, and that's the correct outcome.

Walk through your operation and sort each process into one of three groups.

• Processes that are genuinely standard, like payroll, general ledger, and basic AP. Use a platform. Change your process to match. Don't argue.
• Processes that are odd but not strategic. Odd scheduling, odd approval chains, odd document naming. Look hard at whether the oddness earns its keep. Usually it doesn't.
• Processes that are the reason customers pick you. Custom pricing logic, unusual service guarantees, a proprietary way of estimating or dispatching. Protect these. Build around them if you have to.

The third group is smaller than owners think and bigger than consultants claim. Most companies have two or three real differentiators. Everything else is just how it's always been done.

One more thing that trips people up. Your differentiator might not be a whole workflow. It might be one calculation buried inside an otherwise standard process. In that case you don't need a custom system. You need a small custom piece that plugs into the platform and handles that one thing. We build a lot of those. They're cheaper than a full replacement and they solve the actual problem.

Owning your system is not free of problems, and anyone who tells you otherwise is selling.

You own the maintenance. When a payment processor changes its API, meaning the technical connection between two systems, someone has to update your code. A platform vendor handles that across all customers at once. With a custom build, it's your line item. Budget for it or you'll get surprised.

You don't get the ecosystem. Big platforms have hundreds of prebuilt connectors and a marketplace of add-ons. Custom systems connect to whatever you pay to connect them to. If you rely on a wide web of third-party tools that all happen to have native integrations with one platform, that's genuine value and you should weigh it.

Compliance features are another real gap. Platforms serving regulated industries carry certifications, audit logs, and reporting formats built to satisfy specific regulators. Rebuilding that from scratch is expensive and slow. If you're in healthcare, financial services, or anything with heavy inspection requirements, check what you'd be recreating before you commit.

And custom builds fail when the client can't decide. Software has to encode a decision. If your leadership team can't agree on how something should work, no developer can fix that. A platform at least forces a decision by removing the options. That's a legitimate benefit of buying, and we've seen companies who needed exactly that.

Last one. If your process is genuinely broken and you're paying to preserve it in custom code, you've bought an expensive monument to a bad habit. Change the process. Then decide what to build.

Start by separating two questions that usually get mashed together. Is this process worth keeping? And can this platform support it? Answer the first one without the vendor in the room.

Then price the workarounds honestly. Count the minutes. Multiply by volume. Multiply by a year. That number is the real cost of changing your process to fit the software, and it belongs in the comparison next to the license fee.

If the arithmetic points toward a platform, use it and adopt the standard workflow with a clear conscience. If it points the other way, you have a case for building something you own, where the process stays yours and nobody raises your rent.

Black Badger builds custom systems for companies in Pinellas and Hillsborough counties from our office at 1221 Turner St, STE 206, Clearwater, FL 33756. If you want a straight answer about whether your process is worth protecting, book a free strategy session or call (727) 306-3202.