Custom ERP work
Changes and new parts for an ERP your company built for itself, plus agents that work in it with or without an API. On-demand ERP modules, each built for one business problem, sit here too.
CadenceWorks is a custom software development company. We build software that does a job your ERP or CRM cannot do on its own, from a new order screen for your sales desk to an AI agent that drafts records for a person to approve. An ERP is the software a company runs its sales, buying, stock and accounts in. A CRM tracks its customers and deals.
Illustration with sample data.
Custom software is built for one company's way of working. A product is one piece of software sold to many companies. A quoting screen that applies your discount rules is custom software. So is the code that moves web shop orders into your ERP.
Most of what we build sits next to an ERP or CRM. It reads and writes their records through an API, the door a system opens for other software. The system you already pay for stays the place where your records live.
We check the two cheaper routes first. Custom software is the right call when both fall short.
Scroll the table sideways to see every column.
| Route | When it fits | What to check first |
|---|---|---|
| Buy a product | A common job that many companies do the same way, such as payroll or email campaigns. | Whether it connects to your ERP, and the license cost per user each year. |
| Extend your ERP | The job lives inside the ERP and the vendor supports the change. Odoo is extended with modules written in Python. NetSuite is extended with SuiteScript. | Whether the change holds up at each upgrade, and whether your plan or edition allows it. |
| Build custom software | The job crosses several systems, no product does it your way, or the ERP is your own build. | Who supports it after launch, and the monthly cost of hosting it. |
Three kinds of work, each tied to the systems you run, with data and cloud work running through all three. Our team has ERP go-lives on SAP, Oracle NetSuite, Odoo, Microsoft Dynamics, ERPNext, Xero, QuickBooks, Sage and custom ERPs. Clients are not named on this site.
Changes and new parts for an ERP your company built for itself, plus agents that work in it with or without an API. On-demand ERP modules, each built for one business problem, sit here too.
Code that moves orders and invoices between your ERP, CRM, web shop and suppliers. It can keep a log of every record it touches.
Agents that read emails and PDFs, such as orders and quote requests, and draft the record for a person to approve. Our team built a multi-agent system for RFQs and RFPs. If plain code does the job, we write plain code.
Our team has done cloud work on AWS, Azure, Google Cloud and private VPS servers, and data work on Salesforce. The platform you pick changes who patches what. AWS calls the split security “of” the cloud against security “in” the cloud.
Scroll the table sideways to see every column.
| Where it runs | Kind of service | What your side looks after | Source |
|---|---|---|---|
| Amazon EC2 | IaaS: rented virtual servers | The operating system, with its updates and security patches, the software on it, and the firewall settings. | AWS, Shared Responsibility Model |
| Amazon S3 or DynamoDB | Managed storage and database | Your data, its encryption options and who has access. AWS runs the operating system and platform. | AWS, Shared Responsibility Model |
| Azure Virtual Machines | IaaS | The virtual machines, operating systems and applications. | Microsoft Learn, shared responsibility |
| Azure App Service, Azure Functions or Azure SQL Database | PaaS: you deploy the app, Microsoft runs the servers | The application's settings, code security and access. Microsoft runs operating systems and runtimes. | Microsoft Learn, shared responsibility |
| Google Compute Engine | IaaS | The bulk of the security work, in Google's words. | Google Cloud, shared responsibility and shared fate |
| Google App Engine, GKE or BigQuery | PaaS | Your data, plus a share of app controls and access. Google takes on more controls than in IaaS. | Google Cloud, shared responsibility and shared fate |
| A private VPS | A virtual server you rent | The same split as the IaaS rows: whoever runs the server patches its operating system. | Follows the IaaS rows above |
Microsoft says that for every kind of cloud service, “you own your data and identities.” Google says customers always stay responsible for their access policies and data.
Microsoft Learn and Google Cloud, read 16 Nov 2026Google lists IaaS as the fit for moving an existing on-premises workload to the cloud as it is. Google calls that lift-and-shift.
Google Cloud, read 16 Nov 2026On Salesforce, software either runs inside your Salesforce org, which is your company's own Salesforce account, or links to it from outside. Our Salesforce AI agents page covers the agent side.
Data work moves records from one system to another. It usually takes one of four forms, and each turns on one decision.
Records copied from an old system into a new one, then checked by counts and totals. The big decision is what to leave behind. How an ERP data migration runs
Orders, customers or stock kept in step between two systems. Each field needs one system that owns it, or the two overwrite each other.
Records copied out of the ERP and CRM into one place for reports. How fresh the numbers must be, once a day or live, sets the design.
An app or database moved from an office server to AWS, Azure or Google Cloud. The decision is whether it moves as it is or gets rebuilt for a managed service.
Four steps, as they usually run. Your team signs off the written spec before the build starts, and each release before it goes live.
Your ERP and CRM versions, the vendor's documents for them, the cloud or server it will run on, and the screens and files your team uses today.
What the software does, what it reads and writes, how each part is tested, and the scope of each release.
The build runs against a sandbox, a copy of your system where tests cannot touch live records. Automated tests can run on every change.
Small releases your team can check. Support after launch can cover fixes and updates when your ERP vendor changes an interface the software uses.
Name the system it has to work with, where it should run and the job it should take on. The first call is free.
Published figures, with the date each was read. They describe the market, not our prices.
The average software project on Clutch costs $132,480, and the usual timeline is about 13 months, from verified client reviews.
Clutch pricing guide, updated 21 Sep 2026, read 15 Nov 2026Most software firms listed on Clutch charge $24 to $49 an hour. The average monthly cost of a project is $10,209.
Clutch pricing guide, read 15 Nov 2026The median US wage for a software developer was $135,980 in May 2025, and $104,300 for a software tester, before benefits and payroll costs. That is the in-house comparison.
US Bureau of Labor Statistics, read 15 Nov 2026Ask any firm, us included, to price the first release on its own, with hosting and support shown as separate monthly lines.
Each ERP sets its own rules for outside software. These three decide how a custom build connects.
That has been Oracle's guidance since release 2026.1. From 2027.1, no new integration can use token-based authentication, the older sign-in method.
Read the NetSuite AI agents pageOdoo's documentation says the external API is not on One App Free or Standard. A key lasts three months at most, so each link has to swap in a new key.
Read Odoo's external API pageWith approval rules on, an order sent in through the Service Layer, SAP's API, becomes a draft. Feature package 2608 added an MCP server, a standard bridge for AI agents.
Read the SAP Business One noteIt builds and supports software made for one client's way of working, instead of selling one product to many companies. Our work sits next to the ERP and CRM. We change custom ERPs and extend products such as Odoo and NetSuite. We write code that moves records between systems, and AI agents that read documents and draft records. It runs on AWS, Azure, Google Cloud, a private VPS or inside Salesforce.
The paid work of planning, building, testing, releasing and supporting software for a client. Some firms sell one part, such as testing. Ours covers four kinds of work: custom ERP work, links between systems, AI agents, and data and cloud work. Support after launch is sold as well, and each contract sets what it covers.
The stages software goes through from idea to daily use and upkeep: plan, design, build, test, release and support. Firms name the stages in their own way. Ours usually runs in four steps: read what you run, write the spec, build on a copy of your system, then release in small parts. A release is one tested batch of changes that goes live together.
A minimum viable product: the smallest first release that does the core job for real users. In ERP work, an MVP might be one quoting screen or one link that moves web shop orders into the ERP. People use it every day before anything else gets built. That shows whether the idea works before the larger spend.
Here are three from ERP work. A quoting screen applies your own discount rules and saves the quote in NetSuite. A link moves web shop orders into Odoo with the right tax codes. An agent reads a supplier's PDF price list and updates item costs for a person to approve. Each one does a job that no product on the shelf does your way.
The average software project reviewed on Clutch cost $132,480, and the usual timeline was about 13 months (pricing guide updated 21 September 2026). The average monthly cost was $10,209. Clutch is a review site for service firms, and most firms listed there charge $24 to $49 an hour. The range is wide because one link and a whole system are both called custom software. Ask any firm, us included, to price the first release on its own.
Only when no product does the job your way. A product shares its cost across many buyers, and its vendor keeps it updated. Payroll and email campaigns are good examples, so buy those and compare the license cost per user each year. Custom software costs more at the start and needs support of its own. Choose it when the job follows rules only your company uses.
Extend the ERP when the job lives inside it and the vendor supports the change. Odoo's server code is written in Python and is extended with modules. NetSuite is extended with SuiteScript. Build separately when the job crosses several systems, or when a change inside the ERP would need rework at every upgrade. We usually check both routes before we recommend either.
Usually the one you already run. Our team has done cloud work on AWS, Azure, Google Cloud and private VPS servers, and data work on Salesforce. The choice changes who patches what. On an Amazon EC2 server or an Azure virtual machine, your side patches the operating system. On managed services such as Azure Functions or Google's App Engine, the provider runs more of the stack. In every case, your data and your user access stay your job.
Yes. Our team's go-lives include custom ERPs. Without an API, the software can work through the database on a login of its own. PostgreSQL ships a read-only role, pg_read_all_data, and its row security limits which rows a login can read or change. SQL Server has a fixed read-only role, db_datareader. We agree the route with your IT team.
Yes, when the job needs AI. Our team built a system of several AI agents that handles RFQs and RFPs end to end, and AI agents in Salesforce and HubSpot. The common case is an agent that reads an email or a PDF and drafts the record in your ERP for a person to approve. If plain code does the job, we write plain code.
Ask four things. First, how the software reaches your ERP, and what happens when the vendor changes that route. Second, how each part is tested, and on what copy of your system. Third, how your team signs off each release. Fourth, who supports it after launch, with hosting and support priced as separate monthly lines.
It depends on how long the work lasts. The median US wage for a software developer was $135,980 in May 2025, before benefits and payroll costs, says the US Bureau of Labor Statistics. For a software tester it was $104,300. The average software project reviewed on Clutch cost $132,480. So one project and one year of one developer's pay cost about the same. The answer turns on whether the work keeps going after launch.
The contract for each project sets it.
Ongoing support is a service we sell. It can cover fixes, small changes, and updates when your ERP vendor changes an interface the software uses. Odoo, for example, plans to remove the rest of its older XML-RPC and JSON-RPC interfaces in Odoo 22, in fall 2028. What support covers, and for how long, is set in each contract.
Every source behind a figure or a vendor fact on this page, with the day we read it.