CRM, ERP and custom systems
Built around how your company works, in Arabic and English, with your data on your own account. We write the spec first, so you know what you are buying before anyone writes code.
What we build
The systems your company runs on
When spreadsheets and off-the-shelf tools stop fitting the way you work, we build the system that does. Same team, same written spec, same support afterwards.
CRM
Leads, deals and customers moving through the stages your sales team actually uses, with follow-ups nobody forgets.
ERP
Inventory, purchasing, invoicing and accounts in one place, so the same number doesn't get typed into three systems.
Client portals
Customers check their own orders, tickets, documents and balances instead of calling your team for them.
Operations and field apps
Jobs, sites, teams and daily work on a phone, including the parts that happen away from a desk.
Contact centres
Calls, WhatsApp and tickets on one screen, with recordings, queues and the reports a supervisor needs.
Dashboards and reports
The numbers the owner checks every morning, and a clean PDF of anything that has to be printed or sent.
The standard
What every system gets, whatever it does
These are not extras we quote separately. They are how we build.
- Roles and permissions
- Admin, manager, staff and client as a starting point, then shaped to your org chart. People see what their job needs and nothing else.
- Arabic and English
- Right-to-left interfaces designed as the main version, not a translation bolted on. Users switch language without losing their place.
- Reports and PDF
- Anything the business prints, sends or files: invoices, statements, settlements, contracts. Generated from the data, with your letterhead.
- Money handled properly
- When a system touches money, it gets a settlement engine: advances, allocations, VAT, and a trail for every reversal.
- Your account, your data
- The system runs on your server or cloud account, in your name. You get the passwords and the code at handover.
- Training and support
- We train the team that will use it, and stay on for support the same way we do for websites.
Who they are for
Industries we have built for
Described by type. Client names come out only with their permission.
Real estate
A CRM for a brokerage in Saudi Arabia: units, viewings, agents, commissions, and calls handled inside the same screen.
Contracting
An operations system for an Egyptian contractor: projects, site teams, materials, progress and payments.
Support teams
A contact centre: numbers, queues, agents, recordings and the reports a supervisor reads every morning.
Professional services
A practice platform for law firms in the Gulf: matters, documents, deadlines and client access.
Retail and e-commerce
Stores connected to stock and accounts, so a sale online changes the same numbers as a sale in the shop.
Clubs and specialist businesses
A stable management system for equestrian clubs: horses, boarding, feeding, training and billing.
How a project runs
Nothing is built before it is written down
The spec is the contract. It says every screen, every role and every report, and it is agreed before the first line of code.
- 01
Understand
We learn the business first: who will use the system, what they do today and what that costs you.
- 02
Specify
You get a written spec with every screen, role and report, agreed before any code.
- 03
Build
We build in phases. You follow progress and comment on each phase as it lands.
- 04
Launch
Real data loaded, a clean production build, and every password handed over to you.
- 05
Look after it
Updates, backups and security scanning carry on for as long as you're with us.
Common questions
What owners ask us first
If your question is not here, ask it on WhatsApp and you get a straight answer.
How much does a system cost?
It depends on how many modules it has, and guessing before the spec helps nobody. We run a paid discovery, write the spec, and quote the build from it. If you walk away after the spec, the document is yours.
How long does it take?
A focused first version is usually weeks, not months, because we build the part you need working first and add the rest in phases. The spec gives you dates per phase.
Can you take over a system someone else built?
Often, yes. We read the code first and tell you honestly whether fixing it or rebuilding it costs less. We have done both.
Who owns the code?
You do. The repository, the servers and the accounts are in your name, and you get access at handover.
Can it connect to what we already use?
Usually. WhatsApp, payment gateways, accounting software, shipping companies and government e-invoicing are the ones we connect most often.
Tell us what's slowing your business down.
Thirty minutes is enough to tell whether we're the right team. If we're not, we'll say so and point you to someone who is.