We run ERP
programs.
Client-side.

Foundry is the owner's representative for NetSuite, Dynamics, SAP and POS programs. Your systems integrator builds and configures. We run your side of the table: the plan, the decisions, the data, the testing, and the go-live call.

108 sites taken live in a single program
96% of cutovers right the first time
$240K in disputed change orders clawed back on one rescue
50+ transformation projects across the team
Why client-side The other side is fully staffed

The incentive problem nobody prices in.

An ERP program has two sides. The integrator's side is fully staffed: an engagement lead, solution architects, a bench of consultants, their own PMO. The client's side is usually one IT director doing this for the first time, on top of a day job.

That gap has a price. Every week of drift is billable. Every scope gap comes back as a change order, priced once you can no longer walk away. Status gets written by the people being measured. None of this makes your integrator dishonest. It makes them the other side of a commercial relationship.

The numbers are public: Panorama's annual survey puts 42% of programs over their timeline, and Rand Group prices the recovery of a failed implementation at 150 to 200% of the original budget. Someone who has run this playbook dozens of times has to sit on your side. That is the whole firm.

Work Anonymized. References on request.

Four programs, four different jobs.

Every engagement below was run from the client's side of the table. Full write-ups behind each card: what we walked into, what we did, what it measured.

Engagements Three ways in

Built like we expect to be checked.

If ERP program management is a permanent, multi-phase need for your company, you should hire, not retain us. Our own calculator says so, and we will too.

Method The same discipline on every program

The discipline, week by week.

  • One decision log, jointly maintained. Every open item carries its age in days. Anything older than fourteen days gets named in the weekly, with the person it is waiting on.
  • A one-page weekly, written by us. Plan versus actual, spend versus budget, top three risks with owners. Not the vendor's deck about the vendor's work.
  • Exit gates between phases. Design closes when the gate criteria pass, in writing, whatever the calendar says.
  • UAT from your ugliest real transactions. Returns against closed periods, negative inventory, the order your team says the old system handled weirdly. If round one passes above 95%, the scenarios were too easy.
  • Cutover rehearsed twice, rollback included. The go-live call is made against written criteria.
  • Hypercare with exit criteria, not an end date. Week-three problems should not arrive at new hourly rates.
A printed Foundry weekly program report: phase, scenario pass rates, open defects, aged decisions, spend versus budget, and an amber go-live confidence chip
Exhibit 1The weekly one-pager. Representative week 31.
A program RAID and decision log with owners, age in days, and status chips; two aged decisions highlighted
Exhibit 2The decision log. Age in days, named owners.
Toolkit Free. No form.

We publish our working tools.

These are the spreadsheets and checklists we run programs with, formulas included. If you never hire us, use them anyway.

SOW Red-Flag Scorecard

XLSX · 18 clauses

Eighteen contract clauses that cost money later, as a scored sheet with a verdict. Run your draft SOW through it before signature.

Open the sheet →

Program Health Self-Audit

XLSX · 20 statements

Twenty symptom statements, rated 0 to 2, scored to a red, amber, or green read. Ten minutes, no vendor in the room.

Open the sheet →

The Honest Math

XLSX · live formulas

A budget model with the lines the quote leaves out: backfill, data cleanup, contingency. Plus hire-versus-firm with the empty-seat months priced in. It recommends hiring when hiring wins.

Open the sheet →

Rollout Wave Planner

XLSX · 2 sheets

The sequencing model built on the 108-site program: readiness gates, blackout months, wave logic, live counts. Sanitized, formulas intact.

Open the sheet →

UAT Scenario Pack

XLSX · 40 scenarios

Forty pre-written scenarios that break implementations, with a defect log and pass-rate math. If your integrator's test plan looks nothing like it, that is finding number one.

Open the sheet →

The Failure Library

PDF · 7 cases

Seven nine-figure ERP failures, annotated: what the contract said, what broke, and which red flag would have caught it.

Email for the PDF →

The sheets open view-only. To work in one, use File → Make a copy and it is yours. Or email anmol@foundryme.com and we send the full pack.

Firm Founder-led

Who does the work.

Foundry is led by Anmol Agarwal. Ex-Bain. Behind her, a team that has run 50+ transformation projects across ERP, finance systems, and operations. The delivery bench is senior ERP operators, not analysts learning on your budget.

Founder-led: the person you meet is the person in your steering meeting. We keep the roster small enough for that to stay true, and we take no software commissions and no referral fees from integrators. The only side we are paid by is yours.

Anmol Agarwal
Anmol Agarwal Founder · LinkedIn
Contact Replies from Anmol, usually same day

Send the system, the stage, and what worries you.

Two lines is enough. Which platform, where the program stands, and the thing you would not put in the steering deck.