Case studies

Four current named ERP Access engagements and three published, anonymized ERP forensic engagements with their actual figures.

Updated 14 November 2026. Read this page as markdown, or get the whole file in one document.

This page has two parts. The first covers four current engagements, named with each client's knowledge or previously shown on erp-access.com. The second summarizes three earlier forensic engagements that ERP Access published, anonymized, with their actual figures. Status labels mean exactly what they say: "in development" is not live.

Current engagements

George Urban Advisors

  • Sector: commercial real estate, small-bay industrial parks in California and Utah.
  • Status: in use by George Urban's leasing team.
  • Relationship: George Urban is ERP Access's development partner on this platform. The lease grader was George Urban's idea; ERP Access built it with them.

The problem they brought. Leasing back offices re-key the same deal terms again and again: from the letter of intent (LOI) into the lease, from the lease into the signature package, and from there into the property management system (Yardi or AppFolio). Each hand-off is a chance for a wrong rent, date or escalation to reach an executed lease, and each lease costs back-office hours. George Urban wanted the copy and paste gone without taking their leasing team out of the decisions.

What was built

  • A lease portfolio portal at gu.erp-access.com, with seven working views: Portfolio, Lease Book, Renewals Due, Tenant Intel, Documents, Review, and Grade / Generate, scoped by property.
  • A lease grader and LOI-to-lease pipeline. Claude reads the LOI and lease documents and drafts terms. A refusal-first grading step blocks any value the source documents don't support.
  • A deterministic validation gate with bounded financial parameters: rents, dates and escalations are checked by code before a draft moves forward, and filled documents are re-checked after merge.
  • Protection against bad training data. Logic that keeps unverified or contradictory examples from becoming rules.
  • Access by property, enforced with database row-level security, so each operator sees only the properties they manage.
  • A learning loop. Every exception a reviewer catches is written up as a proposed rule.

How it is checked

  • George Urban's leasing lead approves before anything reaches the system of record.
  • A George Urban operator reviews each software release before it ships.
  • The codebase carries an automated test suite (2,783 tests passing as of October 2026, self-reported) and an evaluation gate.
  • Pull requests run an automated security review.

Stack. Claude and Claude Code; Postgres on Supabase with row-level security; a web application on Vercel.

Designed, not built. The following are on the roadmap and are not live: automatic DocuSign routing and Yardi or AppFolio posting (the output is DocuSign-ready today), QR-code intake, broker inquiry handling, and human-approved self-guided touring. Door automation is deliberately last, and the leasing team stays the decision-maker throughout.

Voyont

  • Sector: lending; UCC filing and lien lifecycle for lenders and debt buyers.
  • Status: in development.

The problem they brought. Lenders and debt buyers carry liens across many states and thousands of counties. Filing, amending, assigning and terminating each one is slow, manual work. Warehouse lenders and their verification agents want proof that every filing was actually recorded. When a loan portfolio changes hands, every lien needs a UCC-3 assignment, and every assignment has to be confirmed.

What ERP Access is building. Voyont files UCC-1 financing statements and UCC-3 amendments, assignments and terminations through state filing connections. ERP Access leads development of the layer that makes this work at portfolio scale:

  • Bulk intake. Secure upload (including SFTP) of a whole portfolio file, parsed record by record.
  • Routing. Each record sent to the right state filing connection.
  • Return path. The as-recorded copy comes back and is stored against the original submission.
  • Submitted-versus-recorded verification. Every recorded filing is compared field by field against what was submitted; any mismatch goes to a person.

Design rule. AI is advisory in Voyont, never authoritative. Code decides what is filed and what matches.

Roadmap, in order. Retrieval and verification of as-recorded filings for a small-business lender whose warehouse lender requires proof of filing; state UCC-1 and UCC-3 submission; bulk UCC-3 assignments for debt buyers acquiring loan portfolios, such as residential solar and home-improvement loans; county fixture filings; collateral monitoring.

Medically Home, now combined with DispatchHealth

  • Sector: healthcare.
  • Status: ongoing.

The problem they brought. When two healthcare companies combine, the finance systems still have to close every month. Medically Home's NetSuite environment needed to stay supported, changed safely and audit-ready through its combination with DispatchHealth.

What ERP Access does. NetSuite Admin-as-a-Service across Medically Home's production and sandbox environments: integrations and file feeds, user and role changes, period-close fixes and release upgrade preparation.

How it is checked. Changes are made and tested in sandbox before production. Protected health information stays in the clinical systems built for it and is not routed through the NetSuite AI connector.

RAPT Therapeutics

  • Sector: biotech.
  • Status: ongoing.

The problem they brought. ERP Access has supported RAPT Therapeutics' NetSuite environment as its admin-as-a-service team. As RAPT plans its move off NetSuite, the question became how to leave without losing the years of financial and payroll history that auditors and the next team will ask for.

What ERP Access does. Keeps NetSuite supported through the transition while extracting and archiving RAPT's NetSuite and NetSuite Payroll data in the format the receiving team asks for, starting with samples they sign off on. Archived totals are tied back to NetSuite before hand-off.

Published forensic engagements (anonymized)

ERP Access published three earlier consulting engagements in the open-source SAP Transaction Forensics repository. Company and individual names were removed; the repository states that financial figures, ticket counts, record counts and category distributions are actual, and that the cases are used with permission. The engagements predate the tool and motivated it.

The method behind all three: structured data tells you what happened; unstructured text (tickets, notes, emails, approvals) tells you why. The gap between them is where waste, control failures and dysfunction hide.

Case 1: Healthcare company, NetSuite license optimization

Metric Value
NetSuite users reviewed 289
Licenses that could be eliminated 69
Annual savings identified $103,896
Return on the engagement 14.4 times
Payback period 0.8 months
Savings category Annual savings
Dormant full-access users (8 users, no login in 90+ days) $46,464
Employee Center licenses still held by departed employees (estimated 53) $31,800
Approval-only users (4, replaceable with a no-cost SuiteFlow workflow) $23,232
Deprecated integrations (estimated 4 of 8) $2,400

The user list showed 289 active users and looked clean. Login timestamps and HR termination dates did not.

Case 2: Diagnostics manufacturer, help-desk forensics during an acquisition

The company had been acquired by a Fortune 500 company. ERP data showed normal operations across 3,992 ERP users and 1,423 inventory items. Analysis of 2,525 help-desk tickets told a different story: 38% of tickets were uncategorized, 257 tickets (about 10%) were access requests largely from the acquirer's domains, inventory staff were questioning mutating item numbers, and manufacturing was creating dummy transactions to work around MRP limits.

Case 3: Connected hardware manufacturer, high-growth ERP forensics

More than 3 million ERP records analyzed alongside ITGC audit findings, including 102,000 sales orders, 97,000 return authorizations and 43,000 vendors. Findings from the external ITGC audit and the text layer included seven users with the Administrator role and a terminated employee still active (a SOX risk), segregation-of-duties violations at both role and user level across 153 active users and 40 roles, credit holds overridden to ship anyway, a 28.6% return (RMA) rate, and 7,610 customer deductions routed through rerouted-approver chains.

ERP Access's own products

  • SaaS Rebuild. Open-source protocol and tooling for auditing a SaaS or ERP tenant you administer, with evidence-cited KEEP, SIMPLIFY, DROP or DEFER verdicts and a data preservation manifest. MIT license.
  • FixMySauna. A parts storefront for Coastal Saunas infrared saunas, operated as the authorized Coastal Saunas parts dealer: a catalog organized by model, a quote builder, and quote requests routed to the parts team.
  • deeptrend. A structured AI-trend feed built for autonomous agents, published as JSON, RSS and llms.txt. Paused since April 2026, as its own README states.