<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Revenue House]]></title><description><![CDATA[Here we unpack the problems hiding behind B2B revenue numbers and what it takes to build a business that can with a successful revenue engine.]]></description><link>https://insights.revenue.house</link><image><url>https://substackcdn.com/image/fetch/$s_!gwLT!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fea1a4306-84c6-41be-aad7-2610ceb9d1f7_400x400.png</url><title>Revenue House</title><link>https://insights.revenue.house</link></image><generator>Substack</generator><lastBuildDate>Mon, 16 Nov 2026 11:45:01 GMT</lastBuildDate><atom:link href="https://insights.revenue.house/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Fernanda Lavigne]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[fernandalavigne@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[fernandalavigne@substack.com]]></itunes:email><itunes:name><![CDATA[Fernanda Lavigne]]></itunes:name></itunes:owner><itunes:author><![CDATA[Fernanda Lavigne]]></itunes:author><googleplay:owner><![CDATA[fernandalavigne@substack.com]]></googleplay:owner><googleplay:email><![CDATA[fernandalavigne@substack.com]]></googleplay:email><googleplay:author><![CDATA[Fernanda Lavigne]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[When to Hire Your First RevOps Person (and When Not To)]]></title><description><![CDATA[Opening a RevOps role can feel like the obvious next step when your revenue engine starts creating problems. But do those problems actually require a full-time employee?]]></description><link>https://insights.revenue.house/p/when-to-hire-your-first-revops-person</link><guid isPermaLink="false">https://insights.revenue.house/p/when-to-hire-your-first-revops-person</guid><dc:creator><![CDATA[Fernanda Lavigne]]></dc:creator><pubDate>Mon, 05 Oct 2026 22:25:09 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!FAo_!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!FAo_!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!FAo_!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!FAo_!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!FAo_!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!FAo_!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!FAo_!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:2645382,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://insights.revenue.house/i/218838236?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!FAo_!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!FAo_!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!FAo_!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!FAo_!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9dc44cd8-4871-4a7c-81cf-62b829539620_1672x941.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><h2>Having RevOps work does not mean you need a RevOps hire</h2><p>It is easy to find enough RevOps work to keep someone busy in a growing revenue team. The CRM needs attention, forecasting lacks structure, reporting is unreliable, and cross-functional processes have accumulated without clear ownership.</p><p>That can make a full-time hire feel obvious. But a large workload does not necessarily create one coherent role. The work may combine one-off fixes, recurring execution, specialist knowledge and senior commercial judgement and they all requiring different levels of expertise.</p><p>Hiring before separating those needs can leave you with the wrong profile for a large part of the job. Before opening the role, you need to understand <strong>what requires ongoing ownership, what level of judgement it needs, and how much recurring capacity it creates.</strong></p><p>That matters because RevOps is a broad function. Its remit can span forecasting, reporting, CRM and data, sales process, tooling and cross-functional handoffs. <strong>The work may all sit under RevOps, but it does not necessarily belong to one full-time hire.</strong></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://insights.revenue.house/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://insights.revenue.house/subscribe?"><span>Subscribe now</span></a></p><h2>1. A single RevOps role cannot cover every type of work</h2><p>The first RevOps hire often goes wrong when the business treats everything that falls under RevOps as one job.</p><p>But RevOps is a function, not a single skill set. The work inside it can require very different levels of seniority, expertise and judgement. Some work requires senior commercial judgement and the ability to shape how the revenue engine operates. Other work depends on specialist technical or analytical expertise, while some is recurring operational work that does not require senior experience.</p><p>When all of that is combined into one job description, the company is no longer defining a coherent role. It is asking one hire to cover several different capability requirements at once.</p><p>That creates a difficult hiring trade-off. Hire for the most senior and complex work, and a meaningful part of an expensive person&#8217;s capacity may be spent on work that does not require their level of experience. Hire for the volume of more operational work, and the person may lack the experience to make the higher-impact decisions the business also expects them to own.</p><p>This matters even more when the first hire becomes the entire function. Revenue Operations Alliance&#8217;s 2024 research found that 25.58% of respondents were operating as solo RevOps practitioners. With no wider team to absorb the mismatch, one person is expected to cover the full range of responsibilities <em>(source: <a href="https://www.revenueoperationsalliance.com/state-of-revenue-operations-report-2024/">Revenue Operations Alliance &#8212; State of Revenue Operations Report 2024</a>).</em></p><p>Having enough RevOps work to justify a salary does not mean you have one well-designed role. A company can have more than enough reasons for a job opening and still hire for the wrong combination of capabilities.</p><h2>2. Work out what the business actually needs from RevOps</h2><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!ZP5y!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!ZP5y!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!ZP5y!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!ZP5y!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!ZP5y!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!ZP5y!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1757806,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://insights.revenue.house/i/218838236?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!ZP5y!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!ZP5y!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!ZP5y!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!ZP5y!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F362a62d7-bdbf-4c66-bada-25a867cf9b38_1672x941.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>The cleanest way to define the requirement is to work backwards from what the revenue engine needs over the next 12 months. Identify the responsibilities that need ongoing ownership, then the level of judgement and capacity required to support them.</p><p>That gives you a clearer basis for the role than today&#8217;s backlog and helps separate short-term fixes from long-term needs.</p><h3>Separate the backlog from the ongoing role</h3><p>A growing company often considers hiring RevOps when several problems have accumulated at once. That backlog can make the ongoing role look bigger than it really is.</p><p>Take an unreliable forecast, as an example. Fixing it may require concentrated work to redesign the process and correct the underlying CRM structure. Once that is done, the requirement changes: someone still needs to keep the forecast reliable as the business evolves. However, that will probably require less capacity than the initial rebuild.</p><p>This is the first distinction to make across the RevOps workload. For each significant problem, ask what remains once the immediate fix is complete.</p><p>Some work may disappear once the problem is solved. Other work creates a responsibility that needs an owner month after month. That ongoing responsibility is what should start shaping the role.</p><h3>Define what ownership actually means</h3><p>Once you know which responsibilities continue, define what ownership actually involves.</p><p>Ownership goes beyond completing tasks. It means being accountable for whether that part of the revenue engine continues to work and knowing when it needs to change and that decisions may need different experience levels.</p><p>Pipeline management is a good example. One person may maintain the process and keep the CRM aligned with it. A more senior owner may need to question whether the stages still reflect how buyers move through the sales process and redesign them when they do not.</p><p>Those responsibilities sit under the same function but require very different levels of judgement. The level of experience you hire for should match the decisions the role is expected to make.</p><h3>Work out how much ongoing capacity that ownership requires</h3><p>Once you know which responsibilities need ongoing ownership and what that ownership involves, you can estimate capacity.</p><p>Start with the time required during normal operations, then account for heavier periods created by change.</p><p>This gives you a clearer picture of how much RevOps capacity the business needs and what level of ownership that capacity must support.</p><p>Imagine the business has around 35 hours of RevOps work in a typical week. Perhaps 30 of those hours are relatively operational, while only five require senior RevOps judgement.</p><p>Looking only at the total workload, a full-time senior hire can seem obvious. In practice, most of that person&#8217;s week would be spent on work that does not require their level of experience.</p><p>Hire instead for the 30 operational hours, and you create the opposite problem: the five hours requiring senior ownership are still uncovered.</p><p>Total hours tell you <strong>how much capacity</strong> the business needs. When you separate operational work from responsibilities requiring senior judgement you can better understand <strong>what level of RevOps capability</strong> the role requires.</p><h3>What you should have before moving on</h3><p>By this point, you should be able to answer three practical questions:</p><ul><li><p><strong>Which RevOps responsibilities need ongoing ownership once the current problems are fixed?</strong></p></li><li><p><strong>What level of judgement does that ownership require?</strong></p></li><li><p><strong>How much recurring capacity is needed to support those responsibilities?</strong></p></li></ul><p>If you cannot answer those three questions with confidence, the role is not defined well enough yet.</p><p>Once you do, you&#8217;ll have a  much stronger picture of the RevOps capability the business actually needs. The next decision is whether that requirement is best served by someone inside the company full time or through a fractional operating model.</p><h2>3. Decide which RevOps model fits your business</h2><p>Once the scope is clear, the next step is to decide how the RevOps role should operate inside the business.</p><p>Some companies need a senior RevOps person embedded full time, with ongoing ownership of the function as the business evolves. Others need the same level of senior judgement without requiring five days of internal capacity, making a fractional model more appropriate. And some already have the strategic direction and ownership in place but need third-party support to execute the work.</p><p><strong>The right model depends on how much senior judgement needs to stay close to the business and how much execution capacity the work requires.</strong></p><h3>When full-time RevOps is the right choice</h3><p>A full-time hire makes more sense when the role depends on continuous context, frequent strategic decisions and close coordination across the commercial team.</p><h4>The role needs a permanent seat in strategic leadership</h4><p>Senior RevOps work does not automatically need to sit inside the company. A fractional operator can still challenge the pipeline model, redesign forecasting, shape reporting and advise leadership on how the revenue engine should evolve.</p><p>The case for a full-time senior role becomes stronger when RevOps is expected to be part of the company&#8217;s leadership structure itself.</p><p>The case for a full-time senior hire becomes stronger when RevOps needs to be part of the leadership structure itself. This could mean being involved as strategic decisions are made, contributing to commercial planning and bringing a RevOps perspective into ongoing leadership discussions.</p><p>At that point, the value comes from being continuously embedded in the context around those decisions. When that level of involvement is a recurring part of the role and genuinely requires full-week participation, building senior RevOps capability internally makes more sense.</p><h4>The work depends heavily on daily internal context</h4><p>A close relationship with the commercial team is not enough to justify a full-time hire. A fractional RevOps partner can still join meetings, advise leaders and stay closely connected to the business.</p><p>The stronger case is when there is enough recurring work at the right level of expertise to fill the week. For a senior hire, that may mean continuous involvement in planning, leadership decisions and ownership of the revenue operating model. For a more execution-focused role, it may mean enough systems, reporting and operational work to require dedicated capacity.</p><p>What matters is that the role is filled primarily with work that matches the level of person being hired. If senior judgement is needed only for a few hours and the rest of the week is lower-level execution, a different RevOps model may fit better.</p><h4>You are deliberately building an internal RevOps function</h4><p>The case for an internal hire becomes stronger when the business is no longer resourcing a single role but deliberately building a RevOps function.</p><p>As the commercial organisation grows, RevOps work often separates into areas such as systems and data, planning, analysis and commercial operations. Someone then needs to decide which capabilities belong in the team, where responsibilities sit and when additional capacity should be added.</p><p>That changes the profile of the first hire. Alongside hands-on RevOps work, they may need to define roles, hire and manage additional people, and keep the function aligned to the same commercial priorities.</p><p>When the business is intentionally building that internal capability, hiring makes more sense because the role carries long-term responsibility for the function itself, not only for the RevOps work being delivered today.</p><h3>When fractional RevOps makes sense</h3><p><strong>The strength of a fractional RevOps model is that it lets the business structure the function around the work rather than around one employee.</strong> Senior ownership provides direction and continuity, while execution and specialist support are matched to what the business actually needs.</p><p>There are a few recurring situations where that model becomes particularly useful.</p><h4>You need senior judgement before you need full-time capacity</h4><p>A business may need senior RevOps judgement without needing that level of expertise for a full working week. The mismatch appears when total workload is used to justify the hire: a more junior operator may not have the experience to make the senior decisions, while a senior hire may spend much of the week on work below their level.</p><p>A fractional model separates those needs. Senior ownership stays at the right level, while execution and specialist work are resourced separately. The business gets the judgement it needs without forcing different levels of RevOps work into one role.</p><h4>The work spans more expertise than one hire can cover</h4><p>RevOps spans different types of expertise, and one person will rarely be equally strong across all of them. The person shaping how the revenue engine should operate may not also be the best person to configure the CRM, build reporting or solve a specialist data problem.</p><p>That creates gaps in a single-hire model. The person may be strong in some areas while the business remains under-supported in others. A fractional model can combine consistent senior ownership with specialist expertise where it is needed, rather than expecting one profile to cover the entire function.</p><h4>The problems need attention before a new hire is fully effective</h4><p>Hiring creates two delays: finding the right person and getting them up to speed.</p><p>SHRM&#8217;s 2026 benchmark shows that a non-executive hire takes a median of 39 days to reach offer acceptance. SHRM also cites research suggesting that new employees take around eight months to reach full productivity. Together, that can mean roughly nine months between opening the role and having someone operating at full capacity, before accounting for any notice period (<em>source: <a href="https://www.shrm.org/topics-tools/research/recruiting-benchmarking">SHRM &#8212; Recruiting Benchmarking</a></em>).</p><p>For a company already dealing with unreliable pipeline data, poor forecasting or a CRM that is slowing the commercial team down, that delay can leave important problems unresolved for months.</p><p>Fractional support can start addressing the work immediately, either as the operating model itself or while the business recruits and ramps an internal hire.</p><h4>The amount of RevOps capacity you need is likely to change</h4><p>RevOps workload changes as the business evolves. A CRM redesign may require significant capacity for several months, but once the new system is in place, the need shifts from building it to maintaining and improving it. The same pattern appears with new sales motions, planning cycles, territory changes or tooling migrations: periods of intensive work are followed by a different ongoing requirement.</p><p>A full-time role provides the same amount of capacity each week, even when the workload changes. A fractional model can adjust to those shifts while maintaining continuity of ownership.</p><p>That flexibility allows fractional RevOps to remain a long-term operating model, rather than simply serving as a bridge to an internal hire.</p><h2>4. Not every revenue problem is a RevOps problem</h2><p>RevOps often enters the conversation because the symptoms show up in the revenue system: weak pipeline, poor conversion, unreliable forecasting or inconsistent execution. But a problem appearing in the CRM or funnel does not mean RevOps is the function that can solve its underlying cause.</p><p>A weak pipeline, for example, may be perfectly measurable and still have very little to do with the revenue operating model. If too few qualified buyers are entering the funnel, the constraint may sit in demand generation, positioning or the market itself. RevOps can expose the gap and quantify its impact, but improving the system around the pipeline will not create demand that is not there.</p><p>There is also a difference between needing RevOps and needing specialist operational support. If the main requirement is maintaining CRM, managing users and fixing workflows, the business may need strong CRM administration rather than ownership of the wider revenue operating model.</p><p>Before deciding how to resource RevOps, the business needs to be clear on which problems the function is actually expected to solve. Otherwise, it risks hiring into RevOps when the real constraint sits somewhere else.</p><h2>5. Questions worth asking before making your first RevOps hire</h2><p>A well-designed RevOps role should still make sense six or twelve months after the hire. These questions help clarify ownership, decision-making, workload and what the role is actually expected to achieve.</p><h4><strong>1. What are the three most important responsibilities this person should own over the next 12 months?</strong></h4><p>A permanent role should be built around responsibilities that need continued ownership, even as the work underneath them changes. Forecasting is a good example: rebuilding the process may be temporary, but keeping the forecast reliable as the business evolves is an ongoing responsibility.</p><p>Thinking this way helps separate substantial projects from the responsibilities that genuinely need a long-term owner.</p><h4><strong>2. What should this role explicitly not own?</strong></h4><p>The first RevOps hire can easily become the default owner for anything that crosses teams, touches the CRM or lacks a clear home. Defining the boundaries prevents the role from becoming a catch-all for sales administration, marketing operations, systems support and unrelated commercial problems.</p><h4><strong>3. What level of judgement does this role need on a recurring basis?</strong></h4><p>The role should be levelled around the decisions it needs to make consistently, not the most complex task on the list. If senior judgement is only needed occasionally while most of the work is operational, a senior full-time hire may be a poor fit. If consequential decisions about the revenue engine need to be made throughout the week, the case for seniority is much stronger.</p><h4><strong>4. What becomes harder if this person is not available internally every day?</strong></h4><p>Daily presence should solve a real operating constraint. It matters when decisions happen continuously, priorities shift quickly and the role needs to influence work as it happens.</p><p>Without someone embedded internally, that can mean slower decisions, repeated context transfer and more coordination. But if priorities are clear, context can be shared effectively and decisions can run through an agreed cadence, daily presence may be useful without being essential.</p><p>The test is simple: what would materially slow down, break or become harder to manage without someone in the business full time? If there is no clear answer, the case for requiring daily internal presence is weak.</p><h4><strong>5. Are we ready to make this person successful?</strong></h4><p>A strong hire still needs the right operating environment. Because RevOps sits across Sales, Marketing and Customer Success, the role needs clear decision rights, access to the right information, leadership support and enough authority to challenge how the revenue engine operates.</p><p>The company also needs to be clear on priorities and success measures. If every function can pull RevOps in a different direction, or success is reduced to completing requests, the role quickly becomes reactive. It needs a clear mandate, agreed outcomes and a way to separate high-value commercial work from day-to-day operational demands.</p><p>RevOps cannot compensate for unclear ownership, competing priorities or weak executive alignment. If the business is not prepared to give the role the authority and support it needs, adding headcount will not solve the underlying problem.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!9R8l!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!9R8l!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!9R8l!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!9R8l!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!9R8l!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!9R8l!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1818350,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://insights.revenue.house/i/218838236?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!9R8l!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!9R8l!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!9R8l!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!9R8l!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16b54213-9168-465d-8f76-2009093ebfd4_1672x941.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><h2>6. How Revenue House approaches the decision</h2><p>A RevOps hire should come after the operating model is clear, not become the way the business figures it out.</p><p>Revenue House helps companies make that decision before adding headcount: diagnosing where the revenue engine is failing, defining the capability required to improve it, and determining the right structure for ongoing ownership.</p><p>Sometimes that leads to a full-time internal role. In other cases, the <strong><a href="https://revenue.house/services/#partner">Revenue Engine Partner</a></strong> provides ongoing fractional ownership across CRM and data, sales process, pipeline and forecasting, reporting, tooling and the continued development of the revenue system.</p><p>The first RevOps hire can set the shape of the function for years. A poorly designed role creates gaps, wasted capacity and expectations that one person was never equipped to meet. A well-designed one gives the business the ownership and capability it actually needs.</p><p>That is why the quality of the decision matters more than the speed of the hire.</p><p></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.revenue.house/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Revenue House! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Why Your Sales Forecast Is Always Wrong]]></title><description><![CDATA[When revenue misses the forecast, the gap often exposes a problem that started much earlier, in the way the pipeline was built.]]></description><link>https://insights.revenue.house/p/why-your-sales-forecast-is-always</link><guid isPermaLink="false">https://insights.revenue.house/p/why-your-sales-forecast-is-always</guid><dc:creator><![CDATA[Fernanda Lavigne]]></dc:creator><pubDate>Sun, 27 Sep 2026 21:12:35 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/da3101f4-ed2e-4046-a6a1-35fc3c01f2b2_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!f8XZ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!f8XZ!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!f8XZ!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!f8XZ!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!f8XZ!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!f8XZ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:2224500,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://fernandalavigne.substack.com/i/217728322?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!f8XZ!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!f8XZ!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!f8XZ!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!f8XZ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff7383e18-dd06-4e72-8080-53e01627d15e_1672x941.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://insights.revenue.house/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://insights.revenue.house/subscribe?"><span>Subscribe now</span></a></p><h2>The problem with an unreliable forecast is that it can look convincing until reality proves it wrong.</h2><p>There is a familiar sequence that plays out in B2B companies at the end of a bad quarter. <br>A few weeks earlier, the forecast looked reasonable. There was enough pipeline to support the target. The largest opportunities were progressing. The sales team felt confident about the deals expected to close. Leadership might even have made decisions on the back of that number: hiring, spending, cash planning or targets for the following quarter.</p><p>Then the quarter ends and the number is wrong.</p><p>A $1.2M forecast becomes $800K in actual revenue. Deals that were supposed to close in September suddenly have October dates. An opportunity everyone had been talking about for months quietly disappears. Another closes at half the expected value.</p><p>The post-mortem normally starts with the forecast itself.</p><p>Were the probabilities wrong? Were the salespeople too optimistic? Should managers have challenged the deals more aggressively? Do we need a better forecasting tool? Should we introduce another category between &#8220;best case&#8221; and &#8220;commit&#8221;?</p><p>Those can all be reasonable questions. But they start too late.</p><p>If you are asking <strong>why your sales forecast is always wrong</strong>, the more useful place to look is usually the pipeline that produced it.</p><p>A forecast does not exist independently from your revenue operation. It is the final output of dozens of earlier decisions: what your company considers an opportunity, when a deal moves stage, how its value is calculated, why a close date is entered, when an inactive opportunity is removed, and what evidence is required before a salesperson can say that something is likely to close.</p><p>If those inputs are inconsistent, the forecast can be mathematically perfect and commercially useless.</p><p>That is why improving forecast accuracy often has less to do with becoming better at predicting the future and more to do with becoming better at describing what is happening now.</p><h2>Your forecast is only as good as your pipeline data</h2><p>It is useful to think of the forecast as the last step in a much longer process. Your pipeline data shows the opportunities the business believes are active and progressing. The forecast then uses that information to estimate how much revenue is likely to close within a particular period.</p><p>So if the pipeline data is unreliable, the forecast will be too.</p><p>Imagine a business with $2M of open opportunities against a $600K quarterly target. On the surface, that looks healthy. But the number only matters if the opportunities behind it are credible. They need to be genuinely qualified, sitting in the right stages, carrying realistic values, attached to defensible close dates and, most importantly, still connected to an active buying process.</p><p>This is where forecasting can create a false sense of precision. A $100K opportunity sitting in a stage with a 60% probability contributes $60K to the weighted pipeline. The maths is perfectly correct, but that does not make the output reliable.</p><p>If the opportunity should not be in that stage, the probability is wrong. If the buyer has not agreed the scope, the deal value may be wrong. If the close date exists only because the CRM required one, the timing may be wrong too.</p><p>The calculation can be perfectly sound while the data feeding it is weak.</p><p>This is also why adding sophistication at the forecasting layer rarely fixes a weak revenue system. More categories, AI scoring, stricter calls and more elaborate spreadsheets can improve the way information is analysed, but they cannot compensate for pipeline data that gives an inconsistent picture of what is actually happening.</p><p>Before changing the forecasting methodology, you need confidence that your pipeline data reflects commercial reality: real opportunities, meaningful progress, credible timing and active buying processes.</p><h2>Five pipeline problems that make your forecast less reliable</h2><p>Most forecast problems can be traced back to decisions made much earlier in the sales process. The exact symptoms vary from company to company, but five issues appear repeatedly: when a prospect becomes an opportunity, how deals move through stages, how probabilities are assigned, how close dates are set, and how long inactive opportunities are allowed to remain open.</p><h3>1. Prospects become opportunities too early</h3><p>A prospect replies to an email, agrees to a call or says the product sounds interesting. One salesperson creates an opportunity immediately. Another salesperson on the same team waits until the buyer has confirmed a real problem, discussed a credible project and agreed to a next step.</p><p>Both eventually show up in the CRM as opportunities, even though the level of buying intent behind them can be completely different.</p><p>At a small scale, this may not cause much damage. Across an entire sales team, however, it can significantly overstate how much genuine pipeline the business has. The problem becomes particularly visible when leadership starts using pipeline coverage as reassurance.</p><p>Suppose the quarterly target is $500K and the CRM contains $2M of pipeline. Four times coverage sounds comfortable. But if a meaningful portion of that $2M came from prospects that became opportunities before they were properly qualified, the ratio tells you very little about how much revenue is realistically available to close.</p><p>There is no universal definition of a qualified opportunity. A $250K enterprise software deal and a &#163;10K advisory project should not necessarily follow identical qualification criteria. What matters is that your business has a clear definition and that two salespeople faced with the same situation would reach roughly the same conclusion.</p><p>The question to answer is simple: <strong>what needs to be true before we are willing to call this a real opportunity?</strong></p><p>If that definition is loose, forecast error enters the system from the moment those opportunities start contributing to the pipeline.</p><h3>2. Your stages are based on seller actions</h3><p>The next problem usually appears in the way opportunities progress.</p><p>Many CRM pipelines are built around sales activities: Discovery Completed, Demo Delivered, Proposal Sent, Negotiation, Contract Sent. These stages are convenient because they are easy for the seller to identify. The rep knows whether they sent a proposal or completed a demo.</p><p>The weakness is that seller activity often tells you very little about whether the buyer has genuinely progressed.</p><p>Consider two opportunities sitting in &#8220;Proposal Sent.&#8221; In the first, the buyer has confirmed the scope and budget, involved the economic decision-maker and booked a meeting to review the proposal on Friday. In the second, the prospect finished a call by saying, &#8220;Send me something and I&#8217;ll take a look.&#8221;</p><p>The CRM can show both deals in exactly the same stage. If that stage carries a 60% probability, the forecasting model may treat them almost identically. In reality, they are at very different points in the buying process.</p><p>A stronger pipeline uses observable buyer evidence to define progression. The buyer disclosed budget. The right stakeholder joined the process. Scope was agreed. A proposal review was booked. Procurement started. A decision date was confirmed.</p><p>The goal is to make stage movement depend on evidence the team can see and verify. Complex B2B sales will always require judgement, but clear criteria give that judgement boundaries.</p><p>When stages are tied to specific buyer actions, similar deals are much more likely to be classified in the same way across the team. Leadership can then look at a stage and have a clearer idea of what has actually happened in the buying process, which makes that pipeline data far more useful for forecasting.</p><h3>3. Your probabilities are based on rep judgement</h3><p>Even with well-defined stages, the forecast can still go wrong if the probabilities attached to opportunities have no connection to what has historically happened.</p><p>A salesperson looks at a deal and says they are 80% confident. Another rep might look at a similar deal and call it 50%. Both may have perfectly reasonable arguments, but the number is still based largely on personal judgement.</p><p>This becomes especially problematic when those percentages are used to calculate weighted pipeline. A $200K opportunity at 80% contributes $160K to the forecast. Change the rep&#8217;s confidence to 50% and that contribution drops to $100K. Sixty thousand dollars has disappeared from the forecast without anything changing on the buyer&#8217;s side.</p><p>Historical conversion rates give you a much stronger starting point.</p><p>If only 35% of opportunities that reach a certain stage historically become Closed Won, that tells you something important about what reaching that stage has actually meant in your business. The same applies when you break conversion down by segment, deal size, product or sales motion where there is enough data to do so.</p><p>That does not mean every deal in the same stage has exactly the same chance of closing. Individual opportunities will always have different circumstances. Historical conversion gives you a baseline grounded in what has actually happened, while deal-specific evidence helps you understand where an opportunity may sit relative to that baseline.</p><p>The key is that probability should have a clear basis. When the number comes mainly from a rep&#8217;s confidence, the forecast starts measuring optimism alongside commercial reality.</p><h3>4. Your close dates are often based on assumptions</h3><p>The expected close date has enormous influence over a forecast, yet it is often one of the least defensible fields in the CRM.</p><p>Take the largest deals expected to close this quarter and ask why each one carries that specific date. Sometimes there is a clear answer. The customer&#8217;s existing contract expires at the end of October. Their investment committee meets on the 18th. Procurement needs the agreement completed before the new financial year. The project needs to launch in January and implementation takes six weeks.</p><p>Those dates are tied to the buyer&#8217;s process. They have commercial meaning.</p><p>In other cases, the answer is much weaker. The rep expects the deal to close this month. They want it in the quarter. Or they selected 30 September when the opportunity was created because the CRM required a date.</p><p>Then September arrives and the deal does not close, so the date moves to October. If October passes, it moves again to November. Nothing meaningful may have changed in the buying process, yet the same opportunity continues to appear in successive forecasts as revenue that is expected to arrive soon.</p><p>Over time, this creates a misleading picture of timing. Leadership keeps seeing the same revenue one month ahead, while the evidence behind the close date gets weaker with every move.</p><p>Repeated close-date movement is a useful revenue signal. It tells you either that the organisation does not understand the buyer&#8217;s decision process or that something in that process is not progressing as expected.</p><p>A date entered in a CRM only becomes useful when there is a commercial reason behind it.</p><h3>5. Dead opportunities remain alive for too long</h3><p>Another common problem is stale pipeline: opportunities that remain open in the CRM even though there is little evidence that the buyer is still actively moving towards a purchase.</p><p>Imagine a business showing 40 open opportunities worth $1.2M against a $400K target. At first glance, that looks like plenty of pipeline.</p><p>Then you review the deals properly. Fifteen have recent buyer activity and clear next steps. Eight have received no response for three weeks. Six were supposed to make a decision last month, but nobody knows what happened. Four have no future meeting scheduled. Several others remain open because the salesperson hopes the account will eventually re-engage.</p><p>Once you separate the active buying processes from the stale opportunities, the picture changes completely. The CRM may show $1.2M of pipeline, while only $450K is attached to buyers who are currently engaged and moving forward.</p><p>That gap changes how you should read your pipeline coverage. Against a $400K target, $1.2M looks comfortable. But if only $450K is genuinely active, the business is much closer to the target than the headline number suggests, with very little room for deals to slip or be lost.</p><p>The danger is that stale opportunities can hide that gap for weeks or even months. As long as those deals remain open, leadership may believe there is enough pipeline and hold off on taking action. When it finally becomes clear that those opportunities are unlikely to close, there may be much less time left in the quarter to generate new pipeline or recover the gap.</p><p>This is why every sales process needs clear criteria for keeping an opportunity open. A deal might remain active because the buyer has engaged recently, there is an agreed next step, a future meeting is booked, or there is a clear reason why the process has temporarily paused. If none of those conditions is true for a period that makes sense for your sales cycle, the deal should be reviewed and either taken out of the active pipeline or marked as lost.</p><h2>Your forecast review should challenge the evidence behind each deal</h2><p>Even with better pipeline data, the forecast still needs to be reviewed regularly. Deals change. Timelines move, stakeholders disappear, budgets get delayed and buying processes lose momentum. The purpose of the forecast review is to catch those changes early and make sure the number still reflects what is happening in the deals today.</p><p>That requires more than asking the rep whether they still feel confident. A salesperson can genuinely believe a deal will close because the conversations have been positive, the solution fits and the customer has shown interest. But confidence alone does not tell you whether the buying process has actually moved forward since the last review.</p><p>A useful forecast review should test the assumptions behind the deal. If it is expected to close this month, what has the buyer done that supports that timing? If it remains in a late stage, has the buyer completed the actions required to be there? If the deal is still considered likely to close, what has happened since the last review that supports that view?</p><p>For example, imagine a $150K opportunity that has been in the forecast for three weeks. The rep remains confident, but the procurement process that was supposed to start on Monday has not started, the next meeting has not been booked, and the buyer has not replied to the last two emails.</p><p>At that point, the forecast should change. Depending on the evidence, the deal may need to move out of the current forecast category, have its expected close date pushed back, or be removed from the forecast altogether until the buying process starts moving again. The rep may still believe the deal will eventually close, but the forecast should reflect what the buyer is doing now.</p><p>This is where a good forecast review adds value. It forces the team to compare what the CRM currently says with the latest evidence from the buyer. Deals with stronger evidence can stay where they are. Deals where the evidence has weakened should be challenged, moved or removed from the forecast before the gap appears at the end of the month.</p><p>Over time, this also creates a more consistent standard across the sales team. Reps know what evidence they are expected to bring when they call a deal likely to close, and managers have something concrete to challenge when that evidence is missing.</p><p>The result is a forecast that changes when the buying process changes, rather than weeks later when the expected revenue fails to arrive.</p><h2>How to make your sales forecast more reliable</h2><p>When forecasts miss repeatedly, companies often respond by tightening the forecasting process: more review meetings, more categories, more manager overrides and more scrutiny on individual deals. That can make the process feel more controlled without changing the quality of the pipeline behind it.</p><p>The more useful question is what would have needed to be different earlier in the sales process for the forecast to have been more accurate in the first place. That is where the biggest improvements usually begin.</p><p>Start with the definition of an opportunity. If prospects are entering the pipeline before there is a genuine buying process, every number built on top of that pipeline will already be overstated.</p><p>Then look at stage progression. The business needs clear criteria for what has to happen before an opportunity moves forward, ideally based on observable buyer actions. Without that consistency, two similar deals can sit in different stages depending on who owns them.</p><p>Once those foundations are clear, probability becomes much more useful. Historical conversion rates can tell you how often opportunities at each stage actually become customers, giving the forecast a baseline grounded in your own performance rather than rep confidence alone.</p><p>Close dates need the same discipline. Later-stage opportunities should have a clear reason for why they are expected to close when they are, based on the buyer&#8217;s process rather than the seller&#8217;s target or an arbitrary CRM date.</p><p>The pipeline also needs to stay current. Opportunities that no longer have buyer engagement, a credible next step or a clear reason to remain active should be reviewed so they do not continue inflating pipeline coverage.</p><p>Finally, the forecast review should keep testing whether those assumptions are still true. Deals change, so the stage, probability, close date and forecast category should change when the buyer evidence changes.</p><p>The point is to avoid spending time refining the forecast while the information feeding it is still unreliable. Once the pipeline gives you a more accurate picture of the opportunities in play, the forecast has a much stronger foundation to work from.</p><h2>Some forecast misses are unavoidable</h2><p>No forecast will be perfectly accurate. Buyers change their minds, budgets get frozen and internal decisions get delayed. Some uncertainty will always remain.</p><p>The important question is whether the miss came from something genuinely unexpected or from information that was already visible. A sudden budget freeze is difficult to anticipate. A deal that has already slipped twice, has no next meeting and has gone quiet should not surprise anyone when it misses again.</p><p>A more reliable forecast will not eliminate misses. It will reduce the ones the business should have seen coming.</p><h2>How Revenue House looks at forecasting</h2><p>At <a href="http://revenue.house">Revenue House</a>, we treat forecast accuracy as an output of the wider revenue system rather than an isolated sales-management problem.</p><p>During a Revenue Engine Audit, we look upstream at how opportunities are qualified, what pipeline stages actually mean, how probabilities are set, what evidence moves a buyer forward, how close dates are established, when stale opportunities are removed, and whether leadership can trace the forecast back to something observable in the buying process.</p><p>Sometimes that work reveals a forecasting problem. More often, it reveals something earlier in the revenue system that was making an accurate forecast almost impossible in the first place.</p><p>The objective is to make sure that when the future does surprise you, it happens because something genuinely unpredictable changed &#8212; rather than because the pipeline was carrying assumptions that should have been challenged much earlier.</p><p></p><div><hr></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.revenue.house/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Revenue House! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item></channel></rss>