Software product
StaffFlo
StaffFlo is the workforce side of TheHubb: hiring, scheduling, attendance and performance for teams that never sit at a desk. It is not released, and there is nothing on this page to sign up for. What follows is the problem it is being built for, what covers that work today, and what is deliberately not here yet.
The problem it is designed for
A workforce that never sits at a desk gets recorded in pieces, and the pieces are held by different people.
A person's week exists in four places
The application, the schedule, the timesheet, and somebody's memory of how it went. Each is a fragment of the same person, and none of them is the record.
The schedule is built against who is available in theory
Licences, hours already worked this week, who called out last Friday and who cannot legally drive tomorrow are all facts — held somewhere other than the schedule being built.
Attendance is reconciled by conversation
Somebody remembers that a shift changed hands on the morning it happened. A clock does not, and by payroll the two accounts have to be argued into agreement.
Performance has no durable trace
Over a year, the only lasting record of how somebody worked is what their manager can recall. That is the row of the panel below with no answer, and it is the clearest single reason this product is being built.
What exists today
Nothing you can use. There is no version of StaffFlo running anywhere you could be given access to, and this page is not a preview of one.
There is no waitlist, no private beta and no launch date. When there is something worth using it will appear here.
What does exist is the work it is meant to carry, and every part of it is being handled today. The panel below is what handles which — and the fourth row is the honest answer that nothing does.
What covers this work today
Three of the four are answered by something real. Each row resolves to a registry entry, so this panel cannot claim coverage from something that does not exist.
What covers this today
- Hiring and onboardingEnd-to-end DSP HR & recruitingManaged
A team sources, screens and onboards your drivers, and carries the paperwork through to day-one readiness. You keep the hiring bar and the final decision. It is people doing this, not software you operate — which is why it is a service with a scope rather than a feature with a screen.
- Building the daily boardDSP dispatch servicesManaged
A dispatch team builds the board and handles the exceptions that start arriving at six in the morning. Scheduling software would help them; it would not replace the phone calls, which are most of the job.
- Hours and attendanceMileMarginLive
Hours reach the station-day record because reconciling a day requires them. That means the hours exist and are accurate the same evening — but they are there as a cost on a route, not as a record of a person's week, and the difference is exactly what StaffFlo is for.
- Performance over timeNot covered yet
Nothing covers this today — not a product, and not a service. It is the one row here with no answer, and it stays on the page for exactly that reason: a coverage map that listed only what is covered would be worth nothing.
What is deliberately not on this page
Each of these would be easy to add, and each would be untrue today.
A screenshot or a mockup
There is no interface to photograph. Every product surface on this site is real DOM showing real structure, so a rendering of software that does not exist would be the only fabricated thing on it.
A launch date
A date is a promise somebody has committed to. Nobody has. When there is a date it will be because a commitment was made, not because a page looked empty without one.
A waitlist or a private beta
Both would take an email address in exchange for a place in a queue that does not exist — and this site collects nothing at all, which is stated on the security page and checked on every build.
A feature list
A list of what unreleased software will do is a specification, not a product. It would also be the fastest way for this page to promise something the finished thing turns out not to do.
How this page changes when it ships
The shape above is the page, and it is built to survive its own product launching.
When part of StaffFlo becomes real, a row in the panel changes what covers it — from a team to the product — and this page gains a description of what that part does. Nothing here gets rewritten and nothing gets removed, including the row that has no answer. A page that has to be rebuilt on launch day was written as an announcement rather than as a description of the work.
MileMargin and StaffFlo
Two products on one platform, doing different jobs. Neither requires the other, and they are priced separately.
MileMargin is about the operation's day
Routes, hours, cost, and the record of what actually happened at a station between opening and closing. Its unit is a day.
StaffFlo is about a person over time
Hiring, scheduling, attendance and how somebody has worked across months rather than hours. Its unit is a person. It is not released.
Where they touch
Hours, and only hours. A shift is both a cost on a station day and a fact about a person's week. Today that record sits in MileMargin, because reconciling a day is what needs it — which is why hours are the one part of the workforce problem already covered by software rather than by people.
When only one is relevant
- If the problem is that the numbers arrive too late to act on, MileMargin is the whole answer and StaffFlo would add nothing to it today.
- If the problem is hiring, coverage or who is on the board tomorrow, no software here solves it yet. The managed teams do, and that is a conversation about services rather than about products.
- If the problem is knowing how somebody has worked over a year, nothing here solves it today — including the managed teams. That gap is named rather than left out.
There is no bundle and no discount for taking both. Neither product requires the other, and one of them cannot be bought at all.
There is nothing to sign up for, and no queue to join. If this work needs covering now, the conversation is about the teams already doing it rather than about software that is not finished.