Skip to content

Strategy

Should your ERP partner build your custom software?

What an ERP partner takes on, what they decline, and how to read the shape of the answer before you brief anyone else.

Computing America. Applications, integrations, data analysis and AI/ML engineering.

Send their reply
3 min readComputing America
A desk phone with its handset lifted, beside a thick binder of implementation documentation.

In short

  • Ask the firm that implemented your ERP before you ask anyone else. If they'll do the work inside the platform you already own, you avoid a second system and a second support relationship.
  • A decline often marks where the platform they specialize in ends. It can also be capacity or price, so ask which. Work on the plant floor, in the yard, on a truck or on a device often sits outside the platform.
  • The signal is the shape of the answer. A scoped quote suggests it's in their lane. A long timeline, a large contingency or a redirection to another partner suggests it isn't.
  • Get the answer in writing, with the reason. A platform limit tells another firm what to quote; a capacity or price decline does not.
  • Whatever gets built afterward needs one owner for each record. Two systems that can both edit the same record will disagree, and the ERP is the natural owner of the records it already holds.

Ask the firm that implemented your ERP first, whoever you later commission, us included. If the work belongs inside the ERP, building it there usually avoids a second system, a second support relationship and an integration to maintain. The cost to check is the upgrade path: customizations may need re-testing and rework at each major version (see the last row of the table below).

A decline often marks where the platform ends. It can also be capacity or price. Ask which.

What an ERP partner builds, and what it declines

ERP partners generally build inside the platform, and their practice is shaped around it: certified consultants, platform-specific tooling, and an upgrade path they're responsible for. In our experience the work partners decline clusters in five places, all outside the platform:

  • The plant floor: machine data, line state, anything with a controller behind it.
  • The yard, a truck or a field crew, where connectivity is intermittent and the interface has to work on a phone in a glove.
  • A device or instrument, where the protocol is the hard part.
  • Hard real-time or high-frequency requirements, where latency is the constraint.
  • Interfaces for people who don't have an ERP license and won't get one: customers, subcontractors, inspectors, drivers.

How to read the answer you get

You may not get a flat no. Read the shape of the response, not its wording.

What you hearWhat it may meanWhat to do
A scoped quote with a timeline and named consultants.It may be inside their lane, and they may want the work.Take it seriously and compare it with any other quote.
A long timeline with a large contingency.It may be at the edge of what they do, and they may be pricing the uncertainty, not the work.Ask which parts they're uncertain about. That list is the scope another firm should quote.
A redirection to another partner, an ISV add-on or a marketplace product.It may be outside the platform, and they may know it.Evaluate what they pointed at (sometimes it's exactly right), and treat it as a likely platform boundary.
An offer to do it as customizations to existing modules.It can be done inside the ERP, but check what happens at the next major upgrade.Ask who re-tests and redoes that work at each version, and whose budget it comes from.
What each kind of answer may mean, and what to do with it.

If the answer is no, keep one owner for each record

Fig. 1
  1. ERP

    Owns customers, parts, orders, financials

    • To Integration · records
  2. Integration

    Keys every record to its ERP id; carries edits back to the ERP

    • To New system · read-only copy or snapshot
  3. New system

    Plant floor, yard, field, devices, outsiders; holds read-only copies

    • To Edit request · a user changes a customer
  4. Edit request

    Applied by the ERP, never to the copy

    • To Integration · carried back to the ERP

Data flows out as copies; an edit made in the new system goes back through the integration to the ERP, so nothing is written to the copy.

SourceThe pattern described in this article; no measured data.

Get the answer in writing before you brief another firm, and put the data rule in the brief: the ERP owns customers, parts, orders and financials. The new system keys to the ERP's ids, may hold read-only copies, and does not edit those records outside the ERP. It owns what only it creates (scans, readings, inspections, photos) and sends it to the ERP as transactions the ERP posts.

Next step

Send us what your ERP partner said.

Forward their reply, or paraphrase it. We will tell you whether that is a scope boundary, a platform boundary or a pricing one, and which of the three changes if you ask differently.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing