Overview

Last updated:

|Edit this page

The Content & Docs team has two core goals:

  1. Increase awareness of PostHog, especially among people in our ideal customer profile
  2. Help developers and PostHog users be more successful through great content and docs

We do this by:

  • Building a reputation for world-class content
  • Constantly working to improve our documentation
  • Identifying where content can help users be more successful
  • Holding a high bar for quality in everything we do
  • Never being satisfied with how high that bar is
  • Being weird, opinionated, and unafraid of being wrong
  • Reacting quickly to opportunities whenever they arise
  • Not being precious about our work and priorities
  • Having a team of talented, technically literate writers (and Andy)
  • Not relying on freelancers or guest contributors for content
  • Avoiding tedious enterprise marketing nonsense (PDFs, gated content, webinars, etc.)

The latest goals for marketing can be found on the Content & Docs team page.

Content is the main pillar of our marketing strategy. Our strategy is to go deeper and create better content as we grow. We don't rely on AI. We don't take content in exchange for links. We don't have arbitrary volume goals.

Who is our audience?

  • Founders: Technical and non-technical founders seeking advice on how to run a successful startup. We share what we've learned and curate the best startup advice in our founders hub.

  • Product engineers: Software engineers who want to improve their product skills, understand users, and build successful new products. We share what we've learned and curate useful advice in the product engineers hub.

  • PostHog users: Existing PostHog users who want to develop their skills and learn how to get the most out of PostHog.

  • B2B SaaS companies: Our ideal customers are B2B SaaS companies who need reliable user data and a simplified data stack. Most of our output is tailored toward B2B use cases.

What kind of content do we produce?

  1. Opinionated advice – Articles where we offer a strong point of view on a topic that impacts our audience. Examples include The Product-Market Fit Game, Burning money on paid ads for a dev tool, and How to design your company for speed

  2. High intent SEO comparisons – Articles for people actively considering PostHog, or searching for a product like ours. Examples include comparisons between PostHog and competing products, guides on the best alternatives to popular tools, and guides to most popular tools in our segments.

  3. Helpful evergreen guides: Articles on topics of interest to our users and potential users. They generally target popular search terms. Examples include How to measure product-market fit, The AARRR pirate funnel explained, and 8 annoying A/B testing mistakes every engineer should know.

  4. Engineering tutorials: – Guides on how to do specific things in PostHog. These can be for existing PostHog users, or aimed at potential users who are trying to solve a specific problem. Some, like How to set up Python A/B testing are SEO focused. Others focus on specific PostHog user pain points.

  5. Newsletters: – Our newsletter, Product for Engineers, is both a distribution channel and its own content category. Issues often curate or summarize our existing content, or that of others, into an easy-to-digest, snackable format.

Content distribution

So you've written a great piece of content. Now what? Here are various ways to spread the word:

1. LinkedIn

Share a post using either your own account or the company account, but note that the company account will have dramatically less reach than your personal one. To post using the company account, use Buffer (ask

to add you to it if you don't have access).

Tips for writing a good post:

  • Don't just share the link. Write out an intriguing summary or introduction of the post. Here's a good example.
  • Keep the link in the main post, and don't do that annoying thing of saying "link is in the comments".
  • Attach a compelling image to the post. Example.
    • You can create nice images when clicking Add entry in the changelog. It's under the Social sharing header.

2. Twitter / X

Again, use Buffer to post from the company account.

Tips for writing a good post:

  • Write a brief summary of the post while sharing as much content as possible in it. Good example.
  • Attach an image to the post (don't rely on the link's social graph preview). Again, you can use Add entry in the changelog to create a nice image.
  • Do your best not to sound "corporate" or serious. Authenticity is appreciated on Twitter. Have fun with it!

3. Paid ads + newsletters

You can promote your post by buying sponsored slots in newsletters. Ian Vanagas has a list of newsletters and booked slots we can use to promote content. See sponsorships for more.

If you want to run a paid ad campaign on Reddit, Google, or Twitter, see the paid ads page.

It's a good idea to create an issue highlighting what you'd like to achieve in your campaign. Here's an example

Questions?

Was this page useful?

Next article

Docs ownership

Product teams are responsible for ensuring their docs are up-to-date. This means: Documenting new features when they're launched Correcting mistakes reported by users Clarifying documentation where needed based on support tickets Ensuring public betas have documentation which is linked to from feature preview menu Content & Docs is responsible for improving the docs. This means: Reviewing and improving draft documentation created by product teams Identifying and improving low quality…

Read next article