Growth4 min read
Choosing a software house: 12 questions
Twelve questions to ask every agency you shortlist, including us: who owns the code and when, what is handed over at each milestone, who actually writes it, what the quote excludes, trade licence verification, governing law, and what each evasive answer predicts.
Danial AhmedFounder & engineering manager
On this page
Ask these of every agency you shortlist, including us. They are ordered so that the first four eliminate most of a bad shortlist in a single call, and each one has an answer that is either specific or evasive — there is rarely a middle. None of them is about portfolio quality, because portfolio quality is the thing every agency has already optimised for. Our own answers live on how we work.
Ownership and exit
1. Who owns the code, the designs and the data, and when? A good answer names the clause and says you own the source, the designs and the IP outright. A bad answer is "on final payment" — which is defensible commercially but means you own nothing if the relationship ends mid-project.
2. What is handed over at each milestone, and what is held back until the end? The answer you want is "nothing is held back": the whole repository, history included, handed over at every milestone rather than released once at final payment. An agency that hands over only at the end leaves you with no leverage in a dispute and nothing to continue from if the relationship stops.
3. What exactly do we receive at handover? Repository access is the floor. Ask for: environment configuration and secrets inventory, deployment runbook, architecture note, dependency list with versions, database schema documentation, and a recorded walkthrough. Agencies who have done real handovers can list these without thinking.
Delivery and accountability
4. Who writes the code, and are they employed by you? Ask for names, seniority and location. Subcontracting is not automatically a problem; undisclosed subcontracting is. The follow-up question is which of those people are on your project full-time versus split across four.
5. What happens when we disagree about whether something is a bug or a change? The good answer references a written acceptance criterion. Without one, every ambiguity becomes a negotiation, and negotiations during delivery are how fixed-price projects turn variable.
6. What is the warranty, in days, and what does it cover? Thirty days post-launch covering defects against the agreed specification is a reasonable market position. "We'll look after you" is not a warranty; it is a sentiment with no expiry date and no scope.
Money, scope and risk
7. What is the payment schedule tied to? Milestones tied to deliverables, not to calendar dates. Dates pay for elapsed time; deliverables pay for progress. A 40/30/30 split against three verifiable milestones is a healthy shape.
8. What does the quote exclude? Ask for the exclusions list in writing. Content, translation, photography, third-party licences, paid infrastructure, and post-launch changes are the usual omissions, and together they are rarely small.
9. What is the smallest useful thing you could ship for us, and when? Agencies that think in increments will answer with something concrete in four to six weeks. Agencies that think in big-bang delivery will explain why that is not possible. The second answer correlates strongly with projects that slip.
The UAE-specific checks
10. What is your trade licence number and issuing authority? Verify it. Mainland licences are checkable with the relevant emirate's economic department, free-zone licences with the free zone. Also ask for the Tax Registration Number if they are VAT-registered — invoices should carry it, and it is verifiable through the Federal Tax Authority.
11. What law governs the contract, and which courts? Onshore UAE courts and DIFC courts are different systems with different languages of record and different costs. For a supplier and client both onshore, onshore is normal; if a DIFC clause appears, ask why, and price the difference in enforcement cost.
12. How do you handle personal data, and will you sign a data processing agreement? Any agency touching your customer data is a processor under the UAE's data protection regime. The answer should reference where data is hosted, who has access, retention, and a willingness to sign a DPA without a three-week internal debate. The PDPL checklist covers what good looks like on the client side.
What the answers tell you
Score each agency out of twelve as you go. The pattern to watch for is that firms which answer one to six precisely tend to answer ten to twelve precisely as well, because what the list is testing is operational maturity rather than design talent.
You are not buying a portfolio. You are buying a team's behaviour on the worst week of the project — and these twelve questions are the cheapest available preview of it. If cost is the next question, how to read a website quotation in Dubai covers what actually moves one.