Contribute

Write for us

EveryAny.One publishes contributed writing on SaaS and software from people who have built, sold, bought or operated it. We accept full articles and shorter expert contributions - a quote, a benchmark, a screenshot with a lesson attached - anything a working operator, founder or engineer can bring that a reader will not find on a vendor's own page.

What we publish

Four kinds of contribution work here, and they are all about the same thing: telling a reader something they cannot get from a vendor's own website. The first three are full articles; the last is a shorter expert contribution we can weave into a piece we are already writing.

  1. Operator writing. What actually happened when you priced a product, migrated a stack, ran an experiment or made a purchase you regret.
  2. Original data. A benchmark, a survey, a teardown, a study of your own numbers. Anything where you are the source rather than a summariser.
  3. A specific argument. A clear position on how something in software works, defended properly, including the cases where it does not hold.
  4. Expert insights and quotes. A 100-300 word contribution from someone with direct experience of the topic - a founder, engineer, ops lead or long-time buyer - with a checkable byline and a concrete point. We publish these attributed and linked back to your site.

Topics we cover

If your subject sits in one of these areas, we are interested. If it sits next to them and you think we are missing something, say so in the pitch.

SaaS business and strategy

  • SaaS metrics (MRR, ARR, churn, NDR, CAC payback)
  • Pricing and packaging models
  • Product-led growth and freemium economics
  • Retention, onboarding and activation
  • Bootstrapped and indie SaaS

Software categories and tooling

  • AI tools and AI-assisted workflows
  • SEO and content tooling
  • Marketing automation and email
  • CRM, sales engagement and revenue operations
  • Design, prototyping and design systems
  • Developer platforms, hosting and deployment
  • Productivity, docs and internal knowledge

Buying and operating software

  • Software procurement and vendor evaluation
  • SaaS spend management and stack consolidation
  • Migration and switching costs
  • Security, privacy and data residency in SaaS
  • Integrations, APIs and automation

Technology and the market

  • How AI search is changing software discovery
  • Startup and technology company analysis
  • Founder interviews and operator lessons
  • Original research and benchmark studies

Editorial standards

The same rules that govern our own writing apply to contributed work, and they are not negotiable:

  • Every factual claim is checkable, and prices carry the date they were checked.
  • Sources are linked. Statistics without a source are cut.
  • Articles state who something is not for, not only who it is for.
  • No undisclosed commercial relationship between the writer and a product covered.
  • We edit for concision, structure and house style, and we send edits back to you.

Get in touch

Send us the topic and a link to something you have written or your professional profile, through the form below or by email to [email protected]. We reply to contributors we intend to work with and take the conversation from there.

We store your pitch to reply to it and to keep a record of what was proposed. Nothing else. Ask us to delete it at any time.

Frequently asked questions

Do you accept guest posts and expert contributions on SaaS and software?

Yes, from people with direct operating experience in SaaS, software or technology. We accept both full contributed articles and shorter expert contributions - a quote, a benchmark, an operator lesson - that we can weave into a piece we are already writing.

How long should an article be?

As long as the argument needs and no longer. A 1,000-word piece carrying twenty verifiable facts is more useful than 3,000 words of general commentary. We edit for concision.

Can I include links to my own product?

You can reference your own product where it is genuinely relevant to the point being made, and your byline links to you. Articles written primarily to place a link are not published.

Do you accept AI-generated drafts?

Use whatever tools you like to draft, but you are responsible for every fact in the piece. We check claims, and anything unverifiable is cut. Articles that read as unedited model output are declined.

Who owns the article after publication?

You keep ownership of your work. We ask for the right to publish it on EveryAny.One and to keep it online, and we ask that it is not republished elsewhere in identical form.