The CRM Fixes to Make Before You Lock In an FY27 Revenue Number

Every year, somewhere around late May, businesses do roughly the same thing. Leadership sits down, looks at last year's numbers, picks a new target, usually a good deal above where they finished, and hands it to the sales and marketing team to figure out.

The problem isn't the ambition. Ambitious targets are good. The problem is that the revenue plan almost always gets built before anyone has looked at the CRM data that should be informing it, meaning the target is set against a pipeline that may be inflated with zombie deals, a win rate calculated on incomplete data, and a lead volume forecast based on attribution that was never set up properly.

A revenue plan built on bad CRM data isn't a plan you can stand behind in front of a board. It's expensive optimism with a spreadsheet attached.

The Australian income year runs 1 July to 30 June, which means whatever CRM data exists on 30 June is what FY27 planning gets built on, whether or not anyone has checked it. Here's how to sort the CRM side before that plan gets locked in, and why doing it before 30 June matters more than doing it in August.

Start with what you are holding. APP 11 of the OAIC’s Australian Privacy Principles asks for reasonable steps to protect personal information from misuse and unauthorised access, and a CRM half the company can export is not that.

The CRM Data Your Revenue Plan Actually Depends On

An FY27 revenue plan typically needs to answer four commercial questions: what does the current pipeline tell us about where revenue is coming from, what's the actual win rate and average deal size, which marketing channels are producing the best customers, and how much new pipeline is needed to hit target, at what cost.

Every one of these depends on CRM data. If that data is unreliable, the answers are guesses dressed up as analysis, leadership makes decisions on those guesses, and the year unfolds against targets that were never grounded in reality.

Question 1: What Does the Pipeline Tell Us?

A pipeline that reflects reality shows total deal value at each stage, weighted by actual probability, with close dates updated in the last 30 days. What most pipelines actually show at EOFY is deal value weighted by default probabilities set at implementation and never revised, with close dates last touched in March.

The difference is significant. A weighted pipeline of $2 million built on accurate probabilities and current close dates is a useful planning input. The same number built on outdated data is a number that produces a conversation in October about why the forecast was so wrong.

Before the FY27 plan is set: review your pipeline stage probabilities against your actual FY26 close rate from each stage. Pull a Closed Won report grouped by the last stage before close, your actual win rate at each stage is in that data. If "Proposal Sent" has a configured probability of 60 per cent but the actual close rate from that stage is 38 per cent, the weighted pipeline is overstating revenue by a meaningful margin. Update the probabilities and set the FY27 plan against what's actually likely.

Question 2: What's the Actual Win Rate and Average Deal Size?

These two numbers most directly inform FY27 sales planning, quota design, team size, activity volume targets. If they're wrong, everything downstream is wrong.

Win rate. In HubSpot's custom report builder (Professional and Enterprise), build a Deals report filtered for FY26 close dates, grouped by deal stage at close. Total Closed Won divided by total Closed Won plus Closed Lost is your win rate, but only if your Closed Lost deals have actually been closed out. Deals that should have been closed lost in March but are still technically open inflate the denominator and understate the win rate. Clean the pipeline first, then calculate.

Average deal size. Filter the Closed Won report for FY26 and check the average Deal Amount, and whether amounts were consistently populated. A meaningful percentage of Closed Won deals with no amount logged produces an average that isn't representative of your actual deal economics.

Question 3: Which Channels Are Producing the Best Customers?

This determines where FY27 marketing budget should go, and it's the question most businesses can't answer from HubSpot because attribution was never properly configured.

Reliable channel attribution needs three things confirmed. The tracking code installed and active on the website, without it organic and direct traffic that converts on your site isn't creating a tracked contact record. Ad accounts connected with auto-tracking enabled for Google Ads, Meta and LinkedIn, adding UTM parameters automatically. And campaigns with their emails, landing pages, forms and ads properly associated to the campaign record, since attribution flows through those associations.

With those three in place, a Deals report grouped by the Original Source of the associated contact shows which channels produced the revenue. Without them, the FY27 marketing budget gets set on what feels like it worked rather than what the data shows worked, and businesses that can't attribute FY26 revenue tend to either over-invest in channels that feel visible but underperform, or under-invest in channels genuinely driving revenue that get no credit for it.

Question 4: How Much New Pipeline Do We Need, and at What Cost?

The final planning question is a maths problem, but only if the inputs are right. New pipeline required equals the FY27 revenue target divided by win rate divided by average deal size. Lead volume required equals new pipeline required divided by lead-to-deal conversion rate. Marketing budget required equals lead volume required multiplied by cost per lead by channel.

If the win rate is wrong because the pipeline wasn't clean when it was calculated, the pipeline required number is wrong. If the lead-to-deal conversion rate is wrong because lifecycle stage automation was never built, the lead volume number is wrong. If cost per lead is wrong because attribution was never configured, the budget number is wrong. Getting these right before the plan is set is the difference between a plan that tracks and one that needs constant revision from August onwards.

Why This Needs to Happen Before 30 June, Not After

Two practical reasons to sort this before EOFY rather than at some point in FY27. Data decay, every week between now and a clean pipeline, more deals age without being updated and more attribution data is missed because the tracking code isn't in place. And the planning timeline, most businesses set FY27 plans and budgets in the first four to six weeks of the new financial year, so if the CRM data isn't reliable before that conversation starts, the plan gets built on whatever the CRM currently shows.

What to Actually Do Before 30 June

In order of commercial priority: close out every FY26 deal that isn't actively progressing as Closed Won or Closed Lost, giving a clean starting pipeline and an accurate win rate. Update close dates on every deal being actively worked, so the weighted pipeline means something. Check attribution setup, tracking code, ad auto-tracking, campaign asset association, before FY27 spend starts, since revenue you can't attribute in FY27 can't inform FY28 decisions. And pull the FY26 performance reports, win rate by stage, average deal size, marketing-sourced pipeline by channel, lead-to-deal conversion rate, so any gaps in them are the conversation to have before the plan is set, not after.

The Retention Problem Hiding in the Same Pipeline

Those zombie deals aren't only a forecasting problem. Under Australian Privacy Principle 11.2, personal information that's no longer needed for the purpose it was collected for has to be destroyed or de-identified. A pipeline full of stale deal records tied to contacts you're no longer actively pursuing is exactly the kind of information APP 11.2 expects a business to have dealt with, not left sitting there indefinitely because closing it out never made it onto anyone's list. Cleaning the pipeline before FY27 is a genuine compliance step under the Privacy Act, not only a forecasting one.

Conclusion

The best FY27 revenue plan is the one built on FY26 data you can actually trust in front of a board. The CRM doesn't produce that data automatically, it requires a pipeline that was maintained, attribution that was configured, and reporting set up to answer commercial questions.

None of this is complicated. All of it is the kind of thing that gets deprioritised when June is busy and July feels far enough away to deal with later.

For the automations worth setting up alongside this, see what to build before the new financial year starts, and for the pipeline visibility problem underneath a lot of this, fixing what you can actually see in the pipeline. Our EOFY HubSpot ROI audit checklist covers the same ground in more detail.

Neighbourhood helps businesses get their HubSpot data right before the new financial year starts. Let's make sure your FY27 plan is built on something solid, message us, or see our RevOps and HubSpot work.