No rebuild on day one
A working platform from the start, with the maintenance, hosting and support arrangements written down rather than assumed.
Divisions & platforms
Piton HQ owns the platforms. Each division builds for one industry, and licenses what it builds to the operators who run it. A platform is finished when somebody can be held to what it reports — not when the screens are done.
Software for the operational work around care rather than the medical record itself. Access is enforced per role at the database, so a permission cannot be lost by rendering the wrong screen; every read and write of patient data is recorded; and an export that cannot be reconciled says so on its face instead of presenting a total that quietly disagrees with the invoice beside it.
What it covers
The same operational spine pointed at homebuilding. A builder's real system today is usually a spreadsheet, a group text and one person holding the sequence in their head. The interesting problem is not storing that — it is keeping the schedule and the budget agreeing with each other while both are still moving.
The running system — create an account and put a job through it
What it covers
The part of training that has to survive an audit rather than the part that delivers a lesson: what someone was signed off to do, who signed it, when it expires, and the evidence behind it. It is the piece Piton Clinical already needs, being built out as something that stands on its own.
What it covers
The administrative weight behind any business placing skilled people onto other people's sites: who is available, who is still credentialed, what they actually did, and what they are owed for it — with the three of those reconciled rather than tracked separately and argued about monthly.
What it covers
How the group is put together
One entity owns and licenses; the divisions build; the operating companies run the work. Keeping those three apart is what makes each of them answerable for its own part.
Holding & licensing entity
Licensees
How we hold them
Piton HQ builds and owns the platforms, and licenses them to the operators that run them. It keeps two things apart that are usually tangled together: the company delivering a service, and the software that service depends on.
A working platform from the start, with the maintenance, hosting and support arrangements written down rather than assumed.
Work done for one operator hardens the platform for the next, instead of forking into versions nobody can maintain.
Who owns the code, who owns the data, and what happens to each if the arrangement ends — settled in the agreement, not afterwards.
Start here
The most useful first conversation is about how the work runs today and where it breaks. The specification comes out of that.