RFQ and RFP automation
A system of several AI agents that handles RFQs (requests for a quote) and RFPs (requests for a proposal) end to end, on both sides. RFQ and RFP automation
An ERP is the software a company runs its sales, buying, stock and accounts in. A custom ERP is one shaped around how your company works. Our custom ERP software development starts small: an on-demand module built for one business problem and added to the ERP you already run. We also extend ERPs companies built for themselves, or build one on an open-source base such as ERPNext or Odoo Community. Our team's go-lives include custom ERPs.
Illustration with sample data.
A custom ERP is the system that runs your orders and accounts, shaped around how your company works. Custom ERP software development is the work of building one, or of adding to one you already own.
Clockwise Software, a firm that builds custom ERPs, says the cost gap between projects rarely comes from the number of screens. It comes from the business rules, the links to other systems and the data behind them. So we write the workflows down before anyone picks a base.
The answer can be smaller than a new ERP. One module, added to the system you run, can close the gap. We call that an on-demand ERP module.
A module reads and writes the ERP's own records, so nobody keeps a second system and nothing is replaced. Four kinds of problem suit one.
A quote priced by your own rules, such as a price per cut length or a discount tied to a customer's order history.
A step the ERP has no place for, such as a supplier sample approval or an inspection on returned goods.
Supplier PDFs, customer RFQs or emailed orders read into draft records for a person to check.
An old warehouse tool or a supplier portal that no ready-made connector reaches.
Each ERP has its own way to add a module. The rules below come from each vendor's documents.
Scroll the table sideways to see every column.
| ERP | How a module is built | What to check first |
|---|---|---|
| Odoo | A custom module in Python, Odoo's server language. | Hosting: Odoo Online takes no custom modules, so it runs on Odoo.sh or your own servers. Each module needs updating for every major Odoo version. |
| NetSuite | SuiteScript 2.1 scripts and custom fields, moved between accounts with SDF, Oracle's tool that deploys from files. | NetSuite upgrades every account twice a year, so each script needs a test before each upgrade. |
| Microsoft Dynamics 365 Business Central | An extension written in AL and compiled as an .app package. | Extensions add to Microsoft's objects instead of changing them. Microsoft's own example adds two fields to the item table with a table extension. |
| ERPNext | A Frappe app, made with the bench new-app command and installed beside ERPNext. | Which standard steps the app changes. A Frappe app changes them through a file called hooks.py, which Frappe says extends or intercepts standard behavior. |
| SAP Business One | A service beside SAP that reads and writes through the Service Layer, SAP's API. | With approvals on, an order sent in through the Service Layer is saved as a draft, with error -2028. |
| A custom ERP | A new module in the ERP's own code, or a small service beside it. | Who can reach the code or the database. If there is no API, see the four routes further down this page. |
Each of these four tools changes forms or approvals without code. Try them first, because code costs more to keep running. Odoo's own guide puts the upkeep of custom code at about 25% of its build cost each year.
Adds fields, screens, automation rules and approval rules without code. It needs Odoo's Custom plan.
Adds custom fields to a form and changes the properties of standard fields, from the screen.
NetSuite's workflow tool. Oracle's own example sends a sales rep's estimate through approval, as a set of states the record moves through.
Works in the client. It adds and moves fields on a page, and shows a preview of the change.
Our ERP customization services usually start with these tools. A module is for logic they cannot hold: a calculation across many records, a link to another system, or a document read by an AI agent.
Five stages, as they usually run. Your team signs off each stage before the next one starts.
We look at them in this order, because the later routes usually cost more. The published ranges overlap, so the order is a rule of thumb, not a price list.
Scroll the table sideways to see every column.
| Route | When it fits | What to check first | Published range |
|---|---|---|---|
| Extend the ERP you have Check first | The system works and your team knows it. What is missing is a module, a report or an API. | Who still knows the code and the database, and whether any tests exist. | We found no published range for adding to a home-built ERP. Ask for the new module to be priced on its own. |
| Build on an open-source ERP | Most of your modules are standard, such as accounting and stock, and a few workflows are your own. ERPNext and Odoo Community are two such bases. | The license: GPL-3.0 for ERPNext, LGPL version 3 for Odoo Community. And how your changes survive each upgrade. | $50,000 to $250,000 or more, Clockwise Software's range for customizing an off-the-shelf ERP. |
| Build from scratch | No package fits the core workflow, or the ERP is part of what you sell. | Who looks after it for as long as you run it, and the cost of rebuilding standard parts such as the ledger. | $100,000 to $150,000 for a first version with one core workflow, per Clockwise Software. |
An AI agent is software that does a task on its own, such as drafting an order. Four things decide whether it works well in your ERP. A build can include each one from the first module; what it includes is agreed per project.
The agent reads and writes through it. ERPNext's framework, Frappe, makes a REST API for every record type out of the box. Ask it for a record type and it lists the first 20 records. A build from scratch needs its API written.
The agent signs in as itself, with only the rights its job needs, rather than as an administrator. Frappe logs each request made with an API key against one user and checks that user's roles.
The agent saves a draft order or bill. A person approves it before it counts.
Each change records the old value and who made the change: a person or the agent.
An AI agent needs a way to read and write records. Without an API there are four routes in, and each one stops somewhere. We add a small API first when we can reach the ERP's code or its database.
Scroll the table sideways to see every column.
| Route in | How it works | Where it stops |
|---|---|---|
| Add a small API Our first choice | A thin service on top of the ERP for the few records the agent needs, with your rules checked in code. | Needs access to the ERP's code or its database, and someone to keep it up. |
| A read-only database login | The agent reads tables directly. PostgreSQL's pg_read_all_data role reads all data and still obeys row-level security, the rules that limit which rows a login can see. SQL Server's db_datareader role reads all user tables and views. | Reading only. Writing straight to tables can skip the checks the ERP's own screens make. |
| Screen automation | Software works the ERP's screens the way a person does. | Breaks when a screen changes, and runs slower than an API. |
| File exchange | The agent prepares a file the ERP already imports, such as a CSV of orders. | Runs in batches, and only covers what the import accepts. |
On 14 November 2026 we asked four AI assistants who can build an agent on a custom ERP with no API. They agreed on no firm. Claude and Gemini named no service firm, and ChatGPT and Perplexity named five each, with none in common. Read the full measurement.
Our team has ERP go-lives on custom ERPs, SAP, Oracle NetSuite, Odoo, Microsoft Dynamics, ERPNext, Xero, QuickBooks and Sage, and builds the on-demand modules this page describes. Clients are not named on this site.
A system of several AI agents that handles RFQs (requests for a quote) and RFPs (requests for a proposal) end to end, on both sides. RFQ and RFP automation
Bills and receipts drafted as entries for finance to approve. Emailed orders drafted as sales orders, and purchase orders drafted the same way. AI agent development
Cloud work on AWS, Azure, Google Cloud and private VPS servers, and data work on Salesforce. A custom ERP needs a server to run on and its old records moved in. Custom software development
Published ranges from two firms that build custom ERPs, with the date each firm published them. We read both articles on 15 November 2026. They describe the market, not our prices.
Scroll the table sideways to see every column.
| Scope | Published range | Source |
|---|---|---|
| One module, such as inventory | $30,000 to $80,000 | RaftLabs, 4 Sep 2025 |
| Customizing an off-the-shelf ERP | $50,000 to $250,000 or more | Clockwise Software, 7 Aug 2026 |
| First version, one core workflow | $100,000 to $150,000 | Clockwise Software, 7 Aug 2026 |
| Several modules, 3 to 10 links to other systems | $150,000 to $500,000 | Clockwise Software, 7 Aug 2026 |
| Large enterprise system | $500,000 to $1 million or more | Clockwise Software, 7 Aug 2026 |
A first version usually takes 6 to 12 months. A larger system with several modules takes 12 to 24 months.
Clockwise Software, 7 Aug 2026, read 15 Nov 2026Maintenance runs 15 to 25 percent of the build cost each year, plus hosting that grows with use.
Clockwise Software, 7 Aug 2026, read 15 Nov 2026The two firms count different scopes, so their ranges overlap without matching. Ask for the first module to be priced alone, with maintenance shown as a yearly line.
Say what it is built on and the job you want a module to do. The first call is free.
It is building or changing the system that runs your orders and accounts so it fits how your company works. The other way round is changing your work to fit a packaged ERP. It can mean a new module for an ERP you already own, an ERP built on an open-source base, or a new system written from scratch.
A module built for one business problem and added to the ERP you already run. It might price a quote with your own rules, add a step your ERP has no screen for, or read supplier documents into draft records. It reads and writes the ERP's own records, so nobody keeps a second system. Our team builds these modules.
Yes. A single module is the smaller job. RaftLabs, a firm that builds custom ERPs, puts one module such as inventory at $30,000 to $80,000. Clockwise Software, another builder, puts the first version of a whole new ERP at $100,000 to $150,000. These are their figures for their scopes, not our prices. What a module includes is agreed per project.
When the gap is a field, a screen, an approval or a report. Odoo Studio adds fields, screens, automation rules and approval rules without code. ERPNext's Customize Form adds custom fields and changes standard ones from the screen. NetSuite builds approval steps in SuiteFlow. Business Central's Designer adds and moves fields in the client. A module is for logic those tools cannot hold.
Start with the work, not the screens. Write down each workflow, the records it touches and who approves what. Then choose the base: extend what you have, build on ERPNext or Odoo Community, or start fresh. Build one module first, with its API, its tests and its data moved over. Add the next module once people use the first one every day.
From $30,000 for one module to $1 million or more for a large system. Clockwise Software, a firm that builds custom ERPs, puts a first version with one core workflow at $100,000 to $150,000, and a system with several modules at $150,000 to $500,000 (article of 7 August 2026). RaftLabs, another builder, gives $30,000 to $80,000 for a single module such as inventory. These are their figures for their scopes, not our prices.
About 6 to 12 months for a first version, says Clockwise Software. A larger system with several modules takes 12 to 24 months. Clockwise says the date depends on the number of modules, the links to other systems and how much is customized.
About 15 to 25 percent of the build cost each year, says Clockwise Software, plus hosting that grows with use. For custom Odoo modules, Odoo's own guide puts upkeep at about 25% of the build cost a year. Ask for maintenance as its own yearly line in any quote, ours included.
Start from an open-source ERP when most of your modules are standard, such as accounting and stock, and only a few workflows are your own. Build from scratch when no package fits your core workflow. Clockwise Software prices customizing an off-the-shelf ERP at $50,000 to $250,000 or more. Its range for a new system with several modules is $150,000 to $500,000.
ERPNext is published under the GPL-3.0 license on its GitHub page. Odoo's license page says Odoo 19 Community Edition is licensed under LGPL version 3, and Enterprise Edition under Odoo's own license. Read the license with your lawyer before you build a product on either.
Yes. Our team's go-lives include custom ERPs. First we find out who still knows the code and the database, and whether any tests exist. Then we add what is missing, such as a module, a report or an API, usually without rewriting what already works. Ask for the new module to be priced on its own.
Yes, by one of four routes. Add a small API to the ERP, give the agent a read-only database login, have software work the ERP's screens, or swap files the ERP already imports and exports. On PostgreSQL, the pg_read_all_data role reads every table and still obeys row-level security. On SQL Server, the db_datareader role reads all user tables and views.
Yes. ERPNext is among the ERPs our team has taken live. Frappe, the framework under ERPNext, gives every record type a REST API out of the box, and it checks each request against one user's roles. New features go in a Frappe app of their own, made with the bench new-app command. We are not a Frappe partner.
A custom ERP is one kind of custom software: the kind that holds your orders and your accounts. Custom software also covers smaller tools, such as a quoting screen or a link between two systems. Our custom software development page covers those.
Not in Odoo's plans, which are the ones we read for this page. Odoo 20 adds AI agents that create and update records inside Odoo. It also lets outside AI agents connect to the database through an MCP server, a standard bridge between AI apps and other software. In both cases the records still live in the ERP and the AI works on them.
Every source behind a figure or a vendor fact on this page, with the day we read it. Our own measurement of AI assistant answers is written up in our research note.