
A classic dev tool blog call to action that is somewhat underused these days.
Was going through Martin Gontovnikas blog and found a post from a couple of years back.
He called this "Aside CTA" and the idea is this:
Why this can work well with devs is:
Definitely a classic that is worth trying.

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.

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.

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.

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.

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!

Mux does a few things beautifully in this header.
Value proposition:
Animated visual that is really good for dev tools:

I like this Reddit ad creative that uses a classic, devy, bell curve meme.
This is a good creative to use when what you want to communicate is overcomplication. As in:
Plus, with devs, if you can make something not look like an ad you already won.
And there were a few comments suggesting just that:
LOVED HOW Flagsmith did it here:
And they got people curious to see how Flagsmith makes this Test in production claim reasonable. I'd check it out if I was working on those workflows.

With infrastructure tools, it is notoriously difficult to show people the value quickly.
To really see it they would need to set up everything at their company infra, create dashboards for their use case, and so on.
A lot of work.
That is why creating a sandbox experience is a good way of giving people a taste.
I like the way Axiom calls it a playground and says "Play with Axiom" and "Launch playground".
This copy is good because:

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!

This is a cool story coming from the GOAT of all docs. They added a signup button to their header and the conversions and revenue followed.

All they did was added a "Create Account" button and saw a huge jump in conversions.
Interestingly, Peggy shared that when they added it to Apollo GraphQL docs, signups went up by 20%.

It sounds like a good thing to try out.

Memes are good top-of-funnel, awareness-type content.
Many companies use them on socials as they can "go viral".
But.
You need to either:
I like how Datree connects it to the product here.
They are a Kubernetes configuration tool and talk about exactly that here.
They do that with jargon too "k8", "config". When used well it can help you belong to the tribe you are marketing to.

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

How to get more ROI from your dev conference booth? -> Add obvious CTAs.
Yes, giveaway stuff.
Yes, make it nice and branded.
Yes, make it funny, shareable, and cool.
But give people an easy and obvious option to give back and support you and your goals.
I really liked how Union.ai approached it at the recent MLOps World conference:
Just a nice little tactic but I bet it squeezed a bit more of that ROI juice that we all need in 2023 ;)

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.

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.

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

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.

Copy that lands makes a huge difference in dev tool website conversion.
Earthly proved it with this "tiny" change.
So I am a huge believer in good copy.
Not the clever one but the one that is written with words that your customers use.
That is rooted in product and research.
But I often hear devs or founders say things like "it's just copy".
It is not "just copy" it is your message, it is your positioning.
It is the difference between "cool, let's try it" and "now for me, whatever".
So some time ago I came across this article from the Earthly CEO Vlad Ionescu.
He shared that at some point they decided to run this A/B test with just a "tiny" change.
They changed the word "CI" -> "Build" across the homepage.
And their core website conversion doubled.
So next time you work on website copy give it some more thought and you may be surprised that "just copy" made a huge difference.

Just wanted to share this classic dev tool branding campaign.
There is even a book about this from Jeff Lawson at Twilio.
But I recently saw someone share on HN that it got changed to "How can I reduce acquisition costs by 65%". Made me a bit sad.
But perhaps after years and years of working it stopped delivering any additional brand awareness/affinity.
Could they have come up with another flavor of "Ask your developer."?
Maybe. But maybe at their levels of mind share you are playing a different game.
The good thing is, you are not at that stage ;)
And f you pull off something that is 1% of the success of that famous Twilio campaign you can make your brand noticed and remembered.
I know we are in the year of doing what brings results right now. And branding campaigns may not make the cut.
But maybe we can (and should) afford to do something that helps us deliver that pipeline next year or a year after that?

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?

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.

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

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.

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

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.

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.

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

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.

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.

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.

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.

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:
Got me hooked and kept me watching for sure.
+ funny is memorable so you will get a better recall too.

Vs pages are a classic SaaS marketing.
But I like how Ably adjusts them to the developer audience:

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.

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.

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 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:
💚 Modal solves it beautifully by going simple but smart:
It lands the message that this section should land for sure. I really like 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.

𝗛𝗼𝘄 𝘁𝗼 𝗰𝗿𝗲𝗮𝘁𝗲 𝗴𝗼𝗼𝗱 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝘁𝗵𝗮𝘁 𝘁𝗵𝗲 𝗛𝗮𝗰𝗸𝗲𝗿 𝗡𝗲𝘄𝘀 𝗮𝘂𝗱𝗶𝗲𝗻𝗰𝗲 𝗹𝗶𝗸𝗲𝘀?
The general tip is simple. Create content that the HN audience finds interesting.
𝗧𝗵𝗮𝘁 𝘁𝘆𝗽𝗶𝗰𝗮𝗹𝗹𝘆 𝗺𝗲𝗮𝗻𝘀:
But how do you actually do that?
𝗢𝗻𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗽𝗹𝗮𝘆𝗯𝗼𝗼𝗸𝘀 𝘁𝗵𝗮𝘁 𝘀𝗼𝗺𝗲 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗳𝗼𝘂𝗻𝗱𝗲𝗿𝘀 𝗱𝗲𝗽𝗹𝗼𝘆𝗲𝗱 𝘄𝗮𝘀 𝘁𝗵𝗶𝘀:
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!

Navbar is a hugely important conversion lever on the dev-facing website. I saw it move the needle by x times in some cases/conversion events.
So, what does a good one look like?
Auth0 did a great job on their developer portal. But the learnings can be applied to your marketing website too.
What I like:
That makes it easy for devs to explore. Without having to click out to see what each tab/item means. And when devs know what you mean they are more likely to actually click out. And convert.

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.

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.

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

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.

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.

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.

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.

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

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.

"32 billion reasons to check out..." - I love this ad from Aikido Security.
What I Iove the most is that it doesn't say much, it just points. I think it comes from Harry Dry or the book Made to Stick.
But the idea is that the best stories are not something you write. It is something you tell. You don't say, just point.
And this is what folks from Aikido did:
So they pointed:
Love it! Sometimes I think I live for this stuff ;)
Thank you Marie Jaksman for sharing this gem!

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.

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.

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.

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.

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.

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.

How to communicate the flexible part of your plan?
Many dev tools have 3 plans:
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.

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:

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?

A great example of a quote-style ad.
I like it because:
Great stuff.

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.

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!

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!

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.

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

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.

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.

Scrolling through many feature/capability sections of a dev tool website mostly sucks. But dropping things to make it shorter can suck even more.
This is a cool design pattern that deals with that problem.
Single section that switches subsections on scroll. And folks over at @Graphite did a great job with that on their homepage.
It works like this:
Also, I saw variants of this that also looked great:
What this design helps you achieve is:
I really like this pattern and I have already recommended it to some folks working on their sites recently.

Was scrolling LinkedIn the other day, minding my business and what do I see but a new dev marketing newsletter. DevPMM newsletter by Marek Nalikowski (dev PMM at Oxla).

In the first issue he talks about “Developer product positioning and messaging examples that slap”.
His devy explanation of positioning/messaging is just so cool. Will steal it and us it with eng founder for sure. Here it goes.
One idea that Marek goes into that I don’t see used enough is anchoring. You anchor on something your audience knows. Now classic example of “open-source Firebase alternative” from Supabase is one.
But there are other flavors of anchoring.
Funny enough just last week I talked to a marketer from one of the startups I advise about my personal framing for what they do just to see if I get it. Something along the lines of “If X and Y had a baby, that focused on Z, and had a developer experience of R”. So yeah I did anchoring positioning for myself.
Ok, I digressed. The example that made me want to share this with you is this beauty from Tinybird.
I am talking about this quote that anchors on three popular tools: ClickHouse, Supabase, and Postgres. This one sentence carries so much meaning to people who know them. Good luck landing that message in less words.
This is the tricky part though. You need to know your audience enough to know what concepts are commonly (enough) known by them to use it. So the non-dev audience will likely not get it at all. But this is ok. You should land messaging for the champion.
And Marek argues that this is how devs naturally think and talk about products.
Cannot agree more. I often ask dev founders “so what does the product do” (having read the website)? How do you explain it to dev friends? How do you explain it to other devs on a meetup or conference? Anchoring is surprisingly common in the way they explain it and very rare in their messaging.