Blog

Revenue Operations for Drone Tech Companies

by Jason Shafton

Drone companies sell hardware, software subscriptions, drone-as-a-service contracts, and sometimes data feeds through the same sales team. Yet most RevOps stacks follow a single-ARR-line SaaS playbook that cannot account for a pilot program held up by a Remote ID waiver. We redesign pipeline stages, forecasting models, and comp plans around how drone deals really progress – and stall.

The Challenge

A single CRM stage list is expected to explain four distinct revenue motions

A single deal can carry a hardware sale or lease, a software subscription, a drone-as-a-service line, and sometimes a data or analytics fee, all under one account. Most CRMs were configured around a single ARR number, so reps either force four revenue types into one opportunity object or spin up parallel deals that never roll up cleanly. Leadership ends up reading a pipeline report that cannot answer a basic question: how much of next quarter is hardware margin versus recurring software revenue.

Pilot, regulatory, and fulfillment statuses sit in three separate systems outside the CRM

Whether a pilot program is scoped, running, or stalled sits in a project tracker or an ops team's spreadsheet. Part 107, BVLOS, and Remote ID approval status sits with whoever owns compliance, often outside sales entirely. Hardware lead time and fleet availability sit in the fulfillment or fleet-management tool. None of it syncs to the CRM, so a rep tells a VP a deal is 'in pilot' with no visibility into whether the pilot is actually flying or waiting on a waiver that compliance has been chasing for six weeks.

The sales cycle combines an extended pilot phase with procurement centered on safety sign-off

A generic B2B funnel goes from qualified lead to demo to proposal to close. A drone deal goes from qualified lead into a 60-to-180 day pilot against a real site, real weather, and a real ops team, then into a procurement process that requires safety and compliance sign-off before a PO gets cut – often from a buyer group that never touched the pilot. Forcing that motion into generic funnel stages means the CRM shows deals sitting in 'proposal' for four months with no way to tell whether they're progressing or dead.

Forecasts fall short because a pilot is not a typical funnel stage – it stalls for reasons beyond sales' control

A pilot can stall because a customer's budget cycle resets, because a waiver takes longer than expected, or because the customer's own ops team is short-staffed to run the flights – none of which show up as sales activity or inactivity in a standard CRM. Forecast models built on stage-duration and rep-activity signals treat a stalled pilot the same as a dead deal or a slow-moving one, so the forecast is wrong in both directions: pilots that will convert get written off, and pilots that are quietly dead stay in the number for two more quarters.

How We Support You

We begin by mapping every system involved in a deal – the CRM, the pilot-tracking tool or spreadsheet, the fleet-management or ops platform, and whatever records regulatory approval status – then identify where one deal appears in three places with three conflicting versions of the truth.

Our strategy work restructures pipeline stages around what really occurs in a drone sale: pilot scoping, pilot execution, procurement and compliance review, and PO.

Execution involves connecting pilot-tracking and fulfillment data to the CRM, even if that requires a scheduled sync from a spreadsheet or ops tool instead of a clean API. Partial automation is still better than having a rep manually re-enter pilot status from memory.

Measurement is where our [forecasting](/services/measurement/) work happens. We create a forecast model that distinguishes 'stalled for a reason outside sales control' from 'stalled because the deal is dying' by treating regulatory and procurement blockers as separate signals rather than burying them in generic stage-duration math.

Unlike a generic RevOps build, this approach is designed around the blended revenue model instead of imposing a single-ARR-line SaaS system on it.

What we deliver

A pilot program is not merely a sales-funnel stage. It is an operations project tied to a sales outcome, and treating it as 'proposal sent' is why half of forecast misses are really waiver delays disguised as sales problems.

Our Methodology

We deliver this through a 90-day sprint. Days 1 through 30 focus on the audit: we examine every system connected to a live deal – CRM, pilot tracker, fleet-management tool, regulatory-status log – and compare them with a sample of open pipeline to uncover where the CRM misrepresents a deal's status. We also document the blended revenue lines currently in use (hardware, software, DaaS, data) and the inconsistent ways they are recorded today.

During days 31 through 60, we create the new pipeline stage model, multi-line revenue data structure, and sync mechanism connecting the CRM with whichever system owns pilot and regulatory status – whether that is an API or a scheduled import from a spreadsheet already maintained by the ops team. We also redesign comp plan and territory logic at this stage, partnering with sales leadership so reps buy into the new structure before launch rather than afterward.

Days 61 through 90 establish the forecast model and test it against a live quarter alongside the previous method, letting leadership compare both forecasts before making the full transition. We hand over a pipeline-review cadence that your RevOps or sales-ops lead can manage without us, with stage definitions, the sync process, and forecast logic documented clearly enough for a new hire to take over.

The Insights You Want

Right in your inbox. We’ve done the work, and now we’re sharing it with you. Sign up to stay in the loop.

Get The Latest Updates


Enter your email address

Our Working Approach

The 90-day sprint described above is the primary engagement, followed by an optional lighter quarterly check-in to recalibrate the forecast model as your revenue mix changes. For the first 30 days, we require access to your CRM admin console, pilot-tracking system (however informal), fleet or fulfillment tools, and the person responsible for regulatory/compliance status – without this access, redesigning stages becomes guesswork.

Our team includes a RevOps lead responsible for redesigning the pipeline and data model, along with a sales-ops analyst who develops the sync layer and forecast reporting. On your side, we need a RevOps or sales-ops counterpart, as well as time with a sales leader, a compliance or regulatory owner, and whoever manages pilot or fleet operations. The stage model must represent what these teams truly do, not what a generic sales playbook expects.

The cadence includes weekly working sessions with your counterpart throughout the 90 days, plus a biweekly checkpoint with sales and revenue leadership to assess the stage model and forecast updates as they develop. Comp plan and territory updates follow your current approval process – we provide the design and modeling, while you and sales leadership decide the final rollout schedule.

Since pilot cycles are lengthy, expect forecasting to become visibly more stable over one to two quarters as the new stage definitions and blocker-tracking gather enough deal history to become reliable. Within the 90 days, you receive a pipeline that accurately reflects where deals stand, not a promise of overnight gains in forecast accuracy.

If your drone tech 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

What does a revenue operations engagement cost for a drone tech company?

The 90-day sprint costs $20K to $45K, based on the number of systems requiring reconciliation and how many revenue lines (hardware, software, DaaS, data) are active. Companies that already centralize pilot and regulatory data in a single ops tool fall toward the lower end; those managing pilot status through scattered spreadsheets across several teams require more integration work and fall higher.

How soon will our forecast become more accurate?

The new stage model and blocker-tracking launch within the 90 days, while forecast accuracy improves as deal history builds under the new definitions – most teams notice a meaningfully tighter forecast within one to two quarters. During the build, we run the old and new forecasts in parallel so leadership can watch the gap narrow before making a full transition.

How will your team work with our current sales and RevOps staff?

Rather than replacing your existing RevOps or sales-ops function, we work through it, with a designated counterpart on your team serving as the ongoing point of contact. We also require direct access to sales leadership, the owner of regulatory/compliance status, and whoever oversees pilot or fleet operations, because the pipeline model must reflect how those teams actually operate.

How is Winston Francois different from a typical RevOps consultancy?

Most RevOps frameworks assume a single revenue line and a funnel that concludes at 'closed-won.' We design specifically for the blended mix of hardware, software, DaaS, and data revenue used by drone companies, as well as a sales cycle in which a 60-to-180 day pilot and compliance sign-off fall between qualified lead and PO. This is a fundamentally different pipeline from a SaaS RevOps build, not simply a smaller form of the same model.

How do you evaluate ROI from a revenue operations engagement?

We measure forecast accuracy (quarterly forecasted close versus actual close), the frequency with which deals are wrongly classified as active when they are actually stalled or dead, and the amount of rep and sales-ops time consumed by manually reconciling pilot or fulfillment status. The strongest indicator is whether leadership trusts the pipeline figure enough to base hiring and inventory plans on it.

What type of drone tech company is the best fit for this?

Series A through growth-stage companies with $5M to $100M ARR and a blended revenue model – hardware combined with software subscriptions, DaaS, or data fees – where pilot programs are already a routine part of the sales cycle. This is not the right fit for a company selling one hardware SKU without a recurring revenue line, because there is no blended-pipeline challenge to address yet.


Related Solutions

Solutions

Top Articles

Frank Growth – Episode 224 – The Bootstrapper’s Revenge with Alex Roy

Tuesday, June 16, 2026

Frank Growth – Episode 224 – The Bootstrapper’s Revenge with Alex Roy

Episode #224: Alex Roy — Bootstrapping an AI company for 12 years, no funding He founded an AI company in 2014—when AI was a punchline—bootstrapped it with zero outside capital, and landed Fortune 50 clients. For founders and growth operators figuring out how to build (and sell) AI products in a market that shifts every...
Frank Growth – Episode 242 – Why AI Slop Backfires with Nicole Cassese

Tuesday, October 20, 2026

Frank Growth – Episode 242 – Why AI Slop Backfires with Nicole Cassese

Episode #242: Nicole Cassese — Scaling brand voice without burning out the people behind it How to keep a brand voice consistent across 1,600+ assets and still protect the team writing them. For marketing leaders, creative directors, and copywriters running high-volume content with AI in the workflow. Nicole Cassese is the associate creative director owning...
Frank Growth – Episode 241 – What AI Still Can’t Do with Will Sartorius

Tuesday, October 13, 2026

Frank Growth – Episode 241 – What AI Still Can’t Do with Will Sartorius

Episode #241: Will Sartorius – AI didn’t kill the creative job, it moved it How to split ad creative work between AI and people so your ads stop sounding like everyone else’s. For founders and marketers running paid social who launch plenty of ads but learn little from them. Will Sartorius, CEO of Selfmade, took...
Frank Growth – Episode 246 – Google Analytics for Real Stores with Angie Westbrock

Tuesday, November 17, 2026

Frank Growth – Episode 246 – Google Analytics for Real Stores with Angie Westbrock

Episode #246: Angie Westbrock — Why Standard AI took down every autonomous checkout site How Standard AI turned an autonomous checkout company into a retail analytics business using the same tech stack. For founders and operators whose original business model isn’t working, and for anyone selling into physical retail. Angie Westbrock is CEO of Standard...

See more

Browse Categories

See more

Ready to unlock your growth?

Book Free Call

We take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.