Before You Start
The most useful thing you can bring to a first conversation is not a specification. It is a clear statement of the outcome you want and the constraint that matters most — budget, deadline, or a specific capability you must have. Everything else can be worked out.
We do not charge for the first call or for the preliminary analysis, and we do not require a specification to give you a useful answer. If we think the project should be smaller, cheaper, or done differently, we will say so before quoting rather than after.
How We Work
Every project starts with scoping, produces a written proposal with itemised costs, and then runs in two-week cycles with something working at the end of each one. You see progress on a real build rather than in a status report, and you can change priorities between cycles.
You get access to the repository, the ticket board and the environments from day one. We would rather you verify progress than take our word for it, and it makes the eventual handover trivial.
Commercial Terms
We work on three models. Fixed price against a written scope, when the scope can genuinely be pinned down. Dedicated team at a monthly rate per engineer, when priorities will shift. Time and materials for maintenance and small work.
Whichever model applies, you see the estimate before work starts, the invoice matches what was agreed, and you own everything we produce. There is no clause that makes leaving us expensive.
Working With Clients Abroad
We work regularly with companies in Europe, the Gulf and North Africa. Turkey is one to two hours ahead of Western Europe and within a short shift of Gulf hours, so there is real overlap in the working day rather than one exchange every twenty-four hours.
Project communication runs in English, Arabic-language coordination is available, and contracts, NDAs and invoicing in English are routine. We can also work entirely inside your repositories, cloud accounts and tooling so that nothing sensitive ever leaves your environment.