SaaS SEO Case Study: How 6.4× Organic Demo Requests Were Measured, and How to Replicate the Measurement
The question a CFO asks about SEO is not whether traffic went up but whether pipeline did, and whether anyone can prove it. This case study answers that question on purpose. A B2B SaaS platform grew monthly organic sessions from 4,200 to 17,600, page-one keywords from 18 to 210 and organic demo requests from 9 to 58 per month in eight months, and organic search became its largest single pipeline source. This page sets out how those demo requests were attributed in the CRM before the first page was changed, why first-touch attribution was chosen and how the last-touch view was reported alongside it, how the measurement kept the program funded through two quiet technical months, and how a Canadian SaaS company can replicate it, by country and consent-first. Figures come from the client’s Google Analytics 4, Search Console and CRM.
The headline results
- 9 → 58Organic demo requests per month, first touch
- +320%Monthly organic sessions
- 18 → 210Keywords on page one
- Month 1When attribution was set up
| Metric | Before | After | Change |
|---|---|---|---|
| Organic demo requests per month (first touch) | 9 | 58 | 6.4× |
| Monthly organic sessions | 4,200 | 17,600 | +320% |
| Keywords ranking on page one | 18 | 210 | 11× |
| Channel attribution on demo requests | None | First and last touch recorded on every lead | Set up in month 1 |
| Organic’s place in the pipeline | Minority channel behind paid search | Largest single first-touch source | Channel mix shifted |
Demo requests are from the client’s CRM with first-touch and last-touch source fields populated at lead creation. Sessions and keywords are from Google Analytics 4 and Google Search Console, comparing the month before kickoff with month eight. The client’s name is withheld under NDA; screenshots are available on a video call under the same terms.
Who the client is
| Client snapshot | |
|---|---|
| Business | B2B SaaS platform with long, multi-stakeholder buying cycles |
| Primary conversion | Demo requests, attributed in the CRM by first and last touch |
| Starting position | Core commercial terms on page two; paid search the main channel with rising cost per lead; no channel attribution on demo requests |
| Engagement | Managed SEO: technical, content and authority, eight months at the time of these figures |
| How decisions were made | Monthly from a CRM attribution report reconciled with GA4 and Search Console; each phase funded on the previous month’s pipeline numbers |
| Outcome | Organic search the largest single first-touch pipeline source |
The company sells a B2B SaaS product to operations and finance teams in mid-sized businesses, through a sales-led motion with a long, multi-stakeholder cycle. Its finance lead approved marketing spend quarterly against pipeline, which meant that an SEO program with a two-month technical phase had to prove itself in the CRM before it had produced a ranking.
The challenge
The commercial problem was ordinary: paid search was the main source of demo requests and its cost per lead had risen for three consecutive quarters, while the commercial pages that should have carried organic demand sat on page two. The harder problem was institutional. The company had never attributed demo requests to a channel, so there was no baseline, and the finance lead would not fund a program on rankings. Without measurement in place first, the technical phase, which produces no visible traffic gain, would have been cancelled at the first quarterly review.
The plan therefore started with the CRM rather than the site: attribution fields, a reconstructed baseline and a monthly report that finance would accept, before any page was changed.
Why this was difficult
Three things made the measurement hard. First, the CRM had no source fields on leads, so a baseline had to be reconstructed from referrer data in form submissions and reconciled against analytics, with known gaps. Second, the buying cycle meant that the effect of page changes on demo requests appeared weeks later, so the monthly report had to carry leading indicators (rankings and sessions on commercial pages) alongside the lagging one (demo requests) without letting the leading ones become the measure. Third, the attribution rule had to be chosen before the results existed, so that nobody could be accused of picking the rule that flattered the program afterwards; first touch was agreed in month one and the last-touch view was reported alongside it throughout.
What we did, month by month
- Month 1Attribution before anything elseFirst- and last-touch source fields added to the CRM, UTM and referrer capture on every form, a baseline reconstructed, the monthly report format agreed with finance. Technical audit run in parallel; engineering tickets written.
- Months 1–2Technical fixes; nothing visibleRendering, duplicate URLs and hosting fixed. Sessions barely moved. The month-two report showed organic demo requests unchanged at 9 and commercial-page rankings beginning to improve; finance approved month three on that evidence.
- Months 2–3Commercial pages rewrittenThe commercial pages on page two were rebuilt around buyer questions and the unfocused legacy pages consolidated. The first commercial pages reached page one and demo requests attributed to organic rose for the first time.
- Months 3–5Content and conversionDecision-stage content on the themes closest to a demo request, briefed from sales conversations; demo paths on the commercial pages tightened. Organic first-touch demo requests continued to rise; the last-touch view lagged, as expected in a long cycle, and was shown alongside.
- Months 4–8Authority and compoundingEarned placements aimed at commercial pages; internal links restructured. Sessions passed 13,000 in month six; organic became the largest first-touch source of demo requests.
- Month 8Figures on this page58 first-touch organic demo requests; 17,600 sessions; 210 page-one keywords; attribution report reviewed with the client’s finance lead.
Monthly organic sessions, the leading indicator finance watched
Monthly organic sessions from Google Analytics 4 at the points reported to the client. Sessions led demo requests by several weeks because of the buying cycle; the monthly report showed both so that the lag was expected rather than alarming.
What made the difference
- ✓Measurement before changeAttribution fields, baseline and report format were in place before the first page was touched, which is why the program survived its quiet technical phase.
- ✓Attribution rule chosen in advanceFirst touch was agreed in month one and the last-touch view reported alongside it throughout, so the result could not be accused of a flattering choice made afterwards.
- ✓Leading and lagging indicators togetherCommercial-page rankings and sessions were reported as leading indicators, demo requests as the measure; the lag was explained before it happened.
- ✓A report finance would readOne page a month: organic’s share of demo requests under first and last touch, sessions on commercial pages, and the next month’s plan.
- ✓The work itselfTechnical, then commercial pages, then authority, in that order; the measurement made the order fundable.
How the result was verified
Demo requests were taken from the client’s CRM, where first-touch and last-touch source fields were populated at lead creation from month one and reconstructed for the months before. First-touch figures credit organic where organic search was the first or sole touch; last-touch figures credit the channel of the final visit before the request and were reported to the client alongside. Sessions and page-one keywords are from Google Analytics 4 and Google Search Console, branded queries excluded, comparing the calendar month before kickoff with month eight. The client’s finance lead reviewed the attribution report and this page before publication.
Who this applies to
This case applies to B2B SaaS companies with a sales-led or hybrid motion and a finance function that funds marketing against pipeline, which is most of them past seed stage. It applies especially to companies whose SEO has been cut before because nobody could show what it produced. For Canadian SaaS companies the same measurement should be split by country, because pipeline from Canada and the United States behaves differently, and configured consent-first to PIPEDA and Law 25. It applies less well to product-led tools where the measure is sign-ups and activation rather than demos, though the principle of measuring before changing is the same.
What to expect if you start now
Starting today, expect the first two weeks to go on the CRM rather than the site: attribution fields, baseline reconstruction and a report format your finance lead accepts. Expect the technical phase to show in rankings and sessions before it shows in demo requests, and expect the report to say so in advance. Expect the first change in attributed demo requests a few months in depending on your cycle, and compounding in the second half of the program. For scoping and current pricing, see managed SEO in Canada.
“Ren Hao SEO turned organic search into our biggest pipeline source. We finally have a channel that compounds.”
“The transparency is unlike any agency we’ve worked with. We always know what’s happening and why.”
Frequently asked questions
Why does this case study spend so much time on measurement?
Why first-touch attribution rather than last-touch?
Did the result hold under the last-touch view?
How was demo attribution set up before any page changed?
How can a Canadian SaaS company replicate this measurement?
How was cost per demo compared between organic and paid?
Can you share the client’s name or screenshots?
More case studies
About this page
Written by the Ren Hao SEO team and reviewed by Ren Hao, Founder & Lead SEO Strategist (LinkedIn), who led the engagement. Ren Hao SEO is a data-driven international SEO agency headquartered in Johor Bahru, Malaysia, serving eight country markets (company LinkedIn). Figures come from the client’s Google Analytics, Search Console and CRM and were reviewed with the client before publication; the client’s name is withheld under NDA and screenshots are available on request under the same terms. Last substantive update: October 2026. Drafting is assisted by AI tools and every page is edited and fact-checked by our team before publication; see how we create our content. Nothing on this page is a forecast for any other business.