Tell us what the business does and where the current process breaks down. A short reply with a proposed scope follows.
Systems in production
Languages, Arabic & English
Delivery stages, start to support
Infrastructure we operate ourselves
Every message reaches the team directly. A reply follows by email within one to two working days, and it is a practical one: what we understood, what we still need to know, and a proposed next step.
You do not need a specification. The most useful things to tell us are what the business does, how the work is handled today and where it breaks down, who will use the system and in which languages, and anything already in place that the new system has to work with, such as an accounting package, an online store or a set of spreadsheets. If there is a deadline, say so early, because it shapes what we propose.
Write in whichever language you prefer. The team works in both, and every system we build carries both languages, with full right-to-left support, from the first draft.
The email address and WhatsApp link on this page reach the same team as the form. Use whichever suits you; there is no need to send the same message through more than one.
We build commerce platforms, operations and accounting systems, platforms for trades such as health, education and logistics, applied AI, bots, and the infrastructure they run on. If your project is one of these, or a mix of them, this page is the right place to start. The six areas sets out what each one covers.
If the work is a fit, the next step is the first stage of our method: a study of how the work is done today, written down before any code is. That study is what the design, the build and the cost are all based on, so it is worth being candid in it about what does not work now.
We do not quote a price before we understand the work, because what a system costs depends on what it has to do. The team sets it once the requirements are clear. If you want to understand how custom software is priced before you write, this article explains how the cost is structured and why estimates for the same system can differ.
If you are comparing companies, how to choose a software company covers the questions worth asking on a first call, and early signs a software project is going wrong covers what to watch for once one is under way. You can also see the systems we have built and the areas we work in.