TG3 47 SaaS brands scaled and $84M+ in client pipeline generated. See the proof → Free: 14 SaaS calculators, no signup. CAC, LTV, churn, Rule of 40. Open the tools → We rebuild attribution at the warehouse so every channel gets honest credit. See how →
TG3 SaaS/Services/Conversion optimisation

The SaaS CRO agency for the cheapest lever in your stack.

Service · 06 of 07
Conversion lift · avg
+24%
Win rate
34%
Tests per quarter
12 to 18
Time to first test
2 weeks
What this is

A SaaS CRO agency for B2B SaaS where the marketing is working but conversion is leaking. A 0. 4% lift on the trial flow or pricing page funds the rest of the marketing program. Most SaaS treats CRO as a quarterly clean-up. We treat it as continuous experimentation across trial signup, demo request, pricing page, comparison content and onboarding flow.

01 · Conversion lift
+24%

Average composite conversion lift across CRO engagements past month four. End-to-end funnel.

02 · Test win rate
34%

Win rate on shipped tests. Industry benchmark sits at 17 to 22%. Hypothesis discipline carries the gap.

03 · Tests · per quarter
12 to 18

Volume by quarter. Below 12 we lose statistical floor. Above 18 we lose hypothesis depth.

What's inside the engagement

Six SaaS CRO programs. Picked by where conversion leaks.

The retainer isn't one thing. It's six programs under one team, sequenced by what your stage needs. The audit picks the sequence. Most engagements use four of the six in the first 90 days.

SaaS CRO agency programs · time to impact · suits TG3 SaaS internal · 47 engagements
Program Time to impact What it ships Suits SaaS that
Trial flow optimisation Weeks 2 to 6 Signup form, social proof, friction removal, post-signup confirmation flow. Any SaaS with self-serve trials. The first lever to test on every engagement.
Demo request CRO Weeks 2 to 6 Demo request form, qualifying questions, calendar integration, post-submit experience. Sales-led SaaS where demo is the primary conversion event. 30%+ lifts common.
Pricing page CRO Weeks 4 to 8 Tier structure, anchor pricing, FAQ placement, social proof, sticky CTAs. Every SaaS. The most-trafficked commercial page on the site after the home.
Landing page CRO Weeks 4 to 10 Paid acquisition landing pages, campaign-specific lander tests, multivariate copy. Any SaaS running paid above $20K/month. Direct return on paid spend.
Onboarding flow Weeks 6 to 10 First-run experience, empty state, activation prompts, time-to-value reduction. Self-serve SaaS where activation drives retention. Lifts day-30 retention 10 to 30%.
Pricing comparison plays Weeks 4 to 8 X vs Y pages, alternative pages, feature-matrix comparisons. SaaS in competitive markets. Bottom-funnel intent at the comparison stage.
Most engagements start with 3 of these 6. The audit picks which three →
Fit

When SaaS CRO fits. Two honest columns.

CRO is a multiplier. If the inputs are weak the output is too. We say so.

Right fit

You should run SaaS CRO with us if

  • You have 8,000+ unique monthly visitors on key conversion pages. Below that, statistical power is too weak.
  • Your funnel converts. The leak is identifiable. CRO multiplies what works.
  • Your engineering team will ship CRO experiments within two weeks of design.
  • You can run tests for 21 days without pulling them. Significance needs time.
  • You have analytics that can read test results without us building it from scratch.
Wrong fit

You shouldn't, if

  • Your traffic is under 5,000 monthly to pricing or signup. We'll point you at paid first.
  • You want a redesign. CRO is iterative. Redesigns are projects. Different team.
  • Your engineering won't touch the marketing site. Hire a dev shop first.
  • You'll cancel a test in week one because it doesn't look like a winner. CRO discipline can't survive that.
  • Your conversion problem is upstream (wrong traffic, wrong pricing model). Fix that. Then CRO.
Methodology

Six named steps. Hypothesis first.

Every test traces back to a documented funnel gap and a written hypothesis.

01

Funnel audit

Weeks 1 to 2

End-to-end funnel mapped. Drop-off points named. Session replays watched. Heatmaps run. We find the leaks before we test anything.

02

Hypothesis library

Weeks 2 to 3

Twenty to thirty hypotheses ranked by lift potential and effort. Each one has a written rationale. Half of them get killed at this stage. Only the strongest ship.

03

Test design + spec

Weeks 3 to 4 · then ongoing

Treatment specs, sample size math, success metric, kill criteria. Spec hands cleanly to your engineering team. No "we'll figure it out" tests.

04

Ship and measure

Week 4 onward

Four to six tests live each month. Each test runs 14 to 21 days. Tests killed early if they hit a clear loss. Tests held to significance if they hit promising signal.

05

Win bank + roll-out

Week 6 onward

Winners get promoted to permanent treatment. Win bank logs every lift with the underlying mechanic. Losers stay in the library with a "don't repeat" note.

06

Decision rule cadence

Month 3 onward

Quarterly review with product. Which mechanics consistently win. Which segments respond differently. The hypothesis library rebuilds off this data.

Tools and stack

What we use. And what we don't.

CRO stacks bloat fast. We use what reads cleanly.

A/B platform
VWO · Optimizely
Visitor-side experimentation. We pick by stack fit. Both work. Neither is magic.
Server-side
Statsig · LaunchDarkly
For feature-flag based tests inside the product. Used on activation and pricing flow experiments.
Replay
FullStory · Hotjar
Session replay and heatmaps. Where the qualitative inputs to hypotheses come from.
Personalisation
Mutiny
Audience-segmented landing pages. Used when we have enough volume to segment without losing power.
Forms
Reform · Typeform
Conversion-tuned form layer. Multi-step flows, conditional logic, progressive disclosure.
Analytics
GA4 + warehouse
Test reads end in the warehouse. We don't trust platform attribution on conversion lift.
Design
Figma + in-house
Every test treatment designed in Figma before spec. In-house designers, not freelance.
Project
Notion + Linear
Hypothesis library in Notion. Test tickets in Linear. Win bank in both.
KPIs we report monthly

How we measure a SaaS CRO engagement. Eight numbers.

Most SaaS CRO agency dashboards report 40+ metrics and obscure the ones that matter. We report eight. The CFO can read them in two minutes.

01
Signup-to-activation rate
Percent of trial signups who hit your activation event. The compound metric.
02
Demo request rate
Percent of demo page visitors who complete the form. Below 8% means the page leaks.
03
Pricing page conversion
Percent of pricing page visitors who click pricing tier CTAs. 12%+ is healthy.
04
Form completion rate
Percent of form starts that complete. Below 60% means the form is too long.
05
Test velocity
Tests live per month. Above 4 is the discipline threshold. We aim for 6+.
06
Statistical significance threshold
95% confidence minimum. No "directional" lifts. Discipline matters.
07
Win rate
Percent of tests that beat control. 30% to 40% is healthy. Below that, hypotheses are weak.
08
Pipeline impact
Warehouse-stitched. Which test wins actually showed up in closed-won pipeline.

No vanity metrics. No platform-attributed ROAS that overcounts. No "we hit 4 million impressions" if zero closed. Eight numbers your team can defend in a board meeting. See the full reporting cadence →

Case studies

Two CRO engagements. The math.

CRO questions

What do buyers ask about SaaS CRO?

More on the audit call.

How fast does CRO show results?+

First test live in week two. First winner promoted in weeks four to six. Compounding effect by month four. We won't ship a winner that didn't hit 95% significance.

What if our traffic is too low for tests?+

Below 5,000 monthly visitors on key pages we'll tell you in the audit. We'll point you at qualitative wins (session replay insights, form simplification, hierarchy fixes) that don't need A/B power.

Do we need a dedicated dev team?+

Not dedicated. Your existing team needs to ship two to three CRO tickets a month. Each one is small. Front-end work mostly.

Will you ship things that look ugly?+

Sometimes. The hypothesis library prioritises lift over aesthetic. We'll tell you when a winning test would clash with brand and we'll find a brand-aligned alternative.

What about pricing experiments?+

Yes. Pricing page tests on layout and anchoring frequently. Actual price changes are bigger decisions that go through your CFO. We model them. They sign them.

Do you do mobile CRO too?+

Yes. Roughly 35% of our tests target mobile specifically. Mobile signup flows are where the biggest wins often hide.

What if your tests break our analytics?+

We rebuild your analytics layer first if it's fragile. CRO that can't be measured isn't CRO.

Can CRO replace pricing strategy work?+

No. CRO optimises around pricing decisions. It doesn't make them. We'll surface pricing problems and recommend a separate pricing engagement when needed.

Pricing context

What a SaaS CRO engagement actually costs.

A SaaS CRO retainer in our pricing model sits at $7,500/month minimum with a six-month commitment. The retainer covers experimentation strategy, hypothesis backlog, test build, statistical analysis and quarterly roadmap updates. Tooling (VWO, Optimizely or Convert at $400 to $2,500/month, plus Hotjar or FullStory) runs separately. We do not mark up tooling. The audit and roadmap engagement is fixed-fee at $18,000 if you want a CRO roadmap without retainer commitment. At healthy traffic volumes a single 0.4% pricing-page lift recovers more than a year of CRO retainer cost. The maths works fast.

See all three engagement models Book the 30-minute audit

30 minutes. Your funnel. Our verdict.

Send your URL. We'll come back with a written read on which three tests we'd ship first.

Book a 30-minute audit call See the case studies
Response inside 4 business hours · No sales sequence · We turn down 1 in 3