All insights
GrowBusiness CentralBuying Guide

Build versus buy: customizing Business Central or licensing an industry add-on

When your industry has a gap that the platform does not cover out of the box, you can build the missing piece or license it from a specialist. The right answer depends less on the feature than on the math and the maintenance.

Wired CIOJune 19, 2026
The short version
  • The choice is really one-time build cost versus a recurring license, plus who carries maintenance.
  • A custom build fits genuinely unusual needs; an ISV add-on fits needs that are standard to your industry.
  • Catch-weight is a good example: not native to Business Central, and well-solved by food-industry add-ons.
  • Compare build-plus-maintenance against the license over a realistic five-year horizon before deciding.
Bottom line: Decide each gap on its merits and the math, not on a blanket 'we always build' or 'we always buy.'

Earlier this month, a food distributor scoping a Business Central project ran into a fork in the road. The platform did nearly everything the business needed, purchasing, inventory, and finance, but the one thing it couldn't do sat at the center of how the company made money: the distributor sold a lot of product by weight, and out of the box, the system didn't know how to think in weights.

Most companies adopting an enterprise resource planning (ERP) system, the software that runs finance and operations together, hit a wall like this eventually, where the platform misses the one part that matters most.

A concrete gap: catch-weight

Catch-weight is selling a product by its actual variable weight rather than a fixed unit. One case of chicken isn't exactly the weight of the next, so price and inventory value depend on what each case weighs. Meat, seafood, and produce work this way.

Business Central, Microsoft's ERP for small and mid-sized businesses, doesn't ship with full catch-weight handling. Its flexible units of measure approximate the problem, but the complete experience it doesn't do natively: capturing actual weights at receipt and shipment, valuing inventory on them, and reconciling cases against pounds.

For a food distributor, catch-weight isn't a nice-to-have. It's the math underneath every sale.

So do they build it, or license a food-industry add-on from an independent software vendor (ISV), a specialist that already has it figured out?

The real tradeoff: one-time cost versus recurring license

A more useful framing than "build versus buy" is one-time cost versus recurring cost, plus who carries the maintenance.

Customizing the platform means paying to build the capability once, with no license fee, and getting exactly what you specify. But you own it: Business Central updates regularly, your customization has to keep working through each release, and you've traded a recurring license for a maintenance burden that isn't trivial.

Licensing an ISV add-on means paying a recurring fee to a vendor whose whole business is building and maintaining that capability for your industry. You get functionality proven across many companies like yours and kept current with each release, and you maintain no specialized code, in exchange for the add-on's way of doing things rather than a custom fit.

The cost you can't see on day one

A build has no monthly invoice, which makes it look cheaper than it is. The real price tag is the maintenance you sign up for every time the platform underneath changes, and that bill comes due quietly for years.

How to actually decide

A few questions are worth answering honestly before you spend anything.

  • How standard is your need? If it's close to how your industry works, like catch-weight for food, an ISV has almost certainly solved it better and cheaper than you could. If it's genuinely unusual, a customization may be the only fit.
  • How central is it, and how long will you rely on it? For a capability you'll depend on for a decade, a well-maintained add-on's recurring cost is easily worth it; a narrow, one-off need might be cheaper to build.
  • Who will maintain it? Be honest about whether you've got the capacity to maintain custom code through every platform update. If not, a customization becomes technical debt that breaks at the worst time.
  • What does the math say over time? Compare the build cost plus expected maintenance against the add-on's license over a realistic horizon, like five years.

The mistake we see most is treating this as a philosophy, "we always build" or "we always buy," rather than a per-feature decision with real numbers behind it. Decide each gap on its merits.

Let's talk it through

If you've hit a gap between what Business Central does out of the box and what your industry needs, we're glad to work through the build-versus-buy math on that feature. Our team comes from operations backgrounds, so we push past the philosophy into the real cost, fit, and maintenance, then help you decide. Reach out.

Filed under
Buying Guide
Read more insights
Free strategy session

See where you stand. Then move forward.

Book a free intro call. We'll talk through where you are today and map a strategic plan for growth, protection, automation, and alignment.

A 30-minute discovery call, no obligationA full team of specialists at a fraction of in-house costA clear next step before you spend a dollar
Loading scheduler…