Divisions & platforms

Four divisions, one engineering standard.

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.

Healthcare operations

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.

Platform
Piton Clinical
Status
In production today
Operated by
PICC Access of Atlanta LLC, under licence
Regulatory
HIPAA — operates as a Business Associate

What it covers

  • Referral intake, dispatch and escalation
  • Procedure documentation and clinical photography
  • Clinician credentialing, competency and expiry tracking
  • Facility reporting through an external portal, under the facility's own logins
  • Reconciliation between what was performed and what was invoiced

Residential construction

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.

Platform
Dormer
Status
In production. Live with its first builder
Intended for
Home builder professionals, under licence
Regulatory
No patient data — outside HIPAA scope

Open Dormer

The running system — create an account and put a job through it

What it covers

  • Jobs, phases and schedules across multiple active builds
  • Subcontractor coordination and trade scheduling
  • Change orders, and the invoices they land on
  • Budget against actual cost, reconciled as the build runs
  • Inspections, punch lists and progress photos from the site

Education and competency

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.

Status
In development. Nothing is in production
Origin
Generalised from the credentialing work in Piton Clinical
Regulatory
Scope depends on the setting; assessed per deployment

What it covers

  • Competency frameworks and skills matrices
  • Training records with the evidence attached
  • Sign-off, renewal and expiry tracking
  • Audit-ready export of who was qualified to do what, and when

Workforce operations

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.

Status
In development. Nothing is in production
Origin
Generalised from the dispatch and payroll work in Piton Clinical
Regulatory
Scope depends on the setting; assessed per deployment

What it covers

  • Availability, scheduling and shift coverage
  • Credential and licence expiry, per person and per site
  • Contractor pay, including per-unit and per-procedure models
  • Reconciliation between hours worked, work delivered and money out

How the group is put together

The structure.

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

Piton HQ LLC

Piton Clinical

Healthcare In production

Piton Build

Construction In production

Piton Learn

Education In development

Piton Staffing

Workforce In development

Licensees

PICC Access of Atlanta LLC Piton Clinical
Home builder professionals Piton Build

How we hold them

Built once, licensed to operate.

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.

For the operator

No rebuild on day one

A working platform from the start, with the maintenance, hosting and support arrangements written down rather than assumed.

For the platform

One system, improved once

Work done for one operator hardens the platform for the next, instead of forking into versions nobody can maintain.

For both

Clear ownership

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

Bring us the process, not the spec.

The most useful first conversation is about how the work runs today and where it breaks. The specification comes out of that.