Share an idea about a new concept.
Explain the concept in simple terms.
Back it up with a visualization.
I like the "hand-written" style of this viz that makes it less formal.
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:
And Export SDK executes it (almost) perfectly:
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.
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!
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.
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.
Mux does a few things beautifully in this header.
Value proposition:
Animated visual that is really good for dev tools:
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:
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.
A great example of a quote-style ad.
I like it because:
Great 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.
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.
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.
Memes that resonate with your ICP (in this case website backend devs who use PostgresSQL).
Content like this helps people find their tribe.
And then those memes can get folks to follow your account.
If you mix your content well you can then push them further down the funnel.
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.
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.
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.
Very nice design solution on the homepage.
Classic communication of the world before using your tool and the world after.
Really liked how it felt messy before.
And is nice and clean after.
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.
I love this simple design.
They show:
Simple, and powerful imho.
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.
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.
How to get people to sign up for your office hours?
Why not put it on your docs homepage?
Btw, I really like the concept of office hours.
You get your devrels or product to do those weekly and then you just have to figure out how to get people there.
Classic options are to put info in onboarding sequences, in the app, or on the website hello bar.
But Flatfile had another idea. They put it in their docs homepage header.
I find this idea brilliant as many people who browse your docs (especially for the first time) are in that evaluation mode and would actually want to do that.
Plus calls to action in the docs get more respect by design ;)
Socks as swag always work, but this twist makes it 10x better. From @Sanity 👇
So Sanity, a CMS that lives in the Next ecosystem, gave away socks at Next js conf. Nothing out of the ordinary, but it is a good idea if you have no other ideas. "People will always need socks" kind of a deal.
But.
They did a few things differently:
This is brilliant. Fun, playful.
And it helps you convey that you play nicely with the Next js stack.
What I like about it is how reusable this is for other ecosystems and tools that are just a component of a bigger stack. Kudos Sanity!
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?
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!
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.
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.
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.
This is a very nteresting approach from PubNub.
They could have published an article on their blog and posted a link to Reddit.
Instead, they just posted an entire article, 3851 words . That post got 360 upvotes and made it to the top of r/rust. Wow.
Never seen anyone do that before but I like this. It could be great:
Some things I also liked:
Super interesting approach that I want to test out myself.
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.
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.
Digital Ocean went for an ad for the Hactoberfest in a tricky place.
To keep it in the medium that fits YouTube shorts they:
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 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:
Just a very good baseline.
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.
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.
What if you not only posted entire articles on Reddit but also promoted them?
This is what WarpStream did and I like it.
A few weeks back I shared an example of a company posting not a link with a snippet but an entire article on Reddit.
WarpStream is taking it to the next level by promoting it as an in-feed Reddit ad.
I love this trend 100%:
By doing that you assume that if your piece of content gets read by the right people it will lead to business outcomes. People don't need to go to your site to be retargeted by ads and attacked by popup banners.
That is a very fair assumption, especially with devs.
But even generally in B2B SaaS and social channels like here on LinkedIn that concept of zero-click content, coined by Amanda Natividad, is gaining traction and I'm glad that it does.
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:
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%.
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.
If you want to get your post to do well on HackerNews you may want to break some "marketing rules" you'd expect to work elsewhere when it comes to titles.
And the titles are really important on HN.
People will start a discussion and fight viciously on both sides of the argument without even reading the article.
I even tested it one time by putting an article "Why people on Hacker News comment without reading" on HN. It went to the first spot in 5min and got a few people talking before it got flagged ;) The article obviously had nothing in it. Just an ask for people who clicked out not to comment saying it was empty.
The point stands though. Titles are crucial imho. They set the tone. Good titles give you a better chance.
And no, in this case, Karma didn't play a role here:
What I think mattered was the titles. Very similar theme but a vastly different vibe.
Imho this is what happened here. The Hacker News crowd lives on good hacker life stories, on feeding curiosity. On titles that don't feel like a marketer would post.
So when in doubt go understated.
btw I have a good story of helping an infra startup get to the top of HN Show if you are interested. Added a bunch of links to resources/learnings in there too: https://www.markepear.dev/case-studies/glassflow
Sometimes your pricing is just complex. But you can still make it work.
If you want devs to convert, make it possible for them to estimate the cost.
@Mux does it nicely with a calculator:
What is crucial is that the calculator dimensions need to be understandable and familiar to the reader.:
The goal of this is to make it possible for a person to get an estimate right here right now.
Not have to setup a meeting with half the team to figure your pricing out.
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
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.
Architecture diagrams are awesome.
They have this smell of value that makes you want to share them with others.
This one is particularly good-looking 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!
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.
Explain a concept clearly.
Good visual with concrete numbers makes this example easy to understand.
Because it is beautifuly explained people want to share this with their network to be perceived as helpful (and smart).
"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.
Marketing through free tools is powerful. And Auth0 implemented it beautifully.
In an old article from Gonto I read about some free tools that Auth0 created years ago.
And those tools are still generating traffic and leads today.
And they are helpful to developers and make the Auht0 brand even more appreciated by the community.
One of those tools is JSON Web Token Debugger.
So how this works for them is this:
Now, Gonto suggested that is important to do it on a separate domain to make it less promotional.
I am not sold on that especially when I know there are companies like @VEED.IO that build "SEO tool clusters" in the /tools/ subfolder of their page and crush it in search.
But either way, if you can solve a real problem your target devs have, no matter how small, you should be able to get some developer love (and $) from the value you created.
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.
I really like this Reddit ad from Sentry.
Powerful simplicity.
They don't do:
• long value-based copy
• fancy, in-your-face CTAs
• creative that feels "professional
They go for:
• focus on the pain
• creative that speaks to that pain
• low-key CTA ", get Sentry" rather than "Get Sentry Free!"
• building rapport with the dev with copy "If seeing this in React makes you 🤮"
And through simplicity and focus they deliver a message:
• Stack traces in React are not much fun
• They seem to understand that
• Sentry helps you solve that
Good format.
This has to be one of the better dev-focused headers I've seen in a while.
Headers should deliver your core product message and get people interested. That is true at any stage but early stage especially.
💡You want everyone, even those folks who just take a look and leave to remember. You want them to recall it in their next conversation around this topic.
There may be supporting messages for sure but there is always that one core thing. Make sure it lands.
In the case of Clickhouse, that core message is that they are a database that is fast at a huge scale.
Their supporting messages are:
💚And they deliver that beautifully with:
Headline
Clear as day headline speaking to value delivered at a level that builds rapport with their audience.
Not "Give users seamless web experience at scale" but "Query billions of rows in milliseconds". I like that little touch with "rows" which makes who they speak to obvious
Subhead
Subhead supporting it with "fastest and most resource-efficient DB"
+ talking about the use cases "real time apps and analytics" and it being open-source
Calls to action
These CTAs make the audience feel at home. There are docs in there + clear "we are open-source" CTA
Visual
That supporting visual is just amazing.
It shows the value in the most believable way you could deliver it here imho. Query and an Output that shows the size of the database and speed of the query
Social proof
Social proof in the navbar, almost 34k stars and a GitHub icon.
+ a way to get people to that repository, check it out and leave a star.
There is more social proof below the fold with big logos and stuff but the GitHub icon and stars make it immediately clear that this is a project that people care about.
It is remarkable how brilliantly simple it is all presented. Just a fantastic work IMHO.
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:
This is very developer-focused approach and I love 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).
VS competitor ads are hard to pull off with devs. Not impossible though. 👇
So the problem is that:
@Convex does it really nicely here:
And even though this is by a "aggressive" competitor marketing hundreds of devs liked/bookmarked this tweet.
Good job!
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.
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.
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 a solid swag copy template that resonates with devs.
"I did X and all I got was this lousy Y"
Why this works imho is:
Very solid start if you run out of ideas.
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.
Good format of the tweet copy.
Start with the hook.
Then validate it with more story.
Then open a knowledge gap with a thread.
"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.
How to design the navbar product tab? This is what @PostHog does 👇
Figuring out what to put in the navbar is tricky:
The "Product" tab is especially tricky.
It can get overloaded with a ton of content.
I like how Posthog approached it:
I like it.
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.
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.
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.
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.
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.
One of the best types of developer content is a debugging story.
"What is X" or "How to solve Y" work in some situations, especially when you focus on SEO distribution. But a good debugging story is something that even senior devs want to read.
This is an old article from the GitLab and is such a good example of thos format:
The downside of using this format is the same as with most good developer content. You need a real situation, explained by an actual dev in a technical language.
I like those sidebar CTAs from Auth0.
They go with a sticky Table of Contents which gives a better reading experience.
They put two CTAs below that TOC:
Solid job.
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.
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.
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 :)
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!
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 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.
Instead of giving away hundreds of small things that people will forget give away one thing that leaves an impression.
And a huge LEGO set is a great candidate for that one big thing. There is a big overlap between devs and folks who love LEGOs. They are both builders after in their hearts.
Now, some important considerations:
You need to commit to it too.
Don't do 3 different things like that at a conference. Focus on one play like this at a time and try other cool ideas at another conference.
Folks from Sigma Computing ticked all these boxes. Love it!
Someone shared an old but awesome article with me recently: “I answered 99 Stack Overflow questions and now 2 million developers know about my product“
And while chatGPT/Perplexity/co-pilots may be making the Stack Overflow less effective the rules of engaging in communities very much apply to your Slack/Discord/Reddit.
Also, I often talk about social listening, setting up trackers like Syften, F5Bot, or Gummysearch, and jumping into discussions around your problem space. But I haven’t really shared good examples of how people actually join in the conversation doing that. This is one of them.
So what you do is basically:
Do that enough times, all in relevant discussions, and see how folks refer to your answers and drive more product signups.
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.
Adding CTA in dev-focused articles is hard.
You don't want to be too pushy, but you do want to get conversions.
DigitalOcean strikes a great balance with its in-text article CTA design.
They make this CTA look like an info box that you'd typically see in the documentation.
It is clear that it is a Digital Ocean CTA but it doesn't feel pushy.
It feels like a piece of potentially useful information.
Love it.
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 ;)
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.
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.
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.
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.
So your differentiator is being self-hosted and you want devs to see it. This is a cool trick I saw that feeds into the way devs navigate your site.
One navbar tab devs will click on or at least hover over the docs tab.
So putting your self-hosted deployment guide in there will land.
And likely this guide sits in the docs anyway, you just extract that important piece of information and frontload it. This is exactly what @n8n did on their site and I love this.
People see it first and I am sure (many) will remember that n8n is self-hosted which is one of their differentiators. Simple and strong.
In that vein, you can frontload other important pieces like quickstart/getting started or integrations. Especially when your docs is a toggle tab and not just a clickable link.
I'd argue that having that quickstart frontloaded in the docs tab would be a smart move from n8n too. But anyhow, this is job well done.
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.
OK, the best way of getting GitHub stars is by creating a project that solves real developer problems well.
I assume you have done that already and the metric that people love to hate ⭐ is growing organically.
What do you do now?
I mean you got to ask people in one way or another.
Many companies put it in their navbars or hello bars.
Posthog adds a sticky banner at the bottom of the page that follows you as you scroll.
It also shows a start count which at their size (11k + stars) acts as social proof.
You can close it and the next time you visit the page it will be off not to push too much.
I like the concept makes sense to test it out this way imho.
How to 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.
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:
But the core idea behind making the playground your core navbar resource section CTA is just great.
A nice example of making navbar more developer-focused.
Ask for GitHub stars with a link to the repository.
It does three things:
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.
Great flow of the explainer.
Starts with the outcome "Build search UX".
Goes straight to code and 1-2-3-results format.
Explains every snippet of code as it is added.
Ends with a nicely presented result: a working search on a website.
No voiceover just code and screenshots.
And it's only 45 sec !!!
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.
Say what you do and how you do it.
What:
How:
CTA (bonus):
Vs pages are a classic SaaS marketing.
But I like how Ably adjusts them to the developer audience:
I like how this starts with a [WHAT IT IS ABOUT] scroll stopper.
That is coupled with a big block of code that has:
(presumably) when you click "See more" you get the rest of the text post.
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:
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.
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.
Just an awesome billboard/ad format for a dev too company coming from Vercel.
What I like about it is:
Simple and beautiful.
Btw, they actually run similar ads on Reddit and it makes a lot of sense IMHO.
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!
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.