A considered decision.
Starts with a clear answer.
Answers on system scope, getting started, and protection — and points that need agreement before contracting.
Do we need to enable every module?
No. Your organisation chooses the modules it needs, and can expand as team needs change.
We already have a finance system. Where do we start?
Start by naming the gap: grants, procurement, or MEAL — then discuss a clear initial scope. Integration with your current system needs a technical review before agreement; we do not assume a ready-made connector.
Does each organisation get a separate workspace?
Yes. TenXshift is multi-tenant cloud software. Each organisation gets an isolated workspace with its own role-based access and settings.
Does it support Arabic?
Yes — Arabic with full RTL, and English.
How do we know the cost?
Pricing depends on active users, enabled module bundles, and storage. Estimate your cost on the pricing page; taxes and add-on service costs are set out in the written quote.
Where is data stored? And what is the backup policy?
Hosting location, backup frequency, retention, and restore windows need written confirmation from the TenXshift team before contracting. See the data-protection page for the points that should be agreed.
How do we migrate from Excel files?
Bulk import tools are available. Migration starts by reviewing and cleaning files and mapping fields, then trial import and result verification before expanding scope.
What if we want to stop using the system?
The agreement must clarify data ownership, export scope and formats, the window available to retrieve and delete data, and any cost for migration assistance. Ask to lock these terms before contracting.
Test your grant. Then choose your scope.
Self-explore, then a 20-minute demo, then a subscription by modules and users.