Asset 20 8 2
Does AI recommend your business? Run the free check →

Join 15,000 business owners, marketers and entrepreneurs. The Sunday newsletter you'll be annoyed only arrives once a week.

Article

SaaS Write For Us: Guest Post Guidelines

Yes, SaaS guest posts are accepted on this blog. Its readers are business owners, marketers and agencies who buy software constantly and a few who build it. The accepted pieces carry real numbers: what really moved growth, what churn cost, how you priced something no one can hold. SaaS-marketing-to-SaaS-marketers content gets declined. Pitch a specific growth story with the figures still attached.

The SaaS posts that run here are written for the people who buy and run software, not for other SaaS marketers. If you have actually grown a product, our readers want the version with the numbers still attached.

I'm Lilach Bullock. This blog reaches business owners, marketers and agencies, many of whom buy software constantly and some of whom build it. They care about what actually moves growth, what churn really costs, and how to price something nobody can hold.

60-second SaaS guest post check

A strong submission can answer yes to all five points:

  • The writer has worked directly on the SaaS product, growth channel, pricing decision, onboarding flow, or churn problem.
  • The pitch includes a specific result, number, test, failure, or lesson that cannot be copied from another article.
  • The reader is a founder, business owner, marketer, or agency making a real software decision.
  • The article teaches before it promotes and is not vendor copy wearing an editorial byline.
  • The writer has read the full contributor guidelines before submitting.

Read the guidelines and submit your SaaS guest post

What We're Looking For

Content that helps a business owner make a decision they will not regret:

  • Real SaaS growth stories, including the channels that failed
  • Churn: what caused it and what genuinely reduced it
  • SaaS pricing and packaging decisions, with the outcome
  • Product marketing and positioning done properly
  • Onboarding and activation that moved a real number
  • Going from founder-led sales to a repeatable process
  • Building in public, honestly, including the bad quarters

If your post could be published by any SaaS company with the logo swapped, it is not for us.

Also accepting guest posts on technology and AI.

What We Don't Accept

  • Vendor marketing with a byline on it
  • Content published elsewhere
  • Affiliate round-ups with no real testing behind them
  • Anything written purely for a link, with no value to the reader

Most declined SaaS pitches have a better post hiding inside them. This is where the common ones land, and what to send instead:

Declined pitch Why Pitch this instead
An overview of SaaS growth strategies No first-hand result behind it The one channel you ran, including the part that failed
SaaS marketing written for other SaaS marketers Not the reader here The same lesson written for the owner choosing or running the software
A piece about your own product The guidelines say a post that only promotes a company isn't accepted as a guest post The lesson, with your product as the worked example only if the lesson stands without it
What ARR or CAC means Already covered on the blog (see the list further down) The next layer, such as net revenue retention from your own numbers

What You Get

  • Exposure to an engaged audience of business owners and marketers
  • A quality backlink from an established domain
  • Author bio with a link back to your website
  • Social media promotion across our channels

How to Submit

All guest post submissions go through our main submission page. Please read the full guidelines first:

Submit your guest post here

If you would like to reach a broader marketing audience, you can also write for us, or see the full list of blogs that accept guest posts.

B2B SaaS marketing guest posts: what a strong pitch looks like

The pitches that get accepted here come from people who have actually done the thing, not people summarising what other people have written about it.

A weak pitch says "I would like to write about SaaS growth strategies." A strong one (an illustration, with invented figures) says "We changed our pricing page from three tiers to two. Revenue per signup went up 18 percent and support tickets went down. Here is what we tested and what we got wrong first." One is a brochure. The other is worth reading.

The angles that get accepted fastest

  • A pricing or packaging change, with the numbers before and after
  • The growth channel that failed and what it cost to learn
  • A churn problem traced back to its actual cause
  • Onboarding changes that moved activation
  • Moving off founder-led sales, honestly

Before you pitch, make sure you can state each of these in a line:

  • The one problem the post solves for the reader.
  • Your role: founder, marketer, product lead or the person who ran the change.
  • The product's stage when it happened, so readers can tell whether it applies to them.
  • How you define each metric and the period it covers. State your formula for churn, activation or net revenue retention once (monthly or annual, all customers or one plan) before any number appears, so readers can compare it with their own.
  • Where the numbers come from: your own data or a named public filing. No borrowed benchmarks.

Before you pitch anywhere, it is worth checking the site's links with the free backlink checker, and the write for us finder will find more sites in the same niche.

SaaS automation blog guest post guidelines

If you write about SaaS or automation and want a guest post here, these are the guidelines. Pitch a topic a small business owner would search for, not a product announcement. The article needs to be 1,200 words or more, written for the owner rather than the developer, with a clear answer in the first paragraph and real steps or examples underneath. Links to your own tool are fine where they help the reader, and every link is do-follow. I edit for clarity and cut anything that reads like a sales page. Sponsored placements are handled through the write for me page, where you can also ask about product placement in a listicle.

Work with me

Want AI doing the heavy lifting in your marketing?

I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.

For all guest post guidelines in one place, start at the write for us guidelines hub.

SaaS topics we've already run, and the gaps worth pitching

NIST's cloud definition is a good place to start any SaaS pitch. It says the cloud model has five essential characteristics, three service models and four deployment models, and Software as a Service is one of those three service models. That's a useful reminder of who the reader is: someone buying or running software delivered as a service, not someone who needs the acronym explained again. NIST's keywords for the document list the other two service models as Platform as a Service and Infrastructure as a Service, and that's the line a useful SaaS post draws: what the customer buys and uses, against what the vendor runs underneath.

The basics are covered here already, so please don't pitch them. There's a guide to annual recurring revenue and MRR, a walkthrough of the CAC formula, a piece on the signs of product-market fit, an explainer on sizing TAM, SAM and SOM, a guide to building a customer journey map and a ranking of the Ansoff matrix growth strategies by risk.

What's missing is the next layer down. These are the briefs I'd like to see:

  1. Net revenue retention, explained for a founder. Why NRR tells you more than logo count, with a worked example from your own numbers or a public filing. Reader outcome: they can read their own retention line and know whether expansion is covering churn.
  2. SaaS security questionnaires. What B2B buyers ask before they sign, which answers stall a deal and how to prepare a reusable pack. Reader outcome: their team stops scrambling every time a procurement form lands.
  3. Where your SaaS data lives. The data residency questions customers now raise, and how to answer them honestly without overpromising. Reader outcome: an accurate answer ready before the question comes up.
  4. The weekly founder metrics view. Which SaaS numbers a founder should read every week, before the board pack is due, and which can wait for month end. Reader outcome: a short weekly routine instead of a dashboard nobody opens.
  5. A free trial email sequence that stays useful. Emails that help a trial user reach a first win, not a countdown of reminders. Reader outcome: a sequence they can map to their own product's activation steps.

Briefs 2 and 3 carry one extra rule. Name the specific rule or framework your customers raise, and point to its official page; a compliance claim that can't be checked gets declined, because the guidelines rule out anything inaccurate.

To show the shape a title can take, here are example titles for these briefs (illustrations, not posts that exist):

  • The five questions in every security questionnaire, and the answer pack that ended the scramble
  • Where our customers' data sits, and how we explained it without overpromising
  • Why our trial emails stopped counting down days and started pointing to one first win
  • The weekly founder view: five numbers to read before the board pack
  • From the founder's calendar to a repeatable demo: what we documented first

I'd rather read one of these done well, with your own screenshots and examples, than another overview of what SaaS is. If you mention tools, name them in plain text; the piece should stand on what it teaches.

Frequently asked questions

How long should a guest post be?

Long enough to answer the question properly and no longer. In practice that is usually 1,200 to 2,000 words. Depth matters far more than word count.

How long does a decision take?

We aim to come back to you within a few working days. If the pitch is specific and clearly written, that decision is much faster.

Can I include a backlink?

One contextual backlink to your own site or a relevant resource is fine in an editorial post. More than that reads as link-driven rather than reader-driven.

Do you accept SaaS guest posts from vendors?

Only when the post teaches first. The contributor guidelines say a post that only promotes a company won't be accepted as a guest post; if you want your tool covered, product placements, reviews and sponsorships are the separate routes for that.


Related reading: Link Insertions and Niche Edits on an Established Marketing Blog and Write for Us, Startup Blog | Guest Post on Lilach Bullock.

I go much deeper on this in the content marketing guide.

Published and maintained by the Lilach Bullock team, covering marketing, AI and business growth.
Your buyers are asking AI who to use. Does it say you?

See for free whether ChatGPT, Claude, Perplexity, Gemini and Google name you, and get the plan to become the answer.

Check my AI visibility →
Sundays only

Get the Sunday newsletter.

One email a week. AI experiments, marketing tactics, and the workflows Lilach is building right now in her own business.

Subscribe free

Let’s get your marketing running on AI.

Book a free 30-minute call

We figure out what you need, where AI fits in, and what working together would look like.

Book the call →

Or take the 30-second calculator

You’ll see the hours and the money quietly leaking out of your week, and the three workflows worth building first.

Take the calculator →

Or grab the free AI resource library

Prompt packs, templates, checklists, and swipe files. The exact tools I build for paying clients. Yours, free.

Get the library →
Keep reading

More from the blog.