What we build
Narrow software for specific industries.
We are not building one platform to serve everyone. Each product starts with a group of people doing a particular job, and a decision or a process that is costing them money in a way they can name.
Where we work
Four areas, chosen because they share a shape: real operating costs, time pressure, and people who are underserved by software written for much larger companies.
Decision tools for operators
Software that answers one expensive question fast. A price, a margin, a go/no-go — computed from the operator’s real costs rather than an industry average, on a phone, in the moment the decision is actually made.
Shipped in logistics, where a driver has minutes to price a load.
Local commerce and delivery
Marketplaces that connect a customer, an order and someone to fulfil it. The hard parts are never the map — they are dispatch, timing, trust between strangers, and paying people correctly.
An active area of work for us.
Industry operations and ERP
The systems a business actually runs on: inventory, costing, scheduling, documents, cash. Built narrow and industry-specific rather than as another general platform to be configured for a year before it is useful.
An active area of work for us.
Productivity and internal tools
Tools for the work around the work — the tracking, reporting and coordination that quietly consumes a small team’s week and usually lives in a spreadsheet nobody trusts.
An active area of work for us.
On what is not listed here
We have work underway in more than one of these areas. We do not name a product before people can use it — an announcement is a promise, and an unshipped promise is how software companies lose the trust they need most at the beginning. When something ships, it appears on the home page with its status.
How we build
The same engineering standard applies to every product, from the first one onward. It is deliberately more than a company this size is expected to carry, because the alternative is retrofitting it later under pressure.
Tested before it ships
Every product carries an automated test suite that runs on each change, with a branch-coverage bar and journey tests that exercise the real flows a customer takes. A feature is not done when it works once.
Accessible by default
Interfaces are measured against WCAG 2.2 AA, not eyeballed. Our software is used in cabs, kitchens and vehicles — glare, gloves and one-handed use are the normal case, not the edge case.
Reviewed for security and privacy
Application security review against the OWASP standard, row-level database isolation between accounts, secret scanning in the build, and a written record of what data each product holds and for how long.
Operated, not just launched
Error monitoring, uptime checks, a written rollback and incident procedure, and a named severity scale. We assume our software will break and plan for the hour it does.