Customize your ERP without a developer: Studio and App Builder

Customization is the real ERP problem

Standard ERP modules cover the common parts of a business well: customers, invoices, stock, payroll. The trouble starts with the parts that are specific to you. A cleaning company tracks site inspections. A consultancy tracks statements of work and milestones. A distributor has a returns process that no template matches.

When the ERP cannot hold these, they move to a spreadsheet, and the connected record you bought the ERP for develops a gap. The question to ask any vendor is not how many modules it has, but how much of your own process can live inside the system.

Three levels of customization in Agaro

1. Custom fields on existing modules. Many modules, such as Contacts, Leads, Invoices, Products and Orders, let you add your own fields in Studio and shape the list, grid and board views, so the record carries the facts you need.
2. Custom modules. The Module Builder lets you define your own fields and records and deploy the module to your workspace. A module built this way is not a spreadsheet living outside the system.
3. Apps and websites. App Builder creates landing pages, websites, storefronts and internal tools from a conversation. Forms connect to leads, products to the catalog and checkout to Stripe, so there is no second source of truth.

Describe the change, Agaro builds it, you approve it

The working method is short. You describe what you need in plain language, for example "I need to record a site inspection with a checklist, a status and a sign off, linked to the customer and the invoice". Agaro builds it as a module or an app. You review the result and approve it before it goes live.

Approval matters more for customization than for almost anything else, because a change to how the business records its work deserves a second look. The permission model applies here too: the builder works within what the person asking is allowed to do.

What stays governed

A custom module inherits what a built in module has:

• Workspace isolation. Your custom records belong to your workspace, and no other company can reach them.
• Permissions. Roles and access rules apply to the new records in the same way as to the standard ones.
• Record pages. Each record has a page with its fields and its relationships.
• Activity history. Changes to custom records are written to the same activity log as everything else.

That is the difference between a custom module and a spreadsheet. The process is yours, and it is still part of one system with one set of controls.

Which plan includes what

Studio custom modules, AI agents, API and MCP access, single sign on and multiple companies are part of Scale and up. App Builder is included from Essentials, with 3 published projects on Essentials and 10 on Scale. Essentials and Scale include self serve data migration. The pricing page has the full comparison, and prices are monthly in US dollars.

Questions people ask