Two regional vendors
Choosing between regional ERP vendorswhen both demo well and both speak Arabic
First Bit is an established ERP vendor across the GCC with a large implementation bench, local offices and Arabic-speaking support — the same broad category we sit in, and a serious option for a Saudi contractor. That is what makes this comparison harder than a tier-1 one: the obvious differentiators cancel out. This page is about the questions that still separate two regional vendors once both have shown you a polished demo in your own language.
What cancels out
The things both regional vendors will have
Do not spend your evaluation time here. If a criterion is satisfied by everyone on your shortlist, it cannot help you choose — confirm it once and move on to the section below.
Arabic interface and Arabic support
Any regional vendor worth shortlisting will give you Arabic screens, Arabic documents and support staff you can call in Arabic. Confirm it on a printed tax invoice and a report rather than a login screen, then stop scoring it.
- Arabic UI, documents and reports
- Arabic-speaking implementation team
- Hijri alongside Gregorian
ZATCA e-invoicing and local compliance
Both will tell you they are compliant, and both are probably right. Ask each to clear a standard invoice and report a simplified one in front of you, so you have watched it rather than read it.
- Cleared invoice, watched live
- VAT and WPS handled
- A named person for rejections
Local presence and references
Offices in the Kingdom and customers you can phone. Ask for references in your own sector and at your own size — a happy retail customer tells you very little about a contracting implementation.
- In-Kingdom offices and staff
- References in contracting, at your scale
- A support SLA in writing
The contracting chain
Six links a First Bit alternative for Saudi contractors has to cover
These are contracting structures rather than accounting ones. Whatever you shortlist, ask each vendor to demonstrate all six on your own data, in one session, end to end.
BOQ lines that survive into cost codes
A bill of quantities priced in a tender has to become the budget the project is measured against, with the same line structure. Ask to see a real BOQ imported and turned into cost codes without a spreadsheet in the middle.
- BOQ import with rates and quantities
- One cost-code tree from tender to final account
- Variations that re-base the budget
Committed cost, not just spent cost
A contractor's exposure is the purchase orders and subcontracts already signed, not only the invoices posted. Ask where committed cost appears and how it reaches the cost report before anyone invoices you.
- PO and subcontract commitment at raise
- Budget vs committed vs actual in one view
- Cost to complete and EAC
Progress billing — the IPC or مستخلص
Interim payment certificates are their own document type: measured work to date, materials on site, retention held and released, advance recovery, previous certificates. Ask to see one produced and then cleared as an e-invoice.
- Measured work and MOS
- Retention held, released and aged
- Advance payment recovery
Subcontractors, back to back
Subcontract certificates that mirror the main contract's terms — retention percentages, payment terms, defect periods — are what keeps cash from leaking out faster than it comes in.
- Back-to-back certificate terms
- Subcontract retention tracked separately
- Liability and defect period tracking
Labour and plant landing on the right job
Timesheets and plant hours have to cost to a project and a cost code, not to an overhead pool, or the job costing report is arithmetic rather than information.
- Timesheets costed to cost codes
- Internal plant hire rates
- Site allocation of shared resources
ZATCA Phase-2 on a certificate, not just an invoice
Clearing a standard tax invoice is table stakes. The question is whether the invoice raised against a payment certificate carries the right lines, retention treatment and VAT timing when it goes to Fatoora.
- Cleared invoice from a certificate
- Retention and VAT time of supply
- Rejection and resubmission handling
An honest test
What actually separates two regional vendors
When the category-level criteria tie, the decision comes down to depth in your specific chain, who you actually get on the implementation, and how the relationship behaves when something goes wrong.
Who you actually get, not who pitched
Ask for the names and the contracting projects of the people who will be on your implementation, and put them in the contract. A large bench is only an advantage if the part of it you get has done contracting in the Kingdom before.
- Named implementation team
- Their contracting track record
- Written into the contract
Where the tender document enters the system
Someone has to turn a tender PDF into priced BOQ lines. Ask each vendor to show you that step on a real document — whether it is keyed in, imported from a spreadsheet, or read automatically — because it is where weeks and pricing errors hide.
- Tender PDF to priced BOQ lines
- Where transcription errors get caught
- How variations re-enter the chain
How change requests behave
Every implementation needs changes. The question is whether a small change is a conversation or a quotation, and how long it takes. Ask both vendors for a real example from a current customer, with the elapsed time.
- Turnaround on a small change
- Who decides what is in scope
- A real example with dates
Related:Job costing by cost codeBOQ and tender managementIPC and progress billingSubcontractors and retentionZATCA Phase-2 e-invoicingthe wider ERP buyer's guide
How to decide
Running the comparison properly
Score every First Bit alternative for Saudi contractors on the same six links
Turn the chain above into a scorecard before any demo. A prepared demo always works; a scorecard filled in live on your own BOQ does not flatter anybody.
Ask what is product and what is add-on
For every contracting feature, ask whether it ships with the core product or comes from a module, app or partner build — and if it is added on, who supports it, who upgrades it, and what happens when the core version moves.
Price three years, not the licence
Add licences or subscriptions, implementation, the contracting layer, data migration, training and annual support across three years. These comparisons swing on implementation and maintenance far more than on licence cost.
Pilot one live project end to end
Take a real project: import its BOQ, raise a subcontract, cost a timesheet, produce one payment certificate and clear the invoice with ZATCA. Whatever survives that test is the honest shortlist.
FAQ
Frequently asked questions
How do I compare two regional ERP vendors that both demo well?
Stop scoring what they share. Arabic support, ZATCA compliance, local offices and a polished demo will be true of every serious regional vendor, so confirm each once and take it off the matrix. Spend the evaluation on depth in your own chain — BOQ to cost code to certificate — tested on your own data, on who you actually get for the implementation, and on how change requests behave once you have signed.
What should I ask a regional ERP vendor about contracting?
Ask them to show, not tell, on six things: a real BOQ becoming cost codes; committed cost appearing before an invoice does; an interim payment certificate with retention and advance recovery; back-to-back subcontract terms; a timesheet costing to a cost code; and an invoice raised from a certificate clearing through Fatoora. Ask for all six in one session, on your data. Prepared demos are built to pass; a live scorecard is not.
How much does the implementation team matter?
More than the product, in most failed projects we have seen picked up afterwards. Two customers of the same vendor can have completely different experiences depending on who ran the implementation. Ask for the names of the consultants assigned to you, the contracting projects they have delivered in the Kingdom, and get those names written into the contract rather than promised in a meeting.
Is a regional ERP better than a global one for a Saudi contractor?
Not inherently — it is a different trade. Regional vendors typically give you faster implementation, Arabic support as a first-class thing and local compliance built in rather than added on. Global vendors give you depth in manufacturing and consolidation, and a vendor-stability story that some procurement policies score heavily. Score both against what your business actually does most of, not against a general reputation.
What is different about how a tender document enters the system?
This is the step most comparisons skip, and it is where weeks go. Somebody has to turn a tender PDF into priced BOQ lines, and the options are keying it in, importing a spreadsheet somebody else keyed in, or having the document read automatically and checked by a human. Ask each vendor to do it with a real tender in front of you and time it. The differences are large and they compound over every bid.
Can we switch regional ERP vendor partway through a contract?
You can, and it happens, but do the commercial homework first: read the termination and data-export clauses you signed, establish what format your data comes out in, and confirm who holds the ZATCA onboarding credentials. Technically the migration is the normal one — chart of accounts, open balances, live projects and contracts, one month in parallel. Commercially it is the exit terms that decide how painful it is.