Custom ERP for teams whose numbers still live in Excel and paper
We build Arabic-first back-office systems for services companies — invoicing, daily accounting journals, payroll and live financial reporting in one system instead of five spreadsheets.
What we hear in this industry
Every function has its own spreadsheet
Invoices in one file, expenses in another, payroll on paper. Nothing reconciles without someone spending a day on it.
You see the numbers a month late
Management waits for month-end close to find out how the month went — by which point the decisions it should have informed are already made.
Off-the-shelf tools fight Arabic
Foreign ERPs treat Arabic as a translation layer. Reports come out mirrored wrong, invoices look unprofessional, and staff quietly go back to Excel.
Everyone can see everything
Without real roles, the receptionist and the finance manager have the same access — a control problem that grows with every hire.
What we ship instead
Arabic-first, not Arabic-translated
Designed RTL from the first screen, so invoices, reports and journals read correctly and your team doesn't fight the tool.
Billing and accounting in one place
POS invoicing that feeds daily accounting journals automatically — no re-entry, no reconciliation day.
Payroll off paper
Salaries calculated from attendance and adjustments instead of assembled by hand each month.
Live reporting with real roles
Financial dashboards management reads in real time, behind role-based access so people see exactly what their job requires.
We built this for a businessmen-services company that ran entirely on paper and spreadsheets.
Altahdi System
Altahdi now runs the entire company on the system: reception issues PDF invoices in seconds, the day-book is digital, payroll computes itself from attendance and adjustments, and management reads six live charts instead of waiting for month-end. Twenty-two thousand lines of TypeScript replacing paper — with zero accounting lost in the migration.
What teams in this industry ask
Can we migrate our existing data?
Yes. Migration is planned as part of the rollout — we move your existing records in and reconcile them before switchover, so no accounting entry is lost in the transition.
Why build custom instead of buying an ERP?
Buy off the shelf if your process is standard — it's cheaper and faster. Custom makes sense when your workflow is the business, when Arabic-first is non-negotiable, or when licence costs per seat grow faster than your team.
How long does a rollout take?
Altahdi went from design to a running system in 20 weeks, shipped module by module so the team adopted it in stages rather than all at once.
Get a free technical audit
Send us the link to your site, app or dashboard. Within two business days you get a 5-minute recorded walkthrough of what's slowing it down, what's costing you conversions, and what we'd fix first — whether or not you ever hire us.
No sales call required. If we're not the right fit, we'll tell you that too.
Send the link
Your site, app or dashboard. No brief to write and no forms to fill in — the URL is enough.
We go through it
Load performance, the conversion path, mobile behaviour, SEO fundamentals and the technical debt that's already showing.
You get the recording
A 5-minute video with a prioritised list of fixes. It's yours to keep and hand to any team — including your own.
Let's build it right
Tell us what you want to launch or improve. We'll review it, reply with a clear next step, and book a short call if the project is a fit — no commitment.