ERP•AI

What ERP•AI is

ERP•AI is a platform of ready-made business systems with a builder underneath. The home page is titled "Business Systems & Headless SaaS" and promises "ALL APPS": finance, HR, CRM, ops, support, inventory, projects and more, each described as a complete system you can pick and start using. A separate Low-code App Builder page describes the build side in one line, "Drag & drop UI, database, logic, deployment," and a desktop agent called Proto lets you describe a system in plain words and have it drafted. The site does not state where the company is based.

It is written for teams that run on operational software: finance, operations, supply chain, field service and quality teams, and the IT people who configure systems for them. A founder who wants a landing page or a consumer app will find the catalog pointed at a different reader.

What you build and how

Start from a system, change it, or describe a new one. The catalog is organized by industry and by function. The industry filter lists Manufacturing, Logistics, Healthcare, Retail, Construction, Education, Food & beverage and Professional services. The system cards cover B2B CRM, CRM for SaaS and for automotive dealers, Field Service Management, a quality management system, Food & Beverage ERP, material requirement planning, BOM management, a production dashboard, CPQ systems for industrial automation, aerospace components and retail, subscription billing, commission calculation, and supply chain systems for spare parts, warehousing and 3PL. Each card carries a short feature list. Field Service Management, for example, lists skill-based dispatch, service windows, route planning, technician mobile work, offline synchronization and truck stock, and Subscription Billing lists versioned subscription plans, tiered pricing, usage metering, proration and recurring invoicing.

When a card is not quite what you need, the page says: "Describe the system you need. Proto drafts it in a private workspace." That is the AI side of the product.

Proto. The Low-code App Builder page offers "Start now" and "Download Proto" and says: "Use Proto to configure this system for your business. Review fields, rules and approvals before releasing changes." Proto is a desktop app with downloads for macOS, Windows and Linux. The site says Proto is "Free to install. AI usage is charged separately." In the sign-up panel it is described as "Business apps and the Proto desktop agent."

The builder and its workflow layer. The Low-code App Builder page ties the app builder to process automation under one heading, "Triggers, conditions and approvals, in one system." Its "What's inside" section names 6 parts: triggers (forms, records, schedules and events), conditions (rules, limits and exceptions), approvals (human gates with named approvers), actions (records, documents and integrations), runs (history, retries and stops) and audit (who, what, when and why). A sample handoff runs in 5 steps, Submit, Check policy, Approve, Act and Notify. The capability list adds retry and stop, run history, escalation rules, scheduled jobs, agent steps, form intake, document routing, SLA timers and versioned flows.

That is the evidence for the process-automation reader. Related workflow systems on the same page include a Workflow Automation Engine, an Approval Management System, a Document Management System, a Business Process Modeler, a Form Builder Platform, an E-signature Platform, an RPA Task Manager, Data Entry & Validation and a Citizen Service Portal, each with the same capability bullets.

A worked example. The home page shows a Procure-to-Pay system for Manufacturing ERP: a requisition (PR-0004, SGD 18,720) hits an approval described as a human gate for amounts over 10,000, then a purchase order (PO-2041), then a three-way receive-and-match step, then payment authorized by someone independent. The caption reads "11 roles · 5 required-safe workflows active · audit on every step." It is a good picture of how the product thinks: approvals, an independent payment step and an audit trail come first, screens second.

Agents and the API. The home page splits the offer into a "Human layer" (the apps people use) and an "Agent layer" labeled "API FIRST," where "Every app, action, and workflow addressable by code." It says an agent gets "the same rights as a person," and that one prompt teaches it the stack. The Headless SaaS flow is drawn as a gateway with identity and limits, then a permission check, then the App Builder owning the record. The page shows an example call, POST /api/projects/:id/records, and prices writes at "4,000 writes per $1." There is also a terminal command that installs ERP.AI skills for an agent, and a link to create an API key in the apps settings.

Publishing and hosting. The pages say apps are deployed, since deployment is part of the builder's one-line description, but they do not name web, iOS or Android targets, a custom domain option, a hosting region or a code export route. Those would be questions for the company.

Pricing, status and claims

The pages show 2 price points. Proto is free to install and AI usage is billed separately, and writes through the API are priced at 4,000 per $1. The site has a Pricing link and an Enterprise link in its navigation, but the home and builder pages list no plan names, seat prices or free-plan limits.

Status matters here. The builder page labels the Low-code App Builder "Available now" and "Live," yet it also says "A workspace preview is not available yet" and "Capabilities describe the planned system scope." So read the capability lists as the scope of the system, and confirm in Proto what you can configure today before you commit a project to it.

No compliance certifications, customer counts, template counts or integration counts appear on these pages. The footer links Terms of Service, Privacy Policy, Cookie Policy and a System status page, and the navigation offers a Contact link.

Who it suits and who it does not

ERP•AI suits an operations or finance team that wants a working CRM, procure-to-pay, billing or field-service system on day one and then wants to change fields, rules and approvals, instead of designing everything from empty tables. It suits an IT team that cares about approvals with named approvers, audit trails and an API that agents and other systems can call with the same permissions as a person. And it suits a builder who would rather describe a system to an AI agent and review the draft than start from drag and drop.

It is a weaker fit for a solo founder who wants a public marketing site, a consumer app or a store, since the catalog is business back-office systems. Teams that need published pricing, a stated hosting region or a compliance statement before they shortlist a vendor will have to ask, because the pages above do not answer those. And because the capability descriptions are flagged as planned scope, an evaluation should start with a hands-on test of one system, not a reading of the feature lists.