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.
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:
Btw, Nevo says that cat memes work best.
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:
There are a few bonus learnings here as well:
btw I really like that branding. Custom font makes it so memorable. It is, isn't it?
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:
So what did they do right?
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.
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:
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.
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:
This ad does it so gracefully and quickly it is just hard not to love. ย
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!
Mux does a few things beautifully in this header.
Value proposition:
Animated visual that is really good for dev tools:
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:
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 ;)
Make it about belonging.โ
Something some people can deeply connect with.
Nostalgia is a very strong emotion.
It feels good to be a part of something as well.
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.
Nice Reddit ad from kftray.
This is a simple ad format but lands the message:
An interesting fact is that there is no call to action?!
They say "Kftray is an open-source" which is enough for those interested to google "kftray github" or just go to GitHub and find it. And makes the ad less pushy which is a nice touch on Reddit.
But the most important takeaway is this. If the problem is real to the dev audience you target you don't need to go fancy. Just show how you solve it.
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 :)
It's a nice template for ads on socials.
So you have:
Ideally, I'd make it dark to stand out in the feed and make the CTA about that value as well.
But still, great ad imho.
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:
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!
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.
Classic remarketing ad. But things are classic because they work ๐
Youtube remarketing is one of the most popular ways to stay top of mind with devs who visit your site.
Lots of devs spend time on Youtube so it is a solid match.
But, "buy now" style ads rarely work because if they wanted to try/buy they would have already.
They need something more.
That "more" is often trust.
They simply don't trust you, your product, and your company.
They don't think you are the real deal and will solve their problems.
But you can build that trust. And to do that you can use testimonial-style ads:
That is it.
Show enough of these and % of people will trust you and convert.
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.
Takes guts but I love it.
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.
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:
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.
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:
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.
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:
So what did they do right?
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.
Sometimes your product just wins on price.
I like how New Relic owns it on this page:
After reading this I'd trust them to give me a solid price estimate and that it will likely be cheaper than Datadog.
Obviously price is not the only reason why we choose tools, but if that was a problem I had with Datadog, they have my attention.
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!
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 ;)
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.
How to bring attention and trust to a feature section?
Add a testimonial.
Ideally, it should talk about that feature to make your message even stronger.
I like how Appsmith made it animated and it just makes you look.
And you read the testimonial and look at the feature above it.
Good stuff.
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:
All of that in a single diagram.
Now that is a dev-focused header visual.
Most dev tools have two deployment options:
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:
I like how nice and simple solution Retool used on their pricing page:
Explicit, obvious and to the point.
Love it.
"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:
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.
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
I like the design of this crosshead.
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:
Sometimes you don't need to overthink it and can just ask.
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.
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:
But the core idea behind making the playground your core navbar resource section CTA is just great.
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!
โ
Interesting dev blog CTA idea from V7.
CTAs in technical articles is a tricky subject:
I like how V7 approached it here:
What I'd change/test is making this CTA not a generic value prop but something closely connected to the rest of the article.
I like how they use the black dot to show the mouse movements in the UI.
Simple but powerful and clear.
I love that it is static and it blurs everything I don't need to get the concept.
For the dev audience, static graphics, when done well, are better than
Tell me what you do in 1 sec, not 60
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.
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:
Interactive product tours are all the rage.
But how do you make them work for the dev audience?
How do you deal with:
That is hard.
But Vercel somehow made it.
This is by far the best product tour I have seen so far.
What I love:
This product tour is what dev tool startups will aspire to for years (or months ;) ) to come.
Mark my words.
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:
โ
Great above the fold
The subheader explains the value proposition.
Header handles major objections:
Then we have 3 CTAs but they are super focused on devs:ย
Then it goes on to explain how it works with a simple, static graphic.
This whole thing makes me feel peaceful.
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:
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.
This is such a fantastic ad creative because it is just so different.
So basically what Kinde it does is:
๐ That timer is such a great way of catching attention and keeping it while landing your product message. It seems raw and "whatever" but I think it is very intentional in its dev-friendly delivery.
So if you have a dev tool that has awesome devex and can get people to that aha moment quickly then give it a go (and tell me how it went ;)). ย
Testimonial ads are a format that helps you move people from "I know what you are doing" to "I trust you enough to do business with you".
Video testimonials are even better.
You see the person who has a similar role that you do saying things about the product you are considering.
CircleCI did a solid job here.
And so if you are running remarketing to people who went to pricing but didn't sign up, or signed up to a free trial but haven't converted yet this is a good format candidate.
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:
Afaik it was a big hit and I can definitely see why.
๐ A few more notes:
btw, Iย read about it on DX Tips. You want to check out that article on dev conferences from DX Tips
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".
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.
โ
โ
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:
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.
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:
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.
Great example of programmatic SEO from Snyk.
They created a page calledย snyk advisor.
It is a repository of pages about open-source packages.
Each page is created automatically out of publicly available information.
Enhances it with Snyk-generated security scans and reports.
It builds awareness for other Snyk products in the security space.
A lot of those pages rank high in google for the {package} keyword which is incredible.
And when people land on the package report page the CTAs to Snyk products push conversions.
There are a lot of boring vendor t-shirts at conferences.
And they get boring results.
I like this bold design from GitGuardian:
Nice.
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:
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.
When selling dev tools you typically have 3 "buyer" levels:
Individual dev:
Team lead:
Org lead:
How does Postman solve it?:
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.
Usage-based pricing is loved by devs. But has its own problems.
Ok, so first what are those problems?
Value metric:
Predictability and procurement:
But devs love usage-based pricing:
It is great for a dev tool company:
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:
Very interesting approach.
A nice example of making navbar more developer-focused.
Ask for GitHub stars with a link to the repository.
It does three things:
There are many things that I like about 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.
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:
Case study body:
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:
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.
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?
Let's go through these in detail.
Who are you? Why should I listen?
What is the problem really?
What does your product do and how does it work?
Speak "dev to dev"
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.
"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.
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.
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:
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.
The "Resources" tab is the most loved and hated tab for developer marketers.
Ok so the common problem is that you have lots of different resources:
You want to showcase them in the navbar but where do you put them?
Under product? Company? Docs?
How to make sure that people don't go to your blog to read about your product just to find out that you talk about the industry problems there?
Enter the "Resources" tab. The "Miscellaneous" of the navbar world.
And typically it is just crammed with all stuff that doesn't fit anywhere. Just like any respectable misc folder would. ย
How do you deal with that?
Snyk approached it in a clear and logical way:
I love this (and already stole the idea for our site).
Streamlit has an amazing explainer.
They show how to go from:
In 42 seconds.
No audio, just code and a simplified result window.
Amazing stuff.
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.
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.
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:
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.
There are a few developer experience gems here:
Also, their design is super clean, non-invasive, and simple which makes for easy content consumption and more developer love.
This is a nice little touch in the last step of the signup process.
Linear asks you to do two things:
The beauty of it is while this is an ask it is done so gracefully:
Nice and simple and I am sure it gets some folks to subscribe/follow.
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 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:
Top job on that header folks!
I love how simple this delivery is. But this is what makes it powerful:
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.
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:
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.
"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:
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.
Nice way to show code and results straight from the React docs that people love.
And this pattern can be used outside of the docs for sure.
Anyway, a classic situation:
And folks behind React docs solved it nicely by:
Not groundbreaking maybe but a beautiful implementation that is just a delight to use.
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.
I like how it has a proper "hero section" feel to it but it adds a developer-focused twist:
The rest of the Readme is great as well but the hero section is gold imho.
Gonto shared an interesting play that they tried at Auth0 when he was running growth there.
So the story goes like this:
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.
Classic widget PLG loop.
Algolia really crashed it with these. Here is how they made it so successful.
Some time ago I did some research on Algolia marketing looking for gems. Found quite a few as they are truly amazing at this.
One angle that is bringing a lot of traffic to their site is that classic PLG widget.
So what they did is:
And the sites that brought the most traffic were:
I love this tactic as it aligns:
Win Win Win
When you find those "Win Win Win" tactics/strategies you are golden.
I love this copy. It answers:
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.
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.
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:
Try something like that next time you post and see what happens.
Obviously, it is nearly impossible to do when:
But then why would you even post something?
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.
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:
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.
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:
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.
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:
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.
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:
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.
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.
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.
I love this video ad format from Hygraph.
They are reading and reacting to bad reviews.
I saw this in B2C but not in the dev tool B2B. Love it!
So basically how they did that campaign is:
Through all that, you get entertained and learn something about their product. This is such a fun format to test out!
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:
This is a job well done:
And they could have done:
This is how to promote an event. LOVED IT!
Ideating how to do dev tool billboards?
I like these from Snowflake.
Especially the customer showcase ones as the format can almost be copy-pasted ;)
One more interesting thing about those billboards though:
By doing that they seem to have billboards everywhere, fight ad fatigue, and stay top of mind.
Love it.
Beautiful mockery of classic conversion tactics from PostHog website.
So what do we have here:
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.
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:
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.
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:
Great execution. Chapeau bas Latitude.
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!