A note on the numbers upfront, because I'd rather you catch this than a client does: $239,000 is illustrative. It's a composite built from published benchmarks on manual data-processing costs, applied to a mid-market company on a legacy ERP (SAP, NetSuite, or Dynamics). Not a universal constant. Recalculate it against your own client's headcount and error rates before you quote it out loud. The method's laid out below so you can defend it if someone pushes back.
Everyone's tuning prompts. Almost no one's fixing the handoff ðĪ
Scroll through any AI strategy conversation right now, and it's all prompt engineering, model selection, fine-tuning, which LLM reasons best, which agent framework to standardize on. Easy stuff to obsess over, honestly; it's visible, it's measurable, it's fun to tinker with.
Here's the problem though. None of it matters if the AI's output still has to get manually copied, reformatted, and re-keyed into your ERP by a person at 6 pm reconciling the day's exceptions.
That's the handoff. The unglamorous seam between "the AI figured it out" and "the system of record actually has it." And it's exactly where the money leaks out.
Key Definitions ð§
What's "the handoff"?
The manual step where a person moves AI-generated output into the actual system of record (SAP, NetSuite, Dynamics, whatever it is) because nothing automated does it for them.
What's an exception queue?
The pile of records the system genuinely couldn't resolve on its own and needs a human to look at. Before integration, this is most of the work. After, it's a five-minute review.
What the handoff really costs
The research on manual data processing is remarkably consistent, and none of it flatters the status quo:
Manual data entry runs an average of $15 per document once you count labor, error correction, and turnover. A mid-size accounts payable team processing 5,000 invoices a month is sitting at $75,000 a month before a single mistake even gets fixed.
Human error on manual entry runs 1% for skilled operators, up to 4% for average ones, per field. At 20 fields per invoice, that's 0.2 to 0.8 errors per document. Not a risk. A mathematical certainty at any real volume.
Organizations with 100+ employees spend $430,000 to $850,000 a year on manual document processing once you include the hidden stuff, error remediation at $25 to $150 a mistake, plus staff losing 20 to 40% of their time just searching for, verifying, or fixing document issues.
Poor data quality costs the average org $12.9 million a year, per Gartner. Over a quarter of organizations put their own losses above $5 million annually. ðŽ
None of that's actually an AI problem. It's a plumbing problem. And it's exactly the layer most AI rollouts skip, because a chatbot drafting a nice summary is a much easier demo than a pipeline writing clean, validated data straight into SAP.
Back of the envelope, for a mid-market company running a couple legacy systems with a team still reconciling exceptions by hand: a few FTEs' worth of manual reconciliation, plus error remediation on a modest error rate, plus the opportunity cost of good people doing data entry instead of their actual job, adds up fast into six figures. That's where $239,000 comes from. A realistic annual tax for a specific-sized company, not a number that applies evenly to everyone. Run it against your own client's headcount first.
Why the handoff is expensive to fix, and why most vendors underquote it ðē
Custom AI-to-ERP integration work typically runs $10,000 to $35,000 for one well-scoped integration, which lines up with published benchmarks showing point-to-point ERP integrations (SAP S/4HANA to Salesforce, NetSuite to a custom warehouse system, that kind of thing) landing between $10,000 and $50,000+ depending on complexity.
Two things reliably push that number up if nobody scopes them correctly upfront.
1. Legacy system resistance. SAP, NetSuite, and Dynamics are the three we run into most on the mid-market side, and each one has its own friction. SAP specifically wants a CSRF token on every write operation plus an OAuth 2.0 client-credentials handshake most developers haven't touched before. Discovering and solving that alone typically eats 2 to 4 weeks that never show up in the original estimate. It's a big part of why 40 to 60% cost overruns are the norm, not the exception, on integration projects generally.
2. Data cleaning and compliance overhead. An AI system reads a mangled invoice or a half-structured shipping manifest just fine. Your ERP can't. Every field the AI pulls out has to be validated, mapped to the ERP's schema, and checked against whatever compliance rules govern that record type. That mapping work is where most of the real engineering hours go. Not the AI part.
The contrast is simple, honestly. Today, a person is the API between your AI tools and your ERP. After deep integration, they're not.
What six weeks actually looks like ðĢ
Timelines vary a lot by system. Mid-market NetSuite integrations often go live in 4 to 6 weeks thanks to a more accessible API, multi-system builds across five or six applications typically run 8 to 16 weeks, and heavily customized SAP work can stretch past six months. A 6-week, three-phase engagement is realistic for a single-ERP, well-scoped project, and it's on the efficient end of the range on purpose.
Phase 1 â Discovery & data audit (Weeks 1-2)
Map every system currently in the handoff chain. Audit data quality at the source. Find the specific fields and record types causing the most manual rework.
Deliverable: a scoped integration plan with the real cost drivers named, not guessed at.
Phase 2 â Build & validation logic (Weeks 3-5)
Build the connection points. Write the validation and mapping logic between the AI output and the ERP schema. Handle authentication for whichever legacy system is involved.
Deliverable: a working integration in staging, tested against real historical data.
Phase 3 â Rollout & reliability testing (Week 6)
Move to production. Run parallel reconciliation against the old manual process to confirm accuracy. Hand off a monitoring setup so exceptions get flagged instead of buried.
Deliverable: a live integration plus a documented exception-handling process for the edge cases that still need a human. ðĪ
The next step ð
If your team is still the API between your AI tools and your ERP, that's fixable and scoped. It's not a reason to sit on a bigger AI initiative waiting for someday.
Book an AI Reliability & Security Fit Call, and we'll walk through where your specific handoff is leaking time and money, and whether a direct integration is actually the right next move for you.
cal.com
Thanks for reading this one.
Top comments (0)