# RFQ template: IoT & device fleets

Fill this in offline, then copy the answers into the online RFQ form.
The checklist items come from the same fields the form uses. No prices are included.

For connected devices: local profiles, roaming and fleet data.

## Request details

- Work email: 
- Company: 
- Company website: 
- Company type: 
- Your country: 
- Timeline: 
- Request type: 

## Checklist

### Requirements and scope

- [ ] Describe what the service will carry
  - Why it matters: The use case decides which product model and route fit.
  - What a good answer looks like: One paragraph: the application, who uses it, the traffic or data type, and what a good outcome looks like.
  - Your answer: 

- [ ] List the sites, systems and endpoints
  - Why it matters: A quote is scoped per site and per endpoint, not per company.
  - What a good answer looks like: A short table with each site or system, its country and city, and its role at each end.
  - Your answer: 

- [ ] Give the date you need service or a test
  - Why it matters: Lead time depends on access, registration and testing, not only on the order.
  - What a good answer looks like: A target date, whether it is fixed or a preference, and the first step you need.
  - Your answer: 

- [ ] State your company type and what you sell
  - Why it matters: It sets the contract and onboarding path.
  - What a good answer looks like: CPaaS, eSIM brand, MVNO, IoT maker, enterprise, carrier or reseller, in one line, with the main markets.
  - Your answer: 

### Volumes and growth

- [ ] Give a monthly volume for each line
  - Why it matters: Messages, data, devices and bandwidth are sized in different units.
  - What a good answer looks like: One figure per product: messages, terabytes, active devices or Gbps.
  - Your answer: 

- [ ] Add the peak, not only the average
  - Why it matters: Capacity is sized for the busy hour, and an average hides it.
  - What a good answer looks like: The peak rate and when it happens, plus how you measured it.
  - Your answer: 

- [ ] State expected growth over the first year
  - Why it matters: Growth changes the headroom the design needs.
  - What a good answer looks like: A percentage or range, the assumption behind it, and any launch dates.
  - Your answer: 

### Coverage and destinations

- [ ] List every destination country or region
  - Why it matters: Coverage and rules are per country, and a partial list returns a partial quote.
  - What a good answer looks like: Country names or ISO codes, split into launch markets and later phases.
  - Your answer: 

- [ ] Ask which destinations are direct and which are off-net
  - Why it matters: The handoff and the testing differ, and so does the route you can compare.
  - What a good answer looks like: A per-country answer: direct, off-net, or not available, with the handoff named.
  - Your answer: 

- [ ] Say where devices start, move and stay
  - Why it matters: A local profile, a roaming profile and multi-IMSI fit different movement patterns.
  - What a good answer looks like: A country list per fleet segment, with the expected time in each country.
  - Your answer: 

### Technical

- [ ] State the eSIM standard: SGP.22, SGP.32 or both
  - Why it matters: Consumer devices and IoT devices use different provisioning paths.
  - What a good answer looks like: The standard, the device types, and who manages the profile lifecycle.
  - Your answer: 

- [ ] Describe the activation flow
  - Why it matters: QR code, one-tap and push-to-unit need different platform work.
  - What a good answer looks like: The flow, the trigger, and which side runs each step.
  - Your answer: 

- [ ] Say what addressing you need
  - Why it matters: A private APN, fixed addresses and IPsec are design choices, not add-ons.
  - What a good answer looks like: APN model, IPv4 or IPv6, fixed or dynamic addresses, and the sites that connect.
  - Your answer: 

- [ ] Paste the module or device band list
  - Why it matters: Band support decides which networks a device can use.
  - What a good answer looks like: LTE and 5G bands, the module model, and any certification already held.
  - Your answer: 

- [ ] Say whether devices need SMS or voice
  - Why it matters: A data-only profile has no voice, SMS or VoIP capability.
  - What a good answer looks like: Yes or no per fleet, the fallback channel, and any exception you need.
  - Your answer: 

### Compliance and KYC

- [ ] Have the company documents ready
  - Why it matters: Verification is part of onboarding, not a step after the quote.
  - What a good answer looks like: Registration number, registered address, and the documents your legal team can share.
  - Your answer: 

- [ ] Name the person who can complete verification
  - Why it matters: A named contact keeps the review from stalling.
  - What a good answer looks like: Name, role, work email and time zone, with a backup.
  - Your answer: 

- [ ] Write a one-paragraph use-case statement
  - Why it matters: It supports company verification and the route decision.
  - What a good answer looks like: Who sends or connects, to whom, why, and what content or data moves.
  - Your answer: 

- [ ] Declare whether the profiles are data-only
  - Why it matters: A data-only declaration changes the registration path in some markets.
  - What a good answer looks like: Yes or no per fleet, with any voice or SMS exception named.
  - Your answer: 

### Commercial terms to ask about

- [ ] Ask what the billing unit is
  - Why it matters: Messages, sessions, terabytes, Mbps and ports are invoiced differently.
  - What a good answer looks like: The unit, the rounding rule, the measurement window, and what is excluded.
  - Your answer: 

- [ ] Ask about minimum volume and term
  - Why it matters: A minimum changes what a small first order can look like.
  - What a good answer looks like: Minimum quantity, minimum term, and how a ramp is handled.
  - Your answer: 

- [ ] Ask for a test route or test profile
  - Why it matters: A test is the only way to compare delivery or latency before you buy.
  - What a good answer looks like: What the test includes, how long it runs, what results you receive, and who supports it.
  - Your answer: 

- [ ] Ask about term, renewal and change
  - Why it matters: The terms decide how fast you can add a destination or a site.
  - What a good answer looks like: Initial term, renewal, notice period, and how additions or upgrades are handled.
  - Your answer: 

- [ ] Ask how support and reporting work
  - Why it matters: A named escalation path and consistent numbers matter more than a general statement.
  - What a good answer looks like: How a case is opened, who owns the escalation, the report fields, frequency and export format.
  - Your answer: 

- [ ] Ask what happens at the end of the term
  - Why it matters: Number porting, profile migration and address return take planning.
  - What a good answer looks like: Notice period, porting or migration support, and what is handed back.
  - Your answer: 

---

No prices. Every request is quoted per destination, volume and model. Registration and filing rules are confirmed per market.