Developers love your CLI. But then procurement places you in an RFP beside a legacy vendor with 200 sales reps and a category name that doesn't fit. You lose deals you should be winning because buyers lack a name for what you built – so they choose the nearest wrong one. We define the category, create proof points that stand up to security review, and get analysts and buyers adopting your language rather than theirs.
The Challenge
Developers understand it. The person signing the check doesn't.
Your CLI or SDK spreads through GitHub stars, Discord, and word of mouth among engineers who instantly understand what it does. But the VP Eng or CISO approving the six-figure contract wasn't in that conversation.
You get placed in a category designed for somebody else's product
Without a name for what you do, procurement and analysts file you under the nearest legacy label – observability, security, DevOps tooling, whatever's closest. That category has incumbents with entrenched budget lines, existing vendor relationships, and feature checklists your product wasn't built to win on. You end up defending against a scorecard designed for a different architecture.
Each competing feature launch chips away at your differentiation
In infra and dev tooling, feature parity moves fast – what took you 18 months to build, a well-funded competitor ships in a quarter once they see it working. If your pitch is 'we do X better,' that gap closes and your only defense disappears.
Analysts and communities default to the company that named the space first
Gartner, Forrester, ThoughtWorks Radar, and the influential voices in your developer community all need a name to organize the market around.
How We Can Help
We begin with a working session, not a workshop. Your founder, head of product, and whoever leads developer relations work with us for two to three days. We're mapping three things simultaneously: what your architecture genuinely does differently on a technical level, the job developers are actually hiring your tool to perform, and where existing category language falls apart when it's applied to your product.
Next, we draft category candidates and pressure-test each one with three audiences separately, since they don't react to the same language. Developers need a name that can survive a Hacker News thread – specific, technically credible, and free of marketing fluff. Buyers and procurement need one that maps neatly to a budget line and security review checklist.
After we settle on the category, we create the proof architecture: a point-of-view document explaining why the old category falls short for modern use cases, a comparison framework that centers your product's real strengths rather than mirroring a competitor's feature list, and messaging a sales engineer can use during a technical eval without sounding like marketing copy dropped into a demo script.
Execution moves forward on two parallel tracks. The developer-facing track appears in docs, changelogs, README positioning, conference talks, and community channels – places where you earn credibility by being useful, not by repeating a tagline.
We measure this differently from a standard brand engagement. We don't track awareness lift. We track whether your category language appears unprompted in inbound demo requests, whether sales reps stop wrestling with the 'how is this different from X' question and begin answering it with your framing, and whether an analyst or competitor adopts your term instead of a generic one.
Here's what separates this from a branding agency engagement: we embed. You won't receive a strategy deck at the end of the engagement followed by a wave goodbye.
We intentionally remain fractional, too. You don't need a full-time category strategist on your payroll for this – you need someone who has done it before, joins the room for the sprint that counts, and then shifts to an advisory cadence once the category is established and your team is ready to run with it.
What we deliver
- Category definition document – the name, the one-sentence definition, and the underlying architectural or workflow distinction it's built on
- Dual-audience proof framework – separate but consistent messaging for developer-facing channels and buyer/procurement-facing channels
- Competitive displacement narrative – a comparison structure that reframes the buying decision around your category instead of matching a legacy vendor's checklist
- Analyst and community briefing kit – the document set used to introduce the category to analysts, influential community voices, and press
- Sales enablement language – objection-handling scripts and eval talking points built from the category definition, tested against real deal feedback
If a developer can describe what you do in one sentence, but your sales team takes three slides to explain it to a buyer, the issue isn't positioning—it's a missing category.
Our Methodology
Days 1-30 focus on diagnosis and definition. We interview your founders, top sales reps, and several customers who evangelize your product without prompting – they often already use language for the category that your official positioning hasn't yet captured. We also audit every place where your product is currently compared with something else: G2 category pages, competitor battlecards, analyst reports, and RFP templates you've answered. By day 30, we have a category name, definition, and initial proof points, tested internally against your team's hardest objections.
Days 31-60 focus on building and pressure-testing. We write developer-facing and buyer-facing versions of the narrative, create the comparison framework, and test it with real prospects during live sales conversations – not focus groups. This is where category language either holds up with a skeptical technical buyer or fails, and we'd rather learn that in week 6 than after relaunching the website. We revise it around what actually resonates on those calls.
Days 61-90 cover rollout and instrumentation. We introduce the category language across the website, deck, docs, and outbound messaging at the same time, then establish tracking that shows whether it's working – inbound language matching your category terms, changes in competitive-deal win rates, and sales cycle length for evals where reps use the new framing versus the old one. By day 90, your team owns the motion; we continue with lighter advisory check-ins while the category faces the next round of competitor moves.
Our Approach
The initial 30 days are intensive – plan for two to three working sessions each week with founders, product, and whoever leads developer relations or sales. We don't send over a questionnaire and return a month later; we join your Slack, listen to your sales calls, and review support tickets to uncover the language developers already use for the problem you address.
By day 30, you'll have a category name and definition ready to test. Days 31-60 move to a lighter but still hands-on rhythm, with weekly working sessions while we develop the proof architecture and test it in live deals and developer conversations. During this phase, we sharpen the category around what truly persuades a skeptical buyer rather than what merely sounds good in a room without stakes.
Days 61-90 focus on rollout across your GTM surfaces – website, deck, docs, and sales enablement – along with the first instrumentation pass to determine whether the language is taking hold. We remain embedded throughout this phase because rolling out a category always reveals objections and edge cases no one anticipated during strategy.
After 90 days, most clients transition to a fractional advisory setup – a few hours per week or one monthly working session – to keep the category focused as competitors respond and the market changes. We don't vanish when the sprint ends; category design is a position you maintain, not a one-off document. Engagements generally cost $8K-$20K/month, based on team size and how directly you want us involved in execution (content, sales enablement, analyst outreach) versus advising your in-house team.
- Sales conversations shift from feature-by-feature comparison to category-framed evaluation, shortening the objection-handling portion of technical evals
- Developer community and buyer-facing messaging use the same underlying definition instead of two disconnected narratives
- Analyst and press mentions start using your category term instead of defaulting to an adjacent, more crowded category
- Sales team stops improvising an answer to 'how is this different' and starts using a consistent, tested framework
If your developer tools company needs category design leadership, we should talk.
Expand your marketing team output with our experts
Let us take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.
Frequently asked questions
What does category design cost for a developer tools company?
Fractional engagements generally cost $8K-$20K/month, depending on company size and how much hands-on execution you want from us compared with strategic guidance for your internal team. Most companies begin with the core 90-day sprint, then shift to a lighter monthly retainer to keep defending the category as competitors respond.
How soon can we see results from category design?
By day 30, you'll have a named category and pressure-tested proof points, but category design compounds – it's not a launch-day event. Look for early signals within the first 60-90 days: sales reps adopting the new framing without prompting, inbound demo requests mentioning your category language, or changes in how competitive deals are assessed.
Can this work with our current product marketing and DevRel team?
Yes – and it must. Category design that exists only in a strategy document no one uses will die within a quarter. During the sprint, we embed with your product marketing, DevRel, and sales teams, join their planning, and deliver language they can put directly into docs, talks, and sales calls.
What makes this different from engaging a branding or messaging agency?
A branding agency usually provides a positioning deck and new tagline before moving on to another client. We remain embedded throughout the sprint and rollout, refine the category using real feedback from sales calls and developer pushback, and create a dual-audience proof framework that both a technical buyer and working engineer consider credible – not merely polished copy.
How is ROI from category design measured?
We measure leading indicators rather than vanity metrics: whether inbound demos begin mentioning your category language without prompting, whether win rates change in deals where your category framing replaces a legacy comparison, and whether sales cycle length shifts in evals where reps use the new narrative instead of the old one. We establish this tracking during the first 30 days, so you're monitoring real signals from day one rather than waiting on a brand survey that says nothing about revenue.
Does category design make sense for every developer tools company?
No. It's designed for companies from Series A through the growth stage, typically with $5M-$100M ARR, that already have developer adoption and product-market fit but lose deals or see them slow down because buyers default to comparing them with the wrong category.
