B2B SaaS content writing, the craft.
B2B SaaS content writing is putting product knowledge, buyer language and a real argument on the page for people who evaluate software for a living. Not general writing pointed at software topics. The category detail is the work.
Pages we wrote, and what they did to the pipeline.
Three programs. Every figure sits on the case study it links to.
Authority numbers come from Ahrefs, traffic from the client's own analytics, pipeline from the client's CRM. All case studies
Generalists, hedged voice, no argument.
Four failure modes turn up in nearly every content audit we run, and hiring a better generalist fixes none of them.
The category gap
A writer who has never run a SOC 2 audit cannot fake one. The compliance reviewer spots the surface read and closes the tab.
The 2018 voice
Soft opening, long preamble, two hedges before the first claim. It reads as marketing, so the buyer skims and goes.
No position
Pages that explain, summarise and list. Nothing in them is a claim a reader could argue with, so nothing gets quoted.
Prompt-written bulk
AI drafts fast. It does not sit on the SME call, and it cannot defend a claim nobody checked.
The voice is a set of rules, not a personality.
Five of them apply to every page we ship. The sixth, claim before context, is structural, so it sits further down.
Rule 01No hedging unless the hedge is the point
Cut "perhaps", "in some cases" and a bare "it depends". If it depends, name the variable. "It depends on ARR stage" is an answer. "It depends" on its own is filler.
Rule 02Short sentences, period-heavy
Around 14 to 18 words on average. Longer only when a technical point cannot be split. Same topic, two openings: the shorter one carries three claims and names a cause.
Rule 03No buzzwords
Synergize, thought leader, game-changer, paradigm shift, deep-dive as a verb. Each one tells a technical reader the writer had nothing specific to say. Put back the thing the word was covering.
Rule 04Name the controversy
Most topics in your category have a contested position. Say where you disagree with the room and then defend it. A page that plays both sides gives a reader nothing to quote and nothing to forward.
Rule 05End with implication, not summary
The last paragraph says what the reader does differently now. They already know what the page said. They read it.
- What the argument means for your program
- The one thing to change first
- What it costs to keep doing it the old way
- Where the detail lives
Six to twelve readers. One page has to land with all of them.
A deal between $20K and $500K ACV pulls in six to twelve people, and each one runs different searches.
Who reads the page, and what each one came for
| What they type | What the page owes them | |
|---|---|---|
| End-user champion | best X for [use case], alternatives to Y | Workflow fit and the learning curve, shown in a screenshot |
| Manager, budget owner | X vs Y, X pricing | The maths at their headcount, and time to value in weeks |
| Technical reviewer | X API documentation, X integration with Y | Integration depth, rate limits, and what the API will not do |
| Security reviewer | X SOC 2, X data residency | Certification posture and where the data physically sits |
| Finance reviewer | X total cost of ownership, X pricing model | Multi-year cost, contract terms, what makes the bill grow |
| Procurement | X enterprise contract, X vendor risk | Vendor stability, contract flexibility, how an exit works |
The unit is not the sentence. It is the triplet.
Claim, evidence, implication, in two paragraphs. A section that runs past three is hiding a second argument.
Unit 01How a section gets built
The claim is the position. The evidence holds it up. The implication is what changes for the reader. Any of the three can be lifted out and still stand on its own.
Unit 02Claim before context
Lead with the position and support it after. Building context first was the 2018 pattern, and it is now the thing that gets a page closed. Sophisticated readers want sentence one, not paragraph five.
Unit 03Evidence an editor will keep
Generic support is filler and it gets cut. Every section needs at least one point that somebody who wants to prove you wrong could go and check.
Unit 04Technical depth, calibrated
Too shallow and the reviewer calls it marketing. Too deep and the buyer new to the category gets lost. Define the term in brackets the first time. The reviewer skims past the bracket and nobody gets talked down to.
- The claim, with the headline number
- An inline definition, in brackets
- The detail the reviewer came for
- The implication, back in plain words
Written so an assistant can quote it.
AI search now sits in front of a growing share of evaluation queries, so a page that cannot be lifted out of context loses readers it already earned.
Move 01Answer the heading in the first hundred words
Assistants look for a declarative sentence that answers the heading. A section called "What does content writing cost?" answers it in the first line, not the eighth paragraph.
Move 02Define the terms inline
Assistants use definitional context to decide which page to cite, so a page that defines its own terms is easier to attribute. The reader who knows the term skims the bracket and loses nothing.
Move 03Give the parser something to hold
Numbered lists, tables, question headings and named frameworks are parsing anchors. A claim wrapped in "five reasons" gets lifted. The same claim buried in prose does not.
- A list with its count stated in the heading
- A table that survives copy and paste
- Questions as headings, answered underneath
- A named framework, spelled the same way twice
- The source sitting next to the number
Move 04Publish the number, do not repeat it
Assistants cite whoever published a number, not the page that quoted it. If you want the citation, run the survey or publish the benchmark yourself.
Move 05What it looks like when it holds
Da Vinci published eleven months of pages built to be quoted. Organic traffic grew about 25 times, and six assistants now cite the site.
Hiring writers who actually know the category.
Portfolios overstate who did the thinking. A short writing test does not, and it takes a week.
Give a brief, not a portfolio review
One brief on a real topic in your category, one 30-minute SME interview, five to seven days, 800 words. A portfolio tells you what an editor fixed. The test tells you what the writer can do alone.
Score the test on four axes
Category depth, voice discipline, argument structure, and whether they pushed back on weak SME answers. One to five on each, twenty points in total.
16 or higher: hire
Brief once and edit lightly. They structure an argument without being told to and they go back to the SME when an answer is thin.
12 to 15: workable with an editor
Pair them with a senior editor and expect two passes a piece for the first sixty days. Most of the gap is voice, and voice is teachable.
Below 12: pass, whatever the portfolio says
The category-knowledge gap does not close on the job, and neither does a writer who did not notice the SME was guessing.
What a B2B SaaS writer costs
$0.50 to $1.50 a word at contract level, $90,000 to $140,000 fully loaded in-house. At $0.10 to $0.25 a word you are buying a generalist who fails the test.
Budget the editing hours too
About an hour of senior editing per 2,500 to 3,500 words. Compress it to ten minutes and you ship surface polish over a broken argument.
Edit the argument before the grammar
Grammar is twenty minutes. A broken argument sends the writer back to rethink the piece. Ask whether each section makes a claim, whether the evidence is specific, and where the page pads.
What teams ask before they hand over the writing.
Seven questions from first calls: what it costs, how long a piece takes, what AI can and cannot do, and who should own the work at your stage.
What is B2B SaaS content writing?
B2B SaaS content writing is the craft of producing written content that B2B SaaS buyers consume during evaluation and that the marketing team can defensibly tie to pipeline. It differs from generic content writing because the buying committee has 6 to 12 sophisticated personas, the sales cycle runs 60 to 180 days, and the technical depth required for credible content is high.
How is SaaS content writing different from regular content writing?
Three structural differences. The audience is more technical and more inundated, so the voice and evidence bar is higher. The sales cycle is 60 to 180 days, so content has to support a long evaluation rather than convert in a single read. AI search now answers a growing share of evaluation queries, so content has to be built for both human reading and LLM citation.
How much does B2B SaaS content writing cost?
At the contract-writer level, $0.50 to $1.50 per word for writers who can pass the hiring test. At the full-time level, $90,000 to $140,000 fully loaded for the same writers. At the agency level, $8,000 to $30,000 per month for a credible program that covers strategy, writing, production, and editorial review. Below those ranges, the math typically does not support the senior operators the work requires.
Can AI write B2B SaaS content?
Not the argument, not the SME-derived claims, not the editorial decisions. AI assists the production layer effectively (outline drafts, SERP synthesis, first-pass research, structural QA, headline variations). Programs that try to fully automate content production with AI are watching rankings collapse in the algorithm updates that have run since late 2024.
Should we hire freelancers, an agency, or full-time writers?
Below $5M ARR, freelancers plus a part-time editor work if you can manage them. At $5M to $20M ARR, an agency with senior writers usually wins because the editorial layer and SME-coordination overhead is structurally agency-shaped. At $20M to $50M ARR, hybrid (one senior in-house writer plus agency support) is the most common stable model. Above $50M ARR, full in-house starts winning on economics.
How long does it take to write a piece of B2B SaaS content?
A long-form pillar piece (4,000 to 7,000 words) takes 30 to 60 hours from brief to publish including SME interview, draft, editorial review, revision, and final QA. A standard cluster post (1,500 to 2,500 words) takes 12 to 25 hours. Programs that compress these timelines well below these ranges produce content with surface polish but argument problems.
What does a good B2B SaaS content brief include?
The buyer persona, the search intent, the SERP analysis, the proprietary angle, the named SME, the target word count, the internal links, the conversion intent, and the success criteria. Most agency briefs include the keyword and a vague topic. That is not a brief.
Want this bar on your next draft?
Send two pieces you published last quarter and the briefs behind them. In thirty minutes we will tell you where the argument breaks, what to cut, and whether you need new writers or a better brief.
Or email Rizwan