The clients we work with, and the systems we build

UltraTech Kuwait

A full-stack IT contractor nobody searching could find

The problem

UltraTech had been delivering networking, fiber, CCTV and cybersecurity work across Kuwait since 2015, and none of it was reachable by anyone who did not already know the company. Buyers looking for exactly those services had no way to establish, from outside, that the capability existed.

What was built

A bilingual English and Arabic site covering the full service range, built on a proper relational database schema rather than hardcoded pages, with an admin backend that manages every piece of content on it — services, pages and enquiries — without a developer in the loop.

What changed

The company's service range is now published and indexable in both languages, and content is maintained in-house through the admin panel instead of going back to a developer for every change.

• Arabic + English (RTL)
• Relational database schema
• Custom admin backend

Disclosure — UltraTech Kuwait is a sister company under common ownership, not an arm's-length client. The work is real and the site is live and checkable; what it does not demonstrate is that somebody chose us over an alternative.

A barcode scanner app that failed in direct sunlight

The problem

The app was already in daily use, built on a version of its scanning stack that was several releases out of date. It failed in exactly the conditions it was bought for: outdoors and under direct sun, the camera could not resolve a code at all, so staff fell back to reading numbers off the label and typing them in — the task the app existed to remove.

What was built

A rebuild on a current scanning stack, with camera exposure and focus behaviour tuned for high-glare conditions rather than left on library defaults, plus a direct integration into the customer's own database so a completed scan writes to the record it belongs to instead of into an export nobody reconciles.

What changed

Scanning completes in the conditions that previously defeated it, including direct sunlight, and results land in the customer's database without a manual re-entry step in between.

• Barcode scanning
• Camera capture tuning
• Customer database integration

ADTCO — Al-Daajani General Trading & Contracting Co.

A Kuwait contractor whose site described the company but not the work

The problem

ADTCO has traded since 2006 across oil and gas, construction, electrical and mechanical systems, IT infrastructure, ISO certification and several lines beyond those. All of it sat behind a handful of generic WordPress pages that named the company and covered its range in a paragraph. Someone searching for any single one of those services found nothing, because no page on the site was about any single one of them — and the build carried errors that had been there long enough to stop being noticed.

What was built

A rebuild from a brochure into a structured site with a page for each service line, written to say what that service covers and who it is for instead of one paragraph covering everything. The search work then ran on that structure rather than ahead of it: pages first, because a page that does not exist cannot rank for anything.

What changed

The company's full range is now published as roughly thirty indexable pages instead of a handful, each service reachable on its own terms by someone who has never heard of the firm.

• Migrated off WordPress
• Next.js
• Per-service page architecture
• On-page SEO

A spec-sheet catalogue no off-the-shelf store builder could model

The problem

A retailer outside Kuwait, selling a technical range across a national market, where every product carries a specification — chemistry, voltage, capacity, cycle life, controller parameters. Hosted store builders model a product as a name, a price and a variant, so everything past that became a plugin, a workaround, or a field edited by hand one product at a time. Pricing structures and per-product search metadata hit the same ceiling. The catalogue was the business, and the tool it lived in could not describe it or let the team maintain it.

What was built

A custom commerce system designed around the catalogue rather than around a platform's assumptions, with an administration backend where specifications, pricing and per-product SEO fields are all first-class and edited in one place — together with the parts a store builder does not offer at any price, including the sizing calculators and dealer locator a technical range actually needs.

What changed

The catalogue is now maintained in-house from a single backend — specifications, prices and search metadata edited directly by the people who own the data, instead of being worked around in someone else's product model.

• Custom e-commerce
• Specification-driven catalogue
• Per-product SEO fields
• Custom admin backend

A document that had to be editable on screen and exact on paper

The problem

Tailoring one document per recipient usually forces a choice between two bad options: keep a dozen near-identical copies and let them drift out of sync, or edit a single copy destructively and lose the wording that was taken out. Anything edited in a browser then prints approximately — margins shift, pages break in the wrong place, and what was laid out on screen is not what comes out.

What was built

An in-place editor with no forms: every element is click-to-edit, with sixty steps of undo and autosave to browser storage. Content can be hidden rather than deleted, so a section switches off for one recipient and back on for the next without the text ever being lost. Print rules target A4 at fixed margins with page-boundary guides visible while editing, so the printed page matches the edited one instead of approximating it, and the same content exports to PDF, Markdown, plain text or a JSON backup. Where the browser's saved copy and the source file disagree, the tool detects the conflict and asks which should win rather than silently choosing.

What changed

Content is edited in place and exported without a separate publishing step, and the A4 output matches what was on screen rather than approximating it.

• Next.js 16
• React 19
• Tailwind CSS v4
• Print CSS (A4)
• Local autosave

Disclosure — Built in-house as our own tool. Nobody commissioned it and nobody paid for it, so it is not evidence of being hired — it is included because the pattern is the transferable part: non-destructive editing and print-exact output are what any quotation, contract or certificate system needs.

Managing firewalls and switches across sites from one screen instead of many logins

The problem

The company operated firewalls and network switches across multiple physical sites, each administered separately through its own device console by whoever held that device's credentials. There was no single view of status across locations, no shared record of who could change what, and access was effectively all-or-nothing per device rather than scoped to a person's actual role.

What was built

A web-based management panel with real-time monitoring of firewall and switch status across all sites, switch configuration and control from the same interface, and role-based access so a given user's login determines which sites and which modules they can see or change. Devices are polled and controlled over SSH and vendor APIs — including FortiGate, pfSense/OPNsense and MikroTik RouterOS — rather than through screen-scraped device dashboards, with alerts and activity logs centralized instead of sitting on each device individually.

What changed

Network status across every site is now visible from a single dashboard, and access to each site and module is controlled by role instead of by who happens to hold a device's password.

• Next.js / React
• Role-based access control
• SSH / API device polling
• FortiGate
• pfSense / OPNsense
• MikroTik RouterOS
• Multi-site architecture