12 Questions Before You Sign — Plus the WhatsApp Test
Choosing a system to run your business is not buying software; it is a decision that stays with you for years. Most proposals look alike in the first meeting, and the difference only shows six months later, when half the team has drifted back to paper. These questions belong before the signature — and the last one is the hardest: if you handed this system to a warehouse employee today, with no training, would they use it?
The safer path is to start from your need, not from the vendor's demo. Here is a practical checklist to run before you sign, ordered around the points people most regret ignoring.
Start from your need, not the feature list
Before you look at any system, write down what you need in your own words: which operations hurt today? Where do the numbers get lost? Which reports do you want but never get? This list is your measuring stick, and every system is judged against it, not against what the vendor pitches with enthusiasm.
Then separate what is essential from what is merely nice. Essential is what your business cannot run without; nice-to-have is what you would like and can defer. Many shiny features fall into the second bucket, and paying for them from day one is waste that returns nothing.
The pre-decision checklist
Five areas settle most of the decision. Ask about each one plainly and demand a concrete answer, not a general promise:
| Area | The question it answers |
|---|---|
| Functional coverage | Does it cover your core operations without workarounds or side tools? |
| Integration | Does it connect to what you use now: payment gateway, e-invoicing, bank? |
| True cost | What will you pay over three years, not just the monthly subscription? |
| Vendor and support | Who helps you when it breaks, in which language, and at what hours? |
| Data ownership | If you decide to leave, how do you take your data, and in what format? |
Do not settle for a yes or no. Ask the vendor to show you each area working on the system itself; the gap between a promise and a proof is the gap between a sound decision and deferred regret.
Compliance with Saudi requirements
In Saudi Arabia it is not enough for a system to be good globally; it must meet your local requirements. The most important today is support for e-invoicing across its phases as defined by the Zakat, Tax and Customs Authority. Ask the vendor for practical proof rather than a claim, and ask: is their solution compliant, and how does it handle the integration phase?
Regulatory requirements change and are updated over time, so verify the current details from the official source at zatca.gov.sa before you build your decision on a verbal promise.
Costs the quote does not show
The subscription price is usually the smallest part of the bill. Before you compare prices, add up the following over three years:
- Setup and migrating data from your current system.
- Training until your team actually uses the system, not just in name.
- Customization for any process the system does not cover out of the box.
- Per-user fees as your team grows.
- Annual support and upgrades.
Two systems with similar subscription prices can diverge sharply once you add these items up. Compare the total, not the advertised number.
Questions that reveal the vendor
A good vendor answers clearly; an evasive one hides behind general phrases. Put these questions before you sign:
- Show me a business my size using the system in the same sector.
- What happens to my data if I end the subscription?
- How long does implementation really take, from signing to going live?
- Who bears the cost of errors during data migration?
- Is support available in Arabic, and what response time is written into the contract?
Test before you commit
Do not sign a long contract based on a presentation. Try it first, in limited steps:
- Ask for a trial account and load it with real data from your business, not the vendor's ready-made sample.
- Run one complete workflow: from order to invoice to report.
- Involve the employee who will use it daily and hear their view; they are the one who exposes the flaws early.
- Measure plainly: did you finish the task faster and more accurately than with your current method?
A small test on your real data reveals in a week what a full month of demos will not.
The WhatsApp test
Add one question to the list above: how many screens must an employee learn before recording a single transaction? If the answer is anything above zero, you are buying a system and a permanent training project alongside it — and the second cost never appears in the proposal. Businesses that succeed at rollout are not the ones that picked the most powerful system; they are the ones that picked the system their team actually used.
That is why Fahim is built on a tool everyone already uses — see the comparison with Odoo for Saudi businesses before you decide.