Developer marketing examples

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.  

What CTAs should you choose for your open-source project homepage?

Was always wondering what is my default.

There are many options: "See docs", "Get started", "Sign up", "Start X"

But in open-source you want people to start playing with it, install it.

So what should you choose?

Recently came across Astro homepage and loved what they chose.

"Get started"

• Takes you to the quickstart in the docs
• Is action-focused copy
• Sets obvious(ish) expectations

Install code

• Gives you copy-pasteable install command
• + it shows the code to make it more devy

Whatever I choose I will actually get my hands dirty.

I think this will be my default from now on.

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 ;)

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!

Create a connection with your ideal customer profile.

"Wrong answers only" questions are great for that imho.

Need one more call to action idea for your dev tool blog?

How about starting an article with it?

Sounds weird but if done right it can work. Even with devs (or maybe especially with devs).

Earthly did and they are known for great dev-focused content.

Ok, so how does it work?

You start your article with a contextual call to action where you explain:

• Who you are and what your product does
• And how that is relevant to the content of the article
• Link out to more product-focused pages, ideally relevant to content

And then you let people read.

Those who find the topic important will remember you and/or maybe click out to see more.

I like it. It's explicit, transparent, and actually noninvasive.

Funny ad, that makes fun of ads.‍

But it actually communicates that you don't care about the ads but more about something else, like:

• docs
• code examples
• integration
• backend
• UI

There are three CTAs actually.

Common knowledge suggests doing one, maybe two, they do 3:

• build
• see docs
• see examples

Devs want relevant and practical.

Also, devs love docs and examples and check them before signing up.

Action-focused copy is great as well.

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

If your dev tool's USP is that it is faster -> Show it in the header

I like how folks from Bun focus on the fact that they are a faster library.

They show the benchmark as the key visual on the homepage header.

I love it.

If you think about it how else do you really want to show that you are faster?

This is believable, especially with a link to the benchmark so that I can dig deeper.

They show competitors, they don't pretend they don't exist.

And they talk about being faster left right and center.

I mean, they drive this "we are faster" home for me.

If that was important to me, I'd check it out.

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.

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.

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.

Beautiful growth loop that uses GitHub PRs to spread awareness even internally in the org.

And just one dev needs to sign up for the product to start it.

Works like this:

• New user signs up for Snyk
• they connect their GitHub account
• Snyk finds vulnerabilities in their repositories
• Snyk-bot creates Snyk-branded PR to fix them
• other devs in the org see and interact with the PR
• some follow links to check out Snyk
• some of them sign up for Snyk

Heard about it on Lenny's podcast episode with Ben Williams (the story starts at 20:53)

... and then signed up to see the actual PR.

I really love this one as it allows you to spread inside the organization even if everything is on-prem and you never get to see it.

Those PRs are just working behind the scenes doing marketing for you.

Brilliant!

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.

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.

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.

I love this simple design.

They show:

• A GIF of code and console
• Have a few tabs with features, explained
• Social proof with Github stars

Simple, and powerful imho.

An interesting option to push people to read the next article.

You use a slide-in triggered on a 75% scroll with a "read next" CTA in the bottom left.

On the aggressive side for sure but when the article you propose is clearly technical it could work.

And if your articles are not connected to the product explicitly you do need some ways to keep people reading and see more of your brand.

"There are two types of companies": Just a beautiful piece of copy from Fly.io

Doing us vs them doesn't always play out well.

But folks from Fly made it snarky and playful and fun.

And they basically said that they are:

• are developer-centric in the way they sell (self-served)
• are actually easy to use
• are great at the developer experience

And this is just such a nice brand play as well.

You just show personality and confidence in this devy snarky way.

I dig it.

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.

I like that this is both strong and subtle.

It comes right after I've delivered a smell of value with a technical intro.

And I can see that there is more value to come after thanks to the table of contents.

The CTA itself feels like an info box in the docs rather than a typical subscribe CTA.

Good stuff.

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!

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.

‍

How to present many features at once?

Sometimes your dev tool has many features/products that you want to show.

❌ Showing all of them as separate sections doesn't work with more than 3. It just gets too long very quickly.

✅ You can go with the tabs pattern where each tab has copy+visual for a feature.

💡 But there is another option that makes a ton of sense when you have many features to show.

Interactive tiles of different sizes.

💚 I like the implementation of that pattern coming from Clerk:

• Each tile is a combo of feature name + one-liner description + an interactive visual
• When you hover over each tile it starts playing the visualization explaining the feature even more

• Some of the tiles are bigger which makes the entire section more interesting. It could be one (core feature or differentiator) or a few if you present many.

That pattern can work really well on blogs or learning centers too but I think we're going to see more of it on dev tool websites.

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!

𝗛𝗼𝘄 𝘁𝗼 𝗰𝗿𝗲𝗮𝘁𝗲 𝗴𝗼𝗼𝗱 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝘁𝗵𝗮𝘁 𝘁𝗵𝗲 𝗛𝗮𝗰𝗸𝗲𝗿 𝗡𝗲𝘄𝘀 𝗮𝘂𝗱𝗶𝗲𝗻𝗰𝗲 𝗹𝗶𝗸𝗲𝘀?

The general tip is simple. Create content that the HN audience finds interesting.

𝗧𝗵𝗮𝘁 𝘁𝘆𝗽𝗶𝗰𝗮𝗹𝗹𝘆 𝗺𝗲𝗮𝗻𝘀:

• Something that feeds curiosity (how does X work, why did Y happen, what is it like to do Z)
• Something real, transparent, and written in first person (real stories)
• Something technical and focused on the dev or founder crowd

But how do you actually do that?

𝗢𝗻𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗽𝗹𝗮𝘆𝗯𝗼𝗼𝗸𝘀 𝘁𝗵𝗮𝘁 𝘀𝗼𝗺𝗲 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗳𝗼𝘂𝗻𝗱𝗲𝗿𝘀 𝗱𝗲𝗽𝗹𝗼𝘆𝗲𝗱 𝘄𝗮𝘀 𝘁𝗵𝗶𝘀:

• Get your technical founder or core developers to write articles
• Those articles are focused on the technical challenges of building your product
• Again, don't write what your product does but rather how you build it. Mistakes you made, ideas you tried, technical challenges you had to overcome.
• Share real value with that dev audience. And to give people real value, you need to have folks who actually understand their problems. Those are typically senior devs/founders.
• You will inevitably hint that you are building a product and the folks who are interested in your product and you will go deeper.  

That was exactly what folks from CockroachDB did at the beginning.  Heard about it on one of the episodes of the Unusual Ventures podcast with Peter Mattis from Cockroach Labs.

𝗘𝘅𝗮𝗺𝗽𝗹𝗲𝘀 𝘁𝗵𝗮𝘁 𝗵𝗶𝘁 𝘁𝗵𝗲 𝘁𝗼𝗽 𝗼𝗳 𝗛𝗡:

• "CockroachDB Stability Post-Mortem: From 1 Node to 100 Nodes"
• "Serializable, lockless, distributed: Isolation in CockroachDB"
• "How CockroachDB Does Distributed, Atomic Transactions"
 
Kudos Cockroach Labs team and thanks for sharing!

Show how product components fit together.
‍
A good diagram is such a good solution to that.
‍
They use the same colors and eyebrow copy that was used for body sections.
It all clicks now, I get the full picture.

‍

‍

Linked GitHub logo in the navbar

Adding CTA to your GitHub repo makes your company look more dev-friendly.

If you have a ton of stars I'd show those as well to play that social proof card.

But even without it, I think it's a good way to get more traffic to your repo and get those stars :)

Algolia gets over 80% of referral traffic from a single free tool they created called Search Hacker News.

But why does it work so well for them?

Hacker News doesn't really have a native search experience.

Algolia gives devs an amazing search experience out of the box.

So folks from Algolia created their own website where you can search Hackernews... with Algolia search engine.

Of course, when you click on "Search by Algolia" you get directed to the website and can learn how to set up a similar search, which you have just used yourself.

What I love about this:

• solves a real problem for the audience Algolia is after (many software devs read hacker news)
• it shows rather than tells how Algolia's search works. And it works amazingly.
• it feels almost like an extension of HackerNews with the same brand colors and design.

And looking at the results it delivers.

Digital Ocean went for an ad for the Hactoberfest in a tricky place.

To keep it in the medium that fits YouTube shorts they:

• made it into an actual short vid
• used a comic book story

I think doing YouTube shorts is an interesting opportunity in a yet unsaturated market (as of 2022).

And doing ads that fit that medium so nicely is an art.

Good job DO!

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.

Thinking about your next conference giveaway idea?

‍How about a coconut? Datafold did just that!

Coconut + logo burned on it + a person who can open them up

=

A memorable, shareable, fresh (literally), and wholesome conference experience.

And I bet it didn't cost an arm and a leg too.

It goes to show how creativity matters when planning those things.

Thinking about doing a similar thing in Poland... with potatoes of course ;)

A nice example of making navbar more developer-focused.

Ask for GitHub stars with a link to the repository.

It does three things:

• shows where your repository is and that you have something I can see
• lets me see that you have a popular repository
• reminds me that I can star it (if I am a returning user)

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.

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.

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.

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.  

Your dev tool is faster/more scalable/more X -> show it with benchmarks.

For some tools the entire unique selling point is that they are faster.

You build your messaging around that, put a flavor of "fastest Y for X" in the header and call it a day.

But devs who come to your website cannot just take your word for it. They need to see it, test it.

For some tools it is possible to just see it for themselves, get started.

But you cannot expect devs to really take a database or an observability platform for a spin.

As to test the speed or scalability on realistic use case you need to...

... set up a realistic use case. Which takes a lot of time.

But you can set that use case and test it for them. With benchmarks.

I really like how Astro approached it:

• they list out known competition by name
• they hint at technical reasons for why they are faster
• they shows those benchmarks high on their homepage
• they link out to the full report and mention the trusted source

If your usp is that you are faster/more scalable/ more whatever. Back it up. This is the nr 1 thing devs on your website need to trust you with to move forward.

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%.  

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.

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 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 like the design of this crosshead.

• Starts with the gif to catch my attention
• When tabs change the copy, CTA, gif change
• The figs have a nice click cursor that shows what I am doing
• CTA is very "silent", non-intrusive

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.

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.

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.

Many dev tools have complex pricing and packaging.

Say your dev tool/platform has many product offerings.

And you offer usage-based pricing but also enterprise plans but also per-product options, and additional customizations.

But you want to present it in a way that is manageable for the developer reading your pricing page.

Mux solves it this way:

• they direct people to the proper parts of the page in the header
• they give self-served prospects a link to the calculator and metering
• they give enterprise/high volume people a "talk to us" CTA
• they give people who want just a single tool (not the whole platform) a CTA to a dedicated pricing page
• they squeeze in a "start free" CTA + info about free credits
• they give navigation to FAQ, features table, and the calculator

Extended headers on pricing pages are not common as they add friction.

But sometimes adding friction is exactly what you need to do.

Mux managed to make this page (and their offering) easy to navigate by adding a little bit of friction at the beginning.

Maybe you don't browse plans right away but at least you don't waste energy (and attention) on the parts of the page that doesn't matter to you.

Good stuff.

A great example of a quote-style ad.

I like it because:

• Trust: it builds trust via G2 crowd reference and an actual person mentioned
• Value/benefit: the quote talks about what the tool does and what is good about it
• More trust: links to G2 crowd profile, NOT your page -> more trust especially when I don't know the brand yet

Great stuff.

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.

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.

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.

People want to be valued by their tribe.

One of the ways to do that is by being helpful.

So they want to share things that have a "smell" of insight.

Tool stack/workflow/pipeline chart makes them feel that way.

‍

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.

How to communicate the flexible part of your plan?

Many dev tools have 3 plans:

• Free
• Team
• Enterprise

Especially the ones doing some flavor of product-led-sales or open-source go-to-market.

Now, the Team plan is often a self-served version.

And for many dev tools, this part is partially or entirely usage-based.

So how do you present it?

You can just have "+ what you use" and explain it in the big table below.

But if you have just one usage dimension then why not do it here?

Resend does it beautifully communicating right away that it starts at 20$ / month and grows with the amount of emails you send.

Very clear. Very nice.

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.

A great example of a dev-focused Linkedin post format from Khuyen Tran 👇

What I like about this:

• It stands out in the feed with a pink background
• It is helpful and visual. Shows the code and result of the code in one view.
• I know right away what the post is about and why I should "... see more"
• It is a format that can be reused for many scenarios

Just great job!

"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.

I like this idea of showing how your dev tool works.

With developers, you almost have to explain how it works on your homepage.

Many products do some version of Step 1 -> Step 2 -> Step 3 -> Success.

I really like how @SST approached it with a timeline.

I find it more engaging than those disconnected steps.

And when I follow this journey the final and logical step is to try it out. Get started.

In dev tools, you really can solve the problem for a narrow market and extend to adjacent markets over time.

‍Use that -> Snyk did.

Their value proposition stayed pretty much the same for 7 years!

"Find and fix vulnerabilities in open-source software you use."

But the market they served got so much bigger over time:

• They started super narrow with just one Javascript framework, Node.js
• They focused on solving that pain very well before moving to the entire Javascript language
• Then to other popular languages like Ruby, Java, and Python
• Then to the entire Open Source dependencies
• Then fast forward to today and they do Open source + containers +IaC

Again, their core value prop is the same in 2023 as it was in 2016.

But their target market (and revenue share) grew by... a lot ;)

Isn't that just beautiful marketing-wise?

So the takeaway is this:

Start narrow, solve the problem, and extend to other frameworks/languages/tech can still work.

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 :)

‍

An ad that doesn't feel like an ad.‍

I like that this is almost a meme.

But it still explains what the company does.

Love it.

How to promote your important company event? How about right there in the header.

A typical approach to promoting events on your site is to have them in the Hello bar (right above the navbar). This is a solid option of course.

But what if this is a super duper important event that you really want to push?

Put it in the header.

The header is the most viewed part of the most visited page on your site.

Doesn't get much better than that.

But you don't want to distract people from your value propositions and main CTAs too much.

How do you do that?

This is how Vercel did with last year's NEXT.js conf.

• above the H1 headline so as not to break the flow
• prominent but not more distracting than it needs to be
• has conference logo, crystal clear copy, and an event CTA

Nice execution on that pattern.

Simple yet powerful CTA in the navbar resources section.

The resources section in the navbar is mostly navigational. Well, the entire navbar is ;)

But you always have that one action that is more impactful than others.  

💚 And I think that a Plauground  is a great option. You get people to see how your product works. You let people play with it and see for themselves.

Not many next actions can be as impactful as getting people to experience the product.

Especially if you are a heavier infra tool that people cannot really test out in that first session. I mean, you won't really create a realistic example of your core database in 15 minutes to see how that new tool that you just saw works.

🔥 Making this CTA "big and shiny" and showing a glimpse of what will happen after clicking is great too.

🤔 2 changes I'd test out:

• Making the copy more descriptive performs better.  Like "Launch playground", "Play with Sandbox", or something around "Run an example project/app/environment".

• Showing something more exciting about the product (or playground/tour) on that visual

But the core idea behind making the playground your core navbar resource section CTA is just great.

Subtle but effective dev blog CTA -> info box.

Basically a plain article in-text CTA but there is something special about it.

It looks like a docs info box.

It is not a "buy now" style call to action but rather a subtle "you may want to know about X" push.

But for it to really feel like an info box it needs to connect to the section of the section of the article around it.

Otherwise, it will just feel like an intrusive ad anyway.

PlanetScale does a great job here.

They link the part of the article about the sharding library Vitess with their product that was built on top of it.

It feels natural and I am sure it gets clicks and if not then product awareness.

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.

Say what you do and how you do it.

What:

• Supabase owns it with an "open-source firebase alternative"
• They don't streamline project delivery or anything. ‍

How:

• Value proposition around speed of set up
• Then jargon that hits the spot with your ideal developers
• Short, and to the point. 

CTA (bonus):

• "Start your project" action-focused
• Documentation. With devs, this is always a good alternative CTA

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

Handing #1 dev obstacle: "We can do it ourselves".

Check it out from second 0:35:

‍"I bet you're like
We can do it ourselves, it's not that hard.
We know what we're doing.

First, I hear you.
Second, are you sure?"

This is mastery.
Pointing out ignorance without alienating people.

Super short dev tool case study on a single viewport.

Many case studies follow a Hero -> Problem -> Solution -> Results framework.

Many try and do it on a one-pager.

But what @Resend did is next level and I like it.

Especially with devs, you want to be technical and succinct.

And Resend took all the possible fluff out of it.

• They put a strong quote up top
• They highlight the benefits for easy skimming
• They explain the problems and results succinctly
• They show who said it and make it more believable
• They show the customer: logo/ name + what they do

I'd like to have some before or after probably or a stronger results (or pain) ) focused headline.

But I think this is great actually.

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 ;)

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.

Is it better to do one big prize or many small prizes?

This is a decision you have to make when thinking about running a swag campaign.

Turns out that a  small number of huge prizes can get you way better ROI on the same budget.

And NannyML has done it brilliantly here.

They are a monitoring tool and they give away monitoring setup.

This is something that actually can go viral. And it did.

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.

I like how it has a proper "hero section" feel to it but it adds a developer-focused twist:

• Explains in simple words what the tool is
• Adds a lot of navigational links (website, docs, examples, blog)
• Then it goes into detail about what it does

The rest of the Readme is great as well but the hero section is gold imho.

How did this super basic ad get so much engagement on Reddit?

First of all, the value prop is succinct, to the point, and says what it is.

No "streamlining", "boosting", or "democratizing" is involved.
No clever tagline or pains, benefits, or values just says what it is.

But what it is, is "free and open-source" which is what many devs, especially on Reddit want to hear.
And Heroku is a known brand so if you know what Heroku does, you know what Kubero does.

I liked that they linked out to the GitHub project too.

Not 100% sure if that would perform better than a landing page or home.  But I see how it feels more in sync with the channel you are running your ads on.

The screenshot? I don't like it but perhaps it doesn't matter as much here?

What do you think?

Oh, and if you read the comments, you'll see that people actually talked about the project, said that they liked the ad etc.

Good stuff.

Usage-based pricing is loved by devs. But has its own problems.

Ok, so first what are those problems?

Value metric:

• users don't understand your value metric
• even when they do, they cannot map it to their usage patterns.

Predictability and procurement:

• it is easier to predict the headcount than the usage
• per user pricing is obvious, everyone across the org understands it

But devs love usage-based pricing:

• it is "fair", you pay for what you use
• you can scale up/down as you need

It is great for a dev tool company:

• you align user adoption, the value created, and monetization
• as org-wide usage so does the invoice

But pulling it off is not as easy as you may think.

Choosing that value metric, packaging it, and presenting it is a struggle.

@Appsmith solved it in the following way:

• give people an option to go with a usage-based pricing
• but cap a per-user cost at $X a month
• it guarantees a better deal than a flat per-user pricing
• but gives you the predictability of a per-user pricing

Very interesting approach.

Nice post format.
I like it for dev tools that have both API and UI components.
You show code and what it produces in one view.
You can add additional things to the vis part of it for more context.

Developer-focused Reddit ad. 33 upvotes, 30 comments.

So @Zesty is a company that targets devops folks and helps with cloud cost optimization.

And they decided to run Reddit ads.

So they:

• Chose the format that works with devs on (some) subreddits
• The funny message that connects to their main value prop
• Made it clear that they solve that problem in the copy
• Added clear(ish) branding

And they got 33 upvotes and 30 comments.

Some of the comments were technical.

One comment that got 67 upvotes was actually

"Okay, this ad is pretty funny"

And I agree, this is a pretty funny ad that I am sure brought them some brand awareness and clicks.

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.

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.

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.

"How fast do you ship?"

Not many dev tools answer that on their homepage. PostHog does.

In a typical (enterprise) sales process, people often ask:

• what is on your roadmap?
• how fast do you deliver new features?
• what has your product progress been like last year?

And you show them the roadmap or get someone from the product on the next call.

But I haven't yet seen dev tools talk about it on their homepage.

But why not?

Devs who want to buy self-serve want to know it almost just as much.

After all, they won't be able to twist your arm to build that custom feature cause "we are your biggest client and we need it".

I like it, it builds trust, it shows me you are transparent,

And it shows me that those features I can see on the public roadmap will come true.

How do you make your dev tool pricing simple?

I really like this one.

Saw someone share a pricing page from Userfront some time ago and really liked it. They changed it now but I really like the thinking behind the older version.

It is just remarkably simple while hitting all the boxes:

• You have tiers aligned with buyer persona: Free, Self-served (team), Custom (enterprise)
• Your usage metric is obvious (Monthly Active User)
• For Enterprise you just go with "Contact us" CTA (which is what enterprise buyers expect anyway)

Just a very good baseline.

Dorky joke right?

But it does two very important things beautifully.

It gets a smirk (from some people) and when it does you know you just moved someone closer to your brand.

It has a clear CTA which is hard to do with joke-format ads.

This subtle call to conversation/check us out does the job.

Love 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.

Just an awesome billboard/ad format for a dev too company coming from Vercel.

What I like about it is:

• you catch attention with something different
• those who are in your audience get it, maybe they feel more seen
• you reinforce that your brand is very developer-focused
• you don't forget to put the "obvious" branding in there
• and there is a CTA to get people to do something

Simple and beautiful.

Btw, they actually run similar ads on Reddit and it makes a lot of sense IMHO.

VS competitor ads are hard to pull off with devs. Not impossible though. 👇

So the problem is that:

• You want to list problems people have with the competing tool.
• But you don't want to come off as too negative and aggressive.
• And you want people to not think those are just "some bs claims to sell your tool"

@Convex does it really nicely here:

• They start positively by acknowledging that some people do "Love Firebase"
• They tag the competitor to build trust in the claims they are making
• They list problems people have with the competitor explicitly in voice of customer: "request waterfalls", "weak react support", "managing end-to-end consistency"
• And they link to a deeper vs competitor page for details

And even though this is by a "aggressive" competitor marketing hundreds of devs liked/bookmarked this tweet.

Good job!

I like how they use the black dot to show the mouse movements in the UI.

Simple but powerful and clear.

A freaking developer TV.

They took this "be a media company" to the next level.

They created entire TV around their company, audience, and products.

I respect people really going all in.

A classic "It doesn't suck" campaign.

Afaik, Barebones ran the first version of this campaign 20 years ago and it was a huge success.

It is so simple, it just speaks to that inner skeptic.

It doesn't say we are the best, we revolutionize software.

It says it doesn't suck.

That is way more believable and makes me think that there is a dev on the other side of that copy.

And there is something cool about this message that makes me want to wear it to the next conference.

Good stuff.

Great above the fold

The subheader explains the value proposition.

Header handles major objections:

• is it easy to implement?
• can I extend it?

Then we have 3 CTAs but they are super focused on devs: 

• Signup (using action-focused copy)
• See docs which is exactly what many devs want to do before signing up
• See examples, again exactly what most devs want to see before signing up

Then it goes on to explain how it works with a simple, static graphic.

This whole thing makes me feel peaceful.

Funniest dev tool explainer ever? Coming from Wasp.

Let's face it, introducing a problem in an explainer video is often boring. Especially if the problem is

How do you introduce a SaaS boilerplate? Good luck pitching faster time to value or something.

Wasp did something out of the box:

• They start by googling "how to buy a Lamborghini"
• Go to a Rebbit thread where people talk about starting a SaaS on boilerplate. But it is paid.
• Go to Google again and type their positioning ;) "Free open-source SaaS starter".
• Go to their product and show it.

Got me hooked and kept me watching for sure.

+ funny is memorable so you will get a better recall too.

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.

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.

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!

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.

There are a lot of boring vendor t-shirts at conferences.

And they get boring results.

I like this bold design from GitGuardian:

• they go for anime which is loved by many devs
• it feels and looks like an anime t-shirt, not a vendor t-shirt
• they use their core message "Keep secrets out of your source code"

Nice.