Software development
Piton HQ builds, owns and licenses the operating platforms its divisions run on. We ship the unglamorous parts too: the access control, the audit trail, the escalation paths, and the reporting that shows whether any of it worked.
The divisions
Each division builds for one industry and licenses what it builds to the operators who run it. Clinical and Build are both in production; Learn and Staffing are in development behind them. Each card says where it actually stands.
Software for the work around care rather than the chart itself — scheduling, procedure records, credentialing, facility reporting and billing reconciliation. Access enforced per role, an audit trail that survives a records request, and figures a hospital can check against its own invoice. Running in production today under licence.
The same operational spine pointed at residential construction: jobs and schedules, subcontractor coordination, change orders, and keeping the budget and the schedule agreeing with each other while both are still moving. Live, with its first builder running real jobs on it.
Competency, training records and the evidence that somebody was actually signed off — the part of education that has to survive an audit. In development, generalised from the credentialing work in Piton Clinical.
Scheduling, credential expiry, contractor pay, and the reconciliation between hours worked, work delivered and money out. In development, generalised from the dispatch and payroll work in Piton Clinical.
What comes as standard
These are not add-ons and they are not a later phase. A platform without them is a prototype, whatever it looks like on the screen.
Who can see what, enforced at the database rather than in the screen that happens to be open. A hidden button is not a permission.
Who did what, when, and what it looked like before. Written as the action happens, not reconstructed afterwards from logs.
What the system does when the expected thing does not happen — nothing important should depend on somebody noticing.
Exports that agree with the source, and say so plainly when they cannot — a total that is quietly wrong is worse than no total.
How it goes
Each stage ends in something written down, so you can stop at the end of any one of them and still be holding something useful.
We map the work as it runs now — the steps, the handoffs, and the places it breaks.
Data model, access model and the screens, agreed before anything is built on top of them.
Shipped in increments to an environment you can log into and use, not demoed from a laptop.
We operate and maintain it, or hand it over with the documentation to run it yourself.
Start here
A first conversation is about your process, not our software. If we are not the right fit for it we will say so early.