Accessing ERP data since 1998.
ERP Access is a veteran-owned engineering firm in San Carlos, California. In 1998 we put SAP on the internet so a manufacturer could see its sales orders from anywhere. From 2015 we ran NetSuite in the cloud for growing companies. Since 2025 we connect Claude to ERP data through MCP, so people can ask a question in plain English and get an answer that code has checked.
Most of our new work starts with one question: can AI actually do this? George Urban Advisors and Voyont both began that way. Send us yours, and we'll answer plainly, including when the answer is no.
Three eras of ERP access
Read from the bottom up. Each layer is how our clients reached their ERP data at the time, and the older ones kept running after the next arrived. Names with a dot have notes further down the page.
2025 onward: Through Claude and MCP
2015 onward: In the cloud, on NetSuite
1998 onward: Over the internet, on SAP
- NVIDIA
- Juniper Networks
- The Home Depot
- Home Depot Supply
- Microsoft
- QIAGEN
- Dolby Laboratories
- Nike
- Converse
- Goodyear
- Pratt & Whitney
- Pratt & Whitney Canada
- CareFusion
- Intermec
- Computer Associates
- Magma Design Automation
- Arch Chemicals
- JET Tools
- Virco
- Ablestik Laboratories
Company names are trademarks of their owners. A name here records work by our team or our founder, not an endorsement. Engagements before 1998 were at Andersen Consulting and Deloitte Consulting, and some later SAP work ran through partner firms.
How each client reached its data
Four engagements from the three eras, each drawn as the route from a person to the ERP record. Fitbit and Mesa Biotech show the part most systems miss: what sits in free text, help desk tickets, email and timecards.
Virco
Sales orders on a laptop, over the internet
Virco's sales orders lived in SAP at headquarters. We put them on the internet, so people away from the office could look up an order on a laptop in Internet Explorer.
- A laptop running Internet Explorer
- The internet from wherever the person was
- A web layer we built turns the page request into an SAP lookup
- SAP sales orders
Back to the laptop: the order, as a web page.
Fitbit
What the free-text fields knew that the coded fields didn't
In Fitbit's NetSuite years, much of what the business knew sat in free text, such as asset names and transaction references, rather than in the coded fields that reports run on. This is the route we use to bring that text into the open in any legacy ERP export.
The actual problem: when Fitbit moved its open purchase orders to a new international entity in 2015, the reasons behind each order were in memo text, not fields: which MRP run sized it, how far ahead it covered, carton rounding, price changes, and that the quantity was already approved. Every line had to be read and reconciled by hand.
- A legacy ERP export fixed assets, vendors, customers, transactions
- Split into two tracks
- Coded fields: type, class, lifetime, supplier
- Free text: names, descriptions, transaction references
- Code compares the two the text against the field beside it
- A review list each mismatch with its record ID
| In the free text | In the coded field | What code does |
|---|---|---|
| Type: Tooling (12 months) | Lifetime: 24 | Disagree, to a reviewer |
| Transaction: Bill #4471 | Supplier left blank | Supplier found on the bill |
Mesa Biotech
Tickets, email, timecards and the ERP, read together
At Mesa we ran NetSuite support from a Spiceworks help desk, billed our hours against ticket numbers, and extracted the full production database when the engagement ended in 2023. Those are the inputs Claude now reads together: what people asked for, what the work cost, and what the system shows.
The actual problem: not month-end. The help desk opened the week Mesa was acquired, and its real work was getting people into NetSuite and keeping them there under a new parent's controls, plus purchasing, production and inventory fixes in the first months. Consolidation hardly came up, and a large share of the queue was automated mail rather than people.
- Five sources
- NetSuite production data
- Spiceworks help desk tickets
- Timecards and invoices
- Statements of work
- Joined on ticket number and date so each hour and email lands on a request
- Claude reads the text ticket summaries and email
- Code counts and checks every figure traced to a record
- Findings where the request, the cost and the scope disagree
| One source says | Another says | What code does |
|---|---|---|
| Ticket: “Urgent, can’t approve bills” | Ticket priority: Medium | Urgency only in the text |
| Ticket: “New hire needs a role” | Ticket category left blank | Category read from the text |
| Timecard: 3.5 hours on ticket 1042 | SOW: that work isn’t in scope | Hours outside scope, to a reviewer |
Medically Home Group
A question in plain English, answered from live NetSuite records
In September 2025 we set up Oracle's MCP connector for NetSuite on Medically Home's account, signed in through OAuth 2.0 under a NetSuite role. We use it to ask questions of live records.
The actual problem: our first statement of work in 2021 was a 45-day list of fixes: bank and card feeds, bill approvals, expense reports and financial reports. The work that lasted was keeping NetSuite in step with the claims and reimbursement side of the business, and with the controls an audit expects.
- A question in Claude in plain English
- The MCP connector Oracle's, for NetSuite
- OAuth 2.0 sign-in a NetSuite role decides what it can see
- NetSuite records, saved searches, SuiteQL
Back to the person: the answer, with the SuiteQL query that produced it, so anyone can run it again.
Who we're working for now
Four current engagements, and the problem each client brought us. Status means exactly what it says: in development is not live yet.
Voyont
Lending, UCC filingMedically Home
Healthcare, now combined with DispatchHealthRAPT Therapeutics
BiotechEarlier work, on record
What we did, where statements of work and project records let us say it plainly. Most of the SAP years are listed above by name only.
Fitbit
Our founder led business systems as Fitbit's Director of Business Systems. He ran the selection of its next ERP, rolled NetSuite OneWorld out to 27 countries and subsidiaries over 18 months, and shipped more than 50 NetSuite projects while the company tripled in revenue and headcount in 15 months.
Mesa Biotech
We supported the NetSuite implementation alongside the system integrator, then ran administration and support across production and two sandboxes, with a training help desk staffed from California, New Jersey and the Philippines.
Microbiologics
A St. Paul, Minnesota manufacturer with operations in Asia-Pacific, Latin America, Canada and EMEA that chose not to license OneWorld. We deployed NetSuite with locations, custom segments and custom consolidation reporting instead.
Neocis
A maker of robotic dental instruments, buying through Coupa. We resolved the problems in its NetSuite deployment to Taiwan, where stock moved through third-party logistics.
Juniper Networks
We proposed how Juniper's SAP sales organizations should be structured for its Ignition project, which decides the entity each order is booked in.
NVIDIA
SAP implementation work, and later export-compliance consulting on ITAR, deemed exports and access restrictions.
One rule runs through every system we build
It decides what the AI is allowed to do, what code must prove, and who signs off. Read how we apply it day to day.
Claude reads and drafts
Claude reads the documents your team works from, such as leases, LOIs, filings, invoices and email, and drafts the next step in plain language.
Code verifies and calculates
Deterministic code checks every amount, date and business rule. If the source doesn't support a value, the system refuses instead of guessing.
People approve the exceptions
A named reviewer on your team approves anything before it reaches your system of record. The AI never has the last word.
| Term | In the LOI | In the draft | Code check |
|---|---|---|---|
| Base rent | $1.12/sf/mo | $1.12/sf/mo | Matches source |
| Annual increase | 3.0% | 3.0% | Within bounds |
| Lease term | 60 months | 60 months | Matches source |
| Start date | not stated | left blank | Refused, to reviewer |
What we do
Four services. Most clients start with one and add another once the first is running.
Claude systems for operations
Document-to-system pipelines, agents on ERP data, and the tests and review gates that prove them before they go live.
About this serviceClaude for NetSuite
Connect Claude to NetSuite safely, find out what your account actually uses, and move brittle custom scripts into checked logic.
About this serviceNetSuite Admin-as-a-Service
Certified NetSuite engineers who run and change your system month to month, now with Claude in the loop.
About this serviceRetire and replace
Archive NetSuite before you leave it, or replace a SaaS tool with something smaller, backed by evidence of what you actually use.
About this serviceOn site, inside the client's system
That is how our consultants have worked since the SAP years, and it's what the industry now calls forward deployed engineering. What has changed is how much one engineer on site can build, test and hand over with Claude. Our forward deployed engineer program trains people the same way: on real client work, next to a senior engineer.
Veteran-owned
A Service-Disabled Veteran-Owned Small Business, registered in SAM.gov as UEI EG2FYMHACW73, CAGE 10PQ0.
Senior engineers
Certified senior NetSuite engineers, and a forward deployed engineer program that trains on our own client work.
Trained on Claude
We build with Claude and Claude Code every day and train through Anthropic Academy. Certifications are earned by individual engineers, and we name them when they are.
Have a process that runs on copy and paste?
Tell us where your team re-keys data today. We'll tell you plainly whether Claude should do that work, and how we would check it.