A project is only finished when people use it without being told to. This is a selection of what we have built, and the way we run a project from first call to handover.
Filter by the kind of work. Client names are withheld where an agreement requires it.
Showing 7 projects
Gambit Gulf Contracting, Dammam
A complete operating system for an underground infrastructure contractor: one platform covering accounting, payroll, projects, fleet and maintenance, plus a field mobile app and a bilingual corporate website. Replaced spreadsheets and separate systems across the whole company.
Gambit Gulf Contracting, Dammam
The ERP in the crew's pocket. Drivers run their trips, site teams raise material and maintenance requests, and employees submit expenses by photographing the receipt — each one landing straight in finance with VAT and cost centre attached.
Valeur X — our own product
Our SaaS accounting and ERP platform. Every customer company runs in its own database behind a shared control plane that handles identity, billing and provisioning — with ZATCA e-invoicing signed inside the ledger itself.
Valeur X (in-house product)
Boards, calendars and dashboards for teams who would rather ship than sit in a status meeting. Tasks, owners, deadlines and status on one board that updates live for everyone.
TwalaMeals — Canada
A three-sided delivery platform: customers order food, groceries, pharmacy and more from local stores; drivers take assignments and route to the door; merchants run their own storefront and dashboard. Live across Canada.
Daily Breathing
A guided breathing app for iOS and Android: timed exercises for morning, focus, energy, relaxation and sleep, immersive guided experiences, structured lessons, a BOLT breathing-efficiency test and streaks — plus the marketing site behind it.
The same four stages whether the project is a website or a platform for three hundred users.
We map what you actually need and what it would take, then price it. A number given before that conversation is a guess, and guesses get corrected later at your expense.
You approve a written scope and a price against it. Changes are quoted separately rather than absorbed quietly into a timeline that keeps slipping.
Working software on a staging link from the first weeks, not a demo at the end. If something is heading the wrong way, you find out while it is still cheap to change.
Source code, documentation and accounts are yours at the end, and your team is trained on them. Staying with us for support is a choice, never a requirement.
For most projects yes, once we have asked them. Some clients — particularly in government and finance — are under agreements that prevent it, and we will say so rather than invent a reference.
A website is typically four to eight weeks, a mobile app or platform three to six months, and an AI pilot two to six weeks. We commit to a date only after discovery, because a date given before that is a sales figure rather than a plan.
Yes, before any detailed discussion if you prefer. It is the reason several projects on this page describe the sector rather than name the client.
A warranty period is included, during which anything that does not work as agreed is fixed at no cost. After that a support agreement is optional, and you keep everything either way.
Whether it is software that runs your business or a factory that produces your product, you get one partner, one plan and one point of responsibility.