How to Capture a Baseline Before Value Disappears.
Onboarding, when the customer is setting up the product and the 'before' picture still exists
You cannot prove value without a before picture. If you skip the baseline, you are left arguing from anecdote at renewal. The customer remembers the pain vaguely; you have no number to point to. A documented baseline turns 'we think it helped' into 'tickets dropped from 1,200 to 860 - here is the data.' That is the difference between a renewal that feels risky and one that feels obvious.
Where it goes wrong
Without a baseline, you reach the QBR and realise you have usage data but nothing to compare it to. The customer says 'it feels better' but cannot quantify it. Procurement asks for ROI evidence and you cannot provide it. The renewal stalls or discounts.
What you'll be able to do
The CSM can document a clean, customer-confirmed baseline during onboarding and keep it linked to the success plan so every future review has a 'before' to measure against.
How to do it
During kickoff, ask
During kickoff, ask: 'Where does this KPI live today - which system, which report?' Get the source, not just the number.
Pull or request a snapshot of 2-4 metrics that
Pull or request a snapshot of 2-4 metrics that map to the outcome they bought for. Record the value, the source, and the date.
Send a short email confirming the baseline back to
Send a short email confirming the baseline back to the customer contact: 'Just to confirm our starting point - average monthly tickets = 1,200 as of March, from Zendesk. Does that look right?' Get a reply so it is customer-confirmed, not just your note.
Store the baseline in your CRM or CS platform
Store the baseline in your CRM or CS platform against the account, linked to the success plan. Flag it so it survives handoffs.
If the customer cannot provide a number yet, agree
If the customer cannot provide a number yet, agree a proxy and a date by which you will revisit with real data. Do not leave onboarding without something written down.
See the difference
CSM completes onboarding and notes in the account: 'Customer wants to reduce support load.' Six months later, at the QBR, the CSM pulls usage stats showing strong adoption but has no ticket volume figure to compare against. The customer says things feel better. The renewal conversation has no hard evidence.
During kickoff, the CSM asks: 'You mentioned reducing ticket volume - where do you track that today?' The customer says Zendesk. The CSM asks for the last 90-day average: 1,200 tickets per month. The CSM emails: 'Confirming our baseline: avg monthly tickets = 1,200, from Zendesk, as of March 10. We are aiming for 900 by end of Q3. Does that look right?' The customer replies yes. At the QBR, the CSM opens with: 'We started at 1,200. You are now at 870. Here is what changed in the product.'
The CSM can document a clean, customer-confirmed baseline during onboarding and keep it linked to the success plan so every future review has a 'before' to meas
How you'll know it's working
You have got it when every new account in your book has a documented baseline - metric, number, source, date, customer confirmation - before the first 30 days are up.
Questions people ask
How do you capture a baseline before value disappears?
You cannot prove value without a before picture. If you skip the baseline, you are left arguing from anecdote at renewal. The CSM can document a clean, customer-confirmed baseline during onboarding and keep it linked to the success plan so every future review has a 'before' to measure against.
What is the most common mistake to avoid?
Without a baseline, you reach the QBR and realise you have usage data but nothing to compare it to. The customer says 'it feels better' but cannot quantify it.
Hire with Assessment.
£7-10k flat fee. The methodology, delivered.
See Hire with Assessment