Web Application Development
Scope written as a feature list rather than an outcome. A list of 40 features has no natural stopping point, which is how a 12-week build becomes a 9-month one. We scope to the outcome and cut features against it.
What we build
What does Qanat build?
Qanat builds web and mobile applications, MVPs, AI agents and automation, chatbots, internal tools, system integrations, dashboards, e-commerce and SaaS platforms for UAE companies. Every project is quoted as a fixed price against a written scope, and the code is yours from the first commit.
The list below is what we are asked for most. It is not exhaustive — if what you need is software and it is not here, ask.
Software builds
Scope written as a feature list rather than an outcome. A list of 40 features has no natural stopping point, which is how a 12-week build becomes a 9-month one. We scope to the outcome and cut features against it.
Committing to native iOS and Android before the product is proven. It doubles the build and the maintenance for a difference most first versions never need.
Calling something an MVP while specifying it like a full product. If the build cannot be cut in half without losing the question it answers, it is not an MVP and the budget is being spent on the wrong thing.
Forcing a B2C platform to do B2B. Per-customer price lists, credit terms and multi-step approvals are where Shopify stops being cheap and starts being expensive in workarounds.
Building the product for the first customer. A platform shaped entirely around one client's process is a bespoke build with a subscription attached, and the second customer exposes it.
AI & automation
Starting from the model instead of the task. A demo that impresses in a meeting and fails on the fifth real document is the standard outcome when nobody built an evaluation set first.
Automating a broken process. Automation makes a bad process faster and harder to change, so the mapping session sometimes ends with us recommending a process fix and a much smaller build.
Buying a chatbot when the underlying answer does not exist in any system. If your staff cannot answer the question in ten seconds from a screen, neither can a bot — the real project is the data.
Operations & data
Building what the manager describes rather than what the team does. The spreadsheet always contains three undocumented rules, and they are always the ones that matter.
Treating the happy path as the project. Two systems agreeing when everything works is a demo. The build is what happens when one is down, slow, or returns something the documentation never mentioned.
Building the dashboard before the definitions are agreed. Two departments counting revenue differently is a governance problem, and no visualisation fixes it.
Hiring the next agency before understanding why the last one failed. Roughly half the projects we audit failed on scope and decision-making rather than on code, and a new team walks into the same conditions.
We do not publish a rate card: the price of any of these is decided by scope, not by category. If you need a budget figure before talking to anyone, the UAE software cost guide publishes what the market charges, with every figure sourced. That is researched market data, not our price list.
Start here
A scope call, then a written scope and one fixed price against it. 20% of that price is held back until you accept the finished build, and the scope is yours to take elsewhere either way.