Developer marketing examples

Simple and powerful messaging.

They say what they do. Zero fluff.

They make it easy for devs by explaining how they are different than (obvious) competitors.

They add a little developer-focused social proof.

Nicely done Reddit post that went viral on r/MachineLearning.

Reddit dev communities are notoriously hard to market in.

You need to have something really valuable to say to that dev crowd.

But even if you do, it is so easy to screw it up and get trolled or downvoted for "obvious promo".

I know that from experience. So painful to watch.

This is a really nice example of how to do it right:

• Start with an interesting, attention-grabbing but not yet a clickbaity title.
• Say who you are and why you have something (new) and valuable to say here.
• Go straight to the point, to the (technical) value. I like the obvious numbered list delivery.
• Drop emojis, bolding, and extensive formatting if you want to "keep it real".
• Make sentences short. Cut all the fluff. State your opinions and facts "as they are".
• Do implicit CTA. Drop the explicit one but hint at something that those interested may want.

Try something like that next time you post and see what happens.

Obviously, it is nearly impossible to do when:

• You have no real experience to share
• You have nothing really valuable to say
• You don't have opinions and/or facts on the subject

But then why would you even post something?

What to put in the header when your dev tool does a lot?

I like how Appsmith approaches it.

In their case, they have multiple use cases they want to showcase.

But you could use the same idea for many features or products.

Show multiple clickable tabs:

• It invites the user to click and see.
• It hints at all of those different use cases
• It doesn't overwhelm your audience with too much info

A bonus idea is the "Try cloud" | "Self-hosted" CTA.

It communicates right away that you can deploy that dev tool anywhere.

If the self-hosted deployment is important to your customers let them know.

You don't want them to look for it and drop from the page trying to find the FAQ.

This is how you write dev tool JTBD blog posts.

Masterclass of writing this type of content from @WorkOS imho.

Deep 2000 word guide that explains how to add webhooks the your application.

Goes into examples, best practices, everything.

One thing it doesn't do?

It doesn't push the product left right and center.

In fact, the only CTA is hidden in the very last sentence of the very last section.

Why?

Because most likely, the reader's intent is around understanding the problem at this point.

They want to understand what adding webhooks to their app really means from the practitioner's standpoint.

And they did that beautifully.

Could you have pushed the product a bit more? Sure.

But by answering the actual questions devs came here for they managed to build trust.

And I am sure got their fair share of click-throughs and signups anyway.

I love the design of this crossover section on the Tailwind homepage.

I see the code and the result next to each other.

I see how I can get that result with code.

It is interactive and catches my attention.

It makes me feel inspired.

Great job Tailwind team!

Nice and clean code example.

Clear copy, what it does etc.

Calls to action with links to Github and website.

Really long code example which looks great when clicked on.

With/without is a classic marketing campaign theme.

AhoyConnect does it nicely in this ad.

Obviously, not everyone loves memes.

But many devs do.

Those who do may smirk -> smirk builds brand affinity.

Most dev tools have two deployment options:

• SaaS
• On-prem / private cloud

And then companies present it on their pricing page with some flavor of two tabs.

And you need to name them somehow. 

And how you describe those things sometimes adds confusion for your buyers:

• You put “your server” > then does it scale to a more robust infra?
• You put “on-prem" > then can I deploy on private AWS cloud?

I like how nice and simple solution Retool used on their pricing page:

• "Cloud (we host)"
• "Self-hosted (you host)"

Explicit, obvious and to the point.

Love it.

Interactive product tours are all the rage.

But how do you make them work for the dev audience?

How do you deal with:

• Explain your complex dev tool value proposition quickly
• Show both code and UI elements
• Make devs feel great developer experience of your product
• Push devs to the conversion action without being to pushy
• And do all that without overwhelming

That is hard.

But Vercel somehow made it.

This is by far the best product tour I have seen so far.

What I love:

• Great, clean navigation that lets me go back if I want to
• They use their slogan "Develop, Preview, Ship" to reinforce the product message
• They show both code and the UI
• The CTAs are visible but subtle enough not to distract

This product tour is what dev tool startups will aspire to for years (or months ;) ) to come.

Mark my words.

Is this brand campaign 💩 or ❤️?

I like it a lot actually.

It gets attention, it is memorable, it gets reactions.  

And It does speak to a product message: that you have better developer experience than other tools.

It definitely beats flavors of "5x developer productivity".

How to do a dev-focused brand video and get 10M+ views?

Making a memorable brand video is hard.

Doing that for a boring tech product is harder.

Doing that to the developer audience is next level.

Postman managed to create not one but three of those brand videos that got from 4M to 10M youtube views.

The videos I am talking about are:

• "I am gonna push some buttons"
• "Together"
• "We did this"

So what did they do right?

• They are all short playful stories touching on values coming from a centralized API platform.
• They hint at the motif of space which is a clear part of Postman's branding
• They do show the actual UI of the product

Honestly, I am not exactly sure what special sauce they added but those are just great videos that you watch.

And I definitely remember them and the company which is exactly what you want to achieve with brand ads.

How to do a dev-focused brand video and get 10M+ views?

Making a memorable brand video is hard.

Doing that for a boring tech product is harder.

Doing that to the developer audience is next level.

Postman managed to create not one but three of those brand videos that got from 4M to 10M youtube views.

The videos I am talking about are:

• "I am gonna push some buttons"
• "Together"
• "We did this"

So what did they do right?

• They are all short playful stories touching on values coming from a centralized API platform.
• They hint at the motif of space which is a clear part of Postman's branding
• They do show the actual UI of the product

Honestly, I am not exactly sure what special sauce they added but those are just great videos that you watch.

And I definitely remember them and the company which is exactly what you want to achieve with brand ads.

One of the top-performing conversion flows in dev-focused articles.

"Aside CTA" in the "How to do {jobs to be done}" article.

You know the drill:

• Explain how to X without your tool
• Add an "Aside" CTA showing that it can be done with your tool

And Export SDK executes it (almost) perfectly:

• They subtly move you from article to CTA but show that the article ended
• They explain what the tool does and what the offer is
• They show a visual of how the tool solves it
• And they give you a clear link to click

One thing that could be tested and changed is putting this "Aside CTA" mid-article and not at the end (tip from Martin Gontovnikas).

A good thing to try if you are running the "How to do {jbtd}" article strategy.

𝗔𝘁𝘁𝗿𝗮𝗰𝘁𝗶𝘃𝗲 𝗮𝗱 𝗰𝗿𝗲𝗮𝘁𝗶𝘃𝗲 𝗳𝗼𝗿 𝗮𝗻 𝗶𝗻𝗳𝗿𝗮 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝘁𝗵𝗮𝘁 𝗿𝘂𝗻𝘀 𝗶𝗻 𝗮 𝘁𝗲𝗿𝗺𝗶𝗻𝗮𝗹?

Hard, but Run.ai did that.

Infra products are not "obviously cool".

There is no shiny UI, no happy people wearing your sneakers,

So what do you show on your ads?

First off, the rules still apply:

• Catch your audience's attention
• Say what you do in their language
• Better yet, show how it actually does it

And Run.ai ai and MLOps infra tool managed to create a beautiful Linkedin ad IMHO:

• They catch attention with the code visual
• They say what they do quickly with "Dynamic Fractional GPU using One Command"
• They extend on that in the post copy with an action-driven "Open Terminal -> Run Command -> Boom"
• The code shows what it feels like to use the tool
• And it shows you the result -> fractional GPUs

Job well done!

7k likes on an event promo post to the dev audience.

I don't think I've ever seen 7k likes on a developer company post on Linkedin.

Ok, this is Github, but still.

This is a 26sec video where they go:

• "What happens when a CEO..."
• "... builds an app LIVE in 18 minutes ..."
• "... in front of 15000 people..."
• "... with Copilot X for the first time?"
• "What could go wrong?"
• "What it Live"

This is a job well done:

• Super slick but minimal design. Feels a bit like that famous nextjs prisma conference tickets.
• Offers a live coding session which is one of the event types that devs like cause it is real.
• Plays powerful music, but no voiceover that would make it feel more corporate.
• Dev to dev, conversational copy. + this final snarkiness appeals to devs.

And they could have done:

• Copy: "We are happy to announce our CEO streamlining business value for the enterprise"
• Design: Show people at previous events and stuff that you saw a million times
• Offer: Talks from industry leaders (that  are customers using your product)
• Voiceover and music: Boring corporate classic.

This is how to promote an event. LOVED IT!

Newsjacking is a great marketing tactic.
Especially when you can connect it nicely to your product.
‍

And GitGuardian, a tool for secrets management does it beautifully here.
They ran a story on how Toyota suffered from a data breach.
Because they didn't manage their GitHub secrets properly.
‍

Brilliant.

How do you show "save time" to devs?

It is often hard as it is not objective.

But there are options.

Spotlight does it beautifully by showing two implementations next to each other solving the same task.
It is obvious which is faster and saves time.
Great stuff!

I love this dev tool header copy from Neon.

❌ They could have gone with "We make your data fly" or "10x your database developer efficiency" or other stuff like that.

💚 Instead, they spoke in a clear dev-to-dev language:

• What it is: "fully managed serverless Postgress"
• Benefit in technical terms: "Autoscaling, branching, bottomless storage"
• How they do it: "Separate storage and compute"
• Obstacle handling for current Postgres users: "generous free tier"

Simple, clear, and to the point. No fluffs given. Love that.

"But we are selling to the boss of a boss of that developer user persona"

Then let that dev champion understand what you are doing and bring it to their boss.

"But we are going pure top-down"

Then does that boss of a boss of a boss actually evaluate your infra tool themselves or send their architect?

Maybe 90% of your site traffic is the buyer-persona CTO. But my bet is, it isn't even 1%.  

Hacker News developer audience doesn't love promotion to put it mildly.

But some dev tool companies manage to make this audience their biggest ally.

Fly.io is one of those companies.

And they had a super successful product launch a few years back.  

So how did they do it?

• "Who"
• "Problem"
• "What" and "How"
• *Speak "dev to dev". Spec no fluff.

Let's go through these in detail.

Who are you? Why should I listen?

• show your face
• Say who are you and
• hint at why should I trust you

What is the problem really?

• Describe how you discovered the problem
• Agitate that pain, explain technicalities deeply
• Share your stories dealing with that problem (ideally obvious solutions that didn't work)

What does your product do and how does it work?

• Say what it is, like a technical spec.
• Say what it does, like really, low-level job to be done
• Explain how you solve it, be deeply technical

Speak "dev to dev"

• use technical jargon and relevant terms: "docker image", "global router", "VMs", "root filesystem"
• don't explain like I am 5, explain like I am 5 years in my dev journey "we convert docker images into a root filesystem, boot tiny VMs..."
• Don't use words that don't really mean anything and just take space. Speak MECE (mutually exclusive, collectively exhaustive)

By doing it this way you have a chance of gaining love from the prolific HN crowd.

Fly.io definitely did, and is still reaping rewards with constant HN exposure.

OK, the best way of getting GitHub stars is by creating a project that solves real developer problems well.

I assume you have done that already and the metric that people love to hate ⭐ is growing organically.

What do you do now?

I mean you got to ask people in one way or another.

Many companies put it in their navbars or hello bars.

Posthog adds a sticky banner at the bottom of the page that follows you as you scroll.

It also shows a start count which at their size (11k + stars) acts as social proof.

You can close it and the next time you visit the page it will be off not to push too much.

I like the concept makes sense to test it out this way imho.

How to do a dev-focused brand video and get 10M+ views?

Making a memorable brand video is hard.

Doing that for a boring tech product is harder.

Doing that to the developer audience is next level.

Postman managed to create not one but three of those brand videos that got from 4M to 10M youtube views.

The videos I am talking about are:

• "I am gonna push some buttons"
• "Together"
• "We did this"

So what did they do right?

• They are all short playful stories touching on values coming from a centralized API platform.
• They hint at the motif of space which is a clear part of Postman's branding
• They do show the actual UI of the product

Honestly, I am not exactly sure what special sauce they added but those are just great videos that you watch.

And I definitely remember them and the company which is exactly what you want to achieve with brand ads.

Showing code and UI in an explainer video is always a dance and rarely ends well.

You want to show the code to make it devy.
But you don't want to show everything not to overwhelm.

The same goes for UI which should look like your UI.
But show only what is necessary.

It's a struggle but CircleCI does it really nicely in this explainer:

• They blur out all code
• But use colors to make it really look like code
• And the file sits clearly in a text editor (as it should)

They do the same for the UI later in the video.Just a really clean way of explaining things. Nice!

Devs have a love/hate relationship with "Book a demo" call to action.

Mostly hate though.

Especially if what they want is:

• know what they will be paying for your tool
• just see a golden path of how this thing works

Let's just say that sitting through an hour demo call with a salesperson just to get the pricing is not what most devs love to do with their time.

But there are moments in the buyer journey when devs do want to have that live session:

• they tried it, went through the golden path, and have deeper questions
• they know they have specific needs and are unsure/couldn't find it in your docs/website.
• they want to customize the pricing plan to their needs.

Then, having a live session/demo is the fastest way to move forward.

@PostHog handles this dev journey reality nicely with:

• recorded, ungated product demo -> if you want a generic demo just watch it
• transparent pricing and a free plan -> don't need to sit through the demo to ask for price
• if you want a custom demo or just talk to a human -> just schedule a call

This approach solves both scenarios really nicely.  

Pre-roll ads are obviously invasive and annoying, especially to devs. But they are also prime real estate in the ad ecosystem.

You can choose not to do them at all (fair option). Or try and make them more fun and less annoying ;)

I like how Sentry handled it in this 16-second video:

• They start with a funny, disarming hook. A pic of a cat pic ;). It catches my attention and stops me from clicking "skip ad" as I want to understand what it is about.
• They show how those pics didn't come off well and introduce the company saying "Sentry can't fix that". That keeps me interested enough to see what it does.
• They show a straightforward, short product video with the actual application screenshots and zoom-ins to show pieces of the product for the rest of the video.

Basically they managed to "buy" 11 seconds of attention with 5 seconds of a pattern-breaking hook.  In the world of pre-roll YouTube dev-focused ads, I'd say this is a win.

Also, I don't know the results of the "Sentry can't fix that " campaign, but I like how this builds curiosity. Even with that slogan alone.

Why not highlight your free plan?

Most companies highlight their middle paid plan saying it is "most popular".

First thing, yeah, sure it is your most popular plan.

But more importantly, most visitors will not convert to your paid plans right away.

So why not try and capture as many devs as possible on the free plan?

If they like your dev tool there are many things you can do to convert some of them to paid plans.

But if they leave that pricing page and go with some other free tool, you are not converting anyone.

@CircleCI highlights free and they are in the mature, competitive market of CI CD tools.

Idk, it really does make a lot of sense to me.

If people need more advanced features they will choose higher plans anyway.

But if they want to get things started with the basic plans they will choose free or go elsewhere.

I'd rather have them choose free than none.  

This is a simple but great header imho:

• they explain what it is clearly: Stock trading API
• they show the result: trading stocks
• they show the code to drive the "it is for devs" point

Love it.

Very cool project.

You type in your GitHub name and see your history in 3d.

• engaging 3d viz
• cool music
• button to share it on Twitter

And Voila!

You have an intrinsically viral brand awareness campaign.

Just brilliant.

That CTA.

You go straight for the install/download.

I don't know if you can go more developer-focused than that.

It sets the tone for the entire homepage.

And let's be honest (almost) nobody actually clicks that "Sign up" button in the hero section.

Came across this classic What is Segment brand video while watching an interview with one of the folks behind it, Maya Spivak (she is awesome btw).

What I like about it is that:

• it is fun, not formal, builds rapport
• it introduces the core problem the tool solves
• it shows the tech and explains it in a way that is simple but not simplistic

And it follows a flavor of the classic AIDA format:

• Introduce problem
• Agitate it, make the viewer feel it
• Explain obvious solutions + problems with it
• Show how your product solves it
• Tell people how to start

Putting all that in 90 seconds is hard.

And even though this video is 4 years old it could easily still work today IMHO.

Really solid baseline to s̶t̶e̶a̶l̶ get inspired by ;)

This body cross-section is just awesome.

It makes it obvious that I can connect it to my workflow.

This is a must for dev-focused pages imho.

What I like:

- there are many integrations listed

- I can see the code and that it is easy to use

- The CTA is to integration docs, awesome!

‍

Devs are builders.‍

Make your home page for builders.
Go directly into the "how" instead of the way.
Many devs when they land on your home page, already know the "why".

I love that it:

• shows the step-by-step right away in the hero
• CTAs are links to integrations with particular frameworks and libraries
• the hero copy is very toned-down

Scrolling through many feature/capability sections of a dev tool website mostly sucks. But dropping things to make it shorter can suck even more.

This is a cool design pattern that deals with that problem.  

Single section that switches subsections on scroll. And folks over at @Graphite did a great job with that on their homepage.

It works like this:

• as you scroll the progress bar moves to make it clear what is happening right away
• eventually, as you scroll down, the subsection switches to the next one
• each subsections has a headline + one-liner description + call to action + a visual

Also, I saw variants of this that also looked great:

• without the one-liner or Learn more
• auto progress/section switch if you don't act

What this design helps you achieve is:‍

• you get to show many features/capabilities (Graphite showed 5)
• the site feels shorter than it is and you don't feel as tired/lost as you scroll
• because it is all interactive it is easier to drive your attention to a section header

I really like this pattern and I have already recommended it to some folks working on their sites recently.

This is a solid swag copy template that resonates with devs.

"I did X and all I got was this lousy Y"

Why this works imho is:

• it is snarky
• it is a little self-deprecating
• it brags a bit about the work/expertise

Very solid start if you run out of ideas.

Which feature/product to show in the header?

How about all?

Many dev tool products are feature-rich. And you want to show those awesome features.

But it is easy to overwhelm the reader when showing so much info.

That is why I really like the header tabs pattern that @PostHog uses:

• You have clickable tabs with product names + descriptive icons
• Copy + Supporting visual (UI, code etc) and a call to action in each tab
• Supporting visuals are in vastly different colors to make it obvious you switch tabs.

This pattern is especially powerful when you want to communicate completeness.

Posthog definitely wants to do that. If you are on that train I'd strongly suggest considering/testing it.

Marketing through free tools is powerful. And Auth0 implemented it beautifully.

In an old article from Gonto I read about some free tools that Auth0 created years ago.

And those tools are still generating traffic and leads today.

And they are helpful to developers and make the Auht0 brand even more appreciated by the community.

One of those tools is JSON Web Token Debugger.

So how this works for them is this:

• You understand that your target dev audience has a problem
• You realize that helpful blog posts can only do so much
• You create a small tool that helps solve that problem
• You create content that explain the concept to help build SEO
• You link out to that content on the home
• You add links to your core product/events or other offers in the navbar
• You wait for devs to come ;)

Now, Gonto suggested that is important to do it on a separate domain to make it less promotional.

I am not sold on that especially when I know there are companies like @VEED.IO that build "SEO tool clusters" in the /tools/ subfolder of their page and crush it in search.

But either way, if you can solve a real problem your target devs have, no matter how small, you should be able to get some developer love (and $) from the value you created.

Classic Auth0 campaign coming back in 2023.

I love how simple and powerful this message is.

You can outsource a dull but important problem of authentications to them.

That is all the say.

But it is enough to get you interested and understand what they do.

Not sure how to find developers for audience research interviews?

Sometimes all you need is ask.

I really liked what the founders of this startup did:

• Found relevant subreddits where folks working in MLOps/DevOps and ML are (for example r/mlops)
• Clearly explained why they wanted it: building a startup and doing exploratory analysis
• Clearly explained what they wanted: interviews with mlops/devop/data scientists
• Clearly explained what they will give for it: cash, as simple as that

Sometimes you don't need to overthink it and can just ask.

Mux does a few things beautifully in this header.

Value proposition:

• The "what" is explained right away: "Video API", "live and on-demand experiences"
• Super clear on persona "developers" and job to be done "build online video"

Animated visual that is really good for dev tools:

• that have an API/SDK
• that have a UI where the results of that API calls go

Say what we are all thinking. ‍

This tweet is great as it states something that most of us feel.
It is something that you may have had a discussion about with someone recently.
You might have fought about one tool or another.
But at the end of the day tools don't matter.

You can share it with someone as:

• sorry, we had a stupid fight
• rub it in your face :)

‍

Gonto shared an interesting play that they tried at Auth0 when he was running growth there.

So the story goes like this:

• They wanted to increase brand awareness of Auth0.
• They found influencers who were maintainers of open-source frameworks that had landing pages.
• They went to them and offered to redesign these landing pages for free.
• The trick is they redesigned it in the same branding (colors, patterns, layout) as the product (Auth0).
• That made people think those are related (even though they weren't) which increased the brand perception of Auth0.
• They also asked the influencers/maintainers if they could add retargeting pixel to the redesigned site.
• Which helped them serve relevant ads to visitors of those open-source frameworks.

I think that doing just the sponsorship for the retargeting pixel could work.

But when you add that branding consistency between the sponsored site and the product the CTR is better.

Interesting one for sure.

How to show integrations on your dev tool homepage?

Every dev tool needs to integrate with other libraries in the space.

And you want to show how well integrated with the ecosystem you are.

But you ctually want to do a bit more than that.

You want devs to see how easy / flexible / clean it would be for them to use it.

That is why instead of showing just logos from your ecosystem it is good to show the code too.

Meilisearch does that beautifully:

• They show a big list of integrations that show the breadth
• For each, there is a code snippet on a relatable example
• + call to action to all integrations and selected one

I am sure this is getting more clicks than just a list of logos.

How to run developer-focused Reddit ads that get upvoted?

Reddit is well known for anti-promotional sentiments.

Just post something along the lines "you can solve that with our dev tool" and see.

So running ads on Reddit feels even more like a no-no.

Especially if you add problems with bot clicks and attribution as most devs will have some sort of blocks.

But you know your audience is on Reddit.

And for some of us, it may very well be the only social platform they are on.

So what do you do?

This is how @Featureform approached it to get almost 100 upvotes on an ad:

• They start with a simple conversational copy pointing at their target users pains
• They agitate target users pains in their language (lots of jargony terms, tools and problems)
• They use very devy language, likely rooted in deep user understanding (voice of customer)
• They don't talk about their product in the meme
• They show clear branding so that you can connect the dots.

If you are going for brand awareness rather than a direct conversion those types of ads can work very well.

I liked it for sure.

Funny and memorable competitive billboard ad from @Statsig 👇

You have a big incumbent, everyone knows them. Use it to anchor your brand.

And tell the story of how you do things differently.

👀 But first, make people see you. And remember you in the next conversation when the big known brand or a category comes up.

And being funny is one of the best ways of getting attention and being remembered.

💚 I love how folks from Statsig did it here. Such a playful pun on the feature flag category incumbent Launch Darkly. Job well done.

Btw, this was shared by Oleksii Klochai in the Developer Marketing Community (you joined yet?).

Fantastic all-text Reddit ad from Latitude.

Dev ads are hard. Promotion on Reddit is harder.  Running a dev ad on Reddit that gets 50 comments and 90 likes is expert-level hard.

But folks from Latitude managed 🔥

They used one of my favorite Reddit ad formats: all text.

Here is what I liked:

• They start with who you are and what your product is. I love that they put it right in the title. Having open-source in the title helps too, it just makes you more trustworthy by default.
• They introduce themselves as a technical founder. Makes it more likely to get comments as you are technical, you are a founder, you are a human (not a brand) so you will answer questions.
• They apologize for the ad. Acknowledging that this is an ad makes people less combative.
• They explain technically what it is. Use technical terms. It's very dev to dev.
• They give  devs an easy way to try it. And they chose Github, not their website. That is great. It makes it even more developer-centric. More trustworthy.
• They ask for feedback and contributions.  Not signups. And the more feedback they get (as comments) the more visible and trustworthy the ad will get.

Great execution. Chapeau bas Latitude.

Mixpanel primary CTA is to take an interactive tour.

They take you to a 30min video + a guided UI tour.

Not a signup.

That is because with products that have long time to value (like analytics, observability etc) dev will not see value in the first session.

I mean to really see value you need to see real data, real use cases. And if you were to actually test it would take weeks.

That is why many companies do demos. But demos have their own problems (and most are bad).

Interactive tools make it possible for me to explore the value without talking to anyone.

I love this option.

I like how this starts with a [WHAT IT IS ABOUT] scroll stopper.

That is coupled with a big block of code that has:

• input -> code
• output - > results from console

(presumably) when you click "See more" you get the rest of the text post.

Awesome sponsorship ad from Trieve in the Cassidy Williams newsletter.

Not sure who wrote it but it must have been a dev ;) It is just so refreshingly to the point.

💚 What I like:

• "What is it": A product description gives you no fluff "what it is". Feels like something from "Hacker News launch"  almost.

• "What it compares to" | "Why should I care" : They compare vs a well-known dev tool in the space. And this is great, helps the dev anchor with something they know. Helps them understand why this could be valuable. They even give you a life app where you can see for yourself.
• "How can I test it for myself": They offer free credits to play with in a cloud version.

This ad does it so gracefully and quickly it is just hard not to love.  

This is a sandbox experience folks over at Sentry.io created.

I like the navbar CTAs with a big "Documentation" button in there.

Reminds me that I can go and see it when I need it.

But I also get those conversion focused "Request a demo" and "Start a trial" for when I am ready.

On top of that I get tours and help in the sidebar for when I get stuck.

.... and the whole thing is gated behind a work email which I don't love.

But having that work email let's you nurture (and Sentry is known for awesome emails).

Plus it does help sales. If anything it is an additional signal for your account scoring models.

But if you are going to gate a sandbox, make sure to show all that value behind the modal like Sentry did.

With that I can feel compelled to type in that email.

When you promote your feature/product launch on Reddit, it can easily end up being "not well received" to put it mildly.

I am talking downvotes, negative comments that get upvoted  and break the discussion. Or good old crickets.

But Reddit can also be a fantastic source of audience feedback, peer validation for your product, and some of the most vocal advocates you'll ever find.

I really liked how Tom Redman from Convex directed the discussion in the Reddit thread under their laucn post:

• Transparent intro: who you are, what you know

• What you like about the tech: why you think it is valuable to the community

• Community-focused call to action: helpful, feedback-first (not conversion-first), disarming with "if I can't answer I'll ask"

The launch post itself was great too:

"Open sourcing 200k lines of Convex, a "reactive" database built from scratch in Rust" that linked to the GitHub repo.

Doesn't get much more to the point and devy than that.

Very nice design solution on the homepage.

Classic communication of the world before using your tool and the world after.

Really liked how it felt messy before.

And is nice and clean after.

Beautiful mockery of classic conversion tactics from PostHog website.

So what do we have here:

• "3 people would have..."
• "Not endorsed by Kim K"
• "Eco-Friendly"
• "$0 FREE"
• ">1 left at this price"
• "Act now and get $0 off your first order"

I have to admit I chuckled ;)

And I bet many devs who don't think of marketing very highly chucked too.

That builds rapport. (hopefully) makes you one of the tribe rather than another faceless corpo.

BTW, they used it as a bottom of the homepage call to action.

I like it.

Most of the people who scrolled there are not going to buy anyway.

But they may share the website with someone who will.

The problem with presenting API is that it is hidden. It gets the job done in the background.

So it is not "attractive" in the way some other dev tools can be.

But you can:

• show the end result and how it gets the job done.
• show how easy it is to use.
• let people play with something interactive to make it real.

That is how Mux, video API, solves it.

Found this awesome crossover on their homepage.

They give you:

• devvy language that just says what it does without high-level fluff
• code, input/outputs
• end result of your API call, to make it real
• demo to get the feel real-time

Love it!

How to write a "What is {MY CORE KEYWORD}" article that gets to the top of HackerNews? 👇

First of all, almost no one succeeds at that as you write those articles for SEO distribution, not HN distribution.

To get an SEO-first article on HN your content quality bar needs to be super high.

But you can do it.

PlanetScale managed to get their "What is database sharding and how does it work?" on the orange page (kudos to Justin Gage!).

Here is what was interesting about that article:

𝗦𝘂𝗽𝗲𝗿 𝘁𝗼 𝘁𝗵𝗲 𝗽𝗼𝗶𝗻𝘁 𝗶𝗻𝘁𝗿𝗼.

• ❌ No "In today's fast-paced data-driven world enterprises work with data" stuff.
• ✅ Just  "Learn what database sharding is, how sharding works, and some common sharding frameworks and tools."

𝗛𝗶𝘁𝘁𝗶𝗻𝗴 𝗸𝗲𝘆𝘄𝗼𝗿𝗱𝘀 𝘄𝗵𝗶𝗹𝗲 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗿𝗮𝗽𝗽𝗼𝗿𝘁 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗱𝗲𝘃 𝗿𝗲𝗮𝗱𝗲𝗿.

💚 Speaking peer to peer, not authority-student:

• "You’ve probably seen this table before, about how scaling out helps you take this users table, all stored on a single server:"
• "And turn it into this users table, stored across 2 (or 1,000) servers:"
• "But that’s only one type of sharding (row level, or horizontal). "

𝗨𝘀𝗶𝗻𝗴 𝗷𝗮𝗿𝗴𝗼𝗻 𝗮𝗻𝗱 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝗮𝘂𝗱𝗶𝗲𝗻𝗰𝗲

Things like:

• "Partitioning has existed – especially in OLAP setups"
• "Sifting through HDFS partitions to find the missing snapshot "

𝗔𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗲𝘅𝗽𝗹𝗮𝗶𝗻𝗶𝗻𝗴 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹𝗹𝘆 𝗵𝗼𝘄 𝘁𝗵𝗶𝗻𝗴𝘀 𝘄𝗼𝗿𝗸

🔥 Look at the section "How database sharding works under the hood" with subsections:

• Sharding schemes and algorithms
• Deciding on what servers to use
• Routing your sharded queries to the right databases
• Planning and executing your migration to a sharded solution

🎁 𝗕𝗼𝗻𝘂𝘀: 𝗽𝗹𝘂𝗴 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝗴𝗲𝗻𝘁𝗹𝘆

Section "Sharding frameworks and tools" shares open-source tools (every dev, but HN devs in particular like OS projects).

And there as an info box, you have the info that Planetscale comes with one of those OS projects deployed.

Just a beautifully executed piece of content marketing.

Looking for a good dev-focused case study format?

People tell you to follow a classic Hero > Problem > Solution > Results.

They tell you to show numbers, talk value, etc.

And it is true. Great format.

But packaging this for devs is hard.

For example, putting numbers in there, and framing it in a "save 28min every week" is a recipe for losing trust with that dev reader.

That is if you can even get those numbers from your customers.

I like how @LaunchDarkly solves it.

Hero section:

• Change that customer saw (no numbers needed)
• Additional description of the use case (this seems to be optional for them)
• Before and After boxes with bullets (no numbers needed)
• Clear customer logo

Case study body:

• About: one paragraph about the company and use case
• Challenge: why they started looking for a solution
• Solution: why they chose their product
• Results: what they got from it
• They kept it short and focused on the team leader imho

They keep the content down to earth and devy but still frame it in a value-focused way.

I like that that they speak in the currency that devs care about.

Wasted time.

Before: "Took 2-3 weeks to ship"

After: "Can ship experiments every day"

The cool thing is you could actually use this  hero section format and then have a more technical user story below. By doing that you could speak to the why and how.

That depends on your target reader for this page of course.

Anyhow, I do like this format and I am planning to take it for a spin.

13% signup form conversion bump with a dev-focused trust/motivation builder.

Dev goes through your page, clicks the signup button, and sees a signup form. Now you want them to actually sign up.

The V1 approach is to go clean, a few social signup buttons like GitHub and call it a day.

The V2 is to add trust/motivation builders on the page:

• Logos -> big enterprises and hot startups using your product always feel reassuring
• Testimonial -> fellow dev talking about the product makes your claims real
• Value prop-> reiterating what the product does, key capabilities, makes what you can deliver clear
• How-to -> showing how you get to that value with a 1-2-3 steps removes friction, makes it feel easier

Now, Stytch went for an interesting V3:

Code snippet -> how about just show it? this is a flavour of that 1-2-3 how-to but extra dev-friendly. They also made the code interactive so that you can tinker with it, make it feel yours already.

And they saw a 13% signup conversion bump.

Definitely an interesting thing to test out.

Check out Stytch CEO talking about it here.

Modal with updates.

Adding a modal with "what happened lately" for users who come back to the app.

Good idea for re-activating users by showing new features or examples.

+ a link to a deeper resource.

Pushing cold blog readers to try your tool rarely works.

So you need a transitional CTA, something that worms them up.
But it needs to be aligned with the goals of the reader.
And I think pushing folks to a community discord is a solid option.

I like the copy "Discuss this blog on Discord" as it is very reader-focused.
Some folks read the article and have more questions.
They want to discuss it somewhere.

And while you could just do a comments section, a community gives you more options to get people closer to the product.

Navbar is a hugely important conversion lever on the dev-facing website. I saw it move the needle by x times in some cases/conversion events.

So, what does a good one look like?

Auth0 did a great job on their developer portal. But the learnings can be applied to your marketing website too.

What I like:

• They have an explicit division between docs and resources (you can do without it but I like it)
• Community (with all the events, forums, support etc) is clearly emphasized and discoverable
• When you click on the navbar tab you get an extensive mega menu with many options
• Each item in the mega menu gets a one-sentence description of what you'll find there

That makes it easy for devs to explore. Without having to click out to see what each tab/item means. And when devs know what you mean they are more likely to actually click out. And convert.

When selling dev tools you typically have 3 "buyer" levels:

Individual dev:

• wants to experience your value prop
• ideally wants to play/test/use the free tool
• doesn't buy tools but strongly influences buying decisions
• wants to use it right now, not talk to his boss to get a credit card, not talk to sales

Team lead:

• wants to improve teams productivity
• collaboration, developer experience, and happiness are important
• buys tools at a team-level budget
• doesn't want to go through a lengthy sales process but  swipes the card and gets the team on this week

Org lead:

• wants to improve the security and compliance of the entire eng org
• security, control, governance
• buys tools for the entire organization/enterprise
• expects a longer sales process with a lot of moving parts and needs to discuss and negotiate

How does Postman solve it?:

• packages their plans in a way that aligns with those buyers
• different plans have features needed for Dev/Team lead/Org lead
• CTAs are exactly what each buyer wants: Use > Buy > Talk

They even go the extra mile. Something I didn't see too often.

They understand their customer's reality and identified one more level between Org and Team.

Basically a department-level unit that probably has multiple teams but is not at the organization/enterprise level.

I really like what they did hear. Solid.

I love this copy. It answers:

• what it does -> "authentication and authorization"
• how is it different -> "simple to implement, easy to extend"

It doesn't talk about the value as it is obvious to devs.

Obviously, it will save time and make things safer.

Don't talk about it.

If you have an API product presenting it in an exciting visual way is hard.

But Deepgram managed to do just that.

They go for an autoplay presentation that has four acts:

1. Context: playing an audio file showing a spectrogram -> sets the context that this is something audio
2. Code: They show the code from one of the SDKs being typed. And they show tabs at the top with other important SDKs to convey that this is not Python-only.
3. Result: Shows the output of running the code, a transcript, and an AI-generated summary and topics.  
4. Layers: Takes the points above and layers them in one viz to communicate that this is all part of one product, just different "views" of it.

And the delivery is just slick and elegant. Kudos team!

btw, Mux, the video API has a similar design of their visual. I think it is just a great visual element for API products.

Pricing in your docs? That is how @Fly.io does it.

You click a pricing page link on their homepage and you go to the docs!

No 3 boxes with the "most popular" being the middle paid plan ;)

They just give it to you how it is. Exactly what you'd expect from the docs.

There are tables, explanations, and links to other docs pages.

Very bold decision imho. It definitely makes them feel super developer focused.

Plus if you do want a more standard, enterprise stuff you see:

"If you need more support or compliance options, you can choose one of our paid plans. These come with usage included and additional support options."

And that page looks like a classic pricing page.

But they focus on the developer buying experience here. Super interesting.

A docs header worth a thousand words.

For a dev platform or infrastructure tool it is hard to explain where you fit, what you do quickly, and how you connect to existing components quickly.  

Hopsworks docs team does a great job here.

So instead of using words, they use a diagram:

• You get a solid overview of where your tool/platform fits larger context
• It shows you which part of the workflow/infra the platform solves
• Every part of the diagram is a clickable docs link
• Shows where you can deploy it
• Shows what backend you can use.

All of that in a single diagram.

Now that is a dev-focused header visual.

Sometimes you have an article, report, or event you want to drive people to.

And it is important that they read it.

What Plaid did here is an interesting way of putting it right in the hero section without making it overwhelming or distracting.

I like it.

Make login our problem. Not yours.

This is a beautiful messaging of Auth0 solution.

Login

Simple explanation of what it does/gives you.
Simplified of course

Our problem. Not yours.

You "outsource" this boring but important problem to someone else.
It also has a feel of SaaS in there.
They will take care of it.

‍

The main message you want to land on your homepage community section is:

"We have a big community of devs who love using the product"

🚧 That helps you tackle obstacles your dev reader has:

• "is this tool any good"  
• "do real companies use it in production"
• "are there people who can help me when I hit roadblocks"
• "where would I find others using the tool when I have questions"

💚 Modal solves it beautifully by going simple but smart:

• Join our community header and a call to action to join Slack makes it obvious where users are
• Wall of love style testimonials give a feel that there are so many users and they love it enough to share that with others
• They all look like Tweets even though (I presume) some of them aren't. That is a nice trick to boost social proof. People give more value to social post testimonials.
• They show a face, name, role, and company which builds trust and makes it obvious those are other devs (like me)

It lands the message that this section should land for sure. I really like it.

Devs like diagrams.

When you explain a complex concept in one diagram it is just very shareable.

If you are interested in reading more there is an entire "blog post" when you click see more.

Just a very solid content format.

Using memes in the product release.

If you understand your ICP (in this case open-source backend devs) it may be a great idea.

An additional benefit is that people may share a meme... that actually has a link to your announcement.

Streamlit has an amazing explainer.

They show how to go from:

• Writing your first line of code
• To creating data dashboard
• To deploying it across the web

In 42 seconds.

No audio, just code and a simplified result window.

Amazing stuff.

This is a really clever billboard campaign.

Show don't tell they say.

And Segment did exactly that by putting billboards with the wrong location printed on them (LA in SF etc).

The theme/message was "What good is bad data?" which was exactly what they wanted to convey.

What I like about is the alignment between:

• campaign creative
• campaign theme
• product value

This is hard to do imho so big kudos to them 🎉!

Downside?

Reportedly many folks who saw billboards didn't get that it was intentional and Tweeted at them about the error.

Or maybe they were next-level jokers...

Understand who is reading. Add social proof that speaks to them.

Social proof is about showing people/companies who are similar to the reader that they got success with the tool.

Company logos can be good if your reader knows and likes those companies.
But if those are random companies, I am not sure how much value does it bring.

Devs care what other devs who use your product have to say about it.
That's why I like testimonials.

Not the crafted, clean ones with features and values.
But the real stuff. Real devs sharing real stories.

Bonus points for "Okay, I get the point" button copy.
It changes from "Show more" when you click.

Nice!

There are many things that I like about it.

• A clear value proposition: Explains what it is: an open-source alternative to a well-known product Shopify.
• Shows code and what the code does visually. Great product explanation.
• Adds a social proof with "#1 JS ecom platform on GitHub:". When you have 16k stars you should use it!

Overall with very little effort, I understand what it is, and what it does.

And I can go and dig deeper for myself or spread the word with my circles.

This has to be one of the better dev-focused headers I've seen in a while.

Headers should deliver your core product message and get people interested. That is true at any stage but early stage especially.

💡You want everyone, even those folks who just take a look and leave to remember. You want them to recall it in their next conversation around this topic.

There may be supporting messages for sure but there is always that one core thing. Make sure it lands.

In the case of Clickhouse, that core message is that they are a database that is fast at a huge scale.

Their supporting messages are:

• they are best at analytics and real-time apps use cases (where speed/scale matters)
• they are a very popular open-source project

💚And they deliver that beautifully with:

Headline

Clear as day headline speaking to value delivered at a level that builds rapport with their audience.

Not "Give users seamless web experience at scale" but "Query billions of rows in milliseconds". I like that little touch with "rows" which makes who they speak to obvious

Subhead

Subhead supporting it with "fastest and most resource-efficient DB"

+ talking about the use cases "real time apps and analytics" and it being open-source

Calls to action

These CTAs make the audience feel at home. There are docs in there + clear "we are open-source" CTA

Visual

That supporting visual is just amazing.

It shows the value in the most believable way you could deliver it here imho. Query and an Output that shows the size of the database and speed of the query

Social proof

Social proof in the navbar, almost 34k stars and a GitHub icon.

+ a way to get people to that repository, check it out and leave a star.

There is more social proof below the fold with big logos and stuff but the GitHub icon and stars make it immediately clear that this is a project that people care about.

It is remarkable how brilliantly simple it is all presented.  Just a fantastic work IMHO.

The homepage header is about landing your core product message.

For Modal it is basically LLM infrastructure with great developer experience.  

And they do a great job delivering it:

• Input/output visual: I think for infra products this is a great choice.  Show what code you run, show how to run it, show what you get. Ideally, this all looks nice and easy.
• Headline/subheadline: They explain "what is it" and "for whom is it" (or what use case): "what": Serverless infra platform, "whom" ML teams.

• Great calls to action: If you don't know what to put this is the best baseline imho. Get started (Signup) and Docs.

• Social proof: devs want to know if others like them and/or respectable companies use it in production. While dev testimonials do that better, logos is what people expect to see here. Don't have them and you raise flags, especially if you are unknown.

• Branding: if you can make your page/company memorable on top of landing  that message -> great. And with that green gradient and uncommon colours they definitely do.

Top job on that header folks!

This is one of the most interesting content pieces I have seen in dev tools recently 👇

Comes from @SST and believe it or not is a comedy video created to promote integrations.

That's right.

So SST integrated with Astro and instead of creating "just another how-to use X+Y" video they created this:

• A copy of "Between Two Ferns" comedy show
• With one of the founders of Astro framework which they integrated recently
• Where they don't really talk about integration too much ;)
• And reportedly got a ton of signups from this

It was a fun brand play but got way more views than a tutorial ever could.

And it connected with their audience in a human way that will be remembered (and shared).

Nice.

In a mature category, it is safe to assume that people know about other tools.

Especially devs.

I love how Axiom owns its unique selling point and how it stands out from the competition.

• They explicitly say how much more scalable they are vs well-known brands like DataDog, Splunk, SumoLogic, and others.
• They don't pretend to be the only company in the observability space.
• They just own their unique selling point and make it easy for people to understand why choose them not others.

Takes guts but I love it.

I like the simplicity of this announcement.

What: "Vercel Edge Middleware"

Why: "Start delivering dynamic, personalized content without sacrificing end-user performance."

Visual supports this but is super minimal.

I really love this hand-drawn feel.

It makes it super authentic.

Also, starting from scratch (not a ready diagram) makes following it more fun and less overwhelming.

Great stuff.

BTW the tool used for this is called excalidraw.com

How to design the navbar product tab? This is what @PostHog does 👇

Figuring out what to put in the navbar is tricky:

• How should you name tabs
• What should go where
• Should you have "resources" or divide it

The "Product" tab is especially tricky.

It can get overloaded with a ton of content.

• Some teams put docs, and product videos there.
• Some show features, integrations, and code examples.
• Some go with solutions and per person per industry pages.
• Some just put everything in there ;)

I like how Posthog approached it:

• They use the word "features". Most devs like it more than other options.
• They show the data stack with which the tools integrate. That is an important obstacle handler pretty much always.
• They include customers in the product tab. Most devs want to see the product and may not go to the "customers" tab. This is a nice way to add social proof and increase conversion to user stories pages.
• They show customer logos and the results they got from the product. Again more social proof without clicking out.
• They use "customer stories" rather than "case studies" which again feels more devy .

I like it.

The idea behind this conversion play is to put an "Aside CTA" that is unrelated to the content early in the article.

And get that clicked.

But obviously, if you do that it will be pushy and intrusive.

So?

Nevo David from Novu shared this idea on one of the podcasts:

• Put a small section right after the introduction
• Add memes to catch attention and disarm the "I hate ads" reader (a little bit)
• Make an explicit ask. Make it human and somewhat vulnerable

Btw, Nevo says that cat memes work best.

What to say when you have many products? 

Dev tool companies over time grow from one product to suite of products to platforms with products built on top of the core one.

The result is that it is harder to communicate without going full-on fluff mode (my fav "built better software faster").

But for most companies, there is this core capability/product where people start.  The entry product. Why not use that?

I really liked what Stripe did on their docs page here:

• They have maaaany products: billing, tax, radar, identity etc.  
• But all of them are built on top of their core payments product
• So they focus on getting folks to start with the payments
• And make it clear that there are many other products

Even though this is docs, the same applies to homepages and other dev comms.

If you have many products, figure out what is the most important one, the one where most people enter. Focus on that. "Upsell" to other products later.

Good format of the tweet copy.

Start with the hook.

Then validate it with more story.

Then open a knowledge gap with a thread.

This is one of the more devy blog designs I've seen in a while.

It has this docs-like feel.

But is just a bit more fun and loose than most docs would allow.

Here is what I like:

• smells like there could be value with code all over the place
• shows visuals taken from another devy channel, Twitter/X
• hints at social proof through Twitter/X engagement

And if your posts are code-heavy, then a docs-like experience is where you want to be anyway.

But you can spice it up with things that wouldn't fit the docs.

Like a Twitter/X embed or a meme.

Really good product navbar tab from Supabase.

The product tab in your navbar is likely the most visited one on your site.

And there are a million ways of organizing information in there.

But ultimately, you want to help people understand what this product is about at a glance.

Even before they click. Even if they never click.

And how do you explain your product to devs?
By answering common questions:

• "What are the capabilities/features, specifically?"
• "What do people use it for in producution, specifically?"
• "Ok, so how is it different than ... I used before/use now?"

Supabase does it really nicely:

• They show features + give a one-liner explanation
• They show customer logos + a one-liner on what they got from it
• They list the most common competitors with links to deeper comparisons

Very solid pattern imho.

What I'd improve:

• Make the third testimonial copy more dev-centric, more specific -> It reads "... to become top 10 mortgage broker"
• I'd add a link to a page with all comparisons -> what if I don't see mine?

Make a {X} cry in 5 words or less.

Great Linkedin (or Twitter) post format.

This is one of those fantastic self-selecting mechanisms as well.

People who understand the joke are the people you are looking for.

You may get the exact people you want to follow your profile.

With a nicely targeted joke.

Love it.

This is one of my favorite our dev tool vs competitor blog posts.

With these pages, you want to explain when you are better.

But you don't want to berate your competitor.

And above all, you want to help people make a decision.

Chances are (almost 100% ;)) that you are not better for every use case. And your developer audience knows it.

But there should be use cases, tool stacks, or situations when you are the best option.

Talk about those. Dev to dev.

@Convex did a great job in this post that I think can be a template for how to write these:

• They start by saying what is the same. That sets the context.
• Then they say good things about their competitor. Shows respect and understanding
• They follow by listing 3 key differences/situations when you should consider them
• And they go ahead and explain each of these differences deeply

After reading that post you are fairly convinced that if your situation matches the one described and if it makes sense to use it.

Love it.

I like those sidebar CTAs from Auth0.

They go with a sticky Table of Contents which gives a better reading experience.

They put two CTAs below that TOC:

• "See docs" presented in a very subtle, very developer-friendly way
• They put a more aggressive banner but it is still on the tasteful side.

Solid job.

This is one of my favorite header patterns for dev tools lately. Layered video visual from MUX.

So that video design pattern in here is this:

• A looped video on the right that...
• Starts by showing code (MUX video): right away I know this is for devs
• Then it shows me a player (MUX player) that shows the result of that code
• Then it goes to show the analytics (MUX data) of people viewing/interacting with that video
• Ends with all parts of the video code/player/analytics layered on top of each other to drive that this is part of one

There are a few bonus learnings here as well:

• "video infrastructure": that framing communicates that there are many tools I can pick and choose from. + it feels like Stripe for video which is a good framing in dev circles.
• "stream billions of minutes of video every day" hints at their benefit and core use case (streaming at scale)
• They show all the products Video/Player/Data right in the header making it clear what this video infrastructure means. And the layered visual explains it further.

btw I really like that branding. Custom font makes it so memorable. It is, isn't it?

"See docs" is one of my favorite secondary CTA on dev-focused pages.

TailwindCSS takes it to the next level by inserting docs search right into the header CTA.

This takes devs directly to the page they are interested in rather than have them try and find things for themselves.

They could have searched the docs in the docs, of course.

But this is just this slightly more delightful developer experience that TailwindCSS is known for.

Well done templates gallery from Vercel.

For developer-focused products, having an examples/templates/code samples gallery can be a powerful growth lever.

✅ It helps people:

• understand what you do
• see if anyone did what they want
• get started with something real-life(ish)
• get a feel for a product without committing to it yet

Just a great touchpoint in the developer journey.

💚 And Vercel does this one really well IMHO.

They start with an easy-to-find CTA in the navbar resources section. Bonus points for adding one-liner descriptions that make it clear what is on the other side of the click.

On the templates library page, they give you solid use case navigation with tags. And each template tile has a result thumbnail and a one-liner description. The beauty of this is in the simplicity and what they didn't put in here.

Each template page shows the result, gives you a tutorial on how to use this, and clear CTAs to either see this live or deploy yourself. Bonus points for the "Deploy" action copy (instead of "Sign up").

Kudos to the Vercel team. They are one of my favorite inspirations.

Funny dev newsletter CTA. From shiftmag .dev by Infobip.

It starts with a chuckle-worthy:

"Sarcastic headline, but funny enough for engineers to sign up"

Then they follow up by disarming the "is that spam" and building more rapport with:

• "Written by people, not robots - at least not yet."
• "May or may not contain traces of sarcasm, but never spam."

They end with an alternative call to action. RSS feed.

Most newsletters don't do RSS.

But for many devs RSS feed is the preferred content subscription.

Great job!

How to present benchmark results masterclass from RavenDB

The biggest problem with the software benchmarks that you run is?

People don't trust you. Especially when the results are good.

𝗬𝗼𝘂 𝗷𝘂𝘀𝘁 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝘁𝗵𝗮𝘁 𝘁𝗿𝘂𝘀𝘁. 𝗢𝗻𝗲 𝗼𝗳 𝘁𝗵𝗲 𝘄𝗮𝘆𝘀 𝗶𝘀 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 𝘁𝗿𝗮𝗻𝘀𝗽𝗮𝗿𝗲𝗻𝗰𝘆.

People from RavenDB do it by:

• Showing where they ran it (AWS, Linux)
• Showing exactly what infra they ran it on. Extra points for making it interactive.
• Explaining how they ran it with code snippets and setup
• Copy is also very to the point, technical, docs-like

This looks solid because it feels like I could re-run what they did myself.And so I trust them and I probably won't ;)

Most devs want to explore products themselves.

They want to read the docs, see examples, play with the product, or watch a video.

They don't want to hop on a demo call, especially early on in the evaluation process.

And they definitely don't want to sit through the demo to learn what your pricing is.

But there will be moments when they will want to talk to you. They will raise their hands and let you know then.

Posthog speaks to this reality with this copy beautifully:

• They basically say "don't talk to us"
• They give you transparent pricing on the website
• They give you a recorded demo on the website
• They let you try the product for free without talking to them
• But if you want to talk to sales/support you can reach out

This is very developer-focused approach and I love it.

Conference activation idea: Tetris competition at the booth.

It is hard to get devs to your booth if all you offer is a "do you want to see a quick demo" spiel.

You need to get a bit more creative than that.

💚 The team at Storyblok ran a Tetris competition:

• Playing station at the booth to make sure people come by
• Live leaderboard for when people were not playing + to get folks to play again
• Branding around the playing station for those who take photos to share it on socials
• A cool devy prize (mechanical keyboard) to build some additional reason to play talk about it

Afaik it was a big hit and I can definitely see why.

📒 A few more notes:

• make it live at the booth, not available online -> you'll get no buzz for it otherwise (made this mistake)
• try to get organizers to give you a few minutes of the schedule to give away prizes
• if you can connect the game to your product in a memorable way do that.  

btw, I read about it on DX Tips. You want to check out that article on dev conferences from DX Tips

What if you not only posted entire articles on Reddit but also promoted them?

This is what WarpStream did and I like it.

A few weeks back I shared an example of a company posting not a link with a snippet but an entire article on Reddit.

WarpStream is taking it to the next level by promoting it as an in-feed Reddit ad.

I love this trend 100%:

• Platform first: don't force you to click out, read the content here
• Ads as distribution: treating paid options as a distribution channel

By doing that you assume that if your piece of content gets read by the right people it will lead to business outcomes. People don't need to go to your site to be retargeted by ads and attacked by popup banners.

That is a very fair assumption, especially with devs.

But even generally in B2B SaaS and social channels like here on LinkedIn that concept of zero-click content, coined by Amanda Natividad, is gaining traction and I'm glad that it does.

Action-focused copy is usually better than "sign up".

But sometimes it is hard to find a good copy for this.

Some teams like Vercel or Auth0  do "Start building "  

But that doesn't always work.

I really like this "Get API keys" CTA copy.

Now for the Hero section I really like those two CTAs:

• Main CTA: Sign up, again expressed with action-focused "Get API keys" copy
• Secondary CTA: See docs, I like how "See API docs" makes it even more concrete.

Really great job imho.

"32 billion reasons to check out..." - I love this ad from Aikido Security.

What I Iove the most is that it doesn't say much, it just points. I think it comes from Harry Dry or the book Made to Stick.

But the idea is that the best stories are not something you write. It is something you tell. You don't say, just point.

And this is what folks from Aikido did:

• the story is that Wiz got acquired for $32B by Google
• often companies that get acquired the quality drops over time
• some folks in the dev community (on Reddit) are not happy about it

So they pointed:

• They pointed to a Reddit comment (simple screenshot)
• They pointed to them being acquired (which is a huge story in the space)
• They combined it all with a beautiful pun "32 Billion reasons to check out Aikidko"

Love it! Sometimes I think I live for this stuff ;)

Thank you Marie Jaksman for sharing this gem!

Copy that lands makes a huge difference in dev tool website conversion.

Earthly proved it with this "tiny" change.

So I am a huge believer in good copy.

Not the clever one but the one that is written with words that your customers use.

That is rooted in product and research.

But I often hear devs or founders say things like "it's just copy".

It is not "just copy" it is your message, it is your positioning.

It is the difference between  "cool, let's try it" and "now for me, whatever".

So some time ago I came across this article from the Earthly CEO Vlad Ionescu.

He shared that at some point they decided to run this A/B test with just a "tiny" change.

They changed the word "CI" -> "Build" across the homepage.

• Control -> "Earhly makes CI super simple"
• Test -> "Earhly makes builds super simple"

And their core website conversion doubled.

So next time you work on website copy give it some more thought and you may be surprised that "just copy" made a huge difference.

I love how simple this delivery is. But this is what makes it powerful:

• What it does (benefit): "Launch Apps Near Users" just tells you right away what is in it for you
• How it does it (features): some specifics in the header that make you understand the how
• Visual: doubles down on that "near users" by showing which locations they support
• Joke: that little joke "6 continents -> * Antarctica coming soon" makes it more memorable and adds one more point of emphasis to that "near users" story

Bonus points for showing those regions with their balloon logo.

Just loved how they focused their message to the very core and used all of those elements to land it right away. Great job.

How easy it is to get started is a big conversion factor for any dev tool.

Devs want to test things out and if it is hard to do they will be gone testing a competitor that made it easy.

And so a good how-to section on your homepage can make a big difference in getting devs to that first experience.

Appsmith does it beautifully with their 1-2-3 How-to section:

• 1-2-3 format: Connect data -> Drag and drop -> Customize with code
• Interactive GIFs with code snippets and UI elements
• CTAs to integrations, widget library, and docs
• Dev testimonial at the end to make it real

It is so engaging and just beautifully designed. And the CTA to additional resources like integrations, widget library, and docs make the message land. I do believe it is easy to set this up.

Great pattern to copy-paste imho.