How do I configure HubSpot to report against UK financial year dates (April to March)?
HubSpot does not have a native financial year setting that automatically applies April-to-March across all reports. The correct approach is to use custom date range filters with saved date properties, configure your fiscal year start in HubSpot's account settings (available in Sales Hub Professional and above), and apply consistent date filters across every report in your dashboards. For reports that need to compare current financial year against prior financial year, you need to build those comparisons manually using calculated date ranges rather than HubSpot's built-in "this year versus last year" toggle, which will always use January-December unless the fiscal year setting is configured. We configure this across your full reporting environment so new reports inherit the correct boundary.
How do I build a Looker Studio dashboard combining HubSpot pipeline data with Google Ads and Meta spend for a UK business?
Looker Studio connects to HubSpot via the official HubSpot connector, which exposes deal, contact, and company data. Google Ads connects natively. Meta Ads requires either a third-party connector (Supermetrics, Windsor.ai, or similar) or a manual data export into Google Sheets used as a Looker Studio data source. The build involves configuring the connections, creating calculated fields for cost-per-acquisition (total ad spend divided by closed-won deal count, filtered by lead source), and building a blended data view that aligns the date dimensions across all three sources. The main technical challenge is matching HubSpot lead source attribution to the correct ad platform campaign, which requires consistent UTM parameter setup on your UK ad campaigns before the dashboard build begins.
How do I reconcile HubSpot CRM deal revenue with Xero or Sage invoiced revenue in a UK reporting dashboard?
The reconciliation requires a common identifier between HubSpot deals and Xero or Sage invoices. The most reliable approach is to write a unique deal reference from HubSpot into the invoice reference field in Xero or Sage at the point of invoicing, either manually or via a Zapier or Make automation. Once the common identifier exists, you can export both datasets into a Google Sheet or a Looker Studio blended data source, match on the identifier, and calculate the difference. The timing gap between deal close date in HubSpot and invoice date in Xero is the most common source of discrepancy and should be displayed as a separate column rather than treated as an error.
How do I add territory segmentation to HubSpot pipeline reports for a UK sales team?
Territory segmentation in HubSpot pipeline reports requires a deal or contact property that captures territory (for example, London, North West, Scotland, or a postcode region). If this property does not exist, you need to create it, define the territory values, and either back-fill existing records via a CSV import or set up a workflow that assigns territory based on company postcode or owner. Once the property is populated, you can add it as a filter and group-by dimension in HubSpot's deal pipeline reports and in any Looker Studio dashboard connected to HubSpot. The back-fill is the most time-consuming part; ongoing assignment via workflow is straightforward once the property is configured.
What sales dashboard KPIs matter most for a UK B2B professional services or SaaS business?
For UK B2B professional services, the most important pipeline KPIs are pipeline coverage ratio (pipeline value as a multiple of quota), weighted pipeline by stage, average deal size by service line, win rate by lead source, and days-to-close by deal size band. For SaaS, the additional KPIs are monthly recurring revenue by cohort, pipeline velocity (deals times win rate times average deal value divided by average sales cycle length), lead-to-opportunity conversion rate by channel, and churn rate alongside new business pipeline. The financial year alignment matters for both: YTD quota attainment and pipeline coverage are meaningless if the year boundary is wrong.