Talk to Your ERP: Rebuilt from First Principles
Traditional ERPs were designed for factories. We rebuilt ours for service companies — five tightly connected modules, operated through conversation instead of screens.
An AI-native ERP is a business system rebuilt so people operate sales, purchasing, expenses, projects, and accounting through conversation with an agent — not by training on screens.
Mercury Technology Solutions · 14 August 2026 · 8 min read
Live on the channels you already use
Create a sales order for Harbour Advisory — 40 hours of strategy work.
SO-1842 created and linked to Project PRJ-Harbour-Q3. Ready to invoice on milestone.
Raise a PO for the contractor on that project, then tell me if we can invoice.
PO-9031 drafted against PRJ-Harbour-Q3. Delivery is marked complete — invoice is ready.
Definitions
Terms this page uses precisely
- AI-native ERP
- An ERP whose primary interface is conversation. The agent operates the actual business logic of the five modules rather than filling in legacy forms.
- MCP (Model Context Protocol)
- An open protocol that lets any capable AI agent discover and call tools. This ERP is MCP-ready, so agents can operate Sales, Purchase, Expense, Project, and Accounting cleanly.
- OpenClaw
- The agent layer staff already talk to. Complementary Skills run against the five modules, so people create orders, log expenses, and pull numbers in natural language.
The Misfit
Factory software forced onto service work
Traditional ERPs were designed for factories and inventory-heavy businesses. They force service companies into the same mold: endless screens, module sprawl, training sessions that never stick, and teams stuck performing the same repetitive clicks day after day. We decided that was no longer acceptable.
professional services · ERP Software · agent-native infrastructure
Endless screens
Work happens by navigating forms, not by finishing the job.
Module sprawl
Complexity built for edge cases that rarely appear in professional services.
Training that never sticks
Teaching people a user interface is a tax on the business.
Repetitive clicks
The same handoffs, re-keying, and chasing — every single day.
The Surface Area
Five modules. Tight connections. Nothing extra.
We rebuilt our ERP from first principles specifically for service businesses. What remained were the essential loops: winning work, delivering it, buying what is required, tracking costs, invoicing, collecting, and understanding the financial picture.
Sales
Win the work. Quotations and sales orders stay on the same record that later becomes the project and the invoice.
Purchase (PO)
Buy only what delivery requires. Purchase orders sit against the project instead of floating in a separate procurement world.
Expense
Log costs where they belong. Expenses attach to the work, not to a disconnected claims inbox.
Project
Deliver the work with a live link to sales and invoicing — status, readiness, and billing in one loop.
Accounting
See the financial picture without exporting a spreadsheet. Numbers stay current because the other four modules already wrote them.
Project is linked directly to sales and invoicing — so the handoff that usually leaks data simply does not exist.
Why First Principles Changed Everything
What does a service company actually need to run cleanly?
Most of the complexity in conventional systems exists to support edge cases that rarely appear in professional services, agencies, and consulting firms. We stripped those away.
01
Limit the surface area
By keeping only these five modules and making the connections between them explicit — especially Project ↔ Sales/Invoice — we removed the majority of context-switching and duplicate data entry that usually kills productivity.
02
Conversation is the interface
The second principle was even more important: the primary interface should no longer be a screen. Training people on user interfaces is a tax on the business. The new interface is conversation.
MCP-Ready + OpenClaw Skills
The system becomes an agent
The ERP is now fully MCP-ready (Model Context Protocol). Any capable AI agent can discover and call its tools cleanly. We developed and tested complementary Skills for OpenClaw that operate directly against the five modules. These Skills have proven stable in real use. Model Context Protocol
Staff no longer need to learn the ERP interface. They talk to OpenClaw — on the channels people already live in.
This is not a chatbot bolted on top of old forms. The agent operates the actual business logic.
What people now say instead of click
- →Create a sales order
- →Raise a purchase order
- →Log an expense
- →Check project status against invoice readiness
- →Pull accounting numbers
Live on the channels you already use
Create a sales order for Harbour Advisory — 40 hours of strategy work.
SO-1842 created and linked to Project PRJ-Harbour-Q3. Ready to invoice on milestone.
Raise a PO for the contractor on that project, then tell me if we can invoice.
PO-9031 drafted against PRJ-Harbour-Q3. Delivery is marked complete — invoice is ready.
The Revenue Loop
Close the loop without manual work
Matching, chasing, and reporting used to consume hours. The system now runs those loops and brings the result to the people who need it.
Airwallex payment matching
A direct API connection to Airwallex. When a client deposits funds, AI pre-matching runs automatically against outstanding invoices. Staff receive a notification of the match instead of hunting through bank statements and email threads.
29-day multi-channel follow-up
If an invoice remains unpaid beyond 29 days, the system triggers automatic, multi-channel follow-up. Messages can go out via WhatsApp, WeChat, Line, Telegram, or email — whatever channel the client prefers. The tone stays controlled; the chasing does not require a human to remember the calendar.
Daily intelligence, no dashboard
Daily business intelligence reports arrive through OpenClaw without anyone having to open a dashboard or export a spreadsheet. The numbers come to the people who need them.
Built for How Service Firms Make Money
Partners, retainers, and a funnel that does not leak
Two further capabilities address how many service businesses actually make money — and the front of the funnel now uses the same record all the way through.
Partner access and commissions
External or internal partners can work inside the system with the correct visibility and automated commission logic.
Contracts for recurring revenue
Retainers, subscriptions, and multi-period agreements are first-class citizens rather than afterthoughts.
One record from lead to sales order
Lead management now pulls from social and messaging channels directly into the internal CRM. From there the same record flows cleanly into quotation and then into contract or sales order. The handoffs that usually leak information or require re-keying simply disappear.
What Changes in Daily Work
Hours of repetition collapse into a short conversation
The repetitive tasks that used to consume hours are either automated or reduced to a short conversation with the agent. The workflow itself has been redesigned around these realities rather than around the assumptions of 15-year-old ERP architecture.
People spend time on judgment, client work, and decisions. The system handles the rest.
Matching payments
Chasing late invoices
Compiling status reports
Re-entering lead details
Calculating commissions
Keeping a project aligned with its invoices
The Foundation
This is what an AI-native ERP looks like
Built for service companies instead of adapted from manufacturing software. The modules stay focused. The connections stay tight. The interface becomes conversation. And the volume of repetitive work collapses.
Questions
What leaders usually ask
Traditional ERPs were designed for factories and inventory-heavy businesses. Most of their complexity exists to support edge cases that rarely appear in professional services, agencies, and consulting firms. We stripped that away and kept the essential loops: winning work, delivering it, buying what is required, tracking costs, invoicing, collecting, and understanding the financial picture.
Continue
Related pages
ERP Software
The Mercury ERP service page — unified operations for modern businesses.
Agent-Native Infrastructure
Platforms where AI agents are first-class citizens alongside your workforce.
Zero UI
Voice-first and conversational interfaces — the same shift, applied to customers.
Mercury Core
The operating system for human-agent collaboration.
Question the foundation, not another dashboard
If your current system still requires people to be trained on screens before they can do their jobs, it may be time to rebuild from first principles.