A cleantech deal's true status is spread across your CRM, an engineering project tracker, a financing partner's portal, and a permitting jurisdiction's own timeline – with none of them communicating. We build the revenue operations layer that reconciles those systems into one forecast your leadership can genuinely trust, and one quota structure that accounts for how differently deals progress by project size and jurisdiction. The result is a forecast grounded in reality rather than corrected at every board meeting.
The Challenge
Deal Status More Often Lives Outside the CRM Than Within It
A deal's real state – permitting approved, interconnection queue position, financing close date – frequently lives in an engineering project management tool or a financing partner's portal, not your CRM. Sales updates a stage field based on a conversation, while the actual bottleneck sits in a system nobody reconciled against it. Forecasts built purely off CRM stage data end up disconnected from what's actually happening in the field.
Revenue Recognition Doesn't Fit a Simple Close-Date Model
Long installation timelines mean revenue often recognizes across milestones – contract signing, permitting, installation, interconnection, commissioning – rather than at a single close date. When your revenue ops model still treats a deal as won-or-not-won at close, finance ends up reconciling actual recognized revenue against a sales forecast that was never built to reflect milestone-based recognition, and the two numbers never quite match.
Quota and Territory Design Overlooks Vastly Different Deal Cycles by Segment
A residential-adjacent C&I deal can close in three months; a utility-scale project can take two years and depends on an interconnection queue position outside anyone's control. When quota and territory design applies the same cycle-length assumptions across segments, reps working genuinely longer, more complex deals get penalized against a comp plan built for the fast segment, and attrition follows.
Jurisdiction-by-Jurisdiction Differences Break Standard Pipeline Reporting
Permitting timelines, interconnection rules, and incentive eligibility vary by state and even by utility territory, which means two deals at the same CRM stage can be months apart in real timeline. Standard pipeline reporting that treats all deals in a stage as equivalent produces forecasts that look precise and are actually meaningless, because the underlying variance by jurisdiction was never built into the model.
How We Can Help
We begin by mapping where the truth about deal status actually sits across your CRM, engineering project tools, and financing partner portals, then identifying the reconciliation gaps currently corrupting your forecast. Most cleantech revenue ops challenges stem from this precise gap – not a CRM configuration problem, but a systems-integration problem.
Next, we build an integration or, when full integration isn't practical, a structured manual reconciliation process that brings actual permitting, interconnection, and financing status into your CRM on a defined cadence. That way, sales stage reflects field reality rather than an optimistic estimate. This work frequently runs alongside our /services/marketing-ops-for-cleantech-energy/ engagements because the same systems and data hygiene problems typically affect both functions.
We reconstruct your revenue recognition model around milestone-based recognition – contract, permitting, installation, interconnection, commissioning – so sales and finance forecast using the same definition of "revenue," rather than reconciling separate numbers at every quarter close.
For quota and territory design, we create segment-specific models that reflect genuine cycle-length differences – with distinct targets and compensation structures for fast-cycle and long-cycle segments, so reps handling legitimately harder, longer deals aren't evaluated against a timeline that doesn't fit their book of business.
To address jurisdiction variance, we create a pipeline reporting layer that weights deals using actual jurisdiction-specific timeline data – permitting speed, interconnection queue depth, incentive eligibility windows – rather than assuming every deal in the same CRM stage is equal. This gives leadership a forecast with meaningful confidence intervals instead of false precision.
We also establish the recurring reporting cadence your leadership and board truly need – a rolling forecast that incorporates milestone-based recognition and jurisdiction variance, delivered according to your board meeting calendar rather than a generic monthly template.
Most revenue ops consultants use a standard SaaS playbook – MQL-to-SQL conversion, standard sales stages, monthly recurring revenue models – that doesn't suit a business based on multi-year, milestone-recognized, jurisdiction-variable deals. We design the model around the way cleantech deals actually progress.
At the end of the engagement, your forecast incorporates real permitting and financing status, your quota model accounts for true cycle-length variance, and your board receives one number rather than four competing ones.
What we deliver
- CRM-to-engineering-to-financing reconciliation process for deal status truth
- Milestone-based revenue recognition model aligned between sales and finance
- Segment-specific quota and territory design accounting for cycle-length variance
- Jurisdiction-weighted pipeline reporting reflecting real permitting/interconnection variance
- Board-ready rolling forecast cadence
- Coordinated data hygiene process with /services/marketing-ops-for-cleantech-energy/
Two deals in the same CRM stage may be a year apart in actual timeline after accounting for jurisdiction – yet most revenue ops models don't include that variance in the forecast whatsoever.
Our Methodology
We deliver revenue ops engagements as a 90-day sprint. Days 1-30 focus on audit: mapping where the truth about deal status resides across systems, comparing your current revenue recognition model with finance's actual close process, and finding quota-model mismatches across segments.
Days 31-60 focus on building: implementing the reconciliation process, milestone-based recognition model, and segment-specific quota design, all tested against live deals instead of a hypothetical model. Days 61-90 cover rollout: launching the jurisdiction-weighted reporting layer and board-ready forecast cadence, while training your team to maintain it.
This isn't a generic SaaS revenue ops framework repurposed for another vertical. It's designed around milestone-based recognition, jurisdiction-by-jurisdiction timeline differences, and deal cycles that may last two years while depending on factors outside any rep's control.
Our Working Process
Weeks 1-4: the audit phase, mapping systems and reconciliation gaps, with a written findings report identifying specific points of forecast corruption. Weeks 5-8: the build phase, implementing the reconciliation process, recognition model, and quota redesign directly within your CRM and finance systems.
Weeks 9-12: rollout, launching jurisdiction-weighted reporting and the board forecast cadence, along with one complete reporting cycle conducted beside your team.
You receive a lead strategist responsible for the systems and recognition model work, a data specialist who develops the reconciliation and reporting integration, and a compensation design lead who rebuilds quota and territory models – meeting each week with your sales, finance, and RevOps leadership throughout the build phase.
During the build phase, expect a written status update each Friday and direct visibility into the specific reconciliation gaps being closed every week. We flag forecast-corrupting data gaps on the day they're discovered, not at quarter close.
If the forecast in your board deck never aligns with what finance actually recognizes, let's talk.
- Forecast accuracy that reflects real permitting and financing status
- Quota and comp models that fairly account for cycle-length variance
- Aligned revenue recognition between sales and finance
- A board forecast leadership can trust without a manual reconciliation pass
If your cleantech & energy 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 revenue operations support cost for a cleantech company?
Most engagements cost $10K-$18K monthly throughout the 90-day sprint, based on the number of systems requiring reconciliation and how many sales segments need distinct quota models. A single-segment company working with one financing partner costs less than a multi-segment business covering residential-adjacent, C&I, and utility-scale deals. We determine pricing after an initial systems and forecast audit.
How soon will our forecast become more accurate?
Once systems access is established, the reconciliation process begins closing the largest forecast-corrupting gaps within the first 30 days. Complete forecast accuracy, including the jurisdiction-weighted model and revised quota structure, is validated across one full reporting cycle during the 90-day engagement, then further confirmed as it holds through subsequent board cycles.
How does your team collaborate with our current RevOps, sales, and finance staff?
We collaborate directly with the people currently responsible for your CRM, sales operations, and finance reporting, because the reconciliation process must be built alongside those who know where the real data gaps exist. We document the entire process so your internal team can maintain the model after the engagement instead of leaving its logic dependent on us.
How is Winston Francois different from a typical RevOps consultancy?
A typical RevOps consultancy uses a standard SaaS playbook – MRR models, MQL-to-SQL funnels, uniform sales stages – that fails to account for milestone-based revenue recognition, jurisdiction-by-jurisdiction permitting differences, or deal cycles that may take two years due to a variable beyond anyone's control. We built this specifically around how cleantech and energy deals actually progress through procurement and interconnection.
How do you evaluate ROI from a revenue operations engagement?
We measure forecast variance (the difference between the rolling forecast and actual recognized revenue), reduced manual reconciliation time ahead of board meetings, and whether quota attainment becomes fairer across segments with varying cycle lengths. We don't guarantee a particular revenue lift because this work focuses on forecast accuracy and operational trust, rather than directly driving top-line growth.
What kind of cleantech company is best suited to this service?
This service is best suited to companies with $5M-$100M ARR managing deals across multiple segments or jurisdictions, with genuine complexity in permitting, interconnection, or financing timelines. A single-segment, single-jurisdiction business with simple deal cycles may not require this degree of rebuild yet. If your board repeatedly asks why the forecast differs from what finance recognized last quarter, that's the sign that it's time.
