Content strategy for B2B SaaS
A content calendar is not a strategy if nobody can explain why each page exists.
A healthy backlog can still hide an expensive problem: topics are getting approved, drafts are getting published, but the work is not clearly connected to a buyer, a product story, or a next step. Content strategy is where we make those decisions before production turns them into more pages to maintain.
I work with SaaS teams that need a sharper view of what to publish, what to repair, what to leave alone, and how content should connect to the product and the rest of the site. The result is a working direction your team can use, not a slide deck that becomes obsolete the moment the quarter changes.
The problem this solves
More ideas are rarely the missing piece.
Most teams already have more ideas than they can publish. The difficult work is deciding which questions are worth answering now, what job each page should do, where product knowledge belongs, and what evidence will make the argument credible. Without that, a calendar becomes a list of plausible keywords and content starts to sound interchangeable.
That matters more in SaaS. Buyers do not arrive with one neat question. They move between learning a category, understanding an operational problem, comparing approaches, looking for a workable process, and checking whether a product can fit their team. A useful content plan sees those moments as connected rather than treating every article as an isolated traffic bet.
Priorities with an argument
Each recommendation is tied to the reader, the commercial question behind the query, the product context available, and the role the page can play.
Coverage without clutter
We separate pages that genuinely deserve to exist from variants that will compete, overlap, or create more editorial upkeep than value.
A route into the product
Content is planned around the decisions your product can help with, so product mentions have a reason to be there.
What I look at
Content, product context, and the gap between them.
The exact scope depends on the question you need answered. In a strategy engagement, I normally start by getting close to the product and the customer problem, then review the parts of the site that should support the same story. That can include your existing blog, product and solution pages, documentation, sales language, customer questions, competitor positioning, search results, and internal notes.
I am not interested in producing a giant spreadsheet because it looks comprehensive. The point is to make a set of decisions that an editor, writer, founder, or in-house marketer can use when choosing the next page.
Content audit and diagnosis
A practical review of pages that are useful, thin, overlapping, out of date, disconnected from the product, or aimed at the wrong question.
Priority map
A focused list of new, refreshed, consolidated, or deprioritized pages with a clear reason for each decision.
Brief-ready direction
Angles, reader questions, evidence requirements, product context, internal-link opportunities, and the job the page should do after it is published.
What you receive
A plan that tells the team what to do next and what not to spend time on.
The work is documented in a format that matches the engagement. That could be a working content map, a set of priority briefs, a page-level audit, or a decision memo with recommendations. What stays consistent is that each recommendation is specific enough to act on.
- Priority topics or pages, ordered by buyer and business value
- Reader, intent, angle, and evidence notes for each priority
- Recommendations to create, refresh, merge, redirect, or leave alone
- Internal links and nearby service or product pages to connect
- Notes on where product documentation, customer language, or an SME is needed
- A realistic order of work for the next publishing cycle
How we work
Close enough to execution that the work survives handoff.
- Get the contextYou share the product, audience, current goals, existing content, and any questions sales or support hear repeatedly. I review the material before making assumptions about the category.
- Find the real gapI look for gaps in coverage, weak or duplicated pages, unclear positioning, and moments where a reader needs a better explanation before they can move forward.
- Set the directionI turn that review into page priorities, content roles, and brief-level decisions. We identify what needs more research or product input before it is drafted.
- Make it usableYou get a clear handoff for your team. I can also stay involved for briefs, writing, refreshes, and editorial decisions where that is the sensible next step.
What I need from you
You do not need a polished brief. You do need usable context.
Some of the best strategy work starts with a rough backlog and a few honest concerns. I do not need you to have every answer before we begin. But I do need enough access to understand the product, the audience, and the constraints the content needs to work within.
- Your website, product pages, and relevant documentation
- Any current content plan, keyword research, or performance notes
- The audience, buying motion, and business problem you care about now
- Product, sales, support, or customer-success context when it is available
- Someone who can clarify claims and approve the direction
- Honesty about production capacity, so the plan does not pretend you can publish twenty pages next month
When this is not the right first move
Sometimes you need one important page, not a strategy project.
If you have an urgent comparison page, a high-value article that needs a better brief, or a page that is clearly underperforming, the right first step may be a focused writing or refresh engagement. A wider strategy is useful when the decision itself is unclear, when several pages need to work together, or when the team is tired of publishing without a defensible order of operations.
I will say that plainly after looking at the context. There is no benefit in selling a bigger engagement when a narrower piece of work will solve the immediate problem.
Proof and scope
A strategy should be judged by the decisions it makes easier.
My published work spans search strategy, product education, content refreshes, analytics, and commercial content for software teams including SweetProcess, Userpilot, Surfer, StoryChief, and Rockee. The portfolio shows how that thinking carries into finished work.
See the work
Review published pieces and case studies before deciding whether the approach fits your team.
Strategy pricing
Strategy engagements are quoted after I review the site, the number of pages involved, the available product context, and the decisions you need the work to support.
Writing after strategy
If you want me to execute the plan, individual long-form writing projects start at $400. Larger batches are scoped separately.
Questions buyers ask
Content strategy, without the vague bits.
Is this a keyword-research deliverable?
Keyword and search-result research can be part of the work, but the deliverable is not a list of keywords. The useful part is deciding which questions deserve a page, the angle that will make that page worth reading, how it fits the product, and what it should connect to on the site.
Can you work with an in-house writer or content lead?
Yes. The strategy can be designed as a handoff to an internal writer, a freelancer, or a small marketing team. I make the direction concrete enough that the next person is not left guessing about the reader, structure, product context, or evidence needed.
Do you only recommend new articles?
No. New articles are only one option. Sometimes the right recommendation is to refresh a page, merge two overlapping posts, improve a service page, add internal links, or stop investing in a topic that does not fit the business.
Can strategy lead into writing?
Yes, when that helps. I can take priority briefs into content writing, product-led pieces, decision-stage pages, or refreshes. You are also free to use the direction with your own team.
Start with the actual question
Send the site, the backlog, or the part that feels stuck.
Tell me what you are trying to achieve, where content currently feels weak, and who needs to use the work after it is done. I will look at the context and recommend the cleanest next step.