What we do.
We build the software people use, we deploy and connect the systems a business runs on, and we operate the infrastructure underneath. Each page below says what we actually do, at the size we actually do it.
capabilities
Software engineering
Websites, mobile applications, and the custom software a business runs on.
Integration and business systems
Odoo, Sage and the systems already running the business, made to agree with each other.
Cloud and infrastructure
What everything else runs on, from the delivery pipeline to the machines.
Cybersecurity
What we deliver is exposed to the internet. This is how we keep it shut.
Being found
The clients who are already looking for you, and cannot find you.
Our products
Software we build and run ourselves, so part of what we sell is already working before an engagement starts.
Alongside client work we build our own software. When the problem you bring us is one we have already solved in a product, you start from something that runs rather than from an empty repository, and the months that would have gone into building it go into fitting it to your operation instead.
These platforms are licensed rather than sold once and left alone. They carry your branding, they run on your data, and they keep improving while you use them.
The one that is running is bmskaler: till and stock software for West African commerce, built around a constraint most point-of-sale software ignores. Each till holds ticket numbers in reserve, so when the network drops the sale still completes, the ticket still prints, the receipt goes out on WhatsApp, and everything rejoins the ledger when the connection returns.
One product sells by the tonne, the sack and the kilo, each at its own price, while stock is held in a single unit. It reports what a paper book never will: stock that has stopped moving, margin that is slipping, unpaid invoices by age and by customer, and the till variance dated under the name of whoever was on the counter.
sectors we build for
Where we are putting product and research effort.
These are the fields our own software is being built for. They are not a restriction on who we work with, which is organisations in any sector.
- Trades
- Businesses whose margin is decided in the field rather than in the office, where the record of what happened is the part that usually goes missing.
- Cyber security
- Where the product has to hold up against someone actively trying to break it, and the standard of evidence is correspondingly higher.
- Army and defence
- Environments with the strictest requirements on who can reach what, where systems have to work without assuming a connection.
- Health
- Where patient data carries obligations that shape the architecture from the beginning rather than being added to it afterwards.
- Hospitality and real estate
- Operations built on occupancy, turnover and timing, where a day of stale information is a day of decisions taken blind.
- Productivity
- The tools people use to do the work itself, where adoption is decided in the first week and rarely revisited.
Bring us the problem.
We start with a working session on your actual operation, not a generic pitch. You leave it knowing what is happening, what is worth fixing first, and what the path forward looks like.