A Thoyz OS console screen representing licensable software
Licensing & custom builds

When your process needs its own tools.

For the buyer who wants to license part of the platform we built to run our own logistics, or commission a build, and it leads with the constraints, because that is where a software engagement goes wrong.

Start a scoping conversation ↗
Licensethe parts of Thoyz OS that generalise, ledger, billing, renewals
Or builda focused tool for a process, by people who have run it
Honestsmall team, no 24/7 desk, no SOC 2 today, stated up front

License or build

What we can license, and what we would build.

Recognise your own problems in it, or have us build for the one that isn’t covered.

The parts of Thoyz OS that generalise, the trip ledger and billing engine, the document-renewal tracking, the change-control trail, the emissions calculation, can be licensed to a logistics operation that recognises its own problems in them.

Where an off-the-shelf fit doesn’t exist, we build: a focused tool for a specific process, designed by people who have run that process rather than only diagrammed it.

How an engagement works

Four steps, scoped against the team we actually have.

1

Scope

We map the process and agree what the tool must do, and, as important, what it will not do.

2

Fit or build

We tell you plainly whether existing modules fit or a build is warranted.

3

Deliver

Built in stages against a real workflow, so value arrives before the whole thing is done.

4

Hand over

With the documentation and the support terms agreed up front.

What we’re honest about

The constraints, led with.

Because that is where a software engagement goes wrong.

We are a small team, and the platform is maintained alongside a live transport operation. That means we do not run a 24/7 support desk, we do not hold a SOC 2 report today, and we scope timelines against the team we actually have, not the team a sales deck would imply.

For the right engagement, that is a feature: you work directly with the people who built the thing. For the wrong one, a mission-critical system needing round-the-clock support from day one. We will tell you it is the wrong one. The platform, and what is not in it yet →

Describe the process. We’ll tell you whether we’re the right build partner.

Lead with the constraints, and a scoping conversation gets to the honest answer faster, whether that is a licence, a build, or a straight no.

Start a scoping conversation ↗
License what generalisesledger, billing, renewals
Or build focused toolsfor a process, by people who ran it
Honest about the constraintssmall team, no 24/7 desk, no SOC 2 today