Engine Diagnostic

B2B SaaS Marketing Audit & Engine Diagnostic

The Engine Diagnostic is a SaaS marketing audit that ends in a build plan, and it is the first step of Build in the Surge GTM Engine. We measure your baseline across channels, attribution, pricing, the stack and the team, sharpen your ICP and positioning, and turn the findings into the build plan for the engine. Then we build it, run it with your team and measure it against that baseline. It takes 2–3 weeks. A focused version (attribution-only or pricing-only) takes 1–2 weeks.

A team planning strategy with sticky notes on a whiteboardEngine Diagnostic
The challenge

The gaps quietly costing you pipeline.

01Unclear which channels and campaigns are actually generating pipeline
What it costs
Budget keeps flowing to whatever is loudest rather than what produces pipeline.
What we build
A baseline that shows what is working and what is wasting budget, measured against one pipeline number.
02Pricing feels like a guess: tiers and packaging not optimised for NRR
What it costs
Every deal and renewal leaves expansion revenue on the table.
What we build
We review your value metric, tiers and packaging as part of the baseline before any build.
03Martech stack bloated with tools that duplicate each other or aren't used
What it costs
Licence costs climb while data splits across tools nobody fully trusts.
What we build
A stack and data audit, so the build plan uses what you already own and runs on clean data.
04Attribution is broken: you can't connect marketing spend to revenue
What it costs
Spend decisions rest on opinion, and marketing cannot defend its budget.
What we build
An attribution assessment in every diagnostic, so the engine is measured against one pipeline number from day one.
05New hire or CEO asking for an honest marketing assessment before investing more
What it costs
Investing before you know what works risks scaling the parts that waste money.
What we build
A SaaS audit that gives an honest baseline of what is working and what is not, not what you want to hear.
06ICP and positioning too loose for outbound, ABM or content to target properly
What it costs
Every channel aims at a slightly different buyer, so none of them lands.
What we build
ICP and positioning set in the diagnostic, so signals, outbound, ABM and content all target from it.
07Unsure whether to build in-house, outsource, or change agency
What it costs
A wrong call costs a year of budget and momentum before anyone can tell.
What we build
A baseline and build plan that shows what to build, who should run it and in what order.
08Board asking hard questions about marketing ROI you cannot yet answer
What it costs
Without a defensible number, marketing budget becomes the first thing cut.
What we build
A baseline every later number is measured against, so you can answer the board with evidence.
Recognise these?A 30-minute call maps where pipeline is leaking to the part of the engine that fixes it.
Book a Discovery Call
A B2B SaaS leader thinking through where pipeline is leaking
Our approach

How we build, run and measure it.

A team working through their GTM engine together
01Approach

We tell you what is working and what is wasting budget, not what you want to hear. Every number afterwards is measured against this baseline.

02Approach

Pricing and packaging decide what every other stage of the engine can earn. We review your value metric, tiers and packaging as part of the baseline.

03Approach

We audit your stack and data, so the build plan uses what you already own and the engine runs on clean data.

04Approach

Every diagnostic includes an attribution assessment, so the engine is measured against one pipeline number from the first day of the build.

What we cover

What the Engine Diagnostic Covers

Marketing Audit

Comprehensive audit of channels, attribution, tech stack, and team capabilities with a prioritised improvement roadmap.

Pricing Strategy

Value-based pricing analysis, tier and packaging design, and expansion revenue strategy.

Martech Stack Optimisation

HubSpot, Salesforce, analytics, and automation review. Eliminate waste and configure what you have for scale.

Attribution Audit

Multi-touch attribution assessment: identify where your tracking is broken and reconnect spend to pipeline.

ICP, Positioning & Team

Your ideal customer profile and positioning made specific enough to target outbound, ABM, paid and content, plus a review of team structure, skills and capacity against your goals.

Competitive Benchmarking

Channel mix, pricing, and positioning benchmarked against relevant competitors and stage-matched B2B SaaS peers.

How it works

How the Diagnostic Runs, Then Leads Into the Build

01

Scoping and Access

Week 1: agree scope and the decisions you need to make, and get read-only access to your CRM, GA4, Search Console, ad accounts, martech and attribution tools.

02

Data Collection & Interviews

Access your analytics, CRM, ad accounts, attribution tools and martech stack to pull the real numbers, and interview marketing, sales and leadership on what they see.

03

Analysis

Deep analysis of performance data, attribution integrity, pricing benchmarks, and stack efficiency.

04

Findings Draft

Draft findings with your team for context and validation before finalising. We check our interpretation is correct.

05

ICP, Positioning & Build Plan

ICP and positioning agreed per persona, a written definition of a qualified meeting agreed with sales, and the build plan ranked by commercial impact and effort.

06

Into Build & Run

Findings presented to leadership or board, then we start building the first stage of the engine and run it with your team.

How we deliver

What you get, what we need, how we measure it.

Built in your accounts, run with your team, reported against the numbers below.

What you get

  • An engine score out of 100 across 16 modules of Build, Run and Measure
  • Your top 3 pipeline leaks, each sized in £
  • A baseline against one pipeline number your CFO can reproduce
  • Agreed ICP and positioning per persona
  • A written definition of a qualified meeting, agreed with sales
  • Attribution assessment and pricing and packaging recommendations
  • A ranked build plan: what to build, who runs it, in what order

What we need from you

  • Read-only access to CRM, GA4, Search Console, ad accounts, martech and attribution tools in week 1
  • ARR, NRR, ACV, win rate and sales cycle
  • 6–8 people for 45-minute interviews
  • Recordings or notes for 5 won and 5 lost deals

Typical timeline

  1. 012–3 weeks end to end
  2. 02A focused version (attribution-only or pricing-only) takes 1–2 weeks
  3. 03Ends with the ranked build plan, ready for Build in weeks 2–8
Framework F01 · Build

Engine Diagnostic Scorecard

Measure the client's whole go-to-market engine against one pipeline number, score every module 0–5 with evidence, size the leaks in £ and produce the ranked build plan that the rest of the engagement follows.

B2B SaaS teams usually over-invest in the channel they understand and under-invest in the weakest link (often RevOps or attribution). A scored, evidence-based baseline stops opinion-led planning and gives the board a number to track.

When we use it
Signed Engine Diagnostic, a new Build and Run client, or the yearly re-baseline for an existing client.
Typical timeframe
2–3 weeks (focused version: 1–2 weeks)
What it needs
Read-only access to CRM, GA4, ad accounts, martech and attribution tools; 12 months of deal data; 6–8 stakeholder interviews; 5 won and 5 lost deals.
Channels
Video calls, Slack shared channel
Tools, in your accounts
HubSpot / Salesforce, GA4 + GSC, Ahrefs, Profound, Supermetrics / Windsor.ai, Gong / Fathom, Miro, Google Slides / Sheets

What we track

Baseline signed off against one pipeline number
CRM · once
Top 3 leaks sized in £ pipeline
Diagnostic workbook · once
Days from kick-off to readout
Surge Workspace · per diagnostic
Diagnostic → Build and Run conversion
CRM (Surge45) · quarterly
Engine score out of 100
Engine scorecard · monthly from run
Readout CSAT
Survey · per diagnostic

Targets are agreed from your first month of data.

The activity plan

Exactly what the team does.

Phase by phase, with the week each step lands. Week 1 is the start of Build.

01Week 1 day 1Scoping
  • Scoping call. Agree goals, ARR target, decisions the diagnostic must inform, scope (full or focused) and deadlines. Confirm stakeholders and board date if relevant. → Scope document
  • Send data and access request. Send the access checklist (CRM, GA4, GSC, ads, martech, attribution) and data request (12 months deals, spend, team list). → Access and data request
02Week 1 – Week 1–2Data
  • Pull CRM and pipeline data. Export deals, stages, sources, close dates, ACV, lifecycle history. Rebuild the pipeline number and reconcile with what leadership reports. → Pipeline baseline
  • Pull channel data. Paid spend and results, GA4 sessions and conversions, outbound volumes and reply rates, content output. → Channel dataset
  • Search and AI visibility baseline. Ahrefs crawl and rankings; run the fixed prompt set across assistants; record share of voice and citations. → Search and AI baseline
  • Martech and data audit. List every tool, cost, owner, integrations; check field fill rates, duplicates, routing and lifecycle rules. → Stack and data audit
03Week 1–2 – Week 2Interviews
  • Stakeholder interviews. 45-min interviews: CEO/founder, CMO, Head of Sales, 2 SDR/AEs, RevOps, Customer Success. Use the interview guide. → Interview notes
  • Win/loss review. Review 5 won and 5 lost deals: source, cycle, competitors, reasons, buying committee. → Win/loss summary
04Week 2Analysis
  • Score every module. Score each Build/Run/Measure module 0–5 against the rubric with evidence. Calculate engine score. → Scorecard
  • Attribution integrity. Size unattributed and 'direct' pipeline; test source capture end to end. → Attribution assessment
  • Pricing review. Value metric, tiers, discounting and win rate by price point (see F17). → Pricing notes
  • Competitive benchmark. Compare channel mix, pricing, positioning and AI visibility with 3–5 stage-matched competitors. → Benchmark
05Week 3Findings
  • Size the leaks. Quantify top 3 leaks in £ pipeline using the growth model (F12). → Leak list
  • Validate findings. Walk the client lead through draft findings; correct facts before the readout. → Validated findings
06Week 3 – Week 2Plan
  • ICP and positioning agreement. Run the ICP (F02) and positioning (F03) workshops or agree drafts. → Agreed ICP and positioning
  • Define a qualified meeting. Agree with sales what counts as a qualified meeting (ICP fit, role, problem, timing) – the unit every report counts. → Qualified meeting definition
  • Ranked build plan. Score initiatives with F16; sequence by dependency; assign co-run vs managed. → Ranked build plan
07Week 3Readout
  • Readout to leadership/board. Present baseline, scores, leaks, plan, targets approach and proposal. → Readout deck
  • Send proposal. Build and Run proposal priced from Teams & Capacity charge-out rates. → Proposal

What we send you

  • Welcome pack and timeline – sets expectations and dates. Week 1 day 1
  • Access checklist and data request – get data on time. Week 1 day 1
  • Interview schedule and guide – book the right people. Week 1
  • Weekly progress note – no surprises. Every Friday
  • Draft findings – validate before readout. Week 3
  • Readout deck + scorecard – decision document. Week 3
  • Ranked build plan – what to build, who runs it, in what order. Week 3
  • Build and Run proposal – next step. Week 3
Quality

How we know it's done.

Definition of done

  • Qualified meeting definition agreed with sales
  • Every module scored with written evidence
  • Pipeline number reconciled with leadership
  • Top 3 leaks sized in £
  • Findings validated with client before readout
  • ICP and positioning agreed
  • Ranked build plan with owners and order
  • Proposal sent within 2 days of readout
  • Passed VP of GTM QA

Risks we plan around

Late data access
Send access request on day 1; escalate at day 3; start interviews while waiting
Client disputes the pipeline number
Reconcile line by line with RevOps and finance before analysis
Too many findings
Cap at 3 leaks and one ranked plan
Opinion over evidence
Every score needs a data point or quote
Scope creep into build
Log requests; price as Engine Sprint

This service also runs on

Framework F16 · 1–2 days; reset quarterly

Prioritisation Matrix & Ranked Build Plan

Score every possible initiative on impact, confidence, time-to-revenue and effort, then sequence by dependency into the ranked engine build plan: what to build, who runs it and in what order.

Framework F17 · 1–2 weeks

Pricing & Packaging Review

Review the value metric, tiers, packaging, discounting and pricing page, and recommend changes that lift win rate, ACV and expansion.

Proof

Results from past engagements.

Pricing ARR Uplift+31%

31% ARR uplift in 6 months following pricing strategy engagement and packaging redesign.

Marketing Waste Eliminated42%

Marketing budget waste of 42% identified and reallocated to higher-ROI channels following audit.

Attribution Fixed89%

89% of pipeline previously attributed to 'direct' correctly attributed to source channel after attribution audit.

Source: engagements led by our team before Surge45. Client names withheld.

Why Surge45

Why B2B SaaS teams choose us.

B2B SaaS only

We work only with B2B SaaS, so every playbook and benchmark is relevant to your business.

Build, Run, Measure

We build the engine, run it with your team and measure what it returns. No strategy left on a slide.

You own what we build

Everything lives in your own accounts and is documented, so the engine stays with you.

A named senior GTM engineer

One senior person accountable for the work, to you and to your board, not a junior account manager.

Pipeline you can defend

We connect the work to pipeline and revenue in your CRM, with attribution your CFO can reproduce.

Proven across 30+ brands

Playbooks built and run across 30+ B2B SaaS brands.

FAQ

Questions teams ask.

Is this the same as a SaaS marketing audit?

It includes one, and it works as a growth audit rather than a channel check. The diagnostic audits your whole marketing function, not just SEO: channels, attribution, the stack, the team and competitive position. It then goes further, agreeing your ICP and positioning and turning the findings into the plan for what we build first.

How long does the diagnostic take?

2–3 weeks. A focused version (attribution-only or pricing-only) takes 1–2 weeks. It runs in weeks 1–3 of the engagement, and sending domains are bought and warm-up started in week 1 so the build is not held up.

What access do you need?

Read-only access to your CRM, GA4, Search Console, ad accounts, martech and attribution tools in week 1. Your ARR, NRR, ACV, win rate and sales cycle. 6–8 people for 45-minute interviews. Recordings or notes for 5 won and 5 lost deals. When we move into the build, we work inside your own accounts, so everything we build stays yours.

What happens after the diagnostic?

The diagnostic is the first step of Build in the Surge GTM Engine, and it leads straight into the rest of the build and then Run. We build the priority parts of the engine in your own accounts, then run them with your team, Co-run (built in your accounts) or Managed by Surge45, with a named senior GTM engineer accountable. If you would rather run the plan yourselves, it is yours to keep.

What does a SaaS marketing audit cover?

A full SaaS marketing audit covers every active channel, attribution from first touch to closed-won in your CRM, pricing and packaging, the martech stack and data quality, team capacity and competitive positioning. The diagnostic adds an engine score, your top pipeline leaks, an agreed ICP and a written definition of a qualified meeting.

How much does the diagnostic cost?

We do not publish prices. The diagnostic is the first three weeks of an engagement, which is a one-time build fee plus a monthly fee, scoped on a discovery call, with a three-month minimum and then rolling. Tools, data and ad spend are paid by you at cost.

What makes pricing strategy high leverage?

Pricing directly affects MRR, NRR and LTV without increasing acquisition cost, which is why it is reviewed in the diagnostic before anything is built. Where packaging is out of line with the value delivered, fixing it can matter more than adding pipeline.

Ready when you are

Ready to build your GTM engine?

Book a discovery call with a GTM engineer. We'll identify which tier fits your stage and which part of the engine to build first.

A smiling strategist standing in front of a whiteboard of notes