For B2B SaaS
Be present for the six-month research window.
Nobody buys B2B software in one visit. The buying committee reads for months — the workflow, the migration, the integration, the rollout — and most of those questions are answered in a sales call long after the research has finished. Xt4b puts the answers on your own domain, in each market you sell into, before the shortlist is drawn.
This page is about sales-led software, where a committee signs off after a long evaluation. If one person signs up on their own, the closer fit is SEO content for SaaS.
Docs and product pages stay yoursOne line per marketNo per-article quotes
What gets read during an evaluation.
Not a feature announcement with the word “seamless” in it. The questions a committee asks in the two quarters before it buys anything.
- The problem, before the product
- Buyers research the process they are trying to fix long before they evaluate software. Those queries are where the shortlist is formed, and they are rarely answered by a product page.
- The migration and the rollout
- What moves, what breaks, how long it takes, who has to be involved. The single most-asked question in a B2B evaluation, and the one support teams answer by hand.
- The integration question
- How it fits the stack the buyer already runs — described in the terms their own team uses, with a link to the documentation that carries the detail.
- The committee, not the individual
- A technical evaluation, a finance question and an operations objection are three different readers. Distinct posts serve each of them without repeating the same overview.
- The long evaluation window
- In a six-month research cycle, the account that has been answering questions since month one is the one that gets invited to the shortlist.
- A route from the post to the demo
- Posts link to the product, pricing and documentation pages you already publish — taken from your sitemap, so the blog feeds the funnel rather than competing with it.
A product blog that survives a launch week.
Five steps, and one of them is the review that keeps marketing and product honest with each other.
- 01
Scan the product site
Free and without an account: the homepage, the feature pages and the sitemap, plus the evaluation questions the site does not answer yet.
- 02
Connect the domain
One DNS record, usually a subdomain like blog.yourproduct.com. Nothing is installed, no documentation tool is touched and no build pipeline changes.
- 03
Keep the plan honest
Discard a post for a capability that is not shipped or not supported. Nothing is charged per article, so a post you do not want costs nothing.
- 04
Publish on the calendar
A post on each publishing day you picked, per language, with images, metadata and internal links into the pages that take the demo request.
- 05
Measure queries, not vanity
Search Console read-only, per site: which evaluation queries the domain is earning impressions for — the leading indicator, months before a pipeline converts.
What stays with you.
A pipeline should never be the source of a benchmark, a certification or a customer name. Those are checkable claims made by the company that has to stand behind them, and they stay on the pages that do.
What this can do is answer the process questions around them — in every market you sell into — and hand the reader to the page that books the demo, months before they would have found you.
- Benchmarks, uptime, SLAs and anything a procurement team will check
- The roadmap, the pricing model and the packaging
- Security posture, certifications and data-processing terms
- Customer names, logos and references
- What the product genuinely does not do
A launch calendar, or a research calendar.
They are not the same shape, and the second one is the one that compounds.
Publishing around launches
- A burst of posts in the week of a release, then quiet
- Copy written for people who already know the product
- The migration question answered only in a sales call
- One language, on the assumption everyone reads English
- Traffic measured on launch week and never again
Publishing through the cycle
- A post on each publishing day, launch or not
- Queries taken from what the buyer is trying to fix
- Migration and integration explained in public, once
- Each market planned from its own searches
- Impressions per evaluation query, month by month
Where a content blog stops being useful
It cannot close a deal or fix positioning. If the product does not fit, better-written pages bring the misfit to the surface earlier — which is uncomfortable and still cheaper than a wasted quarter.
And it cannot promise a pipeline: rankings, traffic and revenue are not guaranteed, and the terms of service say so. What it does is publish, on a schedule, the pages a buying committee reads on the way to a decision.
Costed per market, not per asset.
20€ per website, per language, per month. The scan comes first and costs nothing — the evaluation questions your site is missing are visible before any budget moves.
One market is one line: no per-article rate, no minimum number of posts, no separate charge for images or hosting the blog. Three languages is three lines, and each is written against that market’s searches rather than translated from the English posts.
Because the blog lives on a domain the company owns, the archive survives the next repositioning, the next website rebuild and the next head of marketing — and it keeps being read while all three are happening.
- The plan: queries, intents, outlines and dates
- Drafting, with the pre-publication review pass
- Cover and in-article images, in the product's colour
- Hosting the blog on a domain the company owns
- The crawlable plumbing: canonical URLs, sitemap, structured data
- Search Console reporting, site by site
More on content
- For agencies
Several client sites, one account, one calendar each.
- For startups
A content function without a content hire.
- For SaaS
Be the answer before the demo request.
- For marketing teams
A pipeline behind the calendar, per site and language.
- For consultants
The enquiries that begin with a search.
Questions SaaS teams ask.
Including whether it writes product pages, whether it names competitors, and how it fits a long sales cycle.
What about the security and compliance questions the committee asks?
They belong on pages your team owns and can stand behind — a trust page, a sub-processor list, a certification, a status page. A claim in a blog post is a claim you have made in public, so the plan targets the query, the post hands the buyer over, and nothing here invents a compliance answer at the wrong moment in the evaluation.
How does the content keep up with a product that ships every month?
Research content and launch content age at different speeds. A post about a workflow or a migration path stays true for a year; a post about a feature is wrong by the next release. The plan is built around the questions that outlive a changelog, and the pages that must track the product stay yours.
How does this fit a six-month sales cycle?
That is the shape it is designed for: one post per publishing day, accumulating over exactly the months a committee spends researching. A page published in month one is still being read in month five, when the shortlist is drawn.
Can it write for a technical and a business reader at once?
Not in one article. Each entry targets one query with one intent, so the technical evaluation and the finance question become separate posts, each written for the reader who typed it. That is also what keeps approval quick: one question at a time.
How does this fit a rollout across several regions?
A region is a line: its own plan, its own queries, its own dates, priced per website, per language, per month. A rollout that starts in two markets and reaches five later means five lines whenever you are ready — and a region that stalls is switched off without disturbing the ones that already report.
What if the plan proposes something product cannot support?
Discard it. The plan is reviewed before anything is written, and an entry for a capability that is not shipped costs one click to remove. Nothing publishes without a plan entry behind it, which is the mechanism that keeps the blog from promising features.
What does it cost, and what does it replace?
20€ per website, per language, per month: no per-article quotes, no minimum volume, the scan free and without an account. It replaces the freelance retainer that produced four posts in a year more reliably than it replaces an in-house content team.
How do you measure content that influences a six-month deal?
Not with last-click attribution, which will always credit the demo request. The usable signals are the ones Search Console already shows: impressions and average position for the evaluation queries you were not in before, on pages that sit in front of the committee while it is still reading. Anything past that is a CRM question rather than a content one.
Start with the product site
Answer the committee before the shortlist.
Connect the product's domain and read the plan: the evaluation questions the site is missing, the outlines behind them, and the dates they would publish on.
Product pages untouched20€ / site / language / month3 days free, no card