Talk to sales
Half an hour, and a written price the same day.
The qualifying questions are published on this page. Read them first, then decide whether the call is worth your time.
Why the questions are published in advance
Most connectivity sales processes are a form, then a discovery call that discovers what you already told the form, then a deck.
We publish the questions instead. Read them, decide whether the answers are worth half an hour, and if they are, the call is a conversation rather than an interrogation.
You also get a price the same day. Not a range in a follow up email, and not a number that depends on how the call felt.
What a team account gives you
A team account is not a discount code applied to consumer accounts. It is a different object.
There is one pool of data owned by the company, and every traveller draws from it. Unused data returns to the pool at the end of a trip instead of expiring on one person's plan.
That single mechanism is the difference. The rest of the category quietly relies on expiry for margin, and industry estimates put wasted purchased travel data at 20 to 35 percent.
On top of the pool there are five controls, and all five are included at every size.
- Pooled data with no expiry. One company balance, and unused gigabytes go back to the pool rather than being deleted on day 30.
- Caps per employee, hard or soft. A traveller cannot spend past a limit without approval, and finance is never surprised by an invoice.
- Cost centre allocation. The invoice arrives already split the way your ledger expects, with a per traveller breakdown attached.
- Consolidated monthly invoicing in USD, EUR or GBP, with the correct VAT or GST treatment applied per jurisdiction.
- SAML sign in and SCIM provisioning, so a leaver loses access when your directory says so rather than when somebody remembers.
- Spend controls at the policy level, including region allow lists and an alert when a cost centre passes 80 percent of its month.
1 day
to a first reply from [email protected], on a working day
1 hour
from the kickoff call to ten travellers connected on a pilot pool
$0
seat fee at every band, from 5 travellers to 20,000
Pricing bands by team size
| Team size | Annual commitment | Per GB | Invoicing | Identity |
|---|---|---|---|---|
| 5 to 24 travellers | 500 GB a year | $1.36 | Monthly, card or transfer | Google and Microsoft sign in |
| 25 to 99 travellers | 2 TB a year | $1.89 | Monthly, 30 day terms | SAML, SCIM provisioning |
| 100 to 499 travellers | 8 TB a year | $0.89 | Monthly, 45 day terms | SAML, SCIM, custom claims |
| 500 to 1,999 travellers | 25 TB a year | $0.89 | Monthly, 60 day terms | SAML, SCIM, audit export |
| 2,000 and above | Negotiated | From $0.89 | Purchase order, custom terms | SAML, SCIM, dedicated tenancy |
There is no seat fee at any band. You pay for gigabytes and nothing else, and the gigabytes do not expire, so an annual commitment is a purchase rather than an allowance.
How the bands actually work
The rates below are global blended rates across the 145 destinations live today. Wholesale is not uniform, so your real rate depends on where your people go.
A team that travels only inside Europe prices below the band. A team that lives in Australia and New Zealand prices above it.
We show you the blended rate for your actual destination mix during the first call, not after signature.
The seven questions we will ask
| Question | Why we ask it |
|---|---|
| How many people travel, and how often? | Headcount is not what we price on. Twelve people who fly every fortnight cost more than four hundred who fly twice a year. We want trips per year and travellers per trip. |
| Which countries, and in what proportion? | Wholesale rates are not uniform. A team living in Europe and Japan prices very differently from one living in Australia and Brazil. Give us your top ten destinations by nights. |
| What do you spend on roaming today? | Usually the honest answer is that nobody knows, because it lands on personal expense claims. If you have a number, we will tell you whether we can beat it, and we will say so if we cannot. |
| Who owns the phones? | Company issued, personal, or both. It decides whether we provision from your directory or send an install link to a personal device, and it changes the privacy posture we design for. |
| What is your identity provider? | Okta, Microsoft Entra, Google Workspace, JumpCloud or something else. This is the difference between SCIM being a two hour job and a two week one. |
| Do you want caps per person, per cost centre, or both? | Both exist. Per person is easier to explain to travellers. Per cost centre is what finance usually wants. Teams that pick both often end up with a policy nobody can predict, so we push back on that. |
| What has to be true for this to be signed? | Procurement, a security review, a pilot, a specific integration. We ask in the first call so that nothing appears in week six which could have been handled in week one. |
What happens in the first week
| When | What happens | Detail |
|---|---|---|
| Day 1 | Kickoff call, 30 minutes | We ask the seven questions and you get a written price band the same day. There is no slide deck. |
| Day 2 | Console and pilot pool | Your workspace is created with a pilot pool of data. Ten travellers can be live within an hour of the call. |
| Day 3 | Identity connected | SAML for sign in, SCIM for joiners and leavers. Your directory becomes the source of truth, so nobody deprovisions anybody by hand. |
| Day 4 | Policy set | Caps per person or per cost centre, approval thresholds, allowed regions, and what happens when somebody hits a limit at 3am. |
| Day 5 | Security review pack | SOC 2 report, penetration test summary, data processing addendum, subprocessor list and the completed CAIQ, sent as one file. |
| Week 2 | Rollout and invoice format | Install instructions inside your own tooling, a test invoice in the format your finance system wants, and a named contact who answers in under 60 seconds. |
This is the plan we actually run, not an ideal case. Where a security review takes longer than a week, it is almost always because a questionnaire needs a named signatory on your side.
What the pilot proves
Put ten travellers on it for two weeks and three numbers come back.
Provisioning success rate, which should sit at or above 99 percent on supported devices. Median install time, which should be under 90 seconds from tap to attached.
And the real cost per traveller per trip, measured rather than modelled. That third number usually settles the business case on its own.
You will also find out where we are weak. The console shows the same measured coverage data we publish openly, so if your team spends its year in a country where our median is below the market, the pilot will show it. We would rather you saw that in week two than in month seven.
Security review, and what is in the pack
We keep the whole pack ready so it arrives as one file on day 5 rather than as seven emails over three weeks.
It contains a SOC 2 Type II report, a recent penetration test summary, a completed CAIQ, the data processing addendum, the subprocessor list and our incident history.
If your questionnaire is bespoke we will fill it in. Where a control is not in place we write not in place, because an evasion in a security questionnaire is worse than a gap.
Questions procurement asks
What does a team account give me that individual accounts do not?
Is there a per seat fee?
What happens to data we commit to and do not use?
How fast can we be live?
Do you support single sign on and automated provisioning?
Can we set a hard spend cap?
What are the payment terms?
Will you sign our security questionnaire?
Price it before you call us
Consumer rates, measured speeds and the full destination list are all public. Check our arithmetic first, then book the half hour.