The things people ask before signing

Usually within a week of the scope being agreed. We keep the team small on purpose, so we take on fewer projects at once and start them properly rather than parking them.

Our record so far: a landing page in three days, a brochure site in a week, a full ordering platform in six weeks the first time and one week the second, a live tournament platform in under a week, and an AI agent in eight. A web app or dashboard is normally six to twelve weeks depending on how much of it is genuinely custom. You get a specific date in the quotation, before anything is built.

Yes. We will build you a working demo of what you are asking for, free, before you commit to anything. If it convinces you we carry on; if it does not, you have lost nothing.

Often. We either take a defined piece of the product end to end, or work alongside your team on the parts they do not have capacity for. We will follow your conventions rather than impose ours.

Not by default, but on request and without argument. Tell us and we will sign before the first call if you prefer.

If the software we deliver does not do what the signed scope says it will do, and we cannot fix it, you do not pay for that work. Where the scope has been partly met — some of it working, some of it not — you are invoiced for the part that works and nothing more. We will not ask you to pay for a feature that does not run. The guarantee covers the functionality agreed in writing. It does not cover changes of mind after sign-off, business outcomes such as revenue or traffic, or third-party services failing outside our control. Scope changes are re-quoted, not absorbed silently.

Because no two builds are the same shape, and a price list would either be so wide it tells you nothing or so narrow it is wrong. You get a fixed quotation after we understand what you need — normally within a few days of the first call.

It depends on how familiar the work is. For a build of a kind we have done before, the deposit is 10% to 25% up front and the balance falls in stages against delivery. For work in territory that is new to us, we start by building a minimal working version so you can see it running, and the deposit is 25% to 50%. On websites the first stage is the UI/UX and the main page, so you approve the look before the rest gets built. Whichever applies to you is written into the quotation before anything is signed.

No. We build the software; what it earns depends on your market, your pricing and your operation, none of which we control. Any agency guaranteeing a revenue figure is guessing.

Yes. On full handover we transfer the code and set it up under your own accounts, with no ongoing fee. There is nothing to buy back later.

We keep the CI/CD pipelines running, fix crashes, and include smaller changes. You get an admin panel so you can see what is happening, plus Google Analytics and monitoring configured. Ongoing support runs on a monthly retainer.

Yes. Every build ships with a CMS, and we train whoever is going to use it. You should not need to call us to change a heading.

We hand it over. Code, design files, and setup on your own accounts. No fee, no notice period, no argument.

Next.js, TypeScript and React on the front end; FastAPI, Python and Node on the back; Swift, Kotlin and Flutter on mobile; PostgreSQL on Supabase or AWS for data; Vercel, AWS, Render and Cloudflare for infrastructure. We list what we have shipped, not what we could learn.

Yes. TAP is live and taking real money in two of our builds, and MyFatoorah is routine work. Gateways are a common failure point for agencies outside the region, and it is one of the reasons clients here come to us. The same goes for integrations generally — POS systems, ERPs, CRMs, delivery platforms, live data feeds. If it has an API, we will connect it.

Yes, as part of a retainer. Or we set everything up on your own accounts and step away. Both are normal.

Kuwait City. We work with companies across the Middle East and run projects remotely as standard, with calls in your working hours.