Skip to content

[ SYS: TALK_TO_ERP // STATUS: CONVERSATION ]

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.

Mercury Technology Solutions · 14 August 2026 · 8 min read

OpenClawLive on the channels you already use
  1. You: Create a sales order for Harbour Advisory — 40 hours of strategy work.

  2. OpenClaw: SO-1842 created and linked to Project PRJ-Harbour-Q3. Ready to invoice on milestone.

  3. You: Raise a PO for the contractor on that project, then tell me if we can invoice.

  4. OpenClaw: PO-9031 drafted against PRJ-Harbour-Q3. Delivery is marked complete — invoice is ready.

Definitions

Terms this page uses precisely

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.

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.

01

Endless screens

Work happens by navigating forms, not by finishing the job.

02

Module sprawl

Complexity built for edge cases that rarely appear in professional services.

03

Training that never sticks

Teaching people a user interface is a tax on the business.

04

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.

01

Sales

Win the work. Quotations and sales orders stay on the same record that later becomes the project and the invoice.

02

Purchase (PO)

Buy only what delivery requires. Purchase orders sit against the project instead of floating in a separate procurement world.

03

Expense

Log costs where they belong. Expenses attach to the work, not to a disconnected claims inbox.

04

Project

Deliver the work with a live link to sales and invoicing — status, readiness, and billing in one loop.

05

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.

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.

Create a sales orderRaise a purchase orderLog an expenseCheck project status against invoice readinessPull accounting numbers
OpenClawLive on the channels you already use
  1. You: Create a sales order for Harbour Advisory — 40 hours of strategy work.

  2. OpenClaw: SO-1842 created and linked to Project PRJ-Harbour-Q3. Ready to invoice on milestone.

  3. You: Raise a PO for the contractor on that project, then tell me if we can invoice.

  4. OpenClaw: 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.

01

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.

02

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.

03

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.

01

Partner access and commissions

External or internal partners can work inside the system with the correct visibility and automated commission logic.

02

Contracts for recurring revenue

Retainers, subscriptions, and multi-period agreements are first-class citizens rather than afterthoughts.

One record from lead to sales orderLead 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 paymentsChasing late invoicesCompiling status reportsRe-entering lead detailsCalculating commissionsKeeping a project aligned with its invoices

The Foundation

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.

Questions

What leaders usually ask

Why rebuild from first principles instead of adapting a manufacturing ERP?
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.
Which five modules does the system include?
Sales, Purchase (PO), Expense, Project, and Accounting. Project is linked directly to sales and invoicing so teams do not re-enter data or lose context between delivery and billing.
What does MCP-ready mean in practice?
The ERP implements Model Context Protocol, so any capable AI agent can discover and call its tools cleanly. Complementary OpenClaw Skills operate directly against the five modules. Staff talk to OpenClaw on the channels they already use — the agent runs the actual business logic, not a chatbot sitting on top of old forms.
How does payment matching and late-invoice follow-up work?
A direct Airwallex API connection runs AI pre-matching when a client deposits funds against outstanding invoices. Staff are notified of the match. If an invoice remains unpaid beyond 29 days, the system triggers automatic follow-up on WhatsApp, WeChat, Line, Telegram, or email — whichever channel the client prefers.
Do teams still need to be trained on the ERP interface?
No. Training people on user interfaces is a tax on the business. Staff create sales orders, raise purchase orders, log expenses, check project-to-invoice readiness, and pull accounting numbers through natural language. If your current system still requires people to be trained on screens before they can do their jobs, it may be time to question the foundation rather than add another dashboard.
What is an AI-native ERP?
An AI-native ERP is a system whose primary interface is conversation. Mercury rebuilt ERP from first principles for service companies — five modules (Sales, Purchase, Expense, Project, Accounting) operated through OpenClaw and MCP, not through a screen-first UI.
Is this ERP for manufacturing or for service companies?
It is built for service businesses — professional services, agencies, and consulting firms. Manufacturing and inventory-heavy edge cases were deliberately removed so the system stays focused on winning work, delivering it, buying what is required, tracking costs, invoicing, collecting, and understanding the financial picture.
What is OpenClaw and how does it relate to the ERP?
OpenClaw is the agent staff talk to. Mercury developed and tested complementary Skills that operate directly against the five ERP modules. Staff no longer learn the ERP interface; they create sales orders, raise purchase orders, log expenses, check invoice readiness, and pull accounting numbers through natural language on the channels they already use.