Most business systems were designed for humans clicking through screens. Our ERP Solution was designed for both — a complete operations platform for multi-entity groups covering people, hiring, payroll, invoicing, immigration, fleet, property, IT infrastructure and tasks, with a native machine interface that lets AI assistants query your real data instead of guessing at it.
Ask a normal ERP “which of our staff have documents expiring in the next 60 days, across all three entities?” and you get a report you have to build, export and read. Ask it in the middle of a board call and you get nothing at all.
Groups running several legal entities feel this hardest. Headcount sits in one place, leave in another, vehicles and leases in a spreadsheet, recruiting in an inbox, invoices in an accountant's folder — and the only person who can join it up is whoever built the spreadsheet. Every question becomes a small project.
Then the second problem arrives: the things that hurt aren't reports, they're dates you missed. A visa that lapsed. A road tax renewal. A domain that expired over a weekend. A warranty that ran out three months before the laptop died. None of those live in a dashboard anyone opens on purpose.
Our ERP Solution closes both gaps: one system that genuinely holds all of it, one calendar that surfaces every expiry from every module before it bites, and a machine interface that lets an AI assistant answer from the live records — in plain language, in seconds, with permissions intact.
Our ERP Solution ships with a Model Context Protocol (MCP) surface — a structured, audit-logged interface exposing the operational modules to AI assistants such as Claude. It is not a chat widget sitting on top of your ERP. It is the ERP, addressable by machines. Your assistant doesn't hallucinate an answer about your business: it queries the same records your staff see, through the same permission model, and returns the actual numbers.
“Who is on leave next week, and does that leave any department below two people?” “Which vehicles have insurance expiring before the end of the quarter?” “What’s our lead-to-hire time by intake source this month?” No report builder. No export. An answer.
Every machine call authenticates as a real ERP user and inherits that user’s row-level security and per-module permission flags. There is no service-role back door. Restricted fields stay restricted — salary, passport, national ID and banking data return as [PROTECTED] or [RESTRICTED], never as plain text, unless the calling identity is explicitly cleared for them.
Every tool invocation writes an audit row with the tool name, the arguments and a timestamp. You can see exactly what was asked, by whom, and when — the machine path is no less accountable than the browser path.
23 tools across 12 business domains. All but eight are read-only. Writes are confined to task workflow (5 tools) and equipment records (3 tools), each gated by the same database rules a human manager faces. Your AI can tell you things; it cannot quietly rewrite your payroll, your employee master data or your financial summaries — those domains have no write surface at all.
Bearer-key authentication with constant-time comparison, 120 requests per minute per instance, a 2 MB response ceiling that forces narrow queries instead of full-table dumps, POST-only, and no CORS headers at all — it is a server-to-server interface, so a browser cannot reach it.
Not a starter product with paid add-ons. Every module below is in production today, used daily across a multi-entity group. Fifteen top-level modules, several of which are hubs with their own sub-modules — the Finance hub alone has nine, Equipment & IT has ten — plus the separate self-service portal staff log into.
Every legal entity, office, bank account, director and tax registration in one place.
Read more ↓Full profiles, reporting lines, documents with expiry tracking, onboarding and offboarding workflows.
Read more ↓A complete applicant tracking system: public intake API, triage inbox, recruiter pipelines, interviews, scorecards, offers, funnel analytics.
Read more ↓Requests, approvals, pro-rata entitlements, balances by type, coverage visible before you approve.
Read more ↓One aggregated timeline of every expiry, deadline and milestone from every other module.
Read more ↓Typed asset register, rack elevations, power and cooling budgets, warranties, depreciation, QR audit labels, IT service accounts, credentials, domains.
Read more ↓Offices and staff accommodation, tenancies, occupancy, cost-per-head, inspection history.
Read more ↓Vehicles, drivers, mileage, insurance/MOT/road tax renewals, condition checks, damage costs.
Read more ↓Visa validity and coverage per entity, days-to-expiry, renewal windows surfaced early.
Read more ↓Payroll, invoicing, advances and loans, attendance, bank accounts, crypto wallets, travel costs, FX rates.
Read more ↓Structured reviews plus retention and sales metrics where the role calls for it.
Read more ↓Loans, property, joint ventures, shares, credit lines and guarantees with an append-only event ledger.
Read more ↓Flight bookings per person and period, costs, check-in status, automatic notification fan-out.
Read more ↓Work assignment across internal staff and external vendors, with subtasks, @mentions and a full activity log.
Read more ↓Role assignment, account approval, per-module visibility flags, complete audit trail.
Read more ↓A separate, narrow surface where staff handle their own leave, details and balances.
Read more ↓Sixteen panels, one per entry above. Everything listed is in production, not on a roadmap.
Multi-entity isn't a licence tier in our ERP; it's the shape of the data. Every employee, asset, lease, invoice and task carries the entity it belongs to, so a cross-entity question is a filter rather than a reconciliation exercise.
The employee profile is the join point for eight other modules. Open one person and you see their leave entitlement, their visa status, the room they live in, the laptop they carry, the documents about to expire and the notes colleagues left — without opening eight pages.
Recruiting usually lives in a separate tool that cannot see your open positions, your entity structure, or the employee record the candidate eventually becomes. Here it's the same system: a hire is a conversion, not a re-typing exercise.
The calendar isn't a meeting diary. It's an aggregation of every date-shaped risk in the system, pulled from more than seven sources in parallel and rendered as one month you can actually scan.
This module started as equipment tracking and grew into IT operations, because the same team that has to know who holds which laptop also has to know which rack has power headroom and which domain expires next month.
For a cross-border employer, an expired permit isn't an HR formality — it's an unlawful worker, a fine, and a person who can't come to work tomorrow. This module exists so that never arrives as a surprise.
Groups that lend, hold property, or take positions in other businesses usually track it in the CFO's spreadsheet. This module gives it a record with a history you can't quietly rewrite.
Most task tools assume every assignee has a login. Real operations run on vendors, contractors, landlords, accountants and lawyers. Our ERP Solution models them as first-class assignees.
“Three roles” is where most SME systems stop, and it’s why people end up over-privileged: someone needs one page, so they get admin. Our ERP Solution separates the role from the module list.
A deliberately separate, narrow surface with its own navigation — not the admin interface with things hidden. An employee logging in sees exactly four things, all their own.
A progressive web app. Staff install it from the browser on desktop or phone — no app store, no MDM rollout, no separate mobile build to fall behind. The service worker precaches the app shell so a flaky connection degrades instead of failing, and an in-app banner tells users when a new version is ready and reloads them into it.
The modules people use away from a desk — inspections, asset checks, candidate calls — are laid out for a phone in hand, not scaled down from a table designed for a monitor.
Admin, Manager and Employee, each combined with per-module visibility flags and a separately-gated protected-fields permission. Rules are enforced by row-level security at the data layer, so the same rules apply whether the request comes from a browser, an AI assistant, or a script.
Salary, passport, national ID and banking details are protected independently of general record access, and masked rather than omitted so the interface stays honest about what exists. CVs, documents and uploads live in private storage reached only through short-lived signed URLs.
Network-level IP restriction available for the whole application. Rate limiting on authentication and on the machine interface. Bot defence on every public intake endpoint. Server-side validation on every write. Secret scanning and a blocking dependency-vulnerability gate on every change before it can ship. Error monitoring in production.
Audit logging across modules, append-only event ledgers where history matters, soft deletes where records must survive, and database-written activity logs that the interface cannot skip.
Right-to-erasure that actually removes the person — cascading records, source submissions, uploaded files and the personal data inside audit rows. Scheduled retention purges for recruiting data. Explicit consent capture at the point of collection.
Designed, written and operated by W.W.M. Ai Labs. One engineering team, one codebase, a direct line to the people who wrote it — no reseller layer between you and a fix.
Our ERP Solution was not built as a product first and sold in hope. It was built because a group of companies operating across multiple jurisdictions needed one, and it has run that group's people, hiring, payroll, invoicing, visas, fleet, property and IT day to day since 2025.
It has already survived the only test that matters: being the thing your own operations team complains to when something breaks.
It's also maintained like a product rather than an internal tool. Every change goes through type checking, linting, an automated test suite, a build, a dependency-vulnerability gate, secret scanning and an automated code review before it can reach production — and the test suite gates the production deploy itself, not just the review.
Our ERP Solution is built for small and mid-sized companies that have outgrown spreadsheets but have no appetite for a six-figure enterprise rollout. It scales from a single company to a group of entities without changing product or tier.
Teams past the point where headcount, leave and assets fit in shared files, but nowhere near needing SAP.
Holding structures where the same person, vehicle, lease or invoice touches more than one company.
Where visas, permits and document renewals are an operational risk, not an HR formality.
Organisations hiring continuously from paid traffic, who need to know which campaign produced hires rather than clicks.
Fleets, equipment, racks, leased offices and staff accommodation that need a register, not a folder.
Where which company issues the invoice changes the VAT treatment.
Organisations that want their assistant working from live business records rather than a stale export.
If your whole operation still fits comfortably in one spreadsheet and nobody has ever missed a renewal, you don't need us yet. Tell us anyway; we'll say so.
We map your entities, headcount and the modules you'll actually switch on. Most groups start with three or four, not fifteen.
Entities, staff records, documents, historical leave and asset registers loaded and reconciled with you; equipment types, leave entitlements, holiday calendars, invoice themes and permission flags configured to your structure.
Accounts provisioned by role with per-module flags set, the self-service portal opened to staff, and the MCP interface connected to your AI assistant if you want it.
No. The MCP interface is a distinct capability you can leave switched off entirely. The ERP is a complete system without it.
Only within a deliberately narrow surface: task workflow and equipment records. Employees, payroll, finance, leave, visas, fleet, rentals and hiring have no write path through the machine interface at all — they are read-only by design, not by configuration.
The same way we stop a person seeing them. The machine interface authenticates as an ERP user with its own permission flags, and protected fields are masked unless that identity is explicitly cleared for them. There is no elevated service account behind the interface.
That's the core assumption of the design, not an upgrade path. Entities, staff, assets, invoices, tasks and finances are modelled as a group from the ground up, and every user's entity assignment is enforced at the database.
A real one: public intake API with bot defence, triage inbox, recruiter ownership and pools, interviews, scorecards, offers, open positions with approvals, templated candidate emails, full-funnel and per-campaign analytics, and one-action conversion to an employee record.
No, and it doesn't pretend to. It runs payroll, issues and tracks invoices, and holds employee financial balances and investment positions. It is not a general ledger — it's the operational layer that feeds one.
Consent captured at collection, private storage for personal documents, protected-field gating, full audit trails, a genuine right-to-erasure path that removes files and audit PII as well as records, and automated retention purging for recruiting data.
Yes. It installs as an app from the browser on desktop and mobile, with no app store and no separate mobile build. The field-facing workflows are designed for a phone.
Ask us on the call — the honest answer depends on your entity structure and your regulator, and we'd rather give you the specific one than a marketing one.
Per-seat, with a platform component and an optional machine-interface tier. We'll quote against your actual entity count and headcount on the call.
The team that wrote it. One engineering group, no outsourced tier one.
Thirty minutes, your entity structure on screen, and an honest answer about whether this fits. No slide deck.
