Everyone in an ERP project is selling something. Except you.
The vendor sells licenses. The integrator sells hours. The referral partner collects a commission you'll never see itemized. Then the project runs long, the budget runs over, and the books come out of go-live worse than they went in — which is the documented norm, not the exception: most ERP projects miss their objectives, and a majority exceed their budgets.
We sit on your side of the table: finance-led requirements, a shortlist you can defend, a contract you understand, and oversight until the numbers reconcile.
Last updated: July 2026
The requirements were the vendor's, not yours
Most SMEs start with demos, and demos are scripted to the system's strengths. By the time requirements are "gathered," they've quietly become a description of the product on screen. The failure statistics follow from this inversion: research across the industry consistently finds the majority of ERP projects failing to meet their original objectives, with budget overruns the most visible symptom. The fix isn't a better demo. It's writing the requirements — finance first — before any vendor enters the room.
Compliance is now a selection criterion, not a plug-in
In Saudi Arabia, your system must generate invoices in the mandated XML format, integrate with ZATCA's Fatoora platform, and keep your ledger reconciled to what the Authority cleared. Jordan's national e-invoicing points the same way. A system that "supports" this through a bolt-on you discover at contract signing is a system that was never evaluated properly. Compliance requirements go into the selection matrix on day one — ours do.
Nobody owned the books through go-live
Data migration is where finance quietly breaks: opening balances that don't tie out, a chart of accounts redesigned by a developer, receivables aging lost in translation. The integrator's job ends at "the system works." Ours ends at "the numbers reconcile" — first close after go-live, on time, tying to the old system's last close.
What the engagement covers
A finance-led requirements matrix built from how your business actually runs — including sector-specific needs (freight and logistics operators: job costing, demurrage tracking, multi-currency clearance billing are first-class requirements, not customizations) and the full compliance layer (e-invoicing integration, VAT, audit trail). Then a genuine shortlist, structured vendor demos scored against your matrix, and reference checks the vendors didn't curate.
Total cost of ownership modeled over five years — licenses, implementation, customization, support, and the post-go-live costs vendors leave out of the proposal. Milestone-based payment terms tied to acceptance criteria, not calendar dates. You'll know what you're signing, and what it will actually cost.
We stay through delivery as your side of the table: chart-of-accounts design, data-migration validation (opening balances tie out before go-live, not after), user-acceptance discipline, and a go-live gate with hard criteria. First month-end close after go-live happens with us in the room.
Our neutrality, in writing: Capfide sells no ERP licenses and accepts no commissions, referral fees, or margins from any vendor — and we'll put that in the engagement letter. We build software for our own use in the freight sector; it is never proposed in client selection engagements. Our only client in a selection is the one paying us.
How it works
Process walkthrough and finance review. Output: the requirements matrix — operational, financial, and compliance — weighted and signed off by you before any vendor is contacted.
Market scan, shortlist of 3–4 credible fits, scripted demos scored against the matrix, reference checks, and TCO comparison. Output: a selection report with a defensible recommendation — and the reasons the runners-up lost.
Negotiation support through signature, then implementation oversight to first reconciled close. Ongoing systems and reporting discipline can roll into the Fractional CFO retainer.
Why Capfide
Because we've been on every side of this except the selling side. Seventeen years running finance inside freight forwarding operations — as the user whose month-end depended on the system, not the consultant demonstrating it. We've specified, implemented, and lived inside ERPs; we build finance software for our own operations in the freight sector, which means we know exactly where implementations hide their costs and where vendor claims meet reality. The engagement is led by Majdi Noufal, CPA (New Hampshire), CMA (IMA), with a network of CPA-, CMA- and JCPA-credentialed professionals across Jordan and Saudi Arabia.
The result is a rare position in this market: deep enough in the technology to challenge an integrator line by line, and paid only by you.
Frequently asked questions.
Do I need an ERP consultant, or can I just work with a vendor?
You can work directly with a vendor — most SMEs do, and that's reflected in the outcome data: the majority of ERP projects miss their objectives, and budget overruns are routine. The structural issue is that everyone at the table except you earns more when the project grows. An independent advisor changes that geometry. If your project is small and your requirements are genuinely simple, we'll tell you so in the first call — a selection engagement isn't always warranted.
Which ERP do you recommend?
None, until your requirements exist. Depending on size, sector, and compliance needs, the credible shortlist for a Saudi or Jordanian SME spans regional and international systems at very different price points — the right system falls out of the matrix, not the other way around. What we will say upfront: any system that cannot natively meet ZATCA Phase 2 integration requirements doesn't make a Saudi shortlist, whatever else it does well.
Is your own ERP product part of the shortlist?
No. We build software for our own use in the freight sector, and it is excluded from client selection engagements as standing policy — that exclusion is written into our engagement letter. Neutrality that depends on trust is weaker than neutrality that's contractual.
How much should an SME budget for an ERP?
Honestly: more than the vendor's proposal says. Industry research consistently shows most projects exceeding their initial budgets — which is why we model five-year total cost of ownership before you sign, including implementation, customization, training, support, and the post-go-live costs proposals routinely omit. The number we give you is the one you'll actually spend.
Our implementation is already underway and struggling. Can you come in mid-project?
Yes — implementation oversight can start mid-stream. The first step is a rapid status review: scope versus contract, budget consumed versus milestones accepted, and the state of the finance workstream (chart of accounts, migration, reconciliation plan). Most struggling projects are recoverable if the finance side is caught before go-live.
Before you sit through another demo.
Thirty minutes on where you are — current systems, growth pressure, compliance exposure, and whether a structured selection is worth it for your size. If it isn't, we'll say so.
Book a call →