Custom ERP or a NetSuite partner? How Philippine SMEs can compare
The short answer
A NetSuite partner sets up and configures Oracle’s software, which you then subscribe to every year, usually per user. A custom ERP is software built around your own processes, which you own outright and pay to maintain. The partner route spreads cost over time and gives you a widely known platform. The custom route puts more cost upfront and fits the way you already work.
Neither is automatically cheaper. Compare the total cost over three years, how much your process would have to change, who owns the code and data, and what your BIR registration needs.
What you are actually buying in each case
With a NetSuite partner, you pay the partner an implementation fee to configure the software, migrate your data and train your team. Separately, you subscribe to NetSuite itself, which is licensed by Oracle as a recurring subscription made up of a base platform, user seats and any extra modules. If you stop paying the subscription, you stop using the system.
With a custom build, you pay for the design and development of a system around your workflows. If the contract is written properly, the code and data are yours and the system runs on hosting in your own name. You then pay for maintenance and changes, either as needed or on a monthly retainer.
Compare the three-year cost, not the first invoice
The first quote is the number everyone compares, and it is the least useful one. Ask every vendor to fill in the same lines so you can add them up over three years.
| Cost line | NetSuite partner | Custom build |
|---|---|---|
| Upfront | Implementation and configuration fee | Design and build fee |
| Every year | Software subscription: base, users, modules | Hosting in your own account |
| When you hire | Additional user licenses | Usually nothing per user |
| Changes and support | Partner support plan or hourly work | Maintenance retainer or hourly work |
| Leaving | Export your data; the system stays with Oracle | You keep the code and data |
Ask for the subscription quote in writing next to the implementation quote, and ask how both change when you add users.
When NetSuite or another packaged ERP is the better choice
- Your processes are fairly standard and you are happy to adopt the software’s way of working.
- You run several entities or countries and need consolidated accounting out of the box.
- Your auditors, investors or parent company expect a well-known platform.
- You have, or plan to hire, an in-house team to own the system.
When a custom build is the better choice
- Your rules are part of how you make money, and a template would force you to drop them.
- You have many staff who need access, and per-user pricing would punish growth.
- You want the system, code and data in your own name with no ongoing license.
- You need a few things done extremely well rather than a hundred modules you won’t use.
The risks of going custom, and how to cover them
Custom software depends on the people who built it. Protect yourself in the contract and the handoff:
- The code repository and hosting accounts are in your name.
- You get written documentation, not just a working system.
- There is a maintenance plan with a clear price, and you can leave it.
- Your team is trained to run the system day to day without the builder.
BIR registration applies either way
If the system will issue invoices or keep your books electronically, it generally has to be registered with the BIR as a computerized accounting system, whether it is NetSuite or custom built. Since 2021 the BIR has issued an Acknowledgment Certificate after you submit the documentary requirements, replacing the older Permit to Use process, and major changes to a registered system require a new application. Electronic invoicing rules are also being rolled out separately.
Rules and deadlines change and depend on your taxpayer type. Treat this as a starting point and confirm the requirements for your business with your accountant before you choose a system.
A real example
A cold-storage and logistics SME we worked with had overtime-charging rules that no template ERP could absorb, so billing, collections and HR ran on paper. We built a custom system around their real process on their own Azure and Microsoft 365, with no per-seat licenses. It went live in August 2026 and their own team runs it day to day. Read the case study.
Questions to ask any vendor before you sign
- What is the total cost over three years with our current headcount, and with double?
- Who owns the code, the data and the hosting account?
- Which of our current processes will we have to change, and why?
- How do we export everything if we leave?
- Who handles BIR registration, and what happens when the system changes?
- Who on your side actually does the work, and who supports us after go-live?
Not sure which way your business leans? Book a free ops check. We’ll tell you honestly if a packaged ERP would serve you better, and why.
