Templated policy out of the box
Eligibility, approval thresholds, vehicle class rules, escort rules and advance-notice windows arrive as working defaults you adjust, rather than as blank fields someone has to be paid to fill in.
Solutions · Mid-market ops
Mobility software is built, priced and scoped for programmes with a transport department. You have one person, probably doing this alongside something else. This page covers what that person actually needs — and, further down, the cases where our honest advice is not to buy this yet.
The mismatch
None of these are faults in those products. They are what a product designed for ten thousand seats looks like from six hundred.
Priced for ten thousand employees
Enterprise mobility platforms carry enterprise floors. A programme of six hundred people gets quoted against a minimum built for a programme twenty times the size, and the per-employee economics stop making sense.
Scoped as a programme, not a purchase
A discovery phase, a solution design, an integration workstream and a pilot. All reasonable for a global rollout, and all overhead when one person is going to administer the whole thing.
Configured by someone who leaves
The implementation consultant encodes your policy and goes. Six months later the policy changes and nobody left in the building knows where it was encoded.
Built for a team you do not have
Role separation across a transport manager, a vendor manager, a compliance lead and an analyst. You have one person who is all four, usually alongside another job.
What right-sized means
Mostly about what has been removed — the implementation project, the floor price, the assumed team — rather than what has been added.
Eligibility, approval thresholds, vehicle class rules, escort rules and advance-notice windows arrive as working defaults you adjust, rather than as blank fields someone has to be paid to fill in.
Sites, shifts and an employee list get you to a routed roster. There is no discovery phase to buy, because for a programme this size there is nothing to discover that cannot be seen from the data.
The whole programme is operable by one person from one console, with role separation available if and when you grow into needing it rather than imposed because the product assumes it.
Usage-based, per active employee or per trip. The bill moves with the programme in both directions, which matters more at your size than at ten thousand seats.
Most mid-market programmes start with employee transport because it is the one with a safety obligation attached. Corporate travel runs on the same policy engine and can be added when you are ready, without a migration.
Audit logging, role-scoped access, masked personal data, rate-card enforcement and a three-way match are not a tier you buy up into. The controls are the same ones large programmes run on, which is also what makes an enterprise customer’s security review survivable later.
Getting live
Week one tells you whether to proceed. We would rather you find that out on your own data before signing anything.
Week 1
Employee list, sites and shift patterns in; routes, manifests and costs out. This is where you find out whether the routing holds up on your actual addresses — and it is the step most worth doing before you commit to anything.
Week 2
Adjust the templated policy to what you actually do. Existing operators are set up with their contracted rates; where you are short, supply can be sourced.
Week 3
Live ETA, driver identity and self-serve cancellation. This is the step that removes most of the inbound traffic from whoever is administering the programme.
Then
Travel, additional sites, ERP export, deeper HRIS integration. Each is configuration on a running system rather than a new phase.
When not to buy this yet
This section costs us deals and it stays, because the alternative is selling a programme that fails in month four and takes the reference with it.
A single site, a single shift, under about a hundred commuters
A capable admin with a spreadsheet and one trusted operator can run this well, and probably cheaper. The point at which software starts to win is when shifts, sites or vendors multiply — because that is when the coordination cost, not the fare, becomes the expense.
No contracted supply and no intention of getting any
If every trip is booked ad-hoc on a consumer ride-hailing app at whatever the surge is, there is no rate card to enforce and the largest single lever here does not exist for you. Negotiate supply first; the platform is worth much more afterwards.
Nobody actually owns the programme
If transport is split informally across HR, admin and a facilities vendor with no single owner, a platform will not create one. It will give whoever is eventually appointed a much better starting position, which is an argument for appointing them first.
You are mid-contract with no exit for a year
We would rather say so than sell you a parallel system. Start the data conversation now by all means — the routing analysis is useful whether or not you buy anything — and come back when the contract is actually movable.
Questions
Still unanswered? Our solutions team replies within one business day.
Talk to the team →There is no hard floor, but the honest line is somewhere around a hundred regular commuters, or fewer if you run multiple sites or shifts. Below that a competent admin with a spreadsheet and one reliable operator is genuinely competitive, and we would rather tell you that than have you discover it in month four. What changes the maths is multiplicity — two shifts, three sites, four vendors — because coordination cost grows faster than headcount does.
An employee list with home locations, your sites, and your shift patterns. That is enough to produce routed output you can judge. A rate card and vendor contracts make the cost side meaningful, and HRIS integration makes it maintainable, but neither is needed to see whether the routing works on your own addresses.
That is a reasonable thing to buy for at your size, and yes. taSki holds ISO/IEC 27001:2022 certification and the platform is the same one larger programmes run on — audit logging, role-scoped access, masked personal data and configurable retention are not an upgrade tier. Our security page has the detail, and we complete customer questionnaires directly rather than offering a summary in place of one.
taSki owns no vehicles, but supply can be sourced through the partner network in the cities we operate in, and that is often how mid-market programmes start. Where you already have an operator you keep them — the platform is not a route to replacing your supply, and a vendor whose revenue depended on that would be the wrong one to put between you and your drivers.
Sites, shifts, entities and additional modules are configuration rather than re-implementation, and role separation is there when you have people to separate. The genuine friction points when a programme scales are HRIS integration depth and ERP export mapping, both of which get harder the longer they are left — so they are worth scoping early even if you do not build them yet.
Bring one site’s roster and we will route it and show you the output, at no cost and with no obligation. That is the step that answers the only question worth answering first, which is whether the routing is any good on your addresses rather than on a demo dataset.
Start with week one
Employee locations, your sites and your shift pattern is enough. You get routes, manifests and a modelled cost on your own addresses — free, no obligation, and useful even if you decide against us.
Someone from the team will be in touch within one business day to find a time.
Hi there. How can we help?
Real people, Monday to Saturday