Web development
Marketing sites and web apps in Next.js, ready for Arabic.
A preview URL you can open from the first build
Software studio — UAE
We design, build and run the software that companies across the UAE work in every day.
<48h
Brief to fixed proposal
100%
Senior engineers on your build
Yours
Repository, accounts and domain
100%
Code ownership, in writing
The stack we ship on — in production, not on a slide.
What we build
Six services with a page of their own, and the stack behind each one.
Marketing sites and web apps in Next.js, ready for Arabic.
A preview URL you can open from the first build
iOS and Android from one codebase, shipped to both stores.
Both store accounts and keys stay yours
CRM and internal systems shaped around how you already work.
One module demoed and accepted at a time
AED storefronts with UAE payment rails and VAT handled properly.
Four payment rails, all sandbox tested first
Retrieval and assistants wired into the data you already hold.
A passing score agreed before the build
Office networks, cloud infrastructure, and support that answers.
One hour response when a site is down
How we operate
Eight things you can check before you sign anything.
Soukone is our own AED storefront — a concept build you can open, not a slide about one.
<48h
Defects found after go-live, fixed at no cost.
The same team runs your build from the first workshop to the last deploy. Nothing is handed to a second office.
We reply within four business hours.
100%
Tick the pieces, tell us your deadline, and one itemised quotation comes back before anyone writes code.
Industries
We start from the workflow you already run, never from a template.
Listing portals, broker CRMs and owner dashboards.
Clinic systems, patient portals and careful data handling.
AED storefronts, stock sync and delivery integrations.
Dispatch boards, driver apps and proof of delivery.
Onboarding flows, reporting and audit-ready records.
Booking engines, guest apps and property dashboards.
Enrolment portals, course platforms and parent apps.
Service portals, bilingual forms and accessibility work.
Field reporting, asset registers and offline-first tools.
Practice management, billing and client portals.
Stack
Eight disciplines, named tools, nothing on the list we have not run in production.
10 tools
9 tools
10 tools
10 tools
10 tools
8 tools
11 tools
9 tools
A drawing of an interface assembling itself: a header, a navigation rail, a wide panel and two tiles arriving one after another into a finished layout.
77 tools across eight disciplines. Named because we run them in production, not because a logo fits the grid.
Work
We opened in 2026, so there are no client logos to borrow — these three are ours, designed and measured by the same team.
Engagement
Pick the model, then pick the pieces. The quotation comes back scoped to both — itemised, in writing, and free to ask for.
One scope, one price, one delivery date.
One fixed pricefor the whole agreed scope
Senior engineers who sit inside your team.
Monthly rateper engineer, per month
Someone owns the system after launch.
Monthly feeagainst agreed response times
| What you get | Sysai | Typical vendor |
|---|---|---|
| An itemised written quote before you commit | Yes | No |
| Full repository handover at every milestone | Yes | No |
| Demos on a staging URL, on your cadence | Yes | No |
| Senior engineers only, no handover | Yes | No |
| UAE PDPL considered before launch | Yes | No |
| 30-day warranty written into the contract | Yes | No |
Every row on the left is a commitment we put in writing. Ask any studio the same six questions — the answers are the comparison.
How we work
You always hold something at the end of a stage — a quote, a prototype, a build, a runbook.
Five stages, in order: Scope, Prototype, Build, Launch, Run. Each one ends in something we hand over. The cards below carry the detail, and each turns face-up as you scroll; the text is complete either way.
01
We map the workflow and quote the build.
Artifact: Fixed proposal
02
Clickable screens to argue with before code exists.
Artifact: Clickable prototype
03
Short cycles, each one ending in something you can hold.
Artifact: Demo on your cadence
04
We deploy, watch it, then hand over the keys.
Artifact: Runbook and repos
05
Patches, monitoring and the next release.
Artifact: 30-day warranty
The team
25 in-house engineers, and one person who owns the relationship.
25
Employed here, not sourced per project. The people who scope your build are the people who write it, and nothing is passed to a cheaper team after signature.
Founder & engineering manager
Named on the trade licence, and the person who answers your email. Every proposal, every scope and every escalation goes through him.
Deliberately few builds at a time — two new projects a quarter, so the bench is never spread across more than it can carry.
Why us
Questions
Whatever your scope costs — which is why we quote it rather than publish bands you have to fit yourself into. A five-page site and a fifteen-page bilingual one are different projects, and a band wide enough to cover both tells you nothing. Pick the pieces you need on the quote form, say how fast you need them, and one itemised quotation comes back within 48 hours. Asking costs nothing and commits you to nothing.
As long as the scope you choose actually needs, planned backwards from the date you give us. We stopped publishing a typical schedule because it read as a threat to anyone whose own deadline was shorter and as a promise we had not earned on anyone whose project was bigger. Tell us the date in the second step of the quote form and we will say honestly what fits inside it, what does not, and what would have to change.
We map the workflow you actually run, not the one on the org chart. That means two or three working sessions, a look at the systems you already pay for, and a written list of what is in and out of scope. You end up holding a scoped brief, an architecture sketch and a fixed quote. If the honest answer is that you should not build it, we say so and you keep the brief.
Senior engineers on our own payroll, named on the proposal before you sign it. Whoever scopes your system is the one who builds it and runs the demos — there is no handover to a cheaper team after signature, because there is no cheaper team. We take two new builds a quarter for exactly this reason. If we cannot staff yours properly in the window you need, we will tell you before you sign rather than after.
Yes, before the first technical conversation. Send yours and we will review it within a day, or use our two-page mutual version if you would rather move quickly. Beyond the paperwork: your data stays in systems you control, everything we write for you is yours and is handed over as we go, and nothing you show us appears in a case study, a pitch deck or on this website without your written agreement.
Defects present at go-live are fixed at no cost for thirty days, and the test is the written acceptance criteria, so neither of us argues about it later. After that there is an optional care plan covering monitoring, patching, small changes and an agreed response time, quoted monthly against the system you actually have. It is cancellable with thirty days' notice, and you keep the repositories, the cloud accounts and the domain either way.
Often, yes. We are set up to sit beside an in-house team rather than replace one, so we join your board, your standups and your review process and write the same acceptance criteria either way. On an existing codebase we start with a short paid audit: what is safe to build on, what needs replacing, and what either route involves. You keep that document whether or not we carry on.
Still deciding whether we are the right studio for it?
Read how we workWriting
E-commerce
Send the rough version. You get an itemised quote, a plan built around your date, and an honest answer on whether it is worth building at all.