We build the systems your company runs on.

What we do

• Put AI to work. We find where AI actually saves your people time, then build it into the tools they already use. No pilots that stay in the slide deck.
• Build internal systems and applications. Operations hubs, approvals, pricing, procurement, customer portals. One data layer underneath, with permissions and an audit trail, and screens on top that change as the business does.
• Build products. Data platforms and publications people subscribe to, and software sold on its own. Two of ours are in the list below.
• Connect what you already have. Accounting systems, document stores, practice systems, ERPs. Integrations that move the data so nobody has to retype it.
• Run what we build. Hosting, monitoring, changes and support on a monthly retainer. A fixed number of senior hours from one team that knows your system.

Things we have built

• A subscriber data platform on the Norwegian continental shelf: rigs, fields, licences, wind. Seven years, still running.
• An aquaculture intelligence publication: every farm, every licence, lice and disease reported weekly.
• A reporting platform for accounting firms: their clients' operations reports, generated from the practice system's own exports.
• A practice assistant for a litigation firm that reads every system the firm already has, with its ethical walls intact.
• An invoicing engine for a financial software vendor: transactions across products, tiered pricing, posted to the ERP.
• An operations hub for an exporter of telecom towers, from quote request to bill of lading.
• An IoT platform handling encrypted real-time data from a device fleet, with firmware updates over the air.
• A publications engine: one system that ingests, resolves and publishes, serving several intelligence publications over one pool of entities.
• A document sharing and signing service with engagement tracking, used for every proposal we send.
• Our own companies run on systems we built, from bookkeeping to client delivery.

How we work

We find it easier to talk about something you can click around in than about a description of it. So we usually start with a first draft: a working version of the screens, built from whatever you already have. A spreadsheet, an export, a few files. Some of it will be off. That is fine. It gives us something real to work from, and the conversation gets a lot easier.

From there it goes wherever it makes sense: a fixed-price build, ongoing work on a retainer, or just hosting and running something you already have.

Contact