Question 1

How does an engagement start?

Accepted Answer

Every engagement opens with a short discovery call to understand the outcome you are after, your constraints, and your timeline. Within a few days we follow with a written proposal — scope, milestones, and the team we would assign. Nothing is committed until that proposal is signed, so the first conversation carries no obligation.

Question 2

How long does a typical project take?

Accepted Answer

A focused marketing site or product landing usually ships in three to five weeks. A production web or mobile application typically runs eight to fourteen weeks from kickoff, depending on scope and integrations. We work in two-week cycles with a visible build at the end of each one, so you are never waiting in the dark for a single big reveal.

Question 3

How involved do we need to be during the build?

Accepted Answer

As involved as you want to be. The default rhythm is a weekly review plus a shared board you can check any time. We need timely feedback at the end of each cycle and one empowered decision-maker on your side, but we deliberately keep meetings light so your team can stay focused on its own work.

Question 4

Do we work with a dedicated team or a shared pool?

Accepted Answer

You get a small, named team assigned to your project for its duration — typically a lead engineer, a designer, and a product partner, scaled up only when the work genuinely calls for it. The same people stay with you end to end, so context is never lost in a handoff.

Question 5

What happens after launch — do you offer ongoing support?

Accepted Answer

Yes. Every build ships with documentation and a handover walkthrough so your team can run it independently. If you prefer, we offer a monthly care plan covering monitoring, dependency updates, small enhancements, and priority response. You are never locked in — the codebase and infrastructure are entirely yours.

Question 6

Can you take over or extend an existing codebase?

Accepted Answer

Often, yes. We start with a short technical audit to assess the current state, risks, and the fastest safe path forward. We are candid if a rebuild would serve you better over time than patching, and we will tell you plainly either way rather than quietly building on a fragile foundation.

Question 7

Who owns the work you produce?

Accepted Answer

You do. On final payment, all intellectual property — source code, designs, and assets created for your project — transfers to you in full. We retain no hidden license over your product. Any third-party or open-source components are documented with their licenses so there are no surprises later.

Question 8

Will you sign an NDA?

Accepted Answer

Gladly, and early. We are happy to sign your NDA before discovery, or to provide a mutual one if you prefer. Confidentiality is treated as the default for everything we discuss — we will not reference your project publicly or in our portfolio without your explicit written consent.

Question 9

How do you handle our data and credentials?

Accepted Answer

Sensitive data is encrypted in transit and at rest, and access follows a least-privilege model — people see only what their role requires. Credentials live in a managed secrets store, never in source code or chat. We follow a secure development lifecycle with code review on every change and conduct in-house penetration testing on critical paths before release. These are practices, not certifications we claim to hold.

Question 10

Can our data stay within the UAE?

Accepted Answer

Yes. We can architect deployments with UAE data-residency options when your compliance or procurement requirements call for it, and we are comfortable working within a region of your choosing. We will map data flows with you up front so everyone understands exactly where information lives and who can reach it.

Question 11

Do you build bilingual and right-to-left products?

Accepted Answer

It is one of our specialties. We design and engineer for English and Arabic from the first wireframe — proper right-to-left layouts, bilingual typography, localized content, and number and date formatting — rather than retrofitting it at the end. Adding further languages later is straightforward because the foundation is built for it.

Question 12

Where are you based and which time zones do you cover?

Accepted Answer

We are based in Dubai and work primarily across Gulf and European hours, with flexibility to overlap other zones for key sessions. Most collaboration is remote-first and asynchronous, with on-site working sessions in the UAE when a project benefits from being in the same room.

Frequently asked questions

Process & timeline

Working model

IP & NDA

Security & data

Languages & locations

Still have a question?