This is one of my favorite our dev tool vs competitor blog posts.
With these pages, you want to explain when you are better.
But you don't want to berate your competitor.
And above all, you want to help people make a decision.
Chances are (almost 100% ;)) that you are not better for every use case. And your developer audience knows it.
But there should be use cases, tool stacks, or situations when you are the best option.
Talk about those. Dev to dev.
@Convex did a great job in this post that I think can be a template for how to write these:
- They start by saying what is the same. That sets the context.
- Then they say good things about their competitor. Shows respect and understanding
- They follow by listing 3 key differences/situations when you should consider them
- And they go ahead and explain each of these differences deeply
After reading that post you are fairly convinced that if your situation matches the one described and if it makes sense to use it.