WebisoftWebisoft
Prepared for Mike Alvarez · Royal ContainersConfidential

ERP Modernization
& AI Knowledge Capture

A lightweight intelligence layer over your existing ERP, paired with AI-powered knowledge capture. No rip-and-replace. ROI in 60 days.

Royal Containers·Webisoft·May 27, 2026·v1.0

Prepared by Phil Therien, Partner, Webisoft Technologie Inc.

For Michel (Mike) Alvarez, VP Operations — malvarez@royalcontainers.com

Section 01

Executive Summary

Royal Containers operates a high-output corrugated packaging facility with an experienced leadership team and ambitious growth targets. The core challenge is not a lack of internal talent or data — it is extracting value from both in a system that was not designed to scale.

Two constraints are limiting throughput and leadership bandwidth: a 25-year-old custom ERP that cannot be replaced outright but is slowing scheduling, tracking, and operational visibility — and institutional knowledge concentrated in a single individual, creating a bottleneck that affects every downstream decision.

Webisoft proposes a layered, low-risk modernization: an intelligence layer over the existing ERP, paired with AI-powered knowledge capture that encodes operating expertise and makes it queryable. No rip-and-replace. No year-long implementation. Demonstrable ROI within 60 days.

For organizations ready to think longer-term, we have also outlined an optional ERP Modernization Pathway — a structured route toward full platform modernization that would only be evaluated after early phases demonstrate clear ROI and internal stakeholder alignment is in place.

Phase 1 Investment

<$10K

DISCOVERY · 4 WEEKS

Core Build

$40–65K

PHASE 2 · 8–10 WEEKS

Optimization

$20–35K

PHASE 3 · 6–8 WEEKS

First ROI

60 days

NO RIP-AND-REPLACE

Section 02

What We Heard

Our discovery conversation with Mike surfaced three distinct but connected pain points.

The ERP Is a Ceiling, Not a Foundation

The current system can track historical data but cannot prescribe, predict, or automate. Scheduling across three plants takes five people doing work that one person with the right tooling could handle. Customizations are slow and expensive with limited ROI. Business-critical — can't be turned off — but it cannot be the long-term answer either.

Knowledge Lives in One Place

Mike fields the same questions repeatedly: machine tolerances, run sequencing, conformity rules, material constraints. This knowledge sits with him and one other person. Every time a design or estimating team member needs an answer, they call Mike. Not a documentation problem — a structural dependency that limits how fast the organization can move.

Leadership Style Demands Validation, Not Replacement

Mike leads with instinct developed over 32 years. Not looking for a system to override his judgment — wants analytical tools that confirm what he already senses, surface anomalies he might miss, and give his decisions external credibility with leadership. AI as a truth serum, not a manager.

Section 03

Proposed Solution

Two parallel workstreams that can be initiated together or sequenced based on where the ROI case is strongest internally.

AWorkstream A

ERP Intelligence Layer

A lightweight middleware layer that connects to the existing ERP via API or direct database integration and exposes modern capabilities on top — no rip-and-replace.

What we build

  • Scheduling dashboard with automated sequencing based on material availability, machine capacity, and order priority
  • Automated barcode / QR scan validation at dock doors and key production checkpoints, eliminating manual scan errors
  • Waste and downtime tracking module replacing spreadsheets, with real-time exception alerts
  • Reporting layer surfacing the KPIs Mike and his leadership team currently derive manually

Note

Works with your existing ERP maintainer rather than around him — reducing political friction and preserving the business logic already embedded in the system.

BWorkstream B

AI Knowledge Capture System

A queryable knowledge base trained on Royal Containers' operational context: machine specs, run rules, tolerance thresholds, scheduling logic, conformity standards. Design and estimating staff self-serve answers they currently call Mike for.

What we build

  • Structured knowledge intake sessions with Mike and key operators to encode core decision logic
  • Document ingestion from existing manuals, SOPs, and internal guides
  • AI-powered query interface accessible to design and estimating teams via web or Slack
  • Escalation logic that flags novel questions for human review and grows the knowledge base over time

Note

Not replacing Mike's judgment. Replicating the first layer of it — the answers to questions already answered dozens of times — so his time is reserved for decisions that actually require 32 years of experience.

Section 04

Phased Roadmap

Phase 1 is designed to validate the approach with Mike's leadership team before any significant budget commitment. Prototypes prove value quickly — scoped to demonstrate time savings and gather internal feedback, not over-engineer a solution.

1

Phase 1

Discovery & Prototypes

Start here

Scope

Map ERP data model, conduct knowledge intake sessions, build clickable prototypes for scheduling and knowledge query UI

Investment

<$10,000

Timeline

4 weeks

2

Phase 2

Core Build

Scope

ERP integration layer (scheduling + tracking), knowledge base MVP with query interface

Investment

$40,000 – $65,000

Timeline

8–10 weeks

3

Phase 3

Optimization

Scope

Barcode automation, advanced analytics, expanded knowledge base, team training

Investment

$20,000 – $35,000

Timeline

6–8 weeks

Section 05

Optional Track — ERP Modernization Pathway

Optional · Long-horizon

Pending deep discovery and stakeholder alignment

For organizations that reach a point where layered enhancements are no longer sufficient — or where a legacy system's maintainer transitions out — a full platform modernization becomes the logical next step. Webisoft has deep experience implementing Odoo, a fully customizable open-source ERP, as a modern foundation for manufacturing and distribution operations.

This track would only be considered after Phases 1 and 2 are complete and would require:

Dedicated technical discovery engagement

Map existing business logic, data structures, and integration dependencies — full snapshot before any migration work is scoped.

Full IT cooperation

Knowledge transfer from current ERP stakeholders. The modernization can't be done around them — only with them.

Leadership alignment

Agreed timeline, budget envelope, and change-management approach. The strategic call gets made before the technical work begins.

The modernization pathway is not a replacement of what comes before it — it is the destination that Phases 1 and 2 make possible by de-risking the transition, proving ROI, and building organizational readiness over time. Odoo's architecture is designed to absorb the intelligence layer and knowledge base built in earlier phases — nothing is thrown away.

We raise it here not as an immediate recommendation, but because strategic decisions are made earlier than they appear. If this is a direction Royal Containers wants to evaluate, the right time to begin that conversation is after Phase 1 — not after a crisis.

Section 06

Why Webisoft

Five concrete reasons we fit this engagement — not generic credentials.

Integration-first, not rip-and-replace

We build around existing systems. Your ERP's business logic stays intact while we add the capabilities it was never designed to provide.

Legacy ERP + AI experience

Direct experience layering AI and automation on top of legacy ERP environments in manufacturing and industrial contexts.

Short cycles, visible deliverables

Working software within 30 days of kickoff — not a 90-day requirements document. You see real artifacts before you decide what's next.

Senior-led — engineers build their own scope

The engineers who scope the work are the engineers who build it. No bait-and-switch between sales and delivery.

Odoo partner — ready for the modernization journey

Certified Odoo partner. If and when Royal Containers is ready for the full modernization pathway, the partner relationship is already in place — no re-vetting, no new vendor.

Section 07

Next Steps

Following our meeting on Wednesday May 27th, we propose the following immediate path forward:

1

Mike consults with leadership team + IT

Including the current ERP maintainer — assess internal appetite and cooperation.

2

Webisoft prepares initial research

Architecture options and prototype concepts ahead of the next meeting — no commitment required from your side.

3

Joint review call

Align on priority workstream and Phase 1 scope. Phase 1 is low-risk by design.

We are not asking for a commitment at this stage — only the opportunity to show you what the solution looks like before you decide. Phase 1 is low-risk by design.

phil@webisoft.com  ·  webisoft.com

Phil Therien · Partner, Webisoft Technologie Inc.

Confidential — Prepared exclusively for Royal Containers