ERP & systems · rescue, don’t replace

Your ERP went live. Did it deliver?

Orders still retyped from e-mailed PDFs. A CRM nobody trusts. Reports rebuilt in spreadsheets every Monday. Consultants on the invoice every month. We rescue the ERP you already paid for: read-only first, built around it, never inside it, and owned by your team when we step back.

12 questionsruns in your browserno e-mail asked

Before and after

Where does the work fall between your systems?

Between them, carried by people. Every red line below is someone re-keying, exporting or hunting for something. Switch to after and watch what one connected layer around the ERP does to the same eight systems.

Show the systems

Illustration · a typical manufacturer or distributor

Your systems, before and after

Before · 7 paths people carry by hand

  • Purchase orders arrive as e-mailed PDFs and are re-keyed by hand into the ERP.
  • Reports are exported every week and rebuilt in spreadsheets.
  • The CRM and the ERP are not connected, and nobody owns keeping them in step.
  • The second ERP is merged with the first by hand, in a spreadsheet.
  • Website stock and prices are typed in from the ERP, and drift.
  • Quote requests are priced by searching old e-mails for the last quote.
  • Drawings and models are hunted down by hand for each quote.

After · one connected layer around your ERP

  • Read-only connectors to every system. They can see; they cannot change anything.
  • AI readers turn e-mailed orders and quote requests into proposed lines that a person accepts.
  • One system of record for each field, so price, cost, customer and stock agree everywhere.
  • Validators check every change against the rules your people set.
  • Every connection is checked; a failure is fixed first, and a named owner is alerted when it cannot be.

ERP-01Out of tolerance

Why didn’t our ERP deliver what it promised?

Usually not because the software is bad. Records and workflows were moved half-finished, people fell back on spreadsheets and e-mail, and after go-live nobody owned the gaps.

Sounds like We went live two years ago and we still run half the business out of spreadsheets.

70%+

of recent ERP initiatives will miss their original goals, Gartner predicts

Gartner predicts that by 2027, more than 70% of recently implemented ERP initiatives will not fully meet their original business goals.

What IT Leaders Must Do to Avoid Disappointing ERP Initiatives, read Nov 2026 (opens the source in a new tab)

In Panorama Consulting Group’s 2026 ERP Report (170 organizations surveyed), about 30% of projects ran over budget and about 22% finished late.

Panorama sells ERP consulting · The 2026 ERP Report, Mar 2026 (opens the source in a new tab)

The same Panorama Consulting Group 2026 report is a fair counterweight: 87.3% of the organizations that expected productivity and efficiency gains from their ERP got them.

Panorama sells ERP consulting · The 2026 ERP Report, Mar 2026 (opens the source in a new tab)

An ERP is not a failure by default. The gap is usually what the implementation left undone.

What we do

  1. Connect read-only and scan what the move left behind: duplicate items, broken price ladders, orphaned customers, units that disagree.
  2. Put every open question to the person who can decide it, as a one-minute Decision Card. Their ruling is recorded in their words.
  3. Return each fix as an import file your team loads, and turn each ruling into a check so the problem cannot quietly come back.

Proven at RobbJack · the case study

  • Beginning in July 2026, Michael MacArthur rebuilt how RobbJack runs on SyteLine: around the ERP, not inside it. Nothing was replaced, and the new work added no customizations inside SyteLine.

ERP-02Out of tolerance

Why are we still paying consultants for an ERP we already bought?

Because the knowledge of how it all works lives with them, not with you. Every change becomes a ticket, and every ticket becomes an invoice.

Sounds like We can’t add a field to a report without opening a ticket and waiting two weeks for a bill.

31.4%

of over-budget projects underestimated consulting fees

In Panorama Consulting Group’s 2026 ERP Report, 31.4% of the projects that ran over budget said consulting fees had been underestimated.

Panorama sells ERP consulting · The 2026 ERP Report, Mar 2026 (opens the source in a new tab)

In Panorama Consulting Group’s 2026 ERP Report, the share of organizations seeking outside help with post-implementation and benefits realization rose from 28.3% to 42.1% in a year (among those that sought outside guidance).

Panorama sells ERP consulting · The 2026 ERP Report, Mar 2026 (opens the source in a new tab)

What we do

  1. Build in small, documented pieces your own team can read, change and run.
  2. Write every business rule down with who decided it and when, so the answer to “why does it do that?” is never one person.
  3. Point the alerts at your people. Validators and watchdogs tell your team what broke and what to do, before a customer notices.
  4. If you want senior help on call, the AI Operating Partner is a capped monthly desk, not an open-ended retainer.

Proven at RobbJack · the case study

  • The work was done in-house, without an implementation partner.

ERP-03Out of tolerance

Why doesn’t anyone trust or use our CRM?

Because it doesn’t know what the ERP knows. A CRM without real orders, invoices and open quotes is a contact list reps have to feed by hand.

Sounds like My reps keep their own spreadsheets. The CRM is where leads go to die.

1 in 3

distributors call CRM their most impactful technology

In Industrial Distribution’s 78th Survey of Distributor Operations (2025), more than 1 in 3 distributors named CRM their most impactful technology, against about 10% for AI.

Heightened Complexity (78th Survey of Distributor Operations, part 1), Jun 2025 (opens the source in a new tab)

In a 2024 Gartner survey of 1,026 B2B sellers, 50% were overwhelmed by the technology their job requires, and those sellers were 45% less likely to hit quota.

Gartner Sales Survey (press release), Sep 2024 (opens the source in a new tab)

The U.S. Bureau of Labor Statistics measured median tenure with a current employer at 4.1 years in January 2026 (released September 2026).

Employee Tenure news release, Sep 2026 (opens the source in a new tab)

Every one of those job changes is a contact in your CRM that just went stale.

What we do

  1. Build the CRM on top of the ERP’s own customer records, so orders, invoices, open quotes and ship-tos are simply there.
  2. Route every new lead to the right territory rep automatically, and show who has not followed up.
  3. Scope each rep and distributor to their own accounts, with a reason and a watermark on every export.

Proven at RobbJack · the case study

  • A CRM and lead-management system that sits on top of the ERP’s customer records.
  • 47 Every new website lead is assigned automatically to the right territory sales representative, in 47 states.

ERP-04Out of tolerance

Why does every answer take three systems and a spreadsheet?

Because the data lives in the ERP, the CRM, inboxes, spreadsheets, the website and CAD/CAM, and nothing joins them. People are the integration.

Sounds like To answer one customer question, someone checks the ERP, the CRM, two spreadsheets and their inbox.

55%

of distributors bought the systems but never connected them

According to Distribution Strategy Group’s State of Distributor Technology 2026, 55% of distributors have invested in ERP, CRM, e-commerce and analytics but have not integrated them.

DSG also sells distributor software · State of Distributor Technology 2026, May 2026 (opens the source in a new tab)

What we do

  1. Connect every system read-only and agree one system of record for each field: price, cost, customer, item, stock.
  2. Build the join keys that actually match: customer numbers, part numbers, e-mail domains, drawings to order lines.
  3. Alert the owner the moment two systems disagree, instead of finding out from a customer.

Proven at RobbJack · the case study

  • 76% 76% of sampled distributor order lines link straight to drawings, models and cutting data.

ERP-05Out of tolerance

We run more than one ERP. Do we have to merge them first?

No. A merger is a project for later, if ever. First read both, map the keys between them, and give people one view across both.

Sounds like We bought a company three years ago and still close the month in two systems and a spreadsheet.

3

ERPs or ERP instances at the median finance shared-services organization

APQC’s open benchmarking data (748 companies, read November 2026) puts the median at 3 ERPs or ERP instances across a finance shared-services organization.

Open Standards Benchmarking, measure 105546, read Nov 2026 (opens the source in a new tab)

In a 2025 Gartner survey of 383 finance leaders, 87% of those whose organizations already run an ERP plan to replace or upgrade it within three years.

Gartner Finance Survey Reveals the Top 10 Technologies for Future Investment in Finance, Mar 2025 (opens the source in a new tab)

Before you replace or merge, make sure the data is worth moving.

What we do

  1. Read each ERP read-only, whether it came with an acquisition, runs one division or is the legacy system nobody turned off.
  2. Map items, customers and units of measure across them, and flag the records that mean the same thing under different numbers.
  3. Give people one view that reads both. Plan a consolidation only once the data is clean enough to move.

Live Live read-only connections are proven on two different Infor ERPs: CloudSuite Industrial (SyteLine) and VISUAL.

ERP-06Out of tolerance

Why are we still retyping orders from e-mailed PDFs?

Because orders and quote requests still arrive as e-mails and PDFs, and the ERP can’t read them. People retype them, and some come out wrong.

Sounds like Our best customer-service people spend their mornings copying PDFs into order entry.

1 in 10

sales orders need a correction after entry

APQC’s open benchmarking data (578 companies, read November 2026) has the median company processing 90% of sales orders first time error free, so about 1 in 10 needs a follow-up correction.

Open Standards Benchmarking, measure 110409, read Nov 2026 (opens the source in a new tab)

OWASP’s 2025 list of risks for AI applications ranks prompt injection first, including instructions hidden in documents an AI reads, and lists human approval for high-risk actions among the defenses.

LLM01:2025 Prompt Injection, 2025 (opens the source in a new tab)

That is why a person accepts every line the AI proposes.

What we do

  1. AI reads each e-mailed purchase order or quote request and proposes the order or quote lines, matched to your items and customers.
  2. A person accepts every line. Automated order entry runs under your own account, into your test environment first; your team decides when it goes live.
  3. Each reader is tested on your own past orders before it ships, and again before every change.

Proven at RobbJack · the case study

  • 97% of purchase-order lines read correctly by AI1
  • 0.9% On new quotes, the typical line lands within 0.9% of the quote desk’s hand-done price (the median across 124 quotes).

ERP-07Out of tolerance

Our ERP screens don’t fit how we work. Do we have to customize it?

No. Customizing the core is how upgrades get expensive. Build the screen people need around the ERP, fed by its data.

Sounds like Finding a part means knowing exactly how it was typed. Every new hire learns the workarounds first.

54.9%

of over-budget projects needed extra technology

In Panorama Consulting Group’s 2026 ERP Report, 54.9% of the projects that ran over budget needed additional technology to meet their goals.

Panorama sells ERP consulting · The 2026 ERP Report, Mar 2026 (opens the source in a new tab)

What we do

  1. Build the forms and portals each job needs (a quote builder, a price lookup, an order check) reading the ERP live.
  2. Make search forgiving: case, dashes, spaces and periods never decide whether a part is found.
  3. Send changes back as files your team loads or through your test environment. Nothing inside the ERP is customized, so upgrades stay simple.

Proven at RobbJack · the case study

  • 47 47 search fields were made blind to case and punctuation.

ERP-08Out of tolerance

Why do our reports get rebuilt in spreadsheets every week?

Because nobody trusts the numbers, or the report people need doesn’t exist. So someone exports, fixes and re-keys it every Monday.

Sounds like Every Monday someone exports three reports, fixes them by hand and e-mails a spreadsheet nobody fully believes.

96%

of FP&A teams still plan in spreadsheets

In the Association for Financial Professionals’ 2025 FP&A Benchmarking Survey (362 practitioners), 96% use spreadsheets for planning and 61% say the reliability of their data holds them back.

2025 FP&A Benchmarking Survey (press release), Jan 2025 (opens the source in a new tab)

Panorama Consulting Group’s 2026 ERP Report warns that when nobody owns reporting standards and change requests after go-live, users start building shadow reports.

Panorama sells ERP consulting · The 2026 ERP Report, Mar 2026 (opens the source in a new tab)

What we do

  1. Ground every report in your own data, with every number traceable to the records behind it.
  2. Agree one definition per measure, so sales, finance and operations stop arguing about whose number is right.
  3. Give managers a report builder they use themselves, and checks that flag a bad number before the meeting does.

Proven at RobbJack · the case study

  • A report builder grounded in the company’s own data.

ERP Rescue Scorecard · 12 questions · 6 areas

How far out of tolerance is your ERP?

Answer yes, partly or no. Each area gets a gauge, you get your three most valuable fixes in plain words, and the engagement that fits. It runs in your browser: nothing is sent, nothing is saved, and no e-mail is asked.

0 of 12 answered · runs in your browser · nothing sent

A1 Data you can trust

Do your item, price and customer records agree with each other, with no duplicates or conflicting units and prices?
When a number in a report looks wrong, can someone trace it to the record behind it in minutes, not days?

A2 Manual entry

Do purchase orders that arrive by e-mail reach the ERP without anyone retyping them?
Are quote requests priced from your own history and rules, without hunting through old quotes?

A3 CRM connected to the ERP

Does your CRM show each customer’s real orders, invoices and open quotes from the ERP?
Do your reps use the CRM every week, without keeping their own spreadsheets on the side?

A4 One version of the truth

Is there one agreed system of record for each key field (price, cost, customer, item), even across more than one ERP?
Do your website, quotes and invoices show the same price and stock for the same item?

A5 Forms, reports and workflow

Can your people do their daily work in the ERP’s screens without workarounds outside it?
Do owners and managers get the reports they need without someone rebuilding them in a spreadsheet?

A6 Independence from consultants

Can your own team make a routine change (a field, a report, a price rule) without calling a consultant?
Is how your ERP and its connections work written down, so the business would be fine if one key person left?

Your top fixes

  1. Answer a few questions and your top three fixes appear here, weakest first.

The engagement that fits

Shown once you have answered at least one question.

Talk to Mike about it

How we work · route sheet

Rescue, don’t replace. How does that work?

The same way a part moves through a shop: one operation at a time, each one inspected before the next. Your ERP stays the system of record from the first day to the last.

  1. OP 10Connect read-onlyA read-only login you create and can switch off, or exports. We can see; we cannot change anything.
  2. OP 20Forensic scanEvery item, price, customer and connection checked. Each problem is counted, sized and shown with real example rows.
  3. OP 30Decision CardsEach open question goes to the person with authority as a one-minute card. Their ruling is recorded with who, when and their words.
  4. OP 40Build around the ERPReaders, portals, reports and checks live outside the ERP and read it through its own front doors. Nothing inside it is customized.
  5. OP 50Test first, your people loadNothing reaches production without a test environment and your own people loading it. We read every change back to prove it landed.
  6. OP 60Validators and watchdogsEvery ruling becomes a check that runs on every change. Connections are watched: a failure is fixed first, and a person is alerted when it can’t be.
  7. OP 70Your team owns itDocumented, in your accounts, run by your people. When we step back, nothing stops working and nobody is locked in.

Why the data comes before the AI

Gartner predicts that through 2026, organizations will abandon 60% of AI projects unsupported by AI-ready data (Gartner, February 2025).

Lack of AI-Ready Data Puts AI Projects at Risk, Feb 2025 (opens the source in a new tab)

Works with

Which ERPs do you work with?

Any ERP your people can export from or give us a read-only login to. Here is exactly how each one connects, and where we have live, running connections today.

Live Proven, read-only, running today

Read-only means a login your IT team creates, scoped to what we need, that you can switch off at any time. We can see; we cannot change anything. Changes go back as files your people load.

Read-only first Through their standard APIs or exports

And everything around the ERP

  • Your CRM, or one we build on your ERP’s customer records
  • Shared mailboxes for orders and quote requests
  • Spreadsheets and shared drives
  • Your website and online store
  • CAD/CAM files and tool libraries

All product names are trademarks of their owners. PTAI is not affiliated with or endorsed by any software vendor named here. Infor, CloudSuite and SyteLine are trademarks of their owner. Precision Tolerance AI is not affiliated with or endorsed by Infor.

Proof · a manufacturer, not a slide deck

Has this been done on a real ERP?

Yes. RobbJack is a precision carbide cutting-tool manufacturer that sells through industrial distributors, and Mike MacArthur has been part of the RobbJack team for over thirty years. The results below were measured there; the words beside them are RobbJack’s own, as it approved them.

Proven at RobbJack · the case study

  • 97% of purchase-order lines read correctly by AI1
  • 98% of repeat quotes reproduce the quote desk’s own price ladder2
  • 0.9% On new quotes, the typical line lands within 0.9% of the quote desk’s hand-done price (the median across 124 quotes).
  • −75% quote-engine pricing error5
  • 47 Every new website lead is assigned automatically to the right territory sales representative, in 47 states.
  • 33 33 owner decisions were answered in one morning, each recorded in the decider’s own words.

Beginning in July 2026, Michael MacArthur rebuilt how RobbJack runs on SyteLine: around the ERP, not inside it. Nothing was replaced, and the new work added no customizations inside SyteLine.

  1. 97% of purchase-order lines read correctly by AI. Blind test on 1,395 real purchase orders the AI had never seen: each line it read was graded against what RobbJack’s order desk entered. As of October 2026.
  2. 98% of repeat quotes reproduce the quote desk’s own price ladder. Share of RobbJack’s past repeat quotes where the quote engine produced the same price ladder the quote desk had quoted. As of October 2026.
  3. 20 automated pricing-rule checks run on every change. Count of automated checks on RobbJack’s pricing rules that run every time a price changes. As of October 2026.
  4. 92% of priced SKUs repriced to current material cost, with every SKU accounted for. Share of RobbJack’s priced SKUs whose price was rebuilt on its current material cost. As of October 2026.
  5. −75% quote-engine pricing error. Change in RobbJack’s quote-engine pricing error after the rebuild. As of October 2026.
  6. Measured at RobbJack and published with RobbJack’s written authorization, as percentages and counts only.

Where to start

What does a rescue engagement look like?

Fixed scopes with starting-at prices, written down before work starts. No open-ended retainer: the last step is your team running it.

  1. 01 · Start Data Decision Sprint from $15,000 Thirty days: forensic scan, your rulings on Decision Cards, fixes loaded, checks that keep them fixed. Know your margin by customer, product and line before a buyer or lender asks. Measure first. Thirty days on your real data, and you decide what happens next from what it finds. Talk to Mike about it Details
  2. 02 · Rescue Transformation from $25,000 A twelve-month roadmap, a second project and six months of coaching for the team. When several areas are out: one plan for the whole rescue, delivered in stages, so your team is running it by the end. Talk to Mike about it Details
  3. 03 · Keep it fixed Data Watchdog from $1,950/mo Re-scans your item, price and customer data monthly, includes a monthly AI-readiness score for your catalog, and sends only the new decisions. A monthly re-scan that sends only the new decisions, so the data stays in tolerance. Talk to Mike about it Details
  4. 04 · Instead of a retainer AI Operating Partner from $4,500/mo A senior AI operator on your team: priorities, builds and coaching, capped hours. Senior help on call with capped hours and priorities you set, documented so your team can carry it. Talk to Mike about it Details

Starting-at prices; your fixed price is written down before work starts. All services and prices →

Straight answers

Questions owners ask before an ERP rescue

The same answers are in our security program and client agreement.

Do you replace our ERP?

No. We rescue the one you have. Replacing an ERP is the most expensive answer, and the problems usually move with the data. If a replacement really is the right call, we will say so, and help you get the data ready to move.

Do you write to our ERP?

No. We read, through a read-only login you create and can switch off, or through exports. Every change comes back as an import file your own people review and load, and we read it back to prove it landed. Automated order entry, if you want it, runs under your own account and goes to your test environment first.

Which ERPs do you work with?

Live read-only connections are proven on Infor CloudSuite Industrial (SyteLine), through Infor’s ION API, and on Infor VISUAL, through a read-only database connection. Epicor Kinetic, Prophet 21 and Eclipse, Infor SX.e, NetSuite, Dynamics 365 Business Central, Acumatica, SAP Business One, Global Shop Solutions, JobBOSS, Plex and others connect through their standard APIs or exports, read-only first.

Our implementation partner or consultant is still involved. Do we have to drop them?

No. We work alongside whoever supports your ERP. We stay out of the core they maintain, and everything we build is documented, so they can see it too.

How long does it take?

The usual start is the Data Decision Sprint: thirty days of scan, rulings, fixes your team loads and checks that keep them fixed. A full rescue runs as a Transformation, a twelve-month roadmap. You decide the next step from what the Sprint finds.

Where does our data stay?

In one sealed workspace, for as long as our agreement is in effect, on commercial AI accounts that never train on it and are set to US-only processing. We delete it within 30 days after the agreement ends, or whenever you ask in writing, and send you a signed Certificate of Data Deletion.

Will what you build survive our next ERP upgrade?

That is the point of building around the ERP. Nothing inside the core is customized, so there is no custom code to re-test or re-apply. If an upgrade renames something we read, the connection checks catch it and your team is told.

Do we have to be on SyteLine?

No. SyteLine is where we have the deepest live experience, and the method is the same on any ERP: read-only first, built around it, owned by your team.

Infor CloudSuite IndustrialMore from SyteLine, nothing changed inside itWhat we build around SyteLine without customizing it → Case studyHow a manufacturer rescued a hard ERP migrationThe story, the timeline and the results → Every solutionMargin, rebates, quoting, CRM, channel data, websitesFind yours by the problem you have →

Next step

Start with one read-only look.

Bring the problem that costs you the most hours. Mike reads every message himself, and the first conversation is twenty minutes, no slides.