PXNT · for investors

The platform is the asset. The products prove it.

PXNT wasn't designed on paper. Its engine, Augustus, grew out of two very different products, healthcare and running physical sites; its service network, Mercurius, out of selling services. Both run on one platform.

Request the investor deck The products

PXNTAVGVSTVSMERCVRIVSMDXTBBGIECPKproves the enginevalidates the networkfuture unified products

The thesis

Build the hard half once. Let each product specialize it.

One platform, built once

People, places, work, risk, evidence and consequences are the expensive half of every operations product. PXNT models them once.

Two very different businesses prove Augustus

Care and running physical sites look nothing alike, yet their daily work runs the same way underneath. It held up in both.

A third proves Mercurius

ECPK turns customers, providers, subscriptions and places on a map into a service network that works: Mercurius, proven on its own.

The products

Three products, each with its own page for investors

Each product tells its own market story. Here is what each one is, what it runs on in PXNT, and where to read the rest.

MDXT
Care operations
PXNT Augustus
PXNT applied to people-centred healthcare operations: dossiers, care plans, visits, clinical work, qualifications, evidence and longitudinal follow-up.
On PXNT Its investor page
BBGI
Site operations
PXNT Augustus
PXNT applied to physical operations: staffing, rounds, alarms, incidents, risk, duties, evidence, escalation and handover.
On PXNT Its investor page
ECPK
Service operations
PXNT Mercurius
A service-network product for customers, storefronts, providers, subscriptions, dispatch, location-aware delivery and billing.
On PXNT Its investor page

Where it goes

ECPK is the obvious next product to take Augustus.

Not forced, and not finished. Today ECPK runs pickups, service requests, provider dispatch and job completion on its own flow. Later, PXNT can model the same work as operations:

Service request
What's needed
The job
Only qualified providers
The work, step by step
Steps and proof
Problem found: the follow-up starts by itself
Approval
Billing

Then ECPK runs on both: the network and the engine.

ECPK · Mercurius

Storefront
Subscriptions
Providers
Customers
Billing

ECPK · Augustus

Jobs
Steps
Risk
Proof
Follow-up
Qualification

How it earns

Three revenue lines on one cost base

Subscriptions per platform

Each platform sells to its own market, under its own brand, as software customers pay for every month.

One cost underneath

The platform is paid for once and shared by every product on it, so each new customer anywhere improves the economics of all of them.

Risk kept apart

Separate brands and separate data: a setback in one market does not reach the customers of another.

the next productAVGVSTVSMERCVRIVSBuilt once, shared by allIts own dataorganization, sites, people and workIts own dataorganization, sites, people and workIts own dataorganization, sites, people and workBuilt once, shared. Data never shared.

Why it compounds

Every platform makes the others better

01
A fix in one is a fix in all
Protection built for the strictest market, care, protects every product.
02
What one learns, all get
A better way to sign in, alert or bill, found in one field, becomes part of the core.
03
Each launch is faster
Every product built on the platform leaves it more complete for the next.

The platform

Traction and financing

The figures are in the deck.

Customers, usage, revenue and the current round are in the latest investor deck, with the figures as of that week.

Request the investor deck