Case studies

These are engagement snapshots — categories of real work drawn from the founder’s enterprise career and independent consulting practice. Each one describes a project the way it actually went: the situation, the work, and what changed.

A few ground rules on how we present them:

• Anonymized. No client names. Where a company is described (“a multi-entity manufacturer”), that is the category of business, not a pseudonym you’re meant to decode.
• No invented numbers. Where we cite a figure, it comes from the underlying work record; otherwise we use ranges or plain qualitative outcomes.
• Verifiable background. The employers, roles, and systems behind these projects are listed on the [[Amr Abdel-Motaleb]].

Most of this work was done for manufacturers and distributors, because that’s where the founder’s enterprise career happened. The same patterns — outgrown accounting systems, disconnected data, manual re-keying — show up in construction firms, clinics, professional services, and nonprofits, and the write-ups point out where they carry over.

Engagement snapshots

Automating accounts payable and bank interfaces

Industry: Manufacturing

How supplier invoices and bank files started flowing into the ERP electronically, cutting manual entry for an accounting team.

Outcome: Supplier invoices and bank transactions flowed into the ERP electronically, reducing manual entry and freeing the team for review work instead of data entry.

Consolidated reporting across multiple ERP systems

Industry: Manufacturing

How a multi-entity manufacturer replaced spreadsheet consolidation with a governed platform producing one set of numbers across its ERPs.

Outcome: Corporate accounting produced consolidated results from one governed platform instead of stitching together exports from each ERP.

From Mfg/Pro to QAD Enterprise Edition without losing data

Industry: Manufacturing

How a manufacturer moved from QAD Mfg/Pro to Enterprise Edition with data validated before go-live and finance staff trained on day one.

Outcome: The company moved to a supported ERP version with migrated data validated against the old system and finance users trained before go-live.

Getting shop-floor data into the ERP without paper

Industry: Manufacturing

How shop-floor tracking and barcoding integrated with SyteLine got production data into the ERP as work happened, not days later.

Outcome: Production and labor activity posted to the ERP as work happened instead of being keyed in after the fact, and job costs reflected reality sooner.

One reporting layer over every general ledger

Industry: Manufacturing

How a general ledger data warehouse and dashboards gave a manufacturer one governed reporting layer across multiple ERP systems.

Outcome: Leadership pulled financial results from dashboards backed by one governed dataset instead of waiting on manually assembled spreadsheet packs.

QuickBooks cleanup and inventory tracking for a distributor

Industry: Distribution

How a small distributor cleaned up QuickBooks, added real inventory tracking, and got a month-end close it could trust without a full ERP.

Outcome: The owner closed the books from one system, with inventory counts the team actually trusted.

Sound familiar

If one of these situations reads like your Monday morning, the fastest way to find out whether it applies to your business is a short conversation — no pitch deck, no obligation. Contact us and describe what’s breaking.