Skip to content
The Insight Journal Business & Operations

Contribute · SaaS

Write for Us: SaaS and Business Technology

A neutral, function-first software desk. That neutrality is the product, so the rules about vendor content here are stricter than anywhere else on the site.

Reviewed August 2026 · The Insight Journal Editorial Team

Paid placement Sources required House byline

This desk in one box

Covers
Neutral, function-first software guidance. No thinly veiled vendor pitches.
Written for
Operations and IT leads choosing tools for a small team
Cost
Quoted per pitch. No published price list.
Pitch this desk

What the SaaS desk publishes

In short

This desk publishes function-first software and SaaS writing: what a category of tool actually does, what it costs at scale, and how a company decides between options. Pricing must be current and sourced to the vendor page. Vendor-authored advocacy runs as labeled sponsored content, never as editorial.

Software writing is where the gap between a list and a decision is widest. A feature comparison is easy to produce and tells a buyer almost nothing about what the tool will cost them in year two.

This desk is built around the parts vendors leave out: seat minimums, tier jumps, migration effort, and what happens to the bill when the team doubles.

We are equally strict in the other direction. A tool being unfashionable is not a finding, and we do not publish takedowns any more than we publish advocacy.

Who reads it

  • Operations and IT leads choosing tools for a small team
  • Founders who own the software budget
  • Finance staff auditing a stack for duplicate spend

Write for that reader rather than for a search engine. A draft aimed at the person in the job usually clears our checks on the first pass, because specificity and sourcing tend to arrive together.

Ten angles we would commission today

In short

These ten briefs are open right now. Pitch one directly, or use them to calibrate an idea of your own. They share one property worth copying: each names a decision the reader has to make, rather than a topic they might find interesting.

Anything at this altitude gets read properly. Anything below it gets a form reply, which serves neither of us.

  1. 01

    Total cost at scale, not list price

    Model the bill at 5, 25, and 100 seats, including the tier where a needed feature actually unlocks.

  2. 02

    What a category is really for

    Define the job before the tools. Most buyers pick a category before they have named the problem.

  3. 03

    Migration cost, told honestly

    Data export limits, field mapping, retraining time, and the month the old system stays on in parallel.

  4. 04

    Build versus buy for internal tools

    Where a spreadsheet is still correct, and the point at which maintenance overtakes a subscription.

  5. 05

    Integration reality

    What the published integration does and does not sync, and which direction it flows.

  6. 06

    SaaS metrics used correctly

    Net revenue retention, gross margin, and payback, defined precisely enough to be comparable.

  7. 07

    Procurement and security review

    What an SMB should ask about data residency, subprocessors, and exit, without a legal team.

  8. 08

    Consolidation and stack sprawl

    How duplicate tools accumulate, and how to audit a stack without breaking a workflow.

  9. 09

    AI features in existing products

    What is shipped and measurable today, separated from what is on a roadmap slide.

  10. 10

    Deprecation and lock-in

    What a company owns when it leaves, and how to test that before signing.

What this desk declines

In short

Most pitches are declined for category rather than craft. If your idea sits on this list, no amount of rewriting will move it, and we would rather you knew that before spending a day on a draft than after.

A decline usually means the piece belongs on another desk, or on the sponsored path.

  • Feature lists copied from a vendor comparison page
  • Pricing quoted without a link and a date, or quoted from memory
  • Pieces where the author sells the tool being recommended and does not say so
  • Competitor takedowns and alternative-to pages written by a competitor
  • Top-10 tool roundups with no cost model and no exclusion criteria

The sourcing bar, in specifics

In short

Every non-obvious claim needs a named publisher, a year, and a link a reader can open. On this desk, the sources below cover most of what a draft will need. A figure that traces back to another blog post is not sourced, and it comes out in editing.
Cite the organization that produced the data, not the article that repeated it. Include the year.
Primary sources accepted on the Business Technology & SaaS desk
Vendor pricing and documentation pagesThe only acceptable source for a price, a limit, or a feature tier, cited with the date you checked.
SEC EDGAR filingsRevenue, retention, and customer counts for publicly traded software companies.
NIST Cybersecurity FrameworkSecurity control vocabulary when writing about software risk.
Cloud Security AllianceCloud control and shared-responsibility references.
Official API and changelog documentationIntegration behavior and deprecation timelines.

Our full method is set out in the sourcing standard we publish against.

How placement works on the SaaS desk

In short

Placement here is quoted per pitch against business technology & saas scope rather than from a price list, and the link treatment is agreed before you write. The terms, the editing process, and the link policy are the same across all six desks and are set out once, in full, in the submission standard.
Read first The standard a SaaS draft is edited against Rates, link treatment, editing, revisions, and what a finished draft has to contain. Wrong desk? The five desks that are not SaaS What each one commissions, and which reader it is written for. Paid path Sponsored SaaS placement For work that is promotional by design, labeled honestly and reaching the same readers.

Pitch the SaaS desk

Tell us the topic, the angle, and the sources you plan to cite. If it fits business technology & saas, we reply with scope, link treatment, and a rate.

Replies within 2 business days

Questions

Writing for the SaaS desk: common questions

Can a software vendor write for this desk?
A vendor can write about a problem, a category, or a method. A vendor cannot write the piece that recommends their own product; that is sponsored content and it runs with a visible label on the advertising path.
How do you handle pricing in a submission?
Every price must link to the vendor pricing page and state the date it was checked. We do not publish remembered or approximated pricing, and we date-stamp the page so a reader knows how fresh the figure is.
Do you publish product reviews from contributors?
Reviews are produced in-house so the comparison basis stays consistent across the section. Contributors are better placed on category, cost, and process topics.
Will you link to my SaaS product?
Where it is genuinely relevant to the point being made, yes. Links that form part of a paid arrangement carry the sponsored attribute, and we confirm the treatment before you write.
Do you accept technical or developer content?
Only where it reaches a business decision. Implementation detail is welcome as evidence, but the piece has to answer a question an operator would ask.
What is the fastest way to get a SaaS pitch accepted?
Name the buying decision, and name the vendor pages you will cite for every number. Sourcing plans are what separate an accepted pitch from a declined one here.