How do you replace a fragmented tool stack with one operating platform?
Model the process first, then consolidate. MEGO pulled QuickBooks, CONTPAQi, spreadsheets, RFQs, POs, inventory, warehousing and production scheduling into one operating source of truth with role-based workflows and leadership reporting — without forcing a manufacturing business into a tool that did not match how it actually works.
Alex Scharifker · Senior Product Manager and Systems Architect
Designed and led by Alex Scharifker in his role at MEGO AFEK USA; MEGO is the operating company, not a software vendor.
MEGO Operating Platform
MEGO had fragmented operational workflows across QuickBooks, CONTPAQi, spreadsheets, RFQs, POs, inventory, warehousing, and production scheduling. Teams needed one operating source of truth without forcing the business into a tool that did not match how it actually worked.
How the system is put together
Sources in, deterministic logic in the middle, AI restricted to interpretation.
Data sources
- QuickBooks
- CONTPAQi
- Spreadsheets
- RFQs
- Purchase orders
- Inventory
- Warehousing
- Production scheduling
Layers
- Source consolidation
- Process modeling
- One operating source of truth
- Role-based workflows
- Leadership reporting
Deterministic logic
- Inventory availability
- Raw material requirements
- RFQ and PO status logic
- Production schedule constraints
- Leadership reporting rollups
Where AI is used
- Prototype-led requirement discovery
- Drafting workflow and process documentation
- Accelerated iteration on operational tooling
Decision loop
- Surface operational state
- Route to the accountable team
- Capture the action in-system
- Report to leadership
My role
- Platform architecture
- Process design
- Data consolidation strategy
- Change management
- Stakeholder alignment
- Rollout and training
The architecture case file
Layer-by-layer architecture, deterministic model, AI guardrails, and the decision loop.
A spreadsheet tells you what a load cost. The platform tells you what it really cost, what it sold for, and what was left — on the same record.
Key takeaways
- —One operating system for procurement, inventory, value-added services, invoicing, and settlement.
- —Every dollar traced from vendor cost to invoice margin through a single cost build-up.
- —Cost allocation is deterministic: freight, threading, and assembly land on the unit before margin is calculated.
- —Royalty and commission logic is enforced by the system, not by spreadsheet memory.
Architecture Principle
Cost is allocated before margin is claimed.
- The platform owns the cost build-up end to end.
- Every calculated field traces back to a source record.
- Role-based workflows replace cross-team handoffs and spreadsheets.
Source
RFQs, vendor quotes, and purchase orders are raised in-system with terms and liquidation type set up front.
Receive
Goods land against their PO line: quantities, unit cost, warehouse location, and days on floor.
Allocate
AllocationFreight, threading, and assembly costs are distributed per unit before anything is priced.
Price
Invoice lines are priced against the fully-loaded unit cost pulled straight from the receiving record.
Settle
PayoffPayments are allocated, AR is tracked, and the accounting system syncs from one set of records.
What changed
- One operating source of truth across sales, finance, warehouse, production, and leadership.
- Sales gained direct inventory visibility; production gained raw material planning visibility.
- Leadership moved from manual handoffs to structured reporting and workflow control.
- Change management bridged manufacturing culture and software iteration by embedding in workflows and shipping prototypes.
Follow Me
LinkedInResume
Download PDF
From Chaos to Clarity
Get insights on product management and operations delivered to your inbox.
Subscribe on LinkedIn