Solutions · by industry

Different sector.
Different unit
of work.

What separates one sector from another is not which features it needs. It is what the business counts — a transaction, a load, a work order, an appointment — and which resource runs out first. Answer those two questions and you know which of the nine to start with, and which number should be on the wall.

Configuration

How each sector is
set up.

There is no sector edition of anything. Selecting a sector changes which of the nine applications you buy, what the records are called on screen inside them, and which constraint the scheduler optimises against.

What does not change

The parts nobody
forks for you.

Industry software usually means a sector edition with its own release train, and a vendor who quietly stops investing in the smaller vertical. There is no sector edition of a FlowZa AI application, so there is nothing to fall behind.

01 — NO SECTOR EDITION

Configured, not forked

A patient, a guest, a consignee and a subcontractor are the same kind of thing wearing different labels, so a sector is a configuration of an application rather than a separate build of it. You get the release everyone else gets.

02 — NO VERTICAL FORK

Nine products, not seventy-two

The nine each have their own release train, which is honest. What they do not have is a healthcare edition, a construction edition and a public-sector edition each running a version behind. There is one Finance, and every sector runs it.

03 — ONE SECURITY STANDARD

A familiar review

Identity, permissions, residency and audit are built to the same standard in every application and enforced inside each one. A conglomerate running four of these sectors on five FlowZa AI applications reviews the same controls five times, not five different security models.

Side by side

Eight sectors, and
where to start.

Comparison of eight industries by unit of work, binding constraint, deciding metric, and which of the nine FlowZa AI applications to deploy first
IndustryUnit of workBinding constraintMetric that decidesStart with
Retail & HospitalityThe transactionShelf space and footfallSales per m²POS, then Finance
Logistics & FreightThe loadVehicle and driver hoursMargin per loadLogisPro, then Fleetza
ManufacturingThe work orderMachine capacityCost per unitFinance, then LogisPro
Professional ServicesThe engagementBillable capacityUtilisationFinance, then PMS
ConstructionThe jobPlant and crewCost to completeFinance, then Fleetza
HealthcareThe episode of careClinician time and roomsCost per episodeFinance, then Spa Master
Wellness & BeautyThe appointmentTreatment room and therapistRoom utilisationSpa Master, then POS
Public SectorThe caseBudget appropriationCost per caseFinance, then PMS

“Start with” is a first deployment, not a ceiling — the second column is where most customers go within a year. Sectors that run vehicles add Fleetza; sectors that print anything a customer scans add QRForge; sectors with members rather than customers add Club. Each arrives already holding your parties, items and entries.

Next

Bring your own
edge cases.

Every sector has the process that no vendor demo covers. Those are the interesting forty-five minutes — send us the awkward one in advance.