Twenty-five sectors, and what we have already shipped into each one.
Every page below names the platforms already running in that sector, the operator types it serves, and the parts we would build from zero. Where we have nothing shipped, the page says so and describes the engineering practice instead.
Twenty sectors with platforms already running
These are the sectors where something we have built is already in production. Each page names the platforms, links to every one of them, and states which operator types they do not cover.
The number on each card is what is actually shipped and linkable, not a marketing figure. Where a sector has two platforms rather than thirty, the page says two, and it explains which parts of that sector are custom work as a result.
Not sure which of these describes what you are building?
Book a scoping callFive sectors served by engineering rather than by a catalogue
In these four we have no shipped product, and the pages say so in the first paragraph rather than implying otherwise. What sits behind them is the engineering practice, named and linked.
This is a deliberate distinction rather than a gap we are hiding. Adapting a consumer marketplace to a plant floor or an insurance book would produce something worse than starting properly, so those engagements are custom every time and the page is written accordingly.
Working in a sector that is not listed on this page?
Tell us what you are buildingTwo tracks, and how to tell which one you are on
Every sector page is organized around the same choice: adapt something already running, or build from zero. Most buyers arrive assuming they know which, and about a third of them are wrong.
We are the unusual case of a company that sells both, which means the recommendation is not structurally biased. A firm with only products will find a way to fit you to one; a firm with only consultants will find a reason to build.
The sentence no competitor can say in full
Boutique consultancies understand your sector. Broad agencies list thirty industries. Productized shops hand you a demo. Each is one third of what an evaluation needs.
The third question is the one worth pressing. A vendor whose answer is "we would need a partner for that" has told you where their engagement ends, and it is usually the point where your build gets interesting.
Want a view on which track your build actually belongs on?
Book a scoping callWhat each sector page actually contains
These are not overview pages. Each one is written for a technical buyer evaluating whether we understand their sector, and it is structured the same way so you can compare across them.
The delivery arc, week by week
Seven phases naming what each requires, which have no shortcut, and where a shipped platform removes the work. The point is to show we know what week eight of your build contains.
Eight operator types
Because "fintech" or "logistics" is not one buyer. Each page splits the sector into eight and states which can start from a platform and which need custom work.
Diagrams of the real mechanism
Money flows, custody boundaries, dispatch logic, chain of custody - drawn with the failure mode at each hop rather than as decorative process arrows.
What the sector requires
Six requirements specific to that domain, written as the things that break platforms rather than as a feature list anybody could publish.
Every platform, linked
The products named on each page link to their own live page, so the count can be checked rather than taken on trust.
Twelve real questions
The ones that come up in a first call, including the ones with awkward answers, answered the way we would answer them on the call.
Everyone said they had done our sector before. Only one of them could show us the thing they had built and then tell us honestly which half of our problem it did not solve.
The failure pattern this page is built around
That gap is the whole reason these pages exist. Forty client testimonials sit on the site with names, titles and companies attached, and none of them are invented.
Want the sector page for your industry walked through with an engineer?
Book a technical callIf your sector is not one of the twenty-five
The list above reflects where we have shipped or where we have a named practice. It is not a statement about what we will take on, and the distinction matters.
A hundred and thirty-five engineering practices sit behind these pages, covering languages, platforms, disciplines and hired roles. Most work that arrives does not match a sector page exactly, and that has never been the constraint. What decides whether we are the right team is whether the problem is a software problem, not whether we have published a page about your industry.
Product engineering
Full-stack builds across the languages and frameworks your team already runs, or a considered recommendation where the choice is open.
Software developmentCloud and platform
Infrastructure, pipelines and the operational tooling that decides whether a team can deploy on a Friday afternoon.
DevOps engineeringData and AI
Pipelines, analytics, machine learning and generative systems, with the evaluation discipline that tells you whether any of it works.
Data engineeringSecurity engineering
Review, hardening and the evidence trail an audit needs, built alongside delivery rather than commissioned once at the end.
Cybersecurity engineersEnterprise platforms
SAP, Salesforce and the integration work around them, built to supported interfaces so the connection survives the next upgrade.
SAP developersTeams and leadership
Augmentation, dedicated teams and technical leadership, for organizations whose gap is capacity, ownership or direction.
IT consulting and staffingQuestions about how we work
The ones that come up before a sector page is even opened.
Are these twenty-five the only sectors you work in?
No. They are the sectors where we have shipped platforms or a named engineering practice. A hundred and thirty-five practices sit behind them, and most work that arrives does not match a page exactly.
Do we own the source code?
Yes, in full, on every engagement and both tracks, deployed on your infrastructure. No per-seat licence, no per-transaction fee, no runtime dependency on us.
Are the platform counts real?
Every tile on every sector page links to that product's own page. The counts are what is shipped and linkable rather than a marketing figure, which is why some sectors say two and others say thirty.
Which track will you recommend?
Whichever fits, and we sell both, so the recommendation is not structurally biased. Each sector page states which of its eight operator types can adapt a platform and which need custom work.
How fast can a shipped platform go live?
Six working days, branded and deployed on infrastructure you own. Sector extension beyond the platform as it ships is custom work, scoped and quoted separately. It never covers your licensing, store review or supply recruitment.
How long does a custom build take?
Two to eight weeks, scoped per project. Genuinely complex programmes - regulated finance, insurance, industrial systems - are quoted in writing beyond that before anything starts, and the sector page says so rather than printing a number it cannot hold.
Do you work with our existing team?
Yes, in four engagement models: augmentation, a dedicated team, fixed scope or technical leadership. Which one fits depends on whether your gap is capacity, ownership or direction.
What happens after launch?
Sixty days of dedicated support, six months of priority bug resolution and twelve months of updates, plus a handover your own team exercises while we are still reachable.
Can you work in a regulated environment?
Yes. Several sector pages cover regulated domains directly, including the compliance deliverables that arrive with the build and the assessment support that follows it.
Where do we start?
Open the sector page closest to what you are building and read the delivery arc. If it describes your problem accurately, the call will be short and useful; if it does not, tell us and we will scope from what you actually have.
Question not answered here?
Ask us directlyBuilding something none of these twenty-five pages describes?
Tell us what it isTell us what you are building.
Open the sector page that fits, or skip it and describe the problem. We will tell you which track is right, and we will build whichever it turns out to be.
A first call takes about thirty minutes and covers four things
What you are building
In your words, not fitted to a category on this page.
What already exists
Team, systems and anything running today.
Constraints that are real
Licences, regulators, dates and budgets that will not move.
Who operates it after
Which decides how much of the build is documentation.
Those four answers are usually enough for us to tell you which track fits, roughly what it costs, and which of these twenty-five pages is worth your time. If none of them is, that is a normal answer rather than a problem - there is no category of software work we treat as out of scope.
