A worked SaaS marketing strategy example

Most published strategy advice tells you how to write the document. Almost nobody shows the finished document, because the finished document exposes the numbers and the numbers are arguable. So here is one in full. The company below is a composite of three real plans, anonymised and rounded, for a vertical workflow product sold to finance teams at mid market logistics operators. Call it Ledgerline.

The company context that constrains everything else

Ledgerline ended last year at 4.0M ARR, growing 22 percent, with a 24K average contract value and 14 month CAC payback. Net revenue retention is 104 percent. Three people in marketing, two SDRs, four account executives, one solutions engineer shared with support.

Two of those numbers set the plan. The 14 month payback means the board will fund growth but not a 12 month brand programme with no pipeline attached. The 104 percent NRR means expansion covers very little of the target, so new logos have to carry it. If NRR were 118 percent the whole plan would be different and most of this budget would go to customer marketing instead.

The target for the year is 30 percent growth: 5.2M exit ARR, so 1.2M net new. That single number drives every section that follows. If you want the blank version of this document to fill in yourself, the SaaS marketing plan template mirrors the same six sections.

The ICP as it is actually written in the doc

Not a persona card with a stock photo. Three account filters and two people.

Account filters: freight brokerage, third party logistics or regional carrier; between 80 and 900 employees; already running NetSuite, Sage Intacct or Microsoft Dynamics as the accounting system of record. That third filter matters more than the first two, because the integration is what makes the product install in two weeks instead of five months.

Buyer: VP Finance or Controller, who owns the pain. Technical approver: a single IT generalist who will ask about SOC 2 and SSO and then approve. Economic buyer is the CFO at the larger end, the same VP Finance below about 300 employees. The full buying committee work only kicks in above 500 seats, which is a small slice of this pipeline.

The negative ICP, and the argument it ended

This is the section most plans skip, and the one the sales team read first.

Ledgerline will not pursue: freight tech startups under 80 employees (they have no finance team to sell to, and churn ran above 4 percent monthly in that cohort), enterprise carriers over 2,000 employees (the security review added 11 weeks and two of three deals died in procurement), and any account running a homegrown ERP (integration scoping consumed the solutions engineer for weeks with a 20 percent close rate).

Those exclusions went straight into three systems on the same afternoon: the LinkedIn ads exclusion list, the demo request routing rules in Chili Piper, and the SDR call disposition options. That is the point. A negative ICP that lives only in a slide changes nothing.

Excluded segment	Why it was excluded	Deals lost to the rule	Revenue protected
Under 80 employees	No dedicated finance function, 4%+ monthly churn	~9 per year	Roughly 140 hours of AE time
Over 2,000 employees	11 week security review, 33% close rate	3 to 4 per year	Solutions engineer capacity
Homegrown ERP	Custom integration, 20% close rate	6 per year	Engineering roadmap slippage

Positioning summary and the headline it produced

One paragraph, agreed by the founder, the VP Sales and marketing, and then inherited by every surface.

The competitive alternative is not a competitor. It is a finance analyst reconciling carrier invoices in Excel for six days a month. The unique attribute is a two week install against three named ERPs. The value is closing the month four days earlier with audit ready backup. The category is freight settlement automation, which buyers already search for, rather than a new term invented in a workshop.

Homepage headline that came out of it: “Close the month four days earlier, without a new ERP.” Subhead names the three integrations. The old headline was “Modern financial operations for logistics,” which tested at half the demo request rate on the same traffic. If you want the reasoning behind category choice rather than the output, how to build a SaaS marketing strategy covers the upstream work.

Why hybrid, not product led and not pure sales led

At 24K ACV, pure self serve does not clear the bar. Nobody puts an annual contract on a card without a conversation, and the ERP integration needs a scoping call regardless. Pure sales led wastes AE time on accounts that could have disqualified themselves in twenty minutes inside a sandbox.

So: a guided sandbox loaded with anonymised sample carrier invoices, no credit card, no integration required. The activation event is a user running a reconciliation on the sample data and seeing the exception report. Sales gets notified on that event, not on the form fill. Between those two triggers the opportunity rate roughly doubled, from 19 percent of form fills to 38 percent of activated sandbox users.

The trade off is real. The sandbox took 9 engineering weeks and delayed two roadmap items into the following quarter. It also produces a slower top of funnel, because fewer people finish a sandbox than fill in a form. The product led versus sales led decision here was made on ACV and integration complexity, not on ideology.

The model: 1.2M in ARR becomes 96 opportunities

This is the section that makes the rest of the plan arguable rather than decorative.

The 46 percent win rate looks high, and it is, because Ledgerline only counts an opportunity after a discovery call confirms a budget owner and an evaluation date. Teams that create an opportunity at demo request will see 20 to 25 percent and need roughly twice the volume. Neither definition is wrong. Mixing them inside one model is.

Sources for those 96: 44 inbound, 30 outbound, 14 partner and referral, 8 from two field events. Inbound at a 38 percent sandbox activation to opportunity rate means 116 activated sandboxes, which at 31 percent of sandbox starts means about 375 sandbox starts across the year. That is the number the content and SEO work is actually accountable for. For the same model with the demand gen assumptions broken out by channel, see the demand generation plan template.

The channel plan: budget, owner, stop rule

Total marketing spend is 560K against 4.0M ARR, which is 14 percent. About 340K is the three person team, 220K is programs. Every program line has a name against it and a condition under which it dies.

Channel	Annual program budget	Owner	Target opportunities	Stop rule
Organic and content	72,000	Content lead	26	If sandbox starts from organic are under 140 by 31 August, cut publishing to 2 per month and move spend to partner
Paid search, brand plus 9 bottom funnel terms	48,000	Growth marketer	18	If cost per opportunity exceeds 2,700 for two consecutive months, pause non brand
Outbound sequences and data	34,000	VP Sales	30	If connect rate on the 900 account target list is below 6% by end of Q2, replace the data vendor
Partner and integration co-marketing	30,000	Founder	14	If no partner has sourced 3 opportunities by 30 September, reduce to one partner
Two field events	28,000	Growth marketer	8	If event one produces under 3 opportunities within 60 days, cancel event two
Customer marketing and case studies	8,000	Content lead	0 direct	Never cut, it feeds every other line

Note that the largest opportunity target sits on the cheapest line. Outbound costs 34K in tooling and data because the two SDRs are carried in the sales budget. Presenting it any other way flatters the channel, and finance will find it eventually.

The four quarterly targets

Coverage assumption across all four quarters is 3.2x pipeline to quota, based on the 46 percent win rate plus slippage. Reporting is one dashboard, reviewed every second Monday, with three numbers on it: qualified opportunities by source, cost per opportunity by channel, and sandbox starts. Everything else lives one click deeper. The temptation to report 30 metrics at this stage is strong and should be resisted.

What was cut, and why this is the section that matters

Three things got a written no.

No podcast. It was proposed as a way to build relationships with logistics CFOs, and it might have worked. It also needed roughly 6 hours a week from a three person team for a payback nobody could model inside 18 months. If Ledgerline had 12 months of runway and 40 percent NRR expansion, the answer changes.

No second vertical. Retail distribution came up twice because two inbound deals closed there. Two deals is not a market, and the ERP integration work for a new vertical is a quarter of engineering time. Revisit at 8M ARR.

No G2 category push beyond the free profile and a review drive with existing customers. Paid category presence quoted at 45K for the year, against a category with 60 monthly searches. That is a 12M ARR decision, not a 4M one.

Each of those had a champion who was not obviously wrong. That is exactly why the section exists. A strategy that names only what it will do is a wish list, because it never forces the trade. Read SaaS marketing examples alongside this and you will notice the same pattern: the legible ones are legible because something was refused.

What to do with this

Copy the six section structure, not the numbers. Start with your own version of the model table, because every other section gets easier once the opportunity count is fixed. Then write the negative ICP before the channel plan, and route it into your ad exclusions and lead routing the same week.

If you are starting from zero rather than rewriting, work through the B2B SaaS go to market plan template first, then come back to this page to pressure test the numbers. Benchmarks for the conversion rates used above sit in the SaaS marketing statistics reference, and the underlying structure is explained in the SaaS marketing framework. The whole category overview lives at SaaS marketing.