Service 01
Software development
We build the system your business needs and nobody sells off the shelf. Fixed scope, fixed price, fixed date, and the code is yours from the first day.
What we actually build for companies your size
Not platforms. Not transformation. Specific systems that remove specific work.
| Kind of system | What it replaces |
|---|---|
| Internal operations tools — job tracking, dispatch, scheduling, approvals, inspections | A spreadsheet, a WhatsApp group, and somebody’s memory |
| Customer and partner portals — requests, status, documents, invoices | Phone calls asking “where is my order” |
| Integrations between the systems you already pay for — ERP, accounting, HR, CRM, warehouse | A person re-typing the same data twice |
| Government and compliance integrations — ZATCA e-invoicing, Qiwa, Absher and Nafath sign-in, Mudad payroll | Manual filing and a deadline you cannot miss |
| Document and data automation — reading contracts, IDs, invoices and delivery notes, then filing them correctly | Hours of typing and the errors that come with it |
| Reporting your managers will open — one screen, current, on a phone | A four-day monthly pack that is out of date on arrival |
| Mobile apps for staff in the field or customers | Paper forms, or nothing |
| Rebuilding a system nobody can maintain | Software written by someone who left, on technology nobody supports |
Where AI does the work, and where it does not
We use AI agents in our own build process. That is our business, not yours, and it shows up in your quote rather than in a slogan. Every change is reviewed and signed by a named senior engineer before it reaches you. Nothing else ships.
In the software itself, we use AI only where it earns its place: reading documents, pulling data out of scanned paperwork, matching records that never match exactly, drafting replies, summarising long text. If a plain rule does the job, we write the rule. It is cheaper for you and it does not surprise anyone at 2am.
Engagement
How it runs
- Discovery, on your site. We watch the process being done. We talk to the people doing it, not only to their managers. Half a day to two days, depending on size.
- A written scope. What is included, what is excluded, what happens when you change your mind. Both sides sign it. Short, and in plain language.
- A fixed price and a fixed date. Quoted before you commit. If we cannot price it confidently, we say so instead of padding it.
- Build in visible stages. You see running software every week or two, in an environment you can open yourself. No long silence followed by a demo.
- Testing before you see it. Automated tests, plus a person using it the way your staff will.
- Go live, then stay. We deploy, train the people who will use it, and stay reachable for 30 days of free defect fixes.
Software shaped to how your business already works — not the other way round.
KAFD 20230411 114620 — Ahmed, CC BY-SA 4.0, via Wikimedia Commons
What you receive
- The running system, in your environment or a cloud account in your name.
- All source code, in your repository, from the first week — not on handover day.
- Automated tests, with the coverage level written into the contract.
- Documentation in Arabic and English: how it works, how to run it, how to change it.
- Two training sessions, recorded.
- 30 days of defect fixes at no cost after go-live.
- A written note of anything we would do differently with more budget. Free, and useful whether or not you use us again.
The commercial terms, stated plainly
- Fixed price
- Quoted before the scope is signed. It does not move unless you change the scope, and then you see the new number before any work starts.
- Fixed date
- Agreed in writing. Ask us for a penalty clause — on a properly scoped project we will discuss one.
- Payment
- By milestone, against something you can see working. Not monthly against effort.
- Ownership
- Yours, in full, including anything generic we write for you. No licence, no per-seat fee, no hostage.
- Your data
- Stays where you and the law require. We agree data location and access in writing before we start — PDPL is enforced now, and it is your exposure, not ours.
- Currency
- SAR, on a Saudi invoice from a Saudi company.
Questions we get asked, answered straight
“What if it takes longer than you said?”
That is our problem, not your invoice. It is the whole point of a fixed price. The protection for us is the written scope, which is why we spend time on it.
“What if we want changes halfway?”
Normal, and expected. You get a price and a date for the change before we do it. Small things inside the same effort we absorb without a conversation.
“What happens if we stop working with you?”
You already have the code, the documentation and the accounts. Another team can pick it up. We will also spend a day briefing them, and we will not charge for it.
“Can you work with the vendor we already have?”
Yes. A good part of this work is making a system talk to one somebody else built. We do not need to replace them to be useful.
“Our requirements are not written down.”
Almost nobody’s are. That is what the first one month are for.
Start
One meeting, no charge, at your office. Bring the person who does the work, not only the person who signs.