We are software engineers, not sector specialists, and we will not pretend to know your business better than you do. What we do bring is a clear view of the technical constraints each sector imposes — and the failure modes that follow from ignoring them.
A note on how this page is written. It describes the engineering constraints that characterise each sector and how we design around them. It is not a list of clients, and nothing here is presented as a case study. Where we have permission to discuss specific work, we do so directly with the people asking — not on a public page.
01 — Sectors
Movement of physical things, tracked by people who are rarely at a desk. The defining constraints are intermittent connectivity and events that arrive out of order.
Where a rounding error is a legal problem. Correctness, traceability and reconciliation outrank every other consideration, including speed of delivery.
Law, accountancy, consultancy and agencies. Document-heavy, deadline-driven, and unusually sensitive about who can see what.
Traffic that arrives in spikes and stock that must not be sold twice. The hard part is rarely the storefront — it is everything behind it.
Long-lived equipment, proprietary protocols and systems that predate the web. Integration matters more than interfaces.
Where the software is the business. Multi-tenancy, entitlements and release safety have to be right from the first schema, because retrofitting them is brutal.
02 — Regulated environments
In several of these sectors the requirements are not only functional. Retention periods, audit trails, data residency and access control are stated by a regulator, and the system has to be able to prove it complies.
We are engineers, not your compliance advisers — that role belongs to your counsel. What we do is treat the obligations you give us as hard requirements, implement them explicitly rather than incidentally, and make it possible to demonstrate them on demand.
03 — Fit
Saying this out loud saves everyone a month.
We are a small senior team and we scale slowly on purpose. For programmes that need large parallel headcount, a bigger firm will serve you better and we will say so at the first call.
We will propose a smaller scope that ships on time with its tests intact. If the scope is genuinely fixed and the date is genuinely immovable, we are not the right supplier for that project.
Clinical systems, aviation certification and similar domains carry obligations that require dedicated expertise. We can build alongside a specialist who holds it, but we will not claim it ourselves.
Our process depends on a client representative who can decide and approve. Where nobody has that authority, projects stall regardless of who builds them — and we would rather name that risk before the contract than after.
The list describes where we happen to have worked, not a limit. Describe the constraints and we will tell you honestly whether they are ones we understand.
HALDIR LTD · HE 459882 · Nicosia, Cyprus