Start with Your Fleet's Story

• Give us a short snapshot of your operation—fleet size, vehicle types, and typical daily stops per vehicle.
• Which best describes your primary business model? Options: Last-mile delivery (ecommerce/retail), B2B distribution, Food & beverage delivery, Field service/technicians, Temperature-controlled logistics, Other
• Who currently owns routing each day (role/title)? Options: Dispatcher, Operations Manager, Dedicated Routing Analyst, Third-party/3PL, Automated system, Other
• Roughly how many stops per day do you route across the fleet?
• If you had to pick one word that best captures how route planning feels today, what would it be?

Are Your Metrics Hiding the Real Problem?

• When you compare planned vs actual routes, what's the single biggest discrepancy you see? Options: Extra miles driven, Missed time-windows, Unbalanced driver workloads, High overtime, Frequent re‑routes during day, Other
• How do you currently measure routing performance? Select all metrics you track regularly. Options: Miles driven, Stops per route, On-time %, Driver overtime, Fuel per stop, Customer complaints, Idle time, Other
• Tell us about a recent day when performance was far from expectations—what happened and how did it feel for the team?
• Which of these gaps causes the biggest financial impact today? Options: Fuel and mileage, Labor/overtime, Customer service/penalties, Underutilized vehicles, Lost capacity during peaks, Other
• How confident are you that the data you use to report these metrics is accurate and timely? Options: Highly confident, Mostly confident, Somewhat confident, Not confident

What’s Truly Driving Daily Chaos?

• Which recurring operational issue do you think people have normalized but would honestly change if they could? Options: Late pickups/deliveries, Manual route edits mid‑day, Lack of real-time visibility, Inaccurate ETAs, Driver no-shows, Other
• How often do urgent exceptions (cancellations, new orders, traffic) force manual re-planning during a shift? Options: Multiple times daily, Daily, Few times per week, Rarely
• Describe a recent exception that forced last-minute changes—what was the cause, and who scrambled to fix it?
• When dispatchers make manual routing choices, what trade-offs do they explicitly accept (time, customer priority, driver fairness, etc.)?
• How do drivers typically react to routes created by software versus those built by dispatchers? Any feelings or resistance you've noticed? Options: Prefer dispatcher-built routes, Open to software routes if proven, Neutral, Prefer software routes, Mixed reactions

What If Your Best Assumptions Are Wrong?

• Which long-held belief about routing most deserves a reality check in your organization (for example: 'experienced dispatcher beats algorithm')? Options: Dispatcher intuition is best, We can’t integrate systems quickly, Drivers won’t follow optimized routes, Data quality is too poor, Optimization can't handle our constraints, Other
• Where have you tried small improvements before, and why didn’t they scale or stick?
• If a new approach required changing one daily habit in dispatch or driving, which habit would feel hardest to change and why?
• Which hidden cost do you think your team underestimates when evaluating routing changes (training time, data cleanup, lost short-term productivity, etc.)?
• What internal skeptics or cultural barriers should we expect to encounter during a trial? Options: Dispatch team resistance, Driver pushback, IT resource constraints, Finance scrutiny, Operations inertia, Other

Imagine a Morning Where Everything Clicks

• If a typical day could be transformed, what three concrete improvements would mean this solution 'worked' for you?
• Which outcome would excite Finance most: reduced cost per stop, lower overtime, fewer vehicles, or something else? Options: Reduced cost per stop, Lower overtime, Fewer vehicles needed, Improved on-time %, Reduced fuel spend, Other
• How would success show up to drivers, dispatchers, and customers respectively? Give one tangible example per group.
• Picture a week after rollout—what behavioral changes would indicate adoption is real and sustainable?
• Which one KPIs should we prioritize in the pilot dashboard so busy leaders glance and know if it's working? Options: Miles saved, On-time %, Stops per route, Overtime hrs, Fuel per stop, Customer SLA compliance

What Must a Pilot Actually Prove?

• If you had to define an unambiguous pilot win, what are the three acceptance thresholds (numeric where possible)?
• What sample size and duration feel credible to your stakeholders for a parallel pilot? Options: 10–25 routes / 30 days, 26–50 routes / 30–60 days, 51–100 routes / 60 days, Other
• Which specific routes or days would you insist remain in the pilot (high complexity, peak windows, multi-depot)?
• What would constitute unacceptable risk during the pilot (service level drop, data outages, driver safety concerns, etc.)?
• How will you treat early operational wins that aren’t yet reflected in monthly financials—do you want a qualitative validation channel? Options: Yes—capture driver feedback & anecdotes, No—only quantitative metrics, Both quantitative and qualitative, Unsure

Who Decides—and Who Does the Work?

• Who are the decision-makers that must sign off to run a pilot and to roll to production? List roles and names if possible.
• What internal owners will we need for integrations, data access, training, and daily oversight? Options: IT/Integration Lead, Ops Manager, Dispatcher Lead, Fleet Manager, Finance Point of Contact, Driver Trainer, Other
• Do you have a target go/no‑go date or business milestone tied to the pilot outcome?
• How much internal time can your team realistically dedicate to pilot setup and daily coordination (hours per week)? Options: <5 hours, 5–10 hours, 10–20 hours, 20+ hours
• What level of executive visibility and reporting cadence will be required during the pilot? Options: Daily ops emails, Weekly ops review, Biweekly executive updates, Monthly summary, Ad hoc as needed

The Data & Systems Truth: Can We Get What We Need?

• What source systems hold your stop data, orders, customer windows, and vehicle specs (names of WMS/OMS/TMS/ERP/telemetry)?
• Which of these data challenges best describes your reality? Options: Clean, consistent feeds available, Partial feeds with gaps, Manual CSV exports, Limited telematics access, Multiple systems with conflicting data, Other
• What integrations are must-haves before a pilot (real-time orders, telematics, proof-of-delivery), and which can be staged later? Options: Real-time order feed, Telematics/GPS, Customer master data, Proof-of-delivery ingestion, None required for pilot, Other
• How long does IT typically need to stand up a new webhook/API or schedule secure file sharing for your team? Options: <1 week, 1–3 weeks, 3–6 weeks, 6+ weeks
• Do you have data governance or privacy rules (masked PII, separate prod/test environments) we should plan around? Options: Yes—strict rules, Some rules but flexible, No formal rules, Unsure

Will People Actually Use It?

• What would convince a dispatcher to pick the optimizer’s route instead of their own on a busy morning?
• How do you prefer to train dispatchers and drivers—hands-on workshops, short video modules, shadow sessions, or blended learning? Options: Hands-on workshops, Short video modules, Shadow sessions, Blended learning, Documentation only, Other
• Which mobile features matter most to drivers for adoption: turn-by-turn nav, ETA accuracy, ability to add exceptions, proof capture, or offline support? Options: Turn-by-turn navigation, ETA accuracy, Add exceptions mid-route, Proof-of-delivery capture, Offline mode, Other
• How do you plan to surface wins to frontline teams (scorecards, bonuses, recognition, daily huddles)? Options: Scorecards/dashboards, Monetary incentives, Public recognition, Daily huddles, No formal reinforcement yet
• What concerns do drivers or dispatchers usually voice about new tech, and how have you successfully addressed those concerns before?

The Practicalities: Risk, Support, and Escalation

• If the pilot runs into problems, what is your preferred escalation path and SLA for issue resolution? Options: Ops → IT → Vendor, Dedicated vendor support line, Direct exec escalation, Combined war-room approach, Other
• What non-negotiable safety, compliance, or customer contract constraints must never be violated by route changes?
• Are there external stakeholders (large customers, regulators, or partners) who need notification or sign-off before testing routes on live deliveries? Options: Yes—customers, Yes—regulators, Yes—partners, No external stakeholders, Unsure
• What level of vendor access to your systems and data are you willing to grant for pilot success (read-only, write, admin), and any limitations? Options: Read-only access, Read + limited write, Full admin access, No direct access—use file exchange, Other
• How should we document and hand off pilot learnings so they turn into an actionable rollout plan? Options: Executive summary + ROI, Operational playbook, Training materials + SOPs, All of the above, Other

Agreeing Next Steps — What A Successful Kickoff Looks Like

• What are the three immediate milestones you want to see in the first 30 days of engagement?
• Which stakeholders should be invited to the kickoff and initial design sessions? Options: Operations leadership, Dispatchers, IT/Integrations, Finance, Driver trainers, Customer success/vendor rep
• Do you have any hard calendar blackout dates or peak seasons we must avoid for pilot activity? Options: Yes—specific dates, Yes—seasonal window, No constraints, Unsure
• What's the single biggest thing you need from us to feel confident moving forward right now?
• Are you ready to commit to a discovery-call + data review session within the next two weeks? Options: Yes—schedule now, Yes—but after review, Not yet—need internal prep, No

Start Here — A Snapshot of Today’s Routing

• Walk me through a typical day: how are routes created, who touches them, and what tools they use?
• Which teams own routing, dispatch, and schedule changes in your organization? Options: Dispatch team, Operations manager, Fleet manager, Third-party logistics (3PL), Customer service/CSRs, Other
• Which systems provide your daily stop lists today? Options: Order Management System (OMS), Transportation Management System (TMS), Warehouse WMS, Manual / spreadsheets, EDI feed, API pull, Email/CSV, Other
• Roughly how many routes do you plan daily for the pilot-eligible fleet segment? Options: < 20, 20–50, 51–200, 201–500, > 500
• What part of the current daily routine feels most fragile or time-consuming to your team?

Where the Bottlenecks Hide — What’s Slowing You Down?

• If I told you your current routing process is costing you hidden hours and miles every week, where would you point first?
• How long does it take on average to build and finalize a day’s routes from receipt of the orders? Options: < 15 minutes, 15–30 minutes, 30–60 minutes, 1–2 hours, > 2 hours
• When orders change mid-day, how does the team handle reassignments and reroutes? Options: Manual reassign by dispatcher, Small batch re-optimization, Driver handles deviations, Call customer service, No formal process, Other
• Tell me about a recent day where things felt chaotic—what happened, who reacted, and what was the final impact?
• Which part of the day produces the most exceptions (pickup windows, traffic, missed deliveries, driver availability, equipment issues)? Options: Morning departures, Midday reassignments, Afternoon returns, End-of-day overtime, All day equally

Data and Integrations — What’s Feeding Your Decisions?

• What if your route decisions are only as good as the data feeding them—how confident are you in the accuracy and timeliness of your incoming feeds? Options: Very confident, Mostly confident, Somewhat confident, Not confident
• Which data sources are available in real time versus batched/delayed for planning? Options: Real-time telematics, Real-time order feed (API/stream), End-of-day batch CSV, Scheduled EDI, Manual uploads, Other
• List every system we would need to integrate to run a representative pilot (OMS/TMS, telematics, HR/rostering, CRM, proof-of-delivery).
• What connectivity methods does each system support (API, SFTP, CSV, EDI, manual entry)? Please map system to connectivity if possible.
• Are there data quality gaps you know about (missing addresses, inaccurate ETAs, inconsistent vehicle profiles)? If yes, which are highest priority to fix? Options: Missing addresses, Inaccurate ETAs, Inconsistent vehicle capacity data, Driver shift errors, Duplicate orders, Other

When Things Break — Your Operational Failure Modes

• When a route fails in production, what usually breaks first and who gets the call?
• How often do you experience no-shows, driver refusals, or abandoned stops, and what is the usual root cause? Options: Rarely, Monthly, Weekly, Daily
• Describe the most common manual workaround your team uses to keep deliveries moving when automation fails.
• Which failure mode costs you the most in either time or money—late deliveries, returned loads, excess miles, or overtime? Options: Late deliveries, Returned/failed deliveries, Excess miles, Driver overtime, Customer chargebacks, Other
• When an exception occurs, how is the resolution and root cause tracked (ticketing system, spreadsheets, verbal debrief)? Options: Ticketing system, Spreadsheets, Daily stand-up notes, Not tracked, Other

What Your KPIs Are Missing — Metrics That Actually Matter

• If your current metrics were misleading you, which KPI would you suspect of hiding the real problem?
• Which KPI do you currently track daily vs weekly vs monthly (miles, stops/route, on-time %, OT hours, fuel, cost-per-stop)? Options: Miles driven, Stops per route, On-time percentage, Driver overtime hours, Fuel consumption, Cost per stop, Customer SLA breaches, Other
• How accurate and comparable are historical records for those KPIs (consistent definitions, same measurement windows)? Options: Very consistent, Mostly consistent, Some inconsistencies, Not consistent / ad hoc
• Which KPI improvement would make stakeholders (finance, operations, customers) say the pilot was a clear win? Options: Miles reduction, Stops per route increase, Higher on-time %, fewer OT hours, Lower cost per stop, Improved customer satisfaction, Other
• Do you have baseline reports we can review for a pilot (last 30/60/90 days)? If yes, what format are they in and who owns them? Options: CSV/Excel, BI dashboards, TMS reports, Manual summaries, Not available

Human Factors — Dispatchers, Drivers, and Daily Judgment Calls

• If an optimization suggested a route your most experienced dispatcher would never pick, how would that typically land in the room?
• How many dispatchers would actively use the system in a pilot and what are their tech comfort levels? Options: 1–2 dispatchers, 3–5 dispatchers, 6–10 dispatchers, >10 dispatchers
• What concerns do drivers express most about optimized routes—safety, familiarity, traffic, customer timing, pay structure? Options: Safety, Route familiarity, Traffic unpredictability, Customer time windows, Pay/route-based incentives, Other
• Describe any cultural or labor constraints (union rules, driver shift preferences, local regulations) that influence routing decisions.
• Who signs off on final routes today and what decision rules do they follow (seniority, ETA buffer, customer priority)?

Edge Cases — The Little Things That Break Big Systems

• Which uncommon scenarios regularly trip up your planning (partial loads, returns, temperature splits, multi-depot moves, large special deliveries)? Options: Partial loads, Returns/failed attempts, Temperature-controlled splits, Multi-depot transfers, Oversized deliveries, Other
• Tell me about a recurring exception that you’ve never fully automated—what makes it hard?
• How do customer requirements (appointment windows, delivery instructions, liftgate needs) get represented in your current system and where do they drop out? Options: Captured in OMS/TMS, Added manually by dispatch, Driver app notes, Not consistently captured, Other
• Are there geographic or regulatory limits (low bridges, restricted zones, city curfews) that routinely constrain routes? Options: Yes—many, Yes—some, Rarely, None
• If you had to pick three edge-case scenarios we must simulate during the pilot, which would they be?

What You’d Notice Tomorrow — Quick Wins and Low-Risk Pilots

• If we could prove value in one metric within 30 days, which metric would change your willingness to expand the solution? Options: Miles saved, Stops per route, On-time percentage, Reduced overtime hours, Cost per stop
• Which subset of routes would make the clearest, low-risk pilot population (same-day deliveries, regional routes, longest routes, driver-owned routes)? Options: Same-day/express, Regional trunk routes, Longest-distance runs, High-variability routes, Peak-day routes, Other
• What minimum level of data access would you be comfortable granting for a pilot (read-only API, scheduled CSV exports, limited telematics stream)? Options: Read-only API, SFTP/CSV exports, Limited telematics stream, Full API access, Manual uploads only
• Who are the decision stakeholders we should involve in pilot definition and who needs to see early KPI snapshots? Options: Operations/Dispatch, Fleet manager, IT/Integrations, Finance, Customer success/account owner, Other
• What would feel like an acceptable risk level for trying a parallel pilot on live routes (no driver impact, dispatcher-reviewed, direct driver adoption)? Options: No risk — dispatcher review only, Low risk — limited driver rollout, Moderate risk — phased driver adoption, High risk — full switch

Practical Next Steps — Access, Artifacts, and Quick Decisions

• What documents and artifacts can you share to accelerate mapping (data schema, sample stop files, vehicle roster, driver schedules)? Options: Sample stop files (CSV), Vehicle roster, Driver schedules, Order data schema, Telematics sample, None ready
• Who in IT or integrations will be our point of contact and what is their preferred method for handoffs (email, Jira, Slack)? Options: Email, Jira/Ticketing, Slack/Teams, Scheduled calls, Other
• What legal/privacy or security requirements must we satisfy before we can ingest live order or telematics data? Options: Standard NDA, Data processing agreement, SOC/ISO requirements, IP whitelisting, None / not sure
• What is your ideal timeline from discovery to pilot start (weeks/months), and are there hard dates we must avoid? Options: Within 2 weeks, 2–4 weeks, 1–2 months, > 2 months
• Finally, what would make you feel we’ve earned a short pilot conversation—what evidence or assurance do you need to say yes?

Who's in the Room? Quick introductions that matter

• Which of these people will be directly involved in evaluating the pilot or signing off on decisions? Options: Fleet Manager, Logistics Director, Dispatch Supervisor, Operations Manager, IT Lead, Finance / Controller, CEO / Owner, Driver Representative, Procurement, Other
• For each person you've included, what is their primary decision authority (example: budget approval, technical sign‑off, operations go/no‑go)?
• How aligned are the stakeholder group about the need to change routing today? Options: Completely aligned, Mostly aligned with minor objections, Divided opinions, Skeptical or resistant
• Which departments will need to be actively involved during the pilot execution and why? Options: Dispatch/Operations, IT/Integrations, Fleet Maintenance, Customer Service, Finance, HR/Training, Telematics Vendor, Other
• What recent event or business pressure sparked interest in exploring route optimization now?

If We Saved You Time, What Would You Fix First?

• If routing improved today and saved your team a consistent block of time or miles, what operational problem would you want that fix to solve first?
• What are the top three frustrations dispatchers complain about most when planning the day?
• How often do mid‑day changes (cancellations, add‑ons, driver sick calls) force you to replan routes? Options: Several times per day, Once per day, A few times per week, Rarely
• Tell us about a recent day when routing failed to meet expectations—what happened and what impact did it have?
• Which assumption about your current routing process would you be most surprised to have proven wrong?
• How much time does your dispatch team spend creating/adjusting routes on an average workday? Options: >4 hours, 2–4 hours, 1–2 hours, <1 hour

Where the Money and Time Leak Out

• Where do you believe the biggest avoidable cost or service gap exists in your daily operations?
• Which of these KPIs do you currently track for your fleet? Options: Miles per route, Stops per route, On‑time percentage, Driver overtime minutes, Cost per stop, Fuel consumption per route, Customer SLA breaches, Other
• Please provide the current baseline values for the primary KPIs you just selected (include units and averaging cadence—daily/weekly/monthly).
• How do you calculate cost per stop today (what costs are included)?
• How confident are you in the accuracy of your baseline KPI data? Options: Very confident, Mostly confident, Some gaps exist, Not confident / data is fragmented
• Have you quantified a target ROI or savings threshold that would justify a full rollout? Options: Yes—specific % or $ target, We have a rough target, No, we need help defining it

What You're Doing Today That Feels Uncomfortable

• Which parts of your current routing process feel like workarounds rather than reliable systems?
• How many manual changes (reassignments, route edits, priority overrides) happen on an average route day? Options: >10 per day, 5–10 per day, 1–4 per day, Rarely
• When an optimized route disagrees with a dispatcher's judgment, how is that usually resolved today? Options: Dispatcher overrides optimization, Optimization is adjusted by IT/ops, We run both and compare, No formal process—ad hoc
• Tell a story about the last time routing decisions caused a major customer issue or internal frustration—what signs could have predicted it?
• What internal biases or rules do you think might make your team resist algorithmic suggestions (for example: territory loyalty, familiar driver routes, local shortcuts)?
• Which parts of the dispatcher's job do you most want to protect or preserve through any change?

Integrations, Data, and the Reality of Getting Connected

• If our optimization engine needed one reliable daily feed to run real routes, how close are you to producing it today? Options: Ready today, Some work required (APIs/exports), Significant integration work needed, We don’t know yet
• Which systems currently hold your stop and job data? Options: TMS / Order Management, ERP, WMS, Custom database, CSV uploads / spreadsheets, Other
• Which telematics or vehicle tracking providers do you use (select all that apply)? Options: Verizon Connect, Samsara, Fleet Complete, Geotab, Teletrac Navman, No telematics, Other
• How is stop data currently delivered—batch file, API push, manual CSV, or other? Please specify cadence (real‑time, hourly, daily).
• Can your IT team provide a sample day of historical stop + telematics data for validation within 5 business days? Options: Yes — ready now, Yes — with 1–2 weeks lead, Maybe — needs approval, No / uncertain
• Who in your organization will be the primary technical contact for integrations (name, role, email)?
• Are there contractual or security constraints (VPN, SSO, data residency) we should know about up front? Options: SSO required, VPN / firewall rules, Data residency limits, Third‑party approvals, No major constraints, Other

What Would Pass (and What Would Surprise You)

• What exact result from a 30–60 day parallel pilot would make you comfortable moving to fleet‑wide deployment?
• Which metric should be the single source of truth for pilot success? Options: Miles saved, Stops per route, On‑time %, Driver overtime reduction, Cost per stop, Customer SLA breaches
• What acceptance thresholds would constitute success for your chosen metric(s)? Please include numeric values or ranges.
• How many routes or percentage of your daily volume would you want included in the pilot to feel statistically confident? Options: 1–5 routes (small sample), 5–15 routes (pilot cohort), 15–50 routes (robust sample), >50 routes (near rollout scale)
• Would you require the pilot to run in parallel (software vs manual) or as a staged cutover for selected routes? Options: Parallel (recommended), Staged cutover for selected routes, Hybrid — parallel then cutover, Undecided
• What statistical or business rules must be met to accept pilot outcomes (p‑value, % improvement, minimum days with comparable volumes)?

Who Signs the Check and When?

• Who holds the budget authority for a commercial commitment to deploy a routing platform? Options: Operations / Fleet, IT, Finance, CEO / Owner, Procurement, Other
• What internal approvals or procurement steps must be completed before a contract can be signed? Options: PO approval, Legal review, Security review, Finance ROI signoff, Executive approval, Other
• If the pilot shows the promised improvements, what is your expected timeline to finalize procurement and schedule rollout? Options: <1 month, 1–3 months, 3–6 months, >6 months
• Under what conditions would your budget holder be likely to say no, even if operational metrics improved?
• Who will be the named go/no‑go decision maker at the end of the pilot (role and contact)?

People and Change: Will Your Team Use It?

• If our routes saved minutes but dispatchers consistently ignored them, how confident are you that the business would still capture the savings? Options: Very confident, Somewhat confident, Uncertain, Not confident
• Describe the dispatch team's experience level with optimization or algorithmic tools (novice, some exposure, daily users of advanced tools). Options: Novice, Some exposure, Regular users, Advanced / power users
• What training model would work best for your team? Options: Hands‑on in person, Live remote workshops, Train‑the‑trainer, Self‑paced online modules, Combination
• How do you typically capture and act on driver feedback about routes and navigation? Options: Daily debriefs, Driver app feedback, Email/phone reports, No formal feedback loop, Other
• What incentives or performance measures (if any) would you consider to encourage early adoption among drivers and dispatchers?
• Do drivers have consistent access to smartphones or in‑vehicle devices that can run a mobile routing app? Options: All drivers have devices, Most drivers have devices, Some drivers have devices, Few or none have devices

Pilot Logistics: Can We Actually Run This?

• What single practical issue would derail a parallel pilot inside the first 72 hours if left unaddressed?
• Do you have a test environment or sandbox for integrations and data validation? Options: Ready now, Available with setup, No test environment, Unsure
• Which of these data feeds can your team provide during the pilot? Options: Daily stop list exports, Real‑time order API, Driver schedule/availability, Vehicle specs and capacities, Historical telematics, Customer time windows, Proof‑of‑delivery records
• How many admin/test user accounts can you provision for pilot use (dispatchers, ops, QA)? Options: 1–2, 3–5, 6–10, >10
• Who will own day‑to‑day pilot operations on your side (name, role, responsibilities)?
• Do you have an escalation path for issues during the pilot (on‑call ops, IT support windows)? Options: Yes — documented, Yes — informal, No, Unsure
• Are there regulatory or union considerations that could limit changes to routes or driver assignments during a pilot? Options: Yes — union rules, Yes — regulatory limits, No major constraints, Unsure

If This Works — What Changes Permanently?

• Imagine one year after a successful rollout: what three visible changes would prove to you we got it right?
• Which governance model would you prefer for ongoing tuning and constraint changes post‑pilot? Options: Centralized by Ops, Shared Ops + IT, Vendor‑managed with monthly reviews, Ad hoc as issues arise
• What ongoing cadence for performance reviews and tuning would you want (weekly, monthly, quarterly)? Options: Weekly, Biweekly, Monthly, Quarterly, Other
• What internal budget or headcount is realistically available to support a full rollout and ongoing optimization? Options: Budgeted and approved, Budget flexible after pilot, Needs new approval, No budget yet
• What concerns would keep you from expanding beyond the pilot even if KPIs improved (examples: cultural, technical, vendor dependency)?
• Finally, what would you like us to prepare or demonstrate in the next meeting to help your stakeholders say yes?

Quick Snapshot — Who’s Driving This Change?

• How many active route vehicles does your operation run on a typical weekday? Options: 1–20, 21–50, 51–200, 201–500, 501–2,000
• Which roles will be directly involved in evaluating or running a pilot (pick all that apply)? Options: Fleet Manager, Dispatch Supervisor, Operations Director, IT/Integrations, Finance/Procurement, Site Manager, Other
• What routing method do you primarily rely on today? Options: Manual dispatch (spreadsheets/experience), In-house optimization tool, Basic mapping tool (e.g., Google Maps), Third-party optimizer, TMS with limited routing, Other
• Roughly how many hours per day does your dispatcher team spend building and adjusting routes? Options: Under 1 hour, 1–2 hours, 2–4 hours, 4–8 hours, 8+ hours
• Who is the primary internal champion for improving routing and why (short description)?

If Your Routes Could Talk, What Would They Complain About?

• What if your daily routing process is the main reason your costs aren’t improving—how true does that feel? Options: Very true, Somewhat true, Neutral, Not true
• Describe a recent day where routing broke down—what happened, which routes were affected, and what was the outcome?
• Which recurring operational failure modes cause the most disruption (pick up to 4)? Options: Late deliveries / missed windows, Excessive deadhead miles, Uneven workload across drivers, Frequent day-of reassignments, Vehicle capacity mismatches, Manual data errors, Telematics gaps
• How often do last‑minute changes (cancellations, rush orders, driver call-offs) force on-the-fly re-routing? Options: Daily, Several times/week, Weekly, Monthly, Rarely
• When those disruptions happen, how does it typically feel for your dispatchers and drivers (stress, embarrassment, relief, indifference)? Options: High stress, Frustration, Demoralizing, Manageable, Other

Where Is Money Quietly Leaking From Your Network?

• Would you be surprised if simple routing changes recovered between 5–15% of your variable route cost—how believable is that to you? Options: Very believable, Somewhat believable, Not sure, Unlikely
• Which financial levers matter most when you evaluate routing improvements? Options: Fuel cost, Driver wage/overtime, Maintenance costs, Miles driven, Cost per stop, Customer SLA penalties
• What KPIs are you currently tracking to measure route performance (select all that apply)? Options: Miles per route, Stops per route, On-time delivery %, Driver overtime hours, Cost per stop, Customer NPS/complaints, Other
• Do you have a baseline value for cost-per-stop, miles-per-route, or on‑time % we can use for pilot comparison? If yes, please list which and the figures.
• Who in finance or operations will sign off on the ROI assumptions for a pilot? Options: CFO/Finance lead, Operations Director, Fleet Manager, Site Manager, Other

What Are You Quietly Assuming About Your Data and Systems?

• If your integrations were weaker than you think, how would that undermine a 30–60 day pilot? Options: Data delays, Incorrect routes, Inability to measure, Driver app failures, Other
• Which source systems must we integrate with to run a meaningful pilot? Options: Order management / OMS, WMS, Telematics / AVL, HR / Driver schedules, Customer database, Dispatch system / TMS, Other
• How complete and accurate are your current address and time-window data (pick the best fit)? Options: >95% accurate, 80–95% accurate, 60–80% accurate, <60% accurate, Unknown
• What constraints are non‑negotiable for your routes (vehicle types, temperature classes, driver breaks, customer rules)? Please list and prioritize.
• Have you previously attempted integrations or pilots that failed due to IT or data issues? Tell us what went wrong and how long it took to surface the problem.

Challenge: What Would Have to Go Wrong for the Pilot to Feel Like a Waste?

• What are the top three reasons you’ve declined pilots or new tools in the past?
• Which of these would be an immediate show-stopper for a pilot (pick any that apply)? Options: No data access, Inability to run parallel routes, Security concerns, Unclear success metrics, Excessive IT time, Driver refusal
• If the pilot produced mixed results (e.g., miles saved but some late deliveries), what decision rule would you use to proceed or stop? Options: Proceed with tuning, Extend pilot, Stop and reassess, Proceed for limited rollout, Other
• How emotionally ready is your operations team to trust an automated plan on day one—what would make them comfortable? Options: Side-by-side comparison, Dispatcher override controls, Driver input loop, Incremental rollout, Other
• Who has final authority to call the pilot unsuccessful? Options: Operations Director, Fleet Manager, Cross-functional committee, Finance, Other

Designing a Pilot That Proves Value — What Would That Look Like?

• If a pilot must show clear ROI in 30–60 days, what minimum percentage improvement in miles or cost would convince you? Options: >20%, 10–20%, 5–10%, <5%, Unsure
• Which objective pilot metrics would you require us to capture and report daily (pick up to 5)? Options: Miles driven, Stops completed, On-time %, Driver overtime hours, Stops per route, Fuel consumption, Driver feedback score
• Which sample of routes would give you confidence (pick one)? Options: High-density urban, Long rural routes, Mixed urban/rural, Peak-day routes, Problem routes only, Representative cross-section
• What access can you commit for the pilot: order feeds, telematics, driver mobile devices, and a sandbox environment? Please name which and any limitations.
• Who will own day-to-day pilot oversight and who will be the single point of contact for data validation?

How Will Your Team Know You’ve Succeeded?

• If the pilot is wildly successful but causes short-term friction for dispatchers, what outcome would still justify scaling?
• What specific acceptance thresholds matter most (choose up to 3): miles saved %, on-time %, stops per route %, driver overtime reduction %, cost per stop reduction %? Options: Miles saved %, On-time %, Stops per route %, Driver overtime %, Cost per stop %, Other
• How will you validate the data—do you have a team or tools that will independently audit pilot results? Options: Internal analytics team, Third-party auditor, Vendor-provided reports only, No current validation process
• If pilot metrics hit targets but drivers report negative operational friction, which wins: metrics or driver sentiment? Options: Metrics win (tune later), Driver sentiment wins, Balance both equally, Need case-by-case
• How quickly do you expect actionable tuning changes after pilot data comes in (pick one)? Options: Within 1 week, 2–4 weeks, After pilot ends, Unsure

Scaling Up: What Would a Smooth Rollout Need to Feel Like?

• What would it take for your dispatchers to prefer the new system over their manual process—what features, controls, or assurances?
• Which training model fits your workforce (pick all that apply)? Options: Hands-on sessions, Train-the-trainer, On-demand videos, Shadowing during live routing, Documentation + cheat-sheets
• How do you prefer support during rollout—dedicated onsite resource, remote daily check-ins, or ad-hoc escalation? Options: Onsite resource, Daily remote check-ins, Ad-hoc escalation, Self-service
• What integrations or internal approvals typically slow down deployments in your environment?
• After rollout, what cadence for performance reviews would you want (pick one)? Options: Weekly for first month, Bi-weekly for two months, Monthly ongoing, Quarterly

Real Risks, Non-negotiables, and Final Must-haves

• What security or compliance requirements must we meet before any data is shared (e.g., SOC2, ISO, contractual clauses)? Options: SOC2, ISO 27001, Data residency, Contractual NDA, Other
• Are there any contractual or procurement constraints (PO process, net terms, insurance limits) that would block a pilot?
• What level of system uptime or performance is acceptable during the pilot (pick one)? Options: >99.9%, >99%, 95–99%, Lower acceptable for pilot
• What’s non‑negotiable for your drivers or operations team (e.g., ability to override routes, route visibility, safety limits)?
• If you could remove one internal barrier right now to make a pilot faster and more likely to succeed, what would it be?

Next Moves — Small Bets to Build Confidence

• Assuming we align on scope, how soon could you start providing data and access for a pilot? Options: Immediately (within 1 week), 2–4 weeks, 1–2 months, More than 2 months
• Who are the five people we need involved in the kickoff (name, role, email if known)?
• What is your preferred pilot start window—do you have seasonal peaks we must avoid? Options: Within 2 weeks, 2–6 weeks, Next quarter, After peak season, Other
• Would you like an initial technical checklist sent to your IT lead to speed approvals (we’ll request access details and integration specs)? Options: Yes — send checklist, Maybe — discuss first, No
• Is there anything else we haven’t asked that you feel would make or break this engagement?