Industrial & Manufacturing Automotive Fleet & Commercial Vehicles

Fleet Sales

High-stakes purchases and complex multi-party buying decisions across consumer and commercial segments.

Example organizations in this space: Holman Enterprises Mike Albert Fleet Enterprise Fleet ARI

This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.

Inside this journey
  1. Qualification

    Confirm budget range, decision-makers, timeline, and fleet scale to validate investment in a full discovery.

    Qualification Questions

    Fit: fleet scale, composition, and regulatory complexity

    • Roughly how many vehicles are in scope for this program? Options: Under 50 (below minimum scope), 50-500, 501-2,000, 2,001-20,000, 20,001+ (above supported range)
    • Which vehicle categories make up the majority of that fleet? Options: Sedans and light passenger cars, SUVs, Light pickup trucks, Medium duty trucks, Specialty equipment or upfits, Mixed across categories, Other
    • Do you operate across multiple states or require specialized compliance such as commercial registrations or CDL requirements? Options: Single state, standard registrations, Multi-state, up to 3 states, Multi-state, 4-10 states, Multi-state, 11+ states, Yes, specialized compliance requirements

    Technology and integration readiness

    • Which integration endpoints are already available or planned for a managed fleet program? Select all that apply. Options: Telematics provider credentials available, Telematics provider in place, credentials pending, No telematics in use, Fuel card program in place, Maintenance vendor integrations available, Registration and title systems access available, Other
    • If you selected telematics or other integrations, which vendors or data access methods will we use?

    Budget

    • Is there an allocated budget or expected annual fleet spend range to support a managed fleet engagement? Options: Under $1M, $1M to $5M, $5M to $20M, $20M to $100M, Over $100M, Budget not yet defined

    Decision makers and timing

    • Who needs to be involved or sign off for a full discovery and eventual commercial decision? Select all that apply. Options: Fleet manager or operations lead, VP of Operations, Procurement, Finance or CFO, IT or data team, Legal or compliance, Other
    • What is your target timeline for making a decision or launching a pilot? Options: Within 30 days, 1 to 3 months, 3 to 6 months, 6 to 12 months, 12+ months, No fixed timeline yet
  2. Outcome Discovery

    Map current fleet state, total-cost-of-ownership pain points, stakeholder roles, and measurable success criteria.

    Discovery Questions

    A concise snapshot, the numbers that matter

    • Tell me in one sentence what your fleet is responsible for and the single priority for it this year
    • How many active vehicles does your operation manage today Options: Under 50, 50–249, 250–999, 1,000–4,999, 5,000+
    • Which vehicle types make up the majority of your fleet Options: Light trucks/pickups, Vans, Sedans/SUVs, Specialty equipment, Mixed
    • Walk me through your typical replacement rule for a light truck, including whether you use age, mileage, cost-per-mile, or another trigger Options: Age-based (years), Mileage-based, Cost-per-mile threshold, Condition-based inspections, No formal rule
    • What single fleet metric, if improved materially in the next 12 months, would unlock additional budget from leadership Options: Total cost of ownership, Fleet downtime, Maintenance spend per vehicle, Fuel spend per mile, Residual value at sale

    When maintenance interrupts the mission

    • When was the last time a maintenance or repair event caused multiple vehicles to be out of service and what was the operational impact that month
    • How many unscheduled maintenance events do you average per vehicle per year Options: Fewer than 1, 1–2, 3–4, 5 or more, Unsure
    • Which categories of repair drive the highest downtime or cost in your fleet Options: Powertrain/engine, Electrical/telematics, Collision/body, Tires/brake, Preventive maintenance backlog
    • Tell me how your maintenance network is structured, for example company-owned shops, national third-party network, dealer-only, warranty coverage mix Options: Company-owned shops, National third-party network, Dealer network, Manufacturer warranty covers major items, Mixed model
    • If unscheduled downtime rose above 5% of fleet availability during a quarter, would you pause new acquisitions or financing commitments Options: Yes, No, Depends on cause

    Where administrative work eats your time

    • Walk me through the tasks that take the most admin hours each month, for example titles, registrations, violations, or insurance paperwork
    • How many full time equivalents or hours per week are spent on fleet administration Options: Under 10 hours/week, 10–40 hours/week, 1–2 FTEs, 3–5 FTEs, More than 5 FTEs
    • Which administrative process causes the most missed deadlines or compliance risk Options: Title and registration, Multi-state registrations, Inspections and certifications, Violation processing, Insurance claims
    • Describe a recent example where an administrative lapse created material cost or downtime
    • If you could delegate one administrative area immediately, which would accelerate operations the most Options: Title and registration, Violation management, Insurance and claims, Maintenance dispatching, Fuel card reconciliation

    Who controls decisions and what they care about

    • Which role in your organization must sign off on new fleet funding and what primary concern would make them say no
    • Which stakeholders need to be consulted for a pilot and what is each role's main success criterion Options: Fleet manager - uptime/reliability, Procurement - contract terms/cost, Finance/CFO - funding and ROI, Operations manager - driver uptime, Safety/compliance - regulatory adherence
    • How quickly does procurement expect final commercial terms to align with an existing purchasing window Options: Immediate, Within 30 days, Within 60 days, Next quarter
    • Who in your chain can block a rollout if they are not confident, and what would their single biggest objection likely be
    • If a pilot delivers the agreed savings but one stakeholder objects, what escalation or governance step would be decisive Options: Executive steering committee decision, CFO sign-off, Operational remediation plan, Vote of stakeholders

    How you will know we've succeeded

    • If a pilot reduced total cost of ownership by 10% in year one, what internal hurdle would still prevent you from moving to full rollout
    • Which KPIs will you use to judge a pilot and what target would be acceptable for each Options: TCO reduction target (%), Downtime reduction (days/vehicle), Maintenance cost per vehicle ($), Fuel cost per mile ($), Residual value improvement (%)
    • How will you validate the results, for example invoice audit, telematics data, odometer verification, or third-party appraisal Options: Invoice audit, Telematics feed, Odometer snapshots, Third-party appraisal, Combination
    • Within how many business days after a successful pilot would you expect contracting to complete Options: Immediately (same week), Within two weeks, Within 30 days, Longer than 30 days
    • If the pilot meets agreed targets, can your organization commit to signing within four weeks Options: Yes, No, Maybe, needs CFO approval

    Other paths you're weighing right now

    • Which alternatives are you actively evaluating besides a managed fleet services partner Options: Remain with incumbent provider, Build internal team, Lease-only financing vendors, Other managed service providers, No alternative identified
    • What would have to be true about your current program for you to stay with it instead of changing Options: Lower total cost of ownership, Improved uptime, Better administrative support, Higher remarketing results, No change needed
    • Has anyone internally proposed solving this without an outside vendor and what resource commitment would that require Options: Yes, requires new hires, Yes, reallocating existing staff, No internal proposal, Discussing but not committed
    • Does an incumbent currently manage part or all of your fleet operations Options: Yes, all fleet management, Yes, partial (financing or maintenance only), No incumbent
    • Which vendor capability would be a deal killer if missing Options: Financing options, Maintenance network, Telematics integration, Fuel card management, Title and registration services

    The real blockers we need to see early

    • Which integration, data, or regulatory gap would stop a deployment before it starts
    • Which systems must integrate for a pilot to be meaningful Options: Telematics platform, Fuel card provider, Fleet management system/CMMS, ERP/finance systems, Maintenance network/repair shop system
    • Are APIs or scheduled data extracts available for those systems and is there an internal owner who can provide access Options: All documented APIs and assigned owner, Some APIs available, owner identified, APIs available but owner unknown, No APIs or extracts available
    • What percentage of your VIN-level data is clean and complete today Options: Over 90%, 70–90%, 50–70%, Under 50%, Unknown
    • Do you operate across multiple states and if so, how many Options: Single state, 2–5 states, 6–10 states, More than 10 states
    • Is there a legal or regulatory approval required before field work or pilot vehicles can be enrolled Options: Yes, regulatory approval required, No, Unknown

    Designing a pilot that proves value fast

    • If you ran a pilot, which site or vehicle segment would demonstrate the fastest, most defensible results and why
    • What sample size or vehicle count would your team consider statistically credible for a pilot Options: 10–25 vehicles, 26–100 vehicles, 101–500 vehicles, 500+
    • Which acceptance criteria must be met for you to call the pilot successful Options: X% TCO reduction, Y% downtime reduction, Maintenance cost per vehicle target, Improved utilization metrics
    • Who will be the operational owner responsible for day-to-day pilot decisions Options: Fleet manager, Operations manager, Procurement lead, Assigned project manager
    • If the pilot hits acceptance criteria, will you scale to a full rollout within three months Options: Yes, No, Depends on contract terms

    Data feeds, telematics, and reporting specifics

    • Which missing data feed would force you to pause a demo or proof of concept Options: Telematics location/speed, Odometer/mileage, Fuel transactions, Maintenance history, VIN and title data
    • Which telematics platform(s) are currently installed in your vehicles, listed by category rather than product name Options: OEM-installed telematics, Aftermarket telematics, No telematics in field, Mixed OEM and aftermarket
    • Are telematics API credentials, fuel card integration credentials, and maintenance history accessible for a pilot within two weeks Options: All available within two weeks, Some available, some will take longer, Not available within two weeks
    • What reporting cadence and delivery format will you need to sign off on pilot results Options: Weekly dashboard, Bi-weekly report, Monthly executive summary, Ad hoc data extracts
    • Do you have internal security or data transfer policies that require additional review before integrations can proceed Options: Yes, formal review required, No formal review, Unknown

    Timing, procurement, and budget windows

    • If terms matched your targets, when would you be able to finalize a contract Options: Immediately, Within 30 days, Within 60 days, Next quarter
    • Which procurement route will we follow Options: Direct purchase/PO, RFP process, Piggyback on existing agreement, Master service agreement
    • Are funds already budgeted for fleet changes this fiscal year Options: Fully budgeted, Partially budgeted, Not budgeted yet, Budget pending approval
    • What approval threshold requires CFO review or executive committee sign-off Options: Under $50k, $50k–$250k, $250k–$1M, Over $1M
    • Is there a procurement blackout period that would delay award until the next fiscal cycle Options: Yes, No, Unsure

    Final impressions and the next practical step

    • If we proved the three outcomes you most need, what is the single fastest internal step that would let you sign
    • Who should attend a pilot kickoff from your side, select roles we should invite Options: Fleet manager, Operations manager, Procurement lead, IT/integration owner, Finance/CFO
    • Would you prefer a 30-day sample pilot, a 90-day operational pilot, or a phased approach Options: 30-day sample, 90-day operational, Phased roll with milestones
    • Are there any absolute contract terms you will not accept such as minimum term length, liability cap, or SLA thresholds Options: Minimum term restriction, Liability cap required, Specific SLA threshold required, No absolute restrictions
    • Do you want to schedule a pilot kickoff within the next two weeks Options: Yes, schedule now, Maybe, need internal alignment, No, not ready
  3. Solution Experience

    Walk through how managed fleet services and lifecycle recommendations deliver the buyer's outcomes using real operational scenarios.

    Solution Experience

    • Solution Experience Session
    • Confirm the current state and its cost
    • You confirm the demonstrated maintenance workflow eliminates the unplanned downtime you described.
    • Run a tailored total cost of ownership model using the provided vehicle class and deliver a two-scenario comparison before the follow-up session.
    • Operational scenario: maintenance to availability
    • You confirm the lifecycle recommendation produces the projected TCO improvement for the sample vehicle class.
    • Provide fleet inventory by vehicle class, three months of maintenance and downtime logs, and current replacement policy.
    • Operational scenario: replacement cycling and remarketing
    • Identify one pilot site and nominate the operational owners and their contact information.
    • You align on pilot scope, success metrics, and remaining evidence required to decide.
    • Draft a pilot proposal with objectives, success metrics, timeline, and the expected TCO improvement for review.
    • Integration proof: telematics to maintenance flow
    • Validate the future state
    • Agree remaining evidence and pilot scope
    • Solution Experience Session
    • Solution Experience Deck
    • Solution Brief
    • meeting
    • slides
    • document
  4. Solution Scope

    Define included services (acquisition, financing, maintenance, fuel, telematics, compliance, remarketing), responsibilities, and measurable deliverables.

    Scope Configuration

    • Vehicle Acquisition and Procurement
    • Lease and Loan Financing Execution
    • Title, Registration, and Multi-State Compliance
    • Preventive Maintenance Program Management
    • Corrective Repair and Warranty Coordination
    • Fuel Card Program Administration
    • Telematics Device Installation and Data Integration
    • Accident Intake and Claims Management
    • End-of-Life Remarketing and Auction Services
    • Fleet Dashboard Deployment and Reporting
    • Maintenance Billing Consolidation and Invoicing
    • Driver Safety and Compliance Program Administration

    Scope Questions

    Vehicle Acquisition and Procurement

    • How many vehicles will be included in the initial acquisition scope (provide VIN count or range)? Options: Less than 50, 50-199, 200-999, 1,000-5,000, More than 5,000
    • Which vehicle body types and specific models or trim levels do you require for each operating group (e.g., service vans, pickup 1500, AWD SUVs)?
    • Provide the preferred order lead times per fleet segment (for example: PO to delivery 30 days, 60 days, 90 days). Options: 30 days, 60 days, 90 days, Custom delivery windows
    • Who in your organization will sign final specification sheets and purchase orders and what title will appear on the purchase authorization?
    • Are factory-installed upfits or vendor/dealer-installed upfits required and list each upfit type with estimated quantities (for example: ladder racks, partitioning, liftgates)? Options: Factory upfit required, Dealer upfit required, Mixed; specify in comments
    • Which delivery acceptance checks will you require at receipt (VIN match, odometer threshold, paint/structural inspection, completed upfit checklist)? Options: VIN match, Odometer check, Damage inspection, Completed upfit checklist, Other

    Lease and Loan Financing Execution

    • Specify the financing structure you prefer for each vehicle group (operating lease, capital lease, conditional sales loan, or mixed). Options: Operating lease, Capital lease, Loan/purchase, Mixed
    • Indicate target contract terms per program (term months and annual mileage bands, for example: 36 months / 36k miles per year). Options: 24 months, 36 months, 48 months, 60 months, Custom
    • Provide the internal approval threshold or credit limit that will trigger CFO-level review (for example: > $250,000 per transaction).
    • Identify required financing documents we must collect at execution (examples: credit application, board resolution, proof of insurance certificate).
    • How will you accept electronic finance agreements and signatures (for example: e-signature on PDF, signed physical agreement)? Options: E-signature (PDF), Wet signature (scanned), Wet signature (physical copy)
    • Describe any tax-exempt status, captive finance requirements, or internal accounting rules that affect how leases must be recorded (attach form numbers or policy references if available).

    Title, Registration, and Multi-State Compliance

    • List the registration jurisdictions by state and county where vehicles will be garaged and require title/registration services.
    • Which vehicle groups require apportioned or International Registration Plan (IRP) plates versus full state registration? Options: IRP/apportioned, Full state registration, Mixed; specify by group
    • Provide the expected annual volume of title transfers and registrations we must process (for example: 200 transfers/year). Options: Less than 100, 100-499, 500-1,999, 2,000+
    • Identify any regulatory constraints or permits required for your vehicles (for example CDL requirements, hazmat endorsements, local taxi or for-hire permits).
    • How should multi-state compliance communications be routed internally (name and email of your compliance owner and backup)?
    • Which evidence will validate registration completion for a vehicle (examples: scanned registration card, plate receipt, DMV confirmation number)? Options: Scanned registration card, DMV confirmation number, Plate receipt, Other

    Preventive Maintenance Program Management

    • Which preventive maintenance intervals do you currently use or prefer (miles or time thresholds per asset class, e.g., 5,000 miles or 6 months)? Options: Miles-based intervals, Time-based intervals, Combined mileage/time, Custom schedule
    • Provide the current list of approved maintenance vendors or national chains to include in the network and indicate any excluded shops.
    • Who will own maintenance approvals for out-of-schedule work and what dollar threshold requires written pre-approval? Options: $0-$250, $251-$1,000, $1,001-$5,000, Custom threshold
    • Describe required preventive maintenance deliverables for each PM event (for example: digital inspection form, estimated labor hours, parts list).
    • How should scheduled PM reminders be sent to drivers and fleet coordinators (SMS, email, in-vehicle alert)? Options: SMS, Email, In-vehicle alert, Driver portal task
    • Indicate your acceptable vehicle downtime limit for scheduled PM events (for example: same-day service, next-business-day), by asset class. Options: Same day, Next business day, 2-5 business days, Flexible

    Corrective Repair and Warranty Coordination

    • Describe your current process for reporting a repair need from a driver to a shop and name the platform or method used (phone, work order portal, telematics alert).
    • Which warranty providers and extended coverage plans apply to your fleet assets and supply contract ID or policy numbers where available.
    • What repair authorization thresholds do you require before work can proceed without central approval (for example: $500 parts and labor)? Options: $0-$250, $251-$1,000, $1,001-$5,000, Custom
    • How do you prefer warranty recovery documentation to be submitted (digital invoice with VIN, OEM claim reference, photos of defect)? Options: Digital invoice with VIN, OEM claim reference, Photos attached, Other
    • Identify any fleet-specific repair SLAs you require (for example: initial triage within 2 hours, repair completion within 5 business days).
    • Which data points must appear on a corrective repair job card for your records (VIN, odometer, work code, parts used, warranty flag)? Options: VIN, Odometer, Work code, Parts list, Warranty flag

    Fuel Card Program Administration

    • How many fuel cards do you require initially and how many will be held in reserve for new hires or replacements? Options: Less than 50, 50-199, 200-999, 1,000+
    • Which fueling controls would you like enabled per card (daily dollar limit, gallon limit, restricted merchant categories)? Options: Daily dollar limit, Gallon limit, Merchant category restrictions, No restrictions
    • Who will be the primary fuel program administrator and who is the secondary contact (name, role, email)?
    • Provide required reconciliation frequency for fuel transactions (for example: weekly, monthly) and preferred export format (CSV, XLSX). Options: Weekly, Bi-weekly, Monthly, Custom
    • Describe any tax-exempt or fleet fuel rebate programs you currently participate in and supply program ID if applicable.
    • Which evidence will validate correct fueling transactions (examples: transaction-level CSV with site ID, odometer at transaction, driver ID)? Options: Transaction CSV with site ID, Odometer at transaction, Driver ID logged, Receipt images

    Telematics Device Installation and Data Integration

    • Which telematics device types and protocols must we support for your vehicles (for example: OBD-II plug, hardwired CAN bus, OEM telematics, J1939)? Options: OBD-II plug, Hardwired CAN, OEM telematics, Other
    • How many installation sites and estimated weekly install capacity do you require for hardwired device deployments? Options: 1 site, 2-5 sites, 6-20 sites, 20+ sites
    • Provide the API endpoints or data formats your operations platform requires for integration (for example: REST endpoint, SFTP CSV, MQTT) and indicate if credentials are available. Options: REST API, SFTP CSV, MQTT, Other
    • Who will own telematics device provisioning and who is the technical contact for credential exchange (name, role, email)?
    • Specify required telemetry data fields and minimum data frequency (examples: GPS lat/long every 60 seconds, engine hours, VIN, fault codes).
    • What acceptance criteria will validate successful telematics integration (for example: GPS accuracy within 50 meters, location data latency under 5 minutes, 95% data ingestion rate over 7 days)? Options: GPS <50m / latency <5min / 95% ingestion, Custom SLA - describe in comments

    Accident Intake and Claims Management

    • Describe your current accident reporting workflow from driver notification through claims submission and which systems are used (phone, mobile app, email).
    • Which insurer or claims portal integrations must we support and provide any portal IDs or broker contact details if available.
    • How should minor incident repairs be approved (for example: automatic approval under $1,000, manual approval required)? Options: Auto-approve under threshold, Manual approval required for all, Hybrid - specify threshold
    • Who will be your internal claims liaison and what is the escalation path for high-severity incidents (name, phone, email)?
    • List mandatory claim deliverables for each incident (examples: police report number, photos, VIN, driver statement).
    • Indicate preferred timelines for initial claim acknowledgement and claim resolution milestones (for example: acknowledge within 24 hours, estimate within 5 business days). Options: Acknowledge within 24 hours, Acknowledge within 48 hours, Custom SLA

    End-of-Life Remarketing and Auction Services

    • Which remarketing channels do you prefer to use for retired vehicles (open auction channel, dealer network, private sale, bundle sale)? Options: Open auction channels, Dealer network, Private sale, Bundle sale
    • Provide average expected vehicle condition at retirement by asset class (for example: 70% mechanical health, cosmetic grade B, average odometer).
    • How do you want remarketing floor price guidance delivered (per vehicle reserve, batch floor, guaranteed minimum)? Options: Per vehicle reserve, Batch floor, Guaranteed minimum, No floor guidance
    • Who will approve final disposition recommendations and what turnaround time do you require for offers on retired units?
    • What acceptance criteria will confirm successful remarketing performance (examples: target residual vs. book value %, days-to-sale under 30)? Options: Residual target met (%), Days-to-sale <30, Both; provide targets in comments
    • Specify any environmental or de-fleet requirements prior to sale (for example: battery disposal for EVs, fluid drains, VIN disclosure).

    Fleet Dashboard Deployment and Reporting

    • Which KPIs must appear on the executive fleet dashboard at go-live (examples: total cost of ownership, maintenance cost per mile, utilization, downtime)? Options: TCO, Maintenance cost per mile, Utilization, Downtime, Custom KPIs
    • Provide required report cadence and delivery methods (examples: weekly PDF email, daily CSV push to SFTP, interactive portal). Options: Daily, Weekly, Monthly, Ad-hoc
    • Which user roles need dashboard access and what permission levels (examples: read-only executive, edit for fleet manager)?
    • Specify data retention and historical window requirements for reporting (for example: 12 months, 36 months, since inception). Options: 12 months, 24 months, 36 months, Since inception
    • What evidence will validate dashboard data accuracy at handover (examples: spot-checked VIN-level reconciliation showing 98% parity, sample monthly ledger match)?
    • Identify any export formats or downstream systems that must receive reporting outputs (examples: ERP, BI platform, CSV for accounting).
  5. Mutual Commit

    Finalize commercial terms, SLAs, billing and governance, and confirm acceptance criteria and transition milestones.

    Agreement Modules

    • Master Services Agreement (MSA)
    • Statement of Work (SOW)
    • Order Form and Pricing Schedule
    • Service Level Agreement (SLA)
    • Billing & Payment Terms
    • Acceptance Certificate & Transition Milestones
    • Governance and Change Control Addendum
    • Data Processing Agreement (DPA)
    • Vehicle Financing Agreement & Security Schedule
    • Agent Authorization for Title, Registration, and Filings
  6. Deployment

    Lock readiness facts and configuration values before execution begins.

    1. Pre-Deployment Readiness

      Capture concrete readiness facts — vehicle counts, pilot sites, data access, owners, regulatory and multi-state requirements, and target dates.

      Pre-Deployment Questions

      Environment and site access

      • Which production systems/environments are in scope for deployment? (select all that apply — this determines integration effort) Options: Single production fleet management system, Multiple production fleet management systems, Telematics platform(s), Fuel card / payment platform, Maintenance vendor portal(s), Registration/title system, Other
      • Target date when production environments and endpoints will be available to the deployment team (so we can schedule integration work)
      • Are test or sandbox environments available for each system in scope? Options: Yes, for all systems, Yes, for some systems — we'll list which in DeploymentConfig, No — only production available, Not sure / need seller assistance

      Data and system readiness

      • Which data sources require an initial handover or migration? (select all that apply — these items feed the migration plan) Options: Vehicle inventory / VIN master, Maintenance history and work orders, Fuel transactions, Telematics device mapping, Registration and title records, Driver rosters and assignments, Other
      • Is there a single source-of-truth owner for vehicle inventory and VIN assignments? If yes, provide the role or team name (e.g., 'fleet operations') — helps confirm mapping ownership.
      • Has the field-mapping approach (who owns mapping and whether templates exist) been decided? Options: Yes — buyer owns mapping, Yes — seller will lead mapping, Partially decided — requires joint mapping session, No — mapping not decided

      People and ownership

      • Primary buyer deployment owner (role and contact) — who will approve go/no-go and coordinate internal teams?
      • Named owners (role or team) for these workstreams: integrations, telematics, maintenance network, and compliance/registrations — list each owner so we can assign tasks.
      • Will the buyer provide delegated admin or API-ready accounts for deployment tasks (system admin access), or will access be coordinated by buyer admins? Options: Yes — for all systems in scope, Yes — for some systems, No — access will be coordinated by buyer admins, Not sure / need guidance

      Timing and constraints

      • Do any sites or regions have operational blackout windows or seasonal constraints that must be avoided during rollout? If yes, list site codes/regions and blackout periods.
      • Are there regulatory or multi-state requirements that must be satisfied before pilot (select all that apply)? Options: Multi-state title/registration variations, Commercial insurance endorsements, Special vehicle specs or emissions rules, DOT/IRP compliance, Hazmat or placarding requirements, None of the above / not applicable, Other
      • Target pilot start date and target full rollout date (separate) — providing both dates lets us sequence pilot validation, training, and escalation windows.
    2. Integration & Configuration

      Lock integration endpoints, telematics credentials, fuel card settings, maintenance network mappings, and reporting thresholds for deployment.

      Configuration Details

      Environments & Endpoints

      • Enter the production integration endpoint URL for the platform API (format: https://api.example.com — no trailing slash). This value will be used by the Integration module.
      • Select the integration region for this deployment (Default: US-Central). This choice controls regional endpoint selection in the Integration module. Options: US-Central, US-East, US-West, EMEA, APAC, Other

      Telematics Integration

      • Telematics integration authentication method (select one). Default: OAuth2 (client ID only; credential secret exchanged via your secrets manager at deployment kickoff). Do NOT paste secrets here. Options: OAuth2 (client ID only; secret provided via your secrets manager), API Key (key name only; key secret provided via your secrets manager), SFTP file drop (enter folder name below; no credential in questionnaire), Vendor-managed connector (enter connector ID below), None / Not integrating telematics at deployment
      • Enter the telematics integration identifier — one value only (client ID, integration user name, connector ID, or SFTP folder name). Example format: 'client-abc-123'. This value maps to the telematics connector.
      • Telematics credential owner (person or team name who will approve secret exchange via your secrets manager). Enter a single value (e.g., Fleet IT).

      Fuel Card & Payments

      • Primary fuel program type for deployment (Default: Corporate fuel card program). This determines the fuel transaction mapping variant. Options: Corporate fuel card program (third-party network), Prepaid/central billing cards, Fuel reimbursement only, Corporate fleet card with provider API integration, No fuel program included
      • Fuel card integration identifier — enter the non-secret mapping ID the seller should use to match transactions (card BIN, fleet ID, or provider integration ID). One value only.

      Maintenance Network & Mappings

      • Maintenance vendor mapping file location (enter a secure URL where the deployment will fetch the CSV/JSON mapping: format https://... or s3://...). Enter one URL only; file must contain vendor ID → account number mappings.
      • Default maintenance pricing schedule to apply (select one). Default: National labor + parts. The Maintenance module will apply this schedule when vendor-specific rates are not present. Options: National labor + parts (default), Regional labor band, Customer-provided vendor rates (use mapping file), Use vendor published pricing, Other

      Reporting Thresholds & Alerts

      • Vehicle unscheduled downtime alert threshold in hours (numeric). Default: 48. Enter a whole number of hours; the Reporting module will use this to trigger downtime alerts.
      • Per-vehicle maintenance cost alert threshold in USD per month (numeric). Default: 500. Enter a number (no currency symbol); used by Cost & Alerts reporting.
      • Telematics data freshness threshold in minutes (numeric). Default: 60. Enter a whole number; the Reporting module flags vehicles not reporting within this window.

      Credentials Exchange & Owners

      • Select the secrets exchange method for sensitive credentials (Default: Your secrets manager). The deployment will NOT accept secrets pasted in this questionnaire. Options: Your secrets manager (enterprise vault), Seller's secure portal (vendor-provided), Encrypted transfer at kickoff meeting (least preferred), Other
      • Technical contact to approve and coordinate integrations (enter one value in format: Full Name <[email protected]>). This contact will be used for all integration approvals.
    3. Deployment Execution

      Plan and execute rollout with clear owners, pilot validation, training, sequencing, and escalation paths.

  7. Success

    Review outcomes against success metrics, track operational issues, and manage enhancement requests and continuous improvement.

    Success Reviews

    • Go-live Health Check (weeks 1-4)
    • First Measurement Review (weeks 4-10)
    • Acceptance Gate Review (around day 90)
    • Quarterly Ongoing Success Review

    Issues & Enhancements

    • Refresh the KPI dashboard and distribute quarter-to-date metric snapshots before the next review.
    • Restate acceptance criteria and numeric targets
    • Produce a documented acceptance decision with the buyer's named signatory or a clear conditional remediation plan.
    • Confirm incumbent decommissioning status and archive evidence of contract/renewal decisions and data migration.
    • Agree timelines and verification steps for any failed acceptance criteria.
    • Publish the acceptance decision record with the named signatory and attach the supporting evidence.
    • Create and assign the remediation workplan for any failed criteria with resolution dates.
    • Confirm and document incumbent decommissioning actions, archive receipts, and set read-only access where applicable.
    • Outcomes review against targets
    • Confirm whether maintenance cost per vehicle per month and fleet availability rate (%) meet or exceed the targets recorded in Outcome Discovery.
    • Drive closure of high-priority operational incidents and reduce outstanding incident count quarter over quarter.
    • Maintain a prioritized backlog of enhancement requests with agreed acceptance criteria and timelines.
    • Update the operational incident log with resolution dates and verification steps for each open ticket.
    • Publish the prioritized enhancement backlog with acceptance criteria and target delivery quarters.
    • Re-confirm success criteria and owners
    • Confirm deployment components are live or documented as exceptions requiring remediation.
    • Produce a prioritized list of open issues with remediation actions and target dates.
    • Confirm training completion status and next steps for any user enablement gaps.
    • Publish the go-live exceptions log with remediation actions and target dates.
    • Provide cleaned connectivity and transaction sample logs for any failed integrations.
    • Circulate updated training roster and schedule follow-up sessions for incomplete cohorts.
    • Present first measurement data vs Outcome Discovery targets
    • Validate whether maintenance cost per vehicle per month and average vehicle downtime hours per vehicle are trending toward targets recorded in Outcome Discovery.
    • Agree a prioritized set of corrective actions with delivery dates to address the top root causes.
    • Confirm the data completeness and dashboards required for the Acceptance Gate meeting.
    • Deliver the cleaned KPI dataset and dashboard views used in this review.
    • Implement identified operational fixes (vendor mapping, scheduling rules, data transforms) with target dates.
    • Populate the Acceptance Gate checklist with evidence attachments and readiness notes.
    • Deployment and connectivity validation
    • Operational issues and ticket burn-down
    • Diagnose variance and root causes
    • Present outcome data against each acceptance criterion
    • Agree corrective actions and owners
    • Document pass, fail, or conditional outcome and capture named signatory
    • Enhancement requests and prioritization
    • Early adoption and usage signals
    • Confirm acceptance gate readiness
    • Open issues triage
    • Incumbent decommissioning review
    • Action plan and next quarter checkpoints
    • Agree remediation plan for any failed criteria
    • Agree immediate remediation actions
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.