Autonomous vehicle companies close pilots with fleet operators and OEMs all the time, but most of those pilots never convert into a signed, recurring contract with a real forecast behind it. We install the revenue operating system – pipeline stages, systems, and a conversion process – that turns technical validation into booked revenue.
The Problem
Pilots don't have an exit ramp to a contract
Most AV companies run pilot after pilot with fleet operators, terminals, or OEMs, and each one ends the same way: the technical team calls it a success, and then nothing happens. There's no defined set of criteria for when a pilot converts to a commercial agreement, so deals sit in limbo for a year or more while the team burns runway proving the same thing to the same buyer. Investors and the board see pilot logos on a slide and no matching revenue on the P&L.
The buying committee is bigger and slower than a normal enterprise deal
An AV deal isn't one buyer – it's safety and regulatory, engineering validation, procurement, operations, and an executive sponsor, often at both your company and the customer's. Without a process that tracks each stakeholder's sign-off separately, a deal that looks 90 percent closed can die because the safety team never actually signed off, or procurement was never looped in until the contract was on the table. Nobody owns the coordination, so it defaults to whoever remembered to send the last email.
Forecasts are disconnected from the milestones that actually gate revenue
In AV, revenue timing depends on things sales reps don't control: a safety certification, a permit approval, a technical validation gate, a regulatory filing. When the CRM only tracks generic stages like "proposal" or "negotiation," the forecast has no relationship to what's actually blocking the deal. Leadership walks into board meetings with a number that misses by a full quarter because the thing holding up the deal was never on anyone's dashboard.
BD, partnerships, and engineering are working off different systems
Business development runs deals in a CRM, partnerships tracks OEM relationships in spreadsheets, and engineering tracks pilot performance data in its own tools. Nobody has one place to see whether a pilot is technically on track and commercially on track at the same time. Deals get renewed or expanded based on gut feel because the data that would tell you the truth is split across three teams that don't talk to each other.
How We Help
We start with an assessment of your actual deal flow, not your CRM's version of it. We pull every open pilot, POC, and commercial conversation and map what's really blocking each one: a technical gate, a regulatory step, a procurement process, or just nobody driving it.
From there we build a revenue operating model specific to how AV deals actually progress – stages tied to pilot commitment, technical validation, safety and regulatory sign-off, and commercial contract, not the generic stages a normal B2B CRM ships with. Every stage has an exit criteria and an owner.
Execution means rebuilding or reconfiguring your CRM and reporting so BD, partnerships, and engineering are working off the same record of truth. Pilot performance data, stakeholder sign-off status, and commercial terms live in one place instead of three.
We also fix forecasting. Instead of a number built on sales rep optimism, the forecast is built on the actual gates – which deals are waiting on a safety certification, which are waiting on a customer's internal procurement cycle, which are commercially ready and just need paper signed. That number is defensible in a board meeting because it's traceable to a specific milestone, not a rep's gut feel.
What makes this different from a normal RevOps engagement or a traditional consulting shop is that we're fractional and embedded. We're not handing you a slide deck and disappearing – we sit in your pipeline reviews, work directly with BD and engineering leads, and build the system alongside your team so it survives after we're gone.
Measurement is ongoing, not a one-time report. We set up a weekly cadence that tracks pilot conversion rate, time-in-stage by gate type, and forecast accuracy against actuals, so leadership can see whether the system is actually working and adjust it before a quarter goes sideways.
The deliverables below are what you walk away with – not a report telling you what's wrong, but a working system your team runs after the engagement ends.
What we deliver
- Revenue operating model with AV-specific stages (pilot commit, technical validation, safety/regulatory sign-off, commercial contract) and defined exit criteria per stage
- Unified CRM and reporting setup that gives BD, partnerships, and engineering one shared view of every deal
- Pilot-to-contract playbook defining exactly what has to happen, and who owns it, to convert a successful pilot into a signed agreement
- Milestone-based forecasting model tied to technical and regulatory gates instead of generic deal stages
- Weekly pipeline review cadence and board-ready reporting that ties pipeline health to the milestones actually driving it
A pilot that never gets a defined conversion process isn't a sales win in progress – it's a cost center with a customer logo attached.
Our Methodology
We run this as a 90-day sprint, not an open-ended retainer. The first two to three weeks are assessment: we audit every open pilot and deal, interview BD, partnerships, and engineering leads separately, and identify exactly where deals are stalling and why. This phase ends with a clear map of your real pipeline versus your reported pipeline.
Weeks three through six are build: we design the stage model, the pilot-to-contract playbook, and the CRM/reporting rebuild, and we validate it with the people who will actually run it day to day. We don't build a system in isolation and hand it over – BD and engineering leads are in the room shaping it, because a revenue process nobody agreed to gets ignored within a month.
Weeks seven through twelve are execution and handoff: we run the new system on live deals, sit in the weekly pipeline reviews, coach the team on using it, and tighten the forecasting model against real outcomes. By day 90, your team owns the system – we're not a permanent layer of overhead. That's the difference from a traditional consulting engagement, which usually ends with a recommendations deck, or a generic RevOps agency, which usually installs a template that ignores how technical and regulatory gates actually control your revenue timing.
How We Work
Days 1-30 are assessment and design: full pipeline audit, stakeholder interviews across BD, partnerships, and engineering, and a draft of the new stage model and playbook for your team to react to. By day 30 you have a documented picture of where every deal actually stands and a proposed system to fix it.
Days 31-60 are build and integration: we configure the CRM and reporting changes, finalize the pilot-to-contract playbook, and start running the new forecasting model alongside your existing one so leadership can compare the two before fully switching over. This is also when we set up the weekly cadence that will carry the system forward.
Days 61-90 are live execution: the new system runs on your actual open deals, we sit in pipeline reviews, and we adjust the model based on what's actually happening rather than what we assumed in week one. By the end of the sprint your team is running the cadence independently, with us available for a lighter-touch check-in period rather than embedded full time.
Our team is fractional – typically one senior operator embedded two to three days a week, backed by the rest of the Winston Francois team for CRM configuration and reporting build. We're not staffing a junior account manager and calling it revenue operations. We work directly with your CEO, VP Marketing, or Head of BD, and we expect the same level of access in return – open pipeline data, real stakeholder interviews, and a seat in the meetings where deals actually get discussed.
- Faster, clearer pilot-to-contract conversion with a defined process instead of ad hoc follow-up
- Forecast accuracy improvement because the number is tied to actual technical and regulatory gates
- One shared view of deal health across BD, partnerships, and engineering instead of three disconnected systems
- A pipeline reporting cadence leadership and the board can actually trust quarter over quarter
If your autonomous vehicles company needs revenue operations leadership, we should talk.
Expand your marketing team output with our experts
Let us take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.
Frequently asked questions
How much does a revenue operations engagement cost for an AV company?
It depends on how much of your CRM, reporting, and process needs to be rebuilt versus reconfigured, and how many deal types you're running (fleet operator pilots, OEM programs, municipal contracts, and so on). We scope it after the initial pipeline audit so you're not paying for work you don't need.
How long until we see results?
The assessment phase alone, in the first 30 days, usually surfaces stalled deals and missing ownership that you can act on immediately. The full stage model, playbook, and reporting rebuild are live and running on real deals by day 60.
How does your team integrate with ours during the engagement?
We embed with your BD, partnerships, and engineering leads rather than working from the outside. Expect a senior operator in your pipeline reviews, direct working sessions with whoever owns the CRM, and regular check-ins with the executive sponsor, usually the CEO or VP Marketing.
What makes Winston Francois different from a traditional RevOps consultancy or agency?
Most RevOps consultancies install a generic B2B SaaS pipeline template and move on. AV deals don't work like SaaS deals – they're gated by safety validation, regulatory approval, and multi-stakeholder technical sign-off, and a generic stage model ignores all of that.
How do you measure ROI on a revenue operations engagement?
We track pilot-to-contract conversion rate, time spent in each pipeline stage broken out by gate type, and forecast accuracy against actual outcomes each quarter. The clearest signal is whether the number you bring to the board matches what actually closes – if forecast variance shrinks and pilots stop sitting indefinitely without a next step, the system is working.
What kind of AV company is the right fit for this?
Companies at Series A through growth stage, generally in the $5M to $100M ARR range, that already have paying customers or converted pilots but are struggling to scale that process – whether you're building AV software, sensors, fleet management tools, or teleoperation services. If you're pre-revenue and still purely in R&D, this isn't the right engagement yet.
