01 / IN THE FIELD
Use Claude from the laptop or phone already in the workflow.
No new reporting interface. No hunting through ERP screens. The field team asks in plain language.
NOMIDDLE / BUILD / ERP + AI ENABLEMENT
INTERNAL ARCHITECTURE ACCELERATOR · BUILT BY NOMIDDLE
LET EVERY TEAM MEMBER QUERY THE BUSINESS. WITHOUT WAITING FOR A REPORT.
Field sales is one example. Sales, customer service, finance, operations, and purchasing should all be able to ask a business question and get a current, permission-aware answer from SAP HANA and the systems around it—without opening another ticket or requesting another report.
TEAM SELF-SERVICE · FOOD DISTRIBUTIONTHE TEAM EXPERIENCE
Ask the business. Get an answer with sources.
ILLUSTRATIVE TEAM QUERY
Which customer orders are at risk before tomorrow’s visits?
AI
I found 12 accounts with an open exception. These three need attention first:
FreshMart · Order 1048318 cases short · inbound Tuesday at 8:30 AM
Lakeview Markets · Order 87211Credit hold · $42,180 past due
Northstar Foods · Order 62109Route delay · revised ETA 2:15 PM
SAP HANA · Sales OrdersWMS · InventoryTMS · Delivery StatusAR · Aging
Why is FreshMart short, and what can customer service offer instead?
AI
SKU 44018 is short at the assigned warehouse. SKU 44021 is the approved substitute, with 62 cases available and a 0.8-point lower margin.
Answer limited to the user’s approved accounts, locations, and financial access.
LIVE ENTERPRISE USE CASE
A $500M PE-backed food distributor is using it internally.
Field users open Claude and ask questions about customers, orders, inventory, delivery, pricing, and credit. Claude reaches SAP HANA through the governed architecture—so the answer comes from current enterprise data without giving users direct ERP access.
THE USERFIELD TEAM→THE EXPERIENCECLAUDE→THE CONTROL LAYERNOMIDDLE MCP→THE SYSTEM OF RECORDSAP HANA
02 / CURRENT ANSWERS
Query SAP HANA while the customer decision is happening.
Orders, backorders, availability, substitutions, route status, pricing, margin, credit, and receivables.
03 / ENTERPRISE CONTROL
Keep ERP access governed, permission-aware, and auditable.
Claude only reaches approved tools and data. Identity travels with every request and every query is logged.
04 / THE BUSINESS EFFECT
Turn a report request into an immediate customer answer.
Field teams move independently while IT, finance, and the PE-backed operating company retain control.
WHAT THE TEAM CAN ASK
The questions buried inside reports, systems, and handoffs today.
Every answer respects the team member’s existing permissions.FIELD SALES
“Which customer orders are late, short, or at risk before tomorrow’s visits?”
Open orders · fill rate · backorders · delivery exceptionsCUSTOMER SERVICE
“Why was this order short—and what substitute can I offer right now?”
Available-to-promise · substitutions · inbound inventory · warehouse positionFINANCE + AR
“Where is margin leaking, and which accounts are blocked by credit?”
Customer price · product cost · freight · rebates · aging · disputesOPERATIONS + PURCHASING
“What inventory risk will affect tomorrow’s warehouse and routes?”
Inbound supply · warehouse position · demand · route and delivery statusTHE INTERNAL ARCHITECTURE ACCELERATOR
One question in. One governed route to the answer.
NoMiddle built this reusable MCP architecture to accelerate each engagement. It gives every approved AI application the same safe way to query the business.AI + SME APPLICATIONS
Where the work begins.
Claude + AI clientsSME-built Python appsCopilots + internal toolsScheduled jobs
GOVERNED MIDDLE LAYER
MCP SERVER
Tool registryIdentity + contextPolicy enforcementAudit trail
SYSTEMS OF RECORD
Where trust must hold.
SAP HANAWMS + TMSAzure SQLApproved views + procedures
THE INFRASTRUCTURE UNDERNEATH
Azure Container AppsEntra ID + RBACManaged IdentityKey VaultGitHub + CI/CDContainer RegistryAzure MonitorLog Analytics
THE OPERATING MODEL
Teams move faster. IT and finance stay in control.
The point is not to remove IT or accounting from governance. It is to stop making them manually answer the same operational questions. They approve the tools, data, and permissions once; functional teams can then self-serve inside those boundaries.
TODAY
Every answer becomes another request.
- A team member emails IT, finance, or another function
- Someone runs a report or exports a spreadsheet
- The customer or operating decision waits on stale data
- Analysts repeat the same lookup for the next person
WITH THE MCP SERVER
Any approved team member can ask and get a governed answer.
- Only approved business questions are exposed
- Identity and permissions travel with the request
- The answer comes from current systems of record
- Every query and action remains observable and auditable
WHAT THE MIDDLE ENFORCES
The MCP server is the control plane.
01 / APPROVED TOOLS
Expose capabilities, not database access.
AI clients can call named tools against approved HANA views, procedures, and business services. The system of record stays behind the boundary.
02 / IDENTITY + SECRETS
No hardcoded credentials in SME applications.
Entra ID, RBAC, Managed Identity, and Key Vault control who can invoke each tool and what that tool can reach.
03 / READ FIRST
Prove the safe read path before enabling action.
Approved HANA data moves through controlled views and Azure Data Factory into separated QAS and production schemas.
04 / CONTROLLED WRITE-BACK
Write through staging, procedures, and approval.
Round-trip QAS testing, reconciliation, rollback, and full audit protect SAP HANA before any production write is allowed.
PHASE 1 · FIVE WEEKS
Build the governed read path.
MCP server, Azure foundation, application starter kit, CI/CD, QAS/PROD separation, SAP HANA read tools, monitoring, reference deployment, and knowledge transfer.
PHASE 2 · CONTROLLED EXPANSION
Add write-back when the controls are proven.
Staging, DBA-approved procedures, round-trip QAS tests, reconciliation, rollback, audit, and production-readiness signoff.
ERP + AI ENABLEMENT · MCP ARCHITECTURE
Engagements start at $15K/month.
SCOPE AND TERM SET AFTER FIT
MCP server, enterprise tool design, Azure foundation, SAP HANA integration, identity, secrets, CI/CD, QAS, monitoring, production controls, runbooks, and expansion.
GOVERN · CONNECT · SHIP
ONE GOVERNED MIDDLE. EVERY AI APPLICATION.
Send the ERP, the first application, and the system-of-record boundary that cannot be compromised.
robbie@nomiddle.com