Enterprise
What happens when you get in touch.
This is where the rest of the site points, so it is written as the agenda for that first conversation rather than another argument for having one. If you read it before we speak, we can spend the call on your operation instead of on introductions.
Who this is for
Operational shape matters more than headcount. The characteristics below describe the operations the platform and the teams are actually built around today.
More than one station, or about to be
The problems this platform solves — reconciliation, coverage, a board built from what actually happened — get sharply worse at the second station and worse again at the fourth.
The work is already being done, by people
There is a dispatcher, a recruiter and someone chasing vans. The question is not whether the work exists but whether it should stay on your desk.
The tooling has stopped agreeing with itself
Hours in one system, routes in another, and a spreadsheet holding it together on Friday. That gap is the one the platform exists to close.
You want part of the operation run, not just software
If a tool is all you need, MileMargin on its own is a reasonable answer. The combination is worth more when you want the work taken on.
Who this is not for, today
Said plainly, because finding out on the call wastes an hour of yours.
Procurement that requires SOC 2 or ISO 27001 today
Neither is held. If a certificate has to be on file before you can sign, we cannot clear that yet, and no conversation changes it.
Operations outside Amazon DSP work
The platform underneath is not DSP-specific, but MileMargin and the services are built around how DSPs run. Ask, and the honest answer today may be not yet.
Anyone who needs to buy without talking to anyone
There is no self-serve sign-up, no trial and no published price list. Every engagement starts with a conversation, and that is unlikely to change soon.
Before we talk
Nothing formal. The operational numbers a quote needs are listed on the pricing page — this is about who should be there and what is worth having a view on.
Worth having in the room
- Someone who knows what the daily board actually looks like
- Whoever would own the decision to hand work over
Worth having a view on
- Which parts of the operation you would consider handing over
- What has to stay with your team whatever happens
- What is breaking often enough that you would fix it this quarter
You do not need
- A specification, or a decision
- Budget approval
- A data export, or access to anything
- An answer to every question above — the gaps are useful too
What happens next
The working process, not a funnel. There are no timings here because they genuinely vary with how many stations are involved and which services are in scope — a duration quoted before scoping would be a guess presented as a commitment.
- 01
A first conversation
We ask about your stations, your fleet and where the work currently sits. You ask whatever you need to. Nothing is presented; there is no deck.
- 02
We work out the scope
What we would run, what stays with your team, and where the software fits — written down, and shared with you before it turns into a number.
- 03
We come back with a recommendation
Sometimes that recommendation is to take one service and not three, or to start with software alone. Sometimes it is that this is not the right time, and you will hear that plainly.
- 04
An agreement, if it fits
Scope, boundary, cost and how it ends — gone through with you before signing. Nothing starts until it is agreed in writing.
- 05
Standing the work up
How long this takes depends entirely on which services are in scope and how many stations. We will give you a shape once we know both, and not before.
What you end up with
The outcomes of an engagement, rather than a list of what the software does.
A written scope, not a category
The specific work we run and the specific decisions that stay yours, named — so nobody discovers the boundary six weeks in.
A team you can name
The people doing the work inside your operation are identifiable, and you can know who they are.
One record per station day
Planned against actual, hours, cost and exceptions on the same line — and it is the same record our teams work from, not a report generated for you.
One party answerable
When something goes wrong there is no question of whose fault it is between a vendor and a staffing agency. It is ours.
Before you send the message
Three things people ask in the last minute before getting in touch. Everything else is answered on the pages that own it.
Is this a sales call?
It is a scoping conversation. We ask more than we present, and one of the outcomes is being told that this is not a fit — which happens and is not a negotiating position.
Are we committing to anything by talking?
No. Nothing starts until it is agreed in writing, and there is no trial that quietly begins billing in the meantime.
We already use software we like. Is this a rip-and-replace?
No. Services are sold separately from software, so a team can run your dispatch or hiring while you keep the tools you have. What we would need is the information to flow, not the tool to change.
Getting in touch
Everything above exists so that this part can be short.
Book a demoYou will get an answer about what exists today rather than what we intend to have — the same as everything else on this site.