Custom Software & Data Products

Internal platforms, built on data you already own.

A governed purchasing workflow, a CRM built around your own sales process, an inventory system with variance reporting. Each is a platform over data you already own, with roles, an audit trail and a workflow behind every screen.

illustrations · shape only — no client named

The next step

Book an assessment call

30 minutes · with the engineer who would scope the work

one-page recap within 2 business days of a call that progresses


Platform access path A user's request passes through a role gate before it can reach the application service and the system of record, all inside the platform's own data boundary. The role gate, the application service and the system of record each also write to an append-only audit trail. The platform does not read or write any system outside this boundary. Platform data boundary Userrequests access Role gate(RBAC) Applicationservice System ofrecord Audit trailappend-only Not touched: any system outside this boundary. Platform data boundary Userrequests access Role gate(RBAC) Applicationservice System ofrecord Audit trailappend-only Not touched: any system outside this boundary.
A request passes through a role gate before it reaches the application service and the system of record, inside the platform's own data boundary. The role gate, the application service and the system of record each also write to an append-only audit trail; nothing outside the boundary is touched.

A lot of what a growing operations team needs is not a new off-the-shelf product. It is a screen over data that already lives in a spreadsheet, or in a system nobody trusts anymore, with the roles and the record-keeping a spreadsheet can't give you. These platforms share a shape: a defined set of roles, an audit trail that survives an argument, and a workflow that matches how your business runs its process, not how a vendor assumed it would.

company delivery history · founder-asserted ·

What these platforms look like

The shapes below are illustrations of what this looks like, not client stories — the same register the parent hub uses for its own examples, and for the same reason: we have no client work we are permitted to name, and /case-studies/ publishes none.

company delivery history · founder-asserted ·

A record that can say who did what

None of these shapes is worth building if the platform can't say, later, who did what. That is decided before the first screen exists, not retrofitted once the tool is in daily use.

Roles come first.
Who can see a record and who can approve an action is designed as part of the data model, before any screen is built against it.
Writes are appended, never edited in place.
Where a record has to survive a dispute — a reversed approval, a corrected count — the entries are chained so that altering one breaks the chain, and the break is visible.
Every entry names a person.
The record shows who approved, who adjusted, who overrode — never a shared login or a service account standing in for a name.

company delivery history · founder-asserted ·

Built to be handed over

An internal platform gets the same handover standard as the rest of our custom software: the code in your source control from the first commit, documentation written for the next engineer, a deployment pipeline your team can run without us, and a runbook for when something breaks. The roles and the audit trail are exactly the decisions that standard exists for. They need to be written down, not reverse-engineered from the code a year later.

Continue

Start with a call about the tool nothing off the shelf provides.

Book an assessment call

30 minutes · with the engineer who would scope the work

one-page recap within 2 business days of a call that progresses