Qimma Digital · Amman, Jordan
We don't sell pages. We engineer systems.
We start with the business itself: how it runs, and where the time and the money leak. Then we decide what is worth building — a website, a store, a dashboard, or a whole system — and we build it as real software, not as a configured template.
- systems built
- 8
- live and running
- 6
- app stores
- 2
- built, not translated
- AR / EN
A client asks for a website. Sometimes that is not what they need.
The owner of a solar company asked for a website. An hour with him was enough to make the website the least of it: he was rebuilding a fourteen-page technical and financial proposal by hand, for every single customer who asked him for a price.
So we built the proposal generator instead. We reverse-engineered his pricing out of his own document and solved its constants until the program reproduced that proposal to the decimal. On the way it surfaced an arithmetic error that had been going out to customers unnoticed — so the check for it shipped as a permanent feature inside his system.
That project also contains something we declined to build. He asked about custom invoicing; he already owned it. Telling a client he has already bought something is a stronger position than selling him a worse copy of it.
- Asked for
- A website
- Built
- A proposal generator
What is worth building is decided after understanding the business, not before it.
What we can build
Dashboards and business intelligence
A number on a screen is the last link in a chain: what gets collected, how it is modelled, and who is allowed to see it.
We build the chain, not the chart. Roles and permissions, a data model that can answer a question nobody asked at the start, and queries that stay fast after the tables stop being small.
- Dashboards that change with the role
- Pipelines, funnels and conversion
- Scheduled and exportable reporting
- Measured queries that survive growth
EvidenceA marketing agency in Amman runs its sales floor on one — three roles, six pipeline stages, in daily use since it shipped.
Website design and development
A page has one job, and most sites lose it somewhere between the design and the third framework.
We build the site as software: typed source, real content models, images at the right size before they leave the server, and a first paint a phone on mobile data can afford.
- Bilingual by construction, not translation
- Content models instead of a page builder
- Measured on a real device before launch
- Domain, certificate and hosting handled
EvidenceA perfume house in Amman sells through one. A cleaning company covering Jordan is found through another.
Search architecture
Being indexed is a property of how a site is built, not a plugin installed after it is finished.
Routing, canonicals, per-language alternates, structured data that describes what is actually on the page, sitemaps that match reality, and a blog whose articles are a content type rather than a folder of pages.
- Schema that matches the page it is on
- Canonicals and alternates per language
- Editorial architecture for a real blog
- Technical SEO audits, and the repairs
EvidenceAn artificial-stone manufacturer's site was audited and repaired rather than rebuilt — and recommending against the rebuild was part of the work.
Interactive work
A screenshot of a tool proves you can draw one. A tool that answers proves you can build one.
Configurators, editors, canvases, things that recompute while you drag them. Written to a frame budget, suspended the moment they leave the screen, and replaced by something still when the device or the reader asks for less motion.
- Configurators and editors
- Canvas and WebGL where they earn it
- A frame budget measured, not assumed
- Reduced motion honoured, not ignored
EvidenceThe object beside this paragraph is one. Seven of them, generated from arithmetic, with no 3D library — the whole renderer is under three kilobytes over the wire.
Three dimensions
3D on the web is a performance problem wearing a design brief.
Product configurators, generated geometry, motion that means something. We reach for a library when the scene genuinely needs one and write the renderer when it does not — the cheaper answer is usually the one nobody tries.
- Product and surface configurators
- Generated geometry, not exported assets
- Renderers written to the size of the scene
- A still frame where the device cannot
EvidenceA solar company's roof configurator ships a renderer of ten kilobytes where the obvious library is a hundred and fifty.
Engineering and infrastructure
The part of the work you never see is the part that decides whether the rest survives a year.
Version control, one branch per piece of work, typed source, tests where they earn their cost, containers, environments, backups, and a release you can repeat. Handover is a file in the repository, not a favour.
- Repository, branches, review before merge
- CI that builds and signs the releases
- Containers, and environments kept apart
- Documentation another developer can use
EvidenceAn iOS build ships to the App Store from a Windows machine that has never seen a Mac.
Tools built for one business
Most of what a business actually needs has no name and no product page.
A generator, a calculator, a scanner, an approval queue, an importer — the small piece of software that removes an hour a day. Building it is usually cheaper than the licence for the product that almost fits.
- Document and PDF generators
- QR, scanning and verification
- Calculators and pricing engines
- Importers, exporters, internal queues
EvidenceOne of them retired a fourteen-page proposal that was being rebuilt by hand for every customer who asked for a price.
There is no service list
- Proposal generator
- 3D roof configurator
- Pricing engine
- QR attendance
- Sales pipeline
- Call log and follow-ups
- Role-based permissions
- Bilingual storefront
- Three-sided marketplace
- Technical SEO repair
- Structured data
- ERP modules
- App store release pipeline
- Native mobile apps
- Owner's dashboard
- Booking and scheduling
- Invoicing and receipts
- WhatsApp notifications
- Stock counts and transfers
- Customer portal
- Warranty and service history
- Delivery routing
- Quote approvals
- Membership renewals
- Price lists per customer
- Spreadsheet imports
- Printable labels and barcodes
- Multi-branch reporting
- Audit trail
- Commission calculations
If what you need is not on this list, that is expected — most of what we have built was not on it either, until somebody asked.
How we work
- 01
Understand
A conversation with the owner: what you sell, to whom, how customers reach you today, and where the work jams. Questions about the business, not about the website.
- 02
Define
One sentence on what will be built and why — including, plainly, when part of what was asked for is not worth building at all.
- 03
Engineer
Repository, architecture, data model, permissions, domain and hosting, design system. The decisions that are expensive to reverse are taken here.
- 04
Build
Design and engineering together, in typed source, one branch per piece of work, and never a commit straight onto the production branch.
- 05
Launch
Domain, certificate, environment and hosting are ours to handle. Then the application is actually driven, on a real device profile and as each role — a green build is not a test.
- 06
Grow
After launch: maintenance, search improvements, new features, and further systems as the business grows. The launch is the start of the relationship, not the end of it.
What we hold ourselves to
- 01
Code you could hand to someone else
A structured repository under version control, typed source, and documentation at the level another developer needs to take over. Configuration is not a substitute for a codebase.
- 02
Security enforced on the server
Permissions are enforced in the read layer, not in the view — a field hidden in the interface is still in the payload. Where an authentication model is deliberately minimal for an internal tool, we write that down rather than imply it is hardened.
- 03
Performance as a constraint
The audience is on mid-range Android phones on mobile data. That is why one project's 3D renderer is ten kilobytes instead of a hundred and fifty, and why layout is measured on a real device profile before anything ships.
- 04
Bilingual is an engineering problem
Arabic and English as peers: locale routing, declared alternates, per-language social images, and an Arabic face chosen for Arabic rather than a Latin font falling back.
- 05
We publish what went wrong
Several case studies here contain a defect we shipped or an approach we got wrong the first time. That is deliberate: a supplier who has never told you about a mistake is a supplier you have not worked with long enough.
- 06
We do not invent a number
No ratings, no testimonials, no manufactured statistics. We removed structured markup from an inherited project that was publishing an aggregate rating that came from nowhere — that is a search penalty waiting to be applied, and not something we will ship for a client.
What gets asked before signing
- What does a website cost?
- There is no price list, because a five-page brochure site and a store with stock, roles and reporting are not the same job. The number is decided after the first conversation and arrives in writing, against the work it pays for — including, plainly, the part we think is not worth building.
- How long does it take?
- A brochure site is weeks; a system with roles and data is longer. The date is written down before the work starts, not after — and what moves it is rarely the engineering. It is content and decisions waiting on your side.
- Who owns the site, the code and the domain?
- You do. The domain is registered in your business's name, and the repository is handed over whole — history, documentation, and enough of it for another developer to take over. We do not keep a key that makes coming back to us compulsory.
- Do you build on WordPress?
- We build in code. But the question worth asking first is whether a rebuild is the right thing at all: for one client already on WordPress we audited and repaired the site instead of replacing it, and recommending against the rebuild was part of the work.
- Do you build in Arabic and English?
- Yes, and as peers rather than as an original and a translation of it: locale routing, declared alternates on every page, and an Arabic face chosen for Arabic instead of a Latin one coping. This site is built that way — switch the language above and watch the address bar.
- What happens after launch?
- The launch is the start of the relationship, not the end of it: maintenance, search work, new features, and further systems as the business grows. And if you decide to continue with somebody else, everything that person needs is already in the repository.
Describe the problem. We will tell you what is worth building.
One conversation is usually enough to know whether there is anything here worth building. If there is not, we will say so — we have said so before.
- 01You describe the problem, in Arabic or in English.
- 02We reply within one working day and ask what actually decides the scope.
- 03You get it in writing — including the part we think is not worth building.