first principles
DevTools GTM / Why Us positioning

Why Us? Why It Matters for DevTools—and How to Get It Right

Understanding your product is not the same as choosing it. Why “Why Us” matters, how twelve DevTools companies made their case, and what you should do.

By Himanshu Saxena19 min read

A developer understands your product. They agree the problem is real. They may even like the demo. Then comes the question your feature list has not answered: why should we choose you?

Why your tool instead of a competitor? Why not keep the scripts they already have? Why trust your team with something they will have to operate, explain to colleagues, and possibly migrate away from later?

That is the job of “Why Us.” Not a company biography. Not a row of logos. A clear reason to choose your product over the buyer’s actual alternatives—and enough evidence to make that reason believable.

For a growth-stage DevTools company, this answer cannot live only in the founder’s head or in the best salesperson’s pitch. It needs to survive on the website, in technical content, in a demo, and in the material a buyer shares with their team.

This guide covers three things: why that answer matters, how twelve DevTools companies made their case, and what you should build for your own company.

Why “Why Us” matters

Understanding the category is not the same as choosing your company

“Monitor your applications” tells a buyer what category you belong to. It does not explain why they should replace their current monitoring setup with yours. “Fast, scalable, developer-first” does not help much either: other vendors can say the same words.

A useful Why Us answer makes the difference concrete. Honeycomb connects its approach to investigating production questions that fixed dashboards did not anticipate. Temporal connects durable execution to the founders’ work on earlier workflow systems. Linear explains its view of how teams should build software, then makes that view visible in the product.

These are different arguments. Each gives the buyer something more specific to evaluate than a category promise.

Adopting a DevTool puts work and risk on the buyer

A new tool can mean a migration, another dependency, training, a security review, and an ongoing bill. The engineer recommending it may also become the person colleagues call when it breaks.

Your answer needs to address that decision, not simply make the company sound impressive. Relevant experience helps explain why you understand the problem. A product demonstration helps show that your approach works. A customer with a similar environment helps the buyer judge whether it could work for them.

A famous employer on a founder’s biography is not enough. The missing sentence is: what did that experience teach you, what did you build differently because of it, and why does that difference matter to this buyer?

The buyer has to make your case when you are not in the room

An engineer may try the tool, but a platform lead, manager, or security reviewer can still need a reason to approve it. If the champion can only repeat “the demo was good,” you have left them with a weak argument.

Give them a case they can carry: the problem, the relevant difference, the proof, and the conditions under which your product fits. This is why Why Us belongs across the buying journey—not buried on an About page.

The point is not to tell a more flattering story about your company. It is to make the buyer’s choice easier to understand and defend.

What a good Why Us answer contains

Use this sequence:

Buyer’s problem → what the alternatives miss → your different approach → evidence → next step.

Your team’s experience belongs in that sequence when it explains the approach. It is supporting evidence, not a substitute for customer value.

PartWhat it needs to answerWhat to avoid
ProblemWhich buyer, doing which job, runs into what difficulty?A broad claim such as “infrastructure is broken.”
AlternativesWhat do they use now, and where does it fall short for this use case?Pretending every competitor is bad or the buyer has no existing solution.
DifferenceWhat have you done differently, and what does the buyer gain?A feature list with no connection to the problem.
CredibilityWhy should they believe you can deliver that difference?Job titles, customer logos, or adjectives without an explanation.
Proof and next stepWhat can they inspect, try, or verify?Asking for a sales call before offering evidence for the claim.

You do not have to win every use case. Saying where your approach is a good fit—and where it is not—makes the answer more useful.

How 12 DevTools companies made their case

These examples draw on company writing, founder accounts, documentation, repositories, and customer stories. They show how the companies explain and support their case, not proof that a particular message caused their growth. The lessons below are recommendations for applying the pattern, not claims about the companies’ internal marketing plans.

Honeycomb: Explain the problem differently, then show the product consequence

What they did. Honeycomb’s founders connected the product to their experience debugging complex production systems. The launch described event-driven debugging and flexible exploration. Their writing and the book Observability Engineering developed the underlying argument: engineers need to investigate questions they did not know to ask in advance.

How this answers Why Us. The founder experience is relevant because it explains a product choice. The reason to consider Honeycomb is not merely that the founders worked in operations. It is that their approach to investigation addresses a limitation a buyer may recognize in a dashboard-led workflow.

What you should do. Name the limitation in the buyer’s current approach. Demonstrate a task your different design makes possible. If your claim is about debugging an unexpected failure, show that investigation—not a generic tour of charts.

Original launch · Founder account of debugging in production · Observability Engineering

Temporal: Make relevant experience specific

What they did. Temporal’s history names the workflow systems its founders worked on: Amazon’s Simple Workflow Service, Microsoft’s Durable Task Framework, and Uber’s Cadence. That history connects to the problem Temporal addresses—keeping long-running application workflows recoverable across failures.

How this answers Why Us. “We have built workflow systems before” is stronger when the reader can see which systems, what problem persisted, and how that experience relates to the current product. The timeline gives a buyer a reason to investigate the team’s approach to a difficult infrastructure problem.

What you should do. Replace “decades of experience” with the work that matters. Name the failure mode, your team’s responsibility, and the resulting design decision. Then offer a current test: previous experience does not remove the need to evaluate today’s product.

Company history and timeline · Cadence repository · Early customer testimony

ClickHouse: Put the workload behind the claim

What they did. ClickHouse’s engineering history describes the analytics demands of Yandex.Metrica and the storage decisions that led to a column-oriented database. ClickBench gives readers benchmark methods and scripts they can inspect and reproduce.

How this answers Why Us. The original workload explains why the design exists. The benchmark gives “fast” something more useful than an adjective: queries, configurations, and test conditions that an evaluator can compare with their own needs.

What you should do. If performance is your difference, publish the conditions and method. Explain which workloads benefit from your approach. Include versions, hardware, cache state, concurrency, and cost assumptions where relevant; a number without those details is a weak basis for choosing a database.

Engineering history · ClickBench · Methods and scripts

Sentry: Show the useful work that came before the pitch

What they did. David Cramer describes Sentry as a project he started to solve his own problem: understanding application errors without digging through logs. The Disqus account describes a later production chapter. The public project gives developers something to inspect and use beyond the founder’s recollection.

How this answers Why Us. The story starts with a recognizable engineering job, then points to software built to do it. Other developers’ participation adds context, but the product remains the strongest way to examine the claim.

What you should do. Start with the task your team struggled with. Show what you built, what changed when other teams used it, and how the buyer can try it now. Explain the current relationship between the public project and the commercial offering, including licensing and operating responsibilities.

Founder retrospective · Sentry at Disqus · Repository and license

incident.io: Connect the origin story to an everyday workflow

What they did. incident.io’s founders describe working together at Monzo and building a Slack integration to reduce the coordination work placed on incident leads. The company’s incident management guide teaches the work around the product, while its founding account explains the workflow behind the original approach.

How this answers Why Us. “We have been on call” becomes relevant when it explains why response activities sit where the team already coordinates. The story connects experience to a design decision and a practical benefit the buyer can test.

What you should do. Show where your product removes work from an existing process. Use a realistic walkthrough—from declaring an incident to assigning roles and following up—rather than relying on “built by engineers, for engineers.”

Founding account · Monzo Response repository · Incident management guide

LaunchDarkly: Give buyers a distinction they can use

What they did. Edith Harbaugh described release problems from a product management perspective; John Kodumal brought an engineering perspective. LaunchDarkly’s explanations distinguish deploying code from releasing a feature to users.

How this answers Why Us. That distinction makes the value of feature flags understandable across two roles. Engineering can discuss deployment while product can discuss audience and timing. The origin story supports the argument, but the argument is about control over a release.

What you should do. Find the decision your buyers currently bundle together or struggle to explain. Show how your product changes it. Give your champion language they can use with colleagues, then demonstrate the workflow behind that language.

Early founder interview · Deployment versus release · Technical walkthrough

PostHog: Make your decisions visible, including the uncomfortable ones

What they did. PostHog’s handbook, launch discussion, and founder retrospectives explain why the company exists and how its product decisions changed. Its public history includes the original emphasis on data control and the later move away from paid self-hosted deployments.

How this answers Why Us. A buyer can examine the team’s reasoning rather than taking “transparent” on trust. Publishing a reversal also makes it possible to judge whether the current direction matches what the buyer needs.

What you should do. Explain a meaningful decision, the alternatives you considered, and the tradeoff you accepted. Keep historical claims separate from the current offer. Openness helps only if the buyer can still find a clear answer about what you support today.

Company history · Why PostHog exists · Original launch discussion

Linear: Let the product demonstrate your point of view

What they did. Linear publishes a method for how teams plan and build software. Its design notes connect broad ideas about craft to specific interactions—for example, a contextual menu that exposes commands and keyboard shortcuts together.

How this answers Why Us. The company does not have to leave “quality” as a vague promise. A reader can examine the method and experience a design choice that reflects it. The product gives the point of view something concrete to rest on.

What you should do. If your difference is developer experience, choose a repeated task and show what is better about it. Explain the tradeoff behind the interaction. Let people try it before asking them to agree that your product is intuitive.

Linear Method · Contextual-menu design notes · Building at the early stage

Grafana Labs: Show how you fit the buyer’s existing world

What they did. Grafana’s history connects the project to making operational data accessible and interactive. The repository and data-source documentation show what users can connect and explore. The company’s documentary gives the community a place in that history.

How this answers Why Us. Community and project history provide context. The practical question for a buyer is whether Grafana helps them use the data they already collect. Documentation and integrations make that fit inspectable.

What you should do. Translate “ecosystem” into supported sources and real workflows. Show a buyer connecting something they already use. Be clear about permissions, maintenance, and the boundary between community software and paid services.

Company history · Data-source documentation · Story of Grafana

HashiCorp: Pair a track record with clarity about commitments

What they did. HashiCorp’s founding announcement introduced Mitchell Hashimoto as Vagrant’s creator and maintainer. Its published philosophy and Terraform documentation explain a workflow-oriented approach. Later licensing changes also became part of the public record buyers need to consider.

How this answers Why Us. A maintained project demonstrates work before the company pitch. Clear workflows help buyers understand the approach. But confidence in engineering does not settle questions about licensing, commercial terms, or the cost of leaving.

What you should do. Use your track record to support capability, not to avoid uncomfortable adoption questions. Put current terms, supported versions, and exit options beside the product argument. These are part of the choice, too.

Founding announcement · Design philosophy · Terraform workflow · License change

What they did. Modal presents cloud compute through a Python-oriented developer experience. Its company overview connects that experience to a custom filesystem, container runtime, scheduler, and image builder. Technical posts and cold-start documentation explain the implementation and its tradeoffs.

How this answers Why Us. “Simple” is supported by an explanation of the infrastructure beneath it. The documentation also distinguishes startup behaviour and resource costs, helping the buyer evaluate the promise rather than just admire it.

What you should do. When you hide complexity from users, show enough of the mechanism to make the abstraction credible. Demonstrate the workflow with realistic dependencies. Explain where latency, configuration, or cost can change the result.

Company and architecture · Modal is a computer · Cold-start documentation

Vercel: Separate the reason to try from the reason to buy

What they did. Next.js gives developers a framework they can inspect and use. Vercel’s platform adds a deployment workflow, including preview environments that teams can use to review changes before production. Its launch and rebrand writing explain those related but distinct pieces.

How this answers Why Us. Framework experience can introduce a team to the company. The commercial case still needs to explain what the platform adds. Familiarity with Next.js is not, by itself, an answer to why a team should choose Vercel for hosting.

What you should do. If a free project brings people in, make the paid value explicit. Show the workflow improvement, who benefits, and what other deployment options remain. Do not assume project adoption automatically establishes the case for a purchase.

Next.js launch · Vercel rebrand · Deployment environments · Sonos customer workflow

What these examples have in common

The strongest pattern is not “tell a founder story.” It is connect a reason to choose with something the buyer can examine.

  • Experience explains a decision. Temporal’s lineage and incident.io’s operating experience matter because they relate to the problem and the product—not because a biography is inherently persuasive.
  • A point of view becomes visible in the product. Honeycomb’s investigation model, LaunchDarkly’s release distinction, and Linear’s design choices give the buyer something to evaluate.
  • Claims have supporting material. ClickHouse offers benchmark methods. Modal explains implementation details. Public projects let readers inspect useful work.
  • The buyer’s choice stays central. PostHog’s current offer, HashiCorp’s terms, and Vercel’s platform value still need scrutiny. A good story does not erase a poor fit.

Borrow the connection between the claim and the proof. Do not borrow another company’s biography or assume its public messaging caused its revenue.

What you should do: build your own Why Us case

1. Start with a real choice your buyers face

Read recent sales notes, trial feedback, and conversations with customers who chose another option. Ask:

  • What were they using before they considered us?
  • What made them look for a change?
  • What almost stopped them from choosing us?
  • What did successful customers find valuable after adoption?

Choose one priority buyer and use case. “Why should a platform team choose us instead of maintaining its current scripts?” is a better starting question than “What is our brand story?”

2. Find the decision behind your difference

Interview the founder, engineer, maintainer, or implementation lead who did the relevant work. Ask what they tried, what failed or became expensive, and what they built differently as a result.

Capture a specific connection: we learned X, so we chose Y, which helps this buyer do Z.

If the answer stops at “we worked at a large company,” keep asking. What did the person actually own? Which constraint does the buyer share? Can you point to the resulting product behaviour?

3. Attach proof to the exact claim

Your claim is about…Build or collect…Let the buyer…
Recovery and reliabilityA runnable failure scenario and execution historyInterrupt the workflow and inspect what happens.
PerformanceBenchmark scripts, configurations, and resultsCompare the workload and rerun a relevant test.
Developer experienceA realistic task walkthrough or working trialComplete the task and judge the effort.
AdoptionA customer account with a similar team and workflowUnderstand what changed and what the migration required.
Control and flexibilityCurrent deployment, export, and licensing documentationCheck their options before committing.

A logo does not prove a workflow improved. A benchmark does not prove every workload will be fast. Match the evidence to the claim and state the relevant limits.

4. Write the short answer before the long story

Use this working template. It is a starting point, not wording to publish unchanged:

For [buyer] dealing with [specific problem], [current alternative] becomes difficult when [constraint]. We built [different approach] so you can [valuable outcome]. Our experience with [relevant work] led to [product decision]. See [proof], or try [specific test] to decide whether it fits your environment.

Illustrative example for a fictional workflow tool—not a claim about a real product:

Your billing workflow crosses several services. If a worker stops halfway through, your team has to work out what completed before retrying. We built persistent workflow history so developers can inspect progress and resume supported workflows after an interruption. That design came from dealing with partially completed jobs during a migration. Run our sample billing workflow, stop the worker, and check both the execution history and billing ledger when it resumes. The sample uses idempotency keys for billing calls; that integration requirement still matters.

This example names a problem, a design choice, and a test. It does not claim to eliminate every failure or guarantee every integration.

5. Put the answer where the decision happens

WhereWhat belongs there
Homepage or use-case pageThe buyer’s problem, your relevant difference, and a direct link to the strongest proof.
About pageThe experience and decisions behind the product, with dates and supporting links where available.
Technical content and docsHow the approach works, where it fits, and what the evaluator should test.
Founder posts and talksOne useful lesson or decision, linked to the deeper explanation or demonstration.
Customer storiesThe customer’s situation, alternatives, adoption work, and observed change—not just praise.
Sales follow-upThe evidence for this buyer’s stated objection and an agreed evaluation step.

Keep the central argument consistent, but do not paste the same biography everywhere. A technical evaluator needs detail; an internal champion needs a concise explanation they can share.

6. Check whether buyers understood the case

Give the draft to people who match your target buyer. Ask them, without supplying the answer:

  • What is the main reason to choose this product over what you use now?
  • What makes that reason believable?
  • Where would you expect this product not to fit?
  • What would you need to verify next?

If they repeat “fast and developer-first,” your difference is still vague. If they understand the difference but do not believe it, improve the evidence. If they believe it but do not care, revisit the buyer and problem before polishing the copy.

A practical first month

Use this as a suggested sequence, not a promise of results in four weeks.

WhenFocusWhat you should have at the end
Week 1Review buyer objections and interview the people behind one relevant product decision.One priority use case, its actual alternatives, and a proposed reason to choose you.
Week 2Build or verify the proof and write the short answer.A draft Why Us block and one supporting demo, technical article, or customer account.
Week 3Ask target buyers to explain the case and attempt the next step.Revised wording, missing evidence identified, and a useful evaluation action.
Week 4Publish across the relevant pages and sales materials.A consistent argument, an owner for keeping it accurate, and a plan to review buyer response.

Start with one reason you can substantiate. A page with one clear argument and strong proof is more useful than six claims that all sound like everyone else.

How to tell whether it is helping

First check comprehension: can the buyer explain why your product is different and when that difference matters?

Then look for a meaningful next step: a relevant team trying the demonstrated workflow, testing with its own data, sharing the evidence internally, or completing technical validation. Page views and social reactions can show attention; they do not establish that the argument helped someone choose.

For a causal claim about conversion, compare message variants in a controlled test with a predefined audience, outcome, and observation window. At low traffic, buyer interviews and observed evaluation tasks can help you improve the message, but treat them as directional evidence rather than a measured revenue effect. Guide to controlled online experiments

Keep the distinction clear: the company examples show what was published; your own buyer response tells you what to improve; a valid experiment is needed to isolate an effect.

Frequently asked questions

Is Why Us the same as a founder story?

No. A founder story can explain relevant experience, but Why Us answers the buyer’s choice. If the history does not connect to a product difference and customer value, it belongs in a biography rather than carrying the sales argument.

Is this just an About page exercise?

No. The detailed history can live on the About page, but the reason to choose you should appear wherever buyers evaluate the product: use-case pages, technical content, demos, customer stories, and sales conversations.

Do we need famous founders or big customer logos?

No. You need relevant work and evidence. A small team can publish a useful design explanation, a runnable example, or a documented customer workflow. Recognizable names may prompt interest; they do not replace proof of fit.

Should we name competitors?

Start with the alternatives buyers actually consider. Those may be a competitor, an internal tool, open-source software, or doing nothing. Name specific products when the comparison is accurate and useful. Explain where your approach differs without inventing weaknesses or claiming you are best for every situation. April Dunford on differentiation and alternatives

What if our product does not have a clear difference yet?

Do not manufacture one in copy. Talk to customers about why they chose you and what they value in use. Test whether that reason matters to more buyers with the same problem. If you are still discovering the buyer and use case, treat Why Us as a hypothesis to test—not a finished positioning statement.

The takeaway

A good Why Us answer lets a buyer say: they understand our problem, their approach differs in a way we care about, and we can check the evidence.

The twelve companies above offer different ways to make that case. Your job is to find the one your own product can support—and make it clear enough that a customer can repeat it without you in the room.