And the CEO's playbook to make yours different — twenty years of lessons, from both sides of the table.
I have been the CIO who inherited a half-built ERP from a previous regime — the executive who had to explain to a board why the system everyone hated was the system they had paid eight figures for. And I have been the implementer on the other side: the one walking into a boardroom on day one, watching faces that have already decided this is going to fail.
I built Cloudian because the companies I served deserved a partner who stayed, not just a vendor who delivered and disappeared.
This ebook is not a product brochure. It is not a buyer's guide ranking ERP vendors. It is the conversation I wish someone had forced me to have before I ever signed an ERP contract.
If you are a CEO, an owner, or the person whose name will be on the project charter, this is for you. Read it once, then keep it on your desk through the next twelve months. The chapters you skim today are the ones that will come back to find you.
There is a number that almost no Filipino business owner gets right when they first ask it. The question is: how much does an ERP cost? The answer most owners hear is the license fee — a per-user-per-month figure on a slide. Multiply it by your headcount, multiply by twelve, and you have a number you can take to the board. It looks reasonable. It is also wrong.
The real cost of an ERP is not the software. It is the cost of the year your senior team will spend living inside it. It is the cost of every process you discover is broken once the system refuses to accept your data. It is the cost of the customer order that ships late because the warehouse team is still on the old Excel sheet. It is the cost of the controller who quits because the close cycle she designed in 2018 no longer exists.
ERP is the most expensive software your business will ever buy because the software is the smallest part of what you are actually buying. You are buying a forced rewrite of how your company runs. The license fee is the receipt for the hammer; the renovation is the real bill.
Actual ratios vary by industry, size, and the maturity of existing processes — but the shape of the bar is consistent: the license is a small share of the true total.
This is not an argument against doing it. Most growing Filipino businesses reach a point where the absence of ERP costs more than the presence of it — when the family-built spreadsheet finally cracks, when a second branch makes consolidated reporting impossible, when an audit reveals you have been reporting numbers nobody can reconcile.
It is an argument for doing it with your eyes open. In the chapters that follow, I will walk you through the seven ways I have watched ERP projects collapse — and the leadership moves that, in my experience, separate the companies that come out of an implementation stronger from the ones that come out broken.
Let's start with the failures.
Most ERP failures are not technical failures. The software works. The vendor delivered. The reports run. And yet the company still does not use the system the way it was designed.
The single most predictive sign that an ERP project will fail is this: the kickoff meeting is run by the IT manager. This is not because IT managers are not capable. It is because ERP is not a server upgrade. It is a redesign of how the business operates — finance, sales, inventory, procurement, fulfillment, payroll, reporting.
The IT manager owns none of those processes. He cannot make a decision about credit terms, write-off policy, costing methodology, or which warehouse location is the master. The moment he is asked to, the project stalls.
A CEO who delegates an ERP to IT is treating it the way you would treat a new firewall. It is the kiss of death.
Every decision the IT team escalates upward is a week of delay. Every decision they try to make on their own becomes a process the business will refuse to follow at go-live.
I once walked into a construction company south of Metro Manila whose ERP looked, on paper, like a masterpiece. Custom dashboards. Bespoke project P&L reports. A revenue-recognition engine that handled their unique progress-billing model. The president had personally designed every report.
Eighteen months later, the president left. His successor took one look at the system, asked three people in the office what each report meant, and got three different answers. Nobody could explain why the numbers were structured the way they were. Within a quarter, the new CFO had quietly stopped using half the system and built her own Excel model alongside it.
The best systems I have seen fail were not badly built. They were built for one person, one vision, and one moment in time.
This is the system-for-one problem, and it is endemic in owner-led Filipino businesses. The founder knows what he wants the system to show him. He does not always pause to ask whether his organization knows why.
When the vision lives in one head, the system has a single point of failure. When that person leaves — promotion, retirement, a board reshuffle, a family transition — the system collapses, not because it stopped working, but because it stopped being understood.
ERP has a quiet, brutal property: it does not fix dysfunction. It exposes and amplifies it.
If your sales team has been quoting prices that bypass your margin policy, the ERP will reveal it on day one — and either force the policy to change or watch the team find a way around the system. If your warehouse has been adjusting inventory counts to mask shrinkage, the cycle-count module will surface every variance. If two branches have been recognizing revenue using two different methods, consolidated reporting will refuse to reconcile.
Owners often hope that implementing an ERP is the same as solving the underlying problem. It is not. The system is a mirror. What it shows you is what was already there.
Companies that succeed with ERP do the unglamorous work first. They document the broken process. They make the political call about which branch's method becomes the standard. They write the policy. Then they configure the system to enforce it.
Companies that fail try to do all of that during configuration — and discover, six months in, that they are designing a system on top of arguments that have not been settled.
There is a specific moment, about three months into every implementation, where the CEO stops attending the steering committee. It is understandable. The business does not pause for ERP. The quarter still has to close. Customers still call. The CEO sends a delegate, then a delegate's delegate, then a calendar decline.
By month six, decisions that need owner authority are sitting in someone's inbox for two weeks at a time. The implementation team — internal and external — starts making smaller and smaller decisions, because the larger ones cannot get answered.
By go-live, the CEO returns to find a system he no longer recognizes, configured around compromises he never sanctioned, owned by people who do not have the authority to defend it.
If you are not ready to lead the ERP yourself, do not start.
This does not mean the CEO has to attend every working session. It means the CEO has to be the visible owner — present at kickoff, present at every steering committee, present at user-acceptance testing, present on the day of go-live, and present in the weeks after. The team takes its cue from the leader's calendar. If the calendar says ERP matters, ERP matters.
There is a mirror image of this pattern, and I have seen it at least as often.
The principal — sometimes a C-level, sometimes the patriarch or matriarch in a family business — is not in the discovery sessions. Not in the demos. Not in the follow-up workshops where scope and trade-offs are worked out. The operations team carries all of that, sometimes over weeks, sometimes over months.
Then the proposal lands. Suddenly the principal is in the room. Not to discuss the solution. To negotiate the price.
The next move is predictable. The team is asked to find another vendor offering the same thing for less. They take the proposal, the scope, and the discovery findings, and walk them to a competitor who has done none of the work. The competitor matches the documented spec at a discount. They have nothing to lose by quoting low. They have not earned the right to disagree with a single line of the proposal.
Sometimes the cheaper vendor wins. The implementation, in my experience, is usually where the saving disappears.
I am not making a case against price negotiation. Owners should negotiate. But a negotiation conducted by someone who has not been in the work is conducted with the least information of anyone in the building. The principal does not know which line items are robust and which are thin. The principal does not know which scope items the team genuinely needed and which were nice-to-haves. The principal does not know which partner has actually engaged with the business and which has copied a scope they have never tested.
The owner who arrives only at pricing is, in effect, asking the cheapest vendor to deliver a solution designed by a service provider who understood the requirements better and longer. That is not a saving. It is a discount on the front, paid back many times over in the year that follows.
Both patterns share the same root: leadership engaged at the wrong moment. The first disappears after kickoff. The second never shows up until the price is on the table. The discipline is the same in both cases. Be in the room when the work is being done.
Filipino business is family business. The strengths are real — long horizons, deep loyalty, an instinct for relationships that no MBA can teach. So are the costs.
Family-owned companies bring distinctive governance challenges to an ERP implementation. The patriarch wants the dashboards he is used to. The next-generation COO wants modern controls. The aunt who has run accounting for thirty years has her own method that does not appear in any policy manual. The cousin who handles procurement has authority that does not match his job title.
ERP forces these tensions into the open. The system asks: who approves a payment over five hundred thousand pesos? Who can override a credit limit? Who signs off a journal entry to retained earnings? When the answers are "depends on who's in the office", the implementation cannot proceed.
The companies that succeed treat ERP as an opportunity to professionalize. They use the project as a forcing function for the governance conversation that has been deferred for a decade.
The companies that fail try to encode the existing informality into the system, then watch the system collapse the moment a real-world exception occurs.
There is a date on the project plan called go-live. It feels like the finish line. It is not. It is closer to the starting line.
Vendors are sometimes incentivized — explicitly or implicitly — to hit go-live as quickly as possible. Internal teams want the project to end so they can return to their day jobs. The CFO wants the new fiscal year to start on the new system. Everyone has a reason to push the date.
What gets sacrificed is adoption. Training is compressed into two-day classroom sessions. User-acceptance testing becomes a tick-the-box exercise. The cutover happens with workarounds that everyone agrees will be cleaned up later. They are not.
Three months after go-live, half the team is back on Excel. Six months in, the workarounds have hardened into permanent shadow processes.
The dashboards the CEO asked for have data quality problems nobody has time to fix. The system technically went live, but the business never adopted it.
Most ERP vendors make the bulk of their margin on implementation, and a thin trickle on support. Their commercial incentives reward closing the project and moving the consultants to the next account. The companies they leave behind are often left with an account manager who answers email on a three-day cycle.
The first twelve months after go-live are when the system is most fragile.
New scenarios surface. The auditors arrive and ask for a report nobody anticipated. A user discovers a workflow gap. The business changes — a new product line, a new branch, a new tax rule. If the implementation partner is not present in those months, the system slowly drifts away from the business it was meant to serve.
The right partnership is one where the people who built the system are the people who maintain it, and where the senior leadership of the partner firm remains accessible long after sign-off.
These are the moves that separate the companies that thrive after an ERP from the ones that merely survive it. None of this is about software. All of it is about leadership.
Five commitments to write down, sign, share with your senior team, and re-read every month for a year.
A good implementation begins with what we call Discovery — a structured period, usually three to six weeks, during which the implementation team does almost no configuration. They ask questions.
To owners under deadline pressure, this can feel like wasted time. We are paying consultants to ask questions we already know the answers to. The answer is: you do not know the answers, and neither does anyone else, until the questions are asked properly.
Discovery is not a delay. It is the only chance you get to find these things before they become configuration decisions you cannot reverse without rework.
"The month of Discovery felt slow at the time, but it was the only month of the project where the team got to think instead of react."
— CFO, Cebu-based distribution group
ERP implementations fail not in dramatic explosions but in a thousand small slips — meetings that did not happen, decisions that were not made, owners who did not show up. The discipline that prevents this is unglamorous and largely consists of the following:
Run the project this way and the project tells you, every Friday, whether it is healthy. Skip the discipline and you find out at go-live, which is too late.
The hardest part of an ERP project is not the configuration. It is the change.
Filipino workplaces, in my experience, are conflict-averse. A team that disagrees with a new system rarely raises it openly. They smile, attend the training, then quietly continue doing things the old way. By the time leadership notices, the parallel process is entrenched.
Adoption is a leadership problem, not a training problem.
The signals you send in the first ninety days set the culture for the next decade. Adoption is what you are buying. The license fee is the receipt. Optimise everything in the implementation around it.
The first twelve months after go-live are when the value of the system is either captured or quietly lost. This is the period when:
Treat sustainment as part of the project, not an afterthought. The companies that do are the ones still on the same ERP a decade later — growing into it rather than replacing it.
If Part One is the warning and Part Two is the playbook, Part Three is the decision. It is for the owner asking: what does this mean for my next move?
Before you take a single sales call, work through these ten questions honestly. Score each from 1 (not at all) to 5 (completely true). The total tells you what to do next.
I will not pretend to be neutral. Cloudian Philippines is one hundred percent Acumatica-focused, and it is the platform we have made our standard. But it is worth understanding why.
In the Philippine mid-market, owners typically choose between three categories of ERP:
What we have found, after years of implementing Acumatica across Construction, Manufacturing, Distribution, and Service Management, is that its commercial model is uniquely well-suited to the growing Filipino business. Licensing is based on resources consumed, not seats — meaning you can give every relevant employee access without a per-user penalty. Industry editions provide depth without forcing you onto a heavily customized version. And the platform's openness means the system grows with the business rather than constraining it.
The right answer is not always Acumatica. The right answer is the platform whose strengths match the problem you are actually solving. The wrong answer is choosing on the basis of brand familiarity or sales aggression.
Make this decision the way you would make any other strategic capital decision — with a structured evaluation against criteria you defined before any vendor walked in the room.
Cloudian Philippines operates two delivery models, and the choice between them matters. The honest conversation with a prospective partner should establish which path is right for you in the first meeting.
If you have read this far, you are not the kind of owner who buys software on a whim. You are the kind who wants to walk into the next twelve months with eyes open. There are three useful next moves.
We are an Acumatica Gold Partner, recognized by Acumatica with the Cloud Adoption Partner of the Year Award for Asia and the Customer Excellence Award for Asia.
We work with companies in Construction, Manufacturing, Distribution, Services and Institutions — from fast-growing single-entity businesses to multi-entity conglomerates — and we measure our success by what our clients achieve with the systems we build, long after the implementation is over.
We are based in the Ortigas CBD, Pasig City, with delivery capability across the Philippines and the wider region, including Singapore and Australia. Founded by Rich Quin in 2018, after two decades on both sides of the ERP table — first as the CIO who lived inside other people's implementations, then as the partner who decided to build the kind of firm he had always wished he could hire.