Solutions

Built for a specific industry, or not built at all.

Three lines of business, each with its own delivery model. What they share is that we own the result — the software, the data migration, the training and the support that follows.

Vertical Industry ERP

Purpose-built enterprise resource planning for industries whose operating reality does not fit standard modules.

An automotive trading company and a fit-out contractor have almost nothing in common operationally, yet both are routinely sold the same ERP with different labels on the screens. The result is a system that records what happened after the fact, while the actual business keeps running on spreadsheets and messaging groups.

We build the opposite: a system that matches the shape of the business, so the people doing the work have a reason to use it.

Automotive trading

VIN-level inventory with in-transit, in-bond and in-showroom states
Purchase, shipping, customs and landed-cost tracking per unit
Multi-currency purchasing and settlement with realised and unrealised FX
Chassis-to-invoice traceability for audit and warranty claims
Sales pipeline, reservations, deposits and delivery handover

Construction & interior fit-out

Project budgets against bills of quantities, with committed and actual cost
Variation orders tracked from request through client approval to billing
Subcontractor packages, progress claims and retention release
Procurement and material issue tied to the project, not just the warehouse
Cash-flow forecast built from the billing schedule rather than guesswork

Across both

Role-based access aligned to your real approval hierarchy
Arabic, English and Chinese interfaces with correct right-to-left layout
VAT treatment appropriate to UAE requirements
Deployment on your infrastructure or a hosting arrangement we manage
Documented APIs so the system is never a dead end

Curated Software Distribution

A short, opinionated list of enterprise platforms — selected, localised, deployed and supported by us.

Buying enterprise software is easy. Making it actually take hold inside an organisation is not. The gap is usually not the product: it is tenant design, data migration, integration with what you already run, administrator capability, and someone to call when it breaks.

We only represent platforms we are prepared to be judged on, and we take responsibility for that gap rather than handing over a licence key.

Platforms we represent

Lark — messaging, documents, approvals, calendar and company directory brought together as a single digital workplace
Amap — geocoding, routing, fleet visibility and delivery operations for logistics and field teams
Adjacent line-of-business tools selected case by case for a specific client requirement

What we take responsibility for

Requirement fit assessment before anyone signs anything
Licensing, tenant provisioning and organisation structure setup
Migration from existing tools, including historical data where feasible
Integration with your ERP, finance system or internal applications
Administrator enablement and end-user training
First-line support in English, Arabic and Chinese

Lark and Amap are trademarks of their respective owners. The scope of each partnership, and what it covers commercially, is confirmed in writing during commercial discussion.

03 In active development

CorpOS — AI-Native Enterprise Management

Our flagship programme: an operating layer where AI agents carry the work between systems, and people make the decisions that deserve a person.

Enterprise software has spent three decades getting better at recording work after it happens. CorpOS is our attempt at the harder problem — moving the work itself.

The premise is that a company already has an operating model: how a request becomes an approval, how an approval becomes a purchase, how a purchase becomes a payment. Today that model lives in people's heads and in the gaps between systems. CorpOS makes it explicit, gives agents the context to execute it, and puts a person at the points where judgement, liability or relationships are involved.

Design principles

The operating model is the product — not a chat window added to an existing screen
One company knowledge layer, so an agent answers from the same facts a person would
Every automated action is attributable, reviewable and reversible
Human approval where judgement matters; automation where it genuinely does not
Open interfaces to the systems a company already runs

CorpOS is under active development. We are working with a small number of design partners ahead of general availability — if the problem sounds like yours, we would like to hear from you.

Not sure which of these you need?

That is a normal place to start. Describe the process that is causing pain and we will tell you which of the three — if any — actually applies.

Talk to our team