惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

酷 壳 – CoolShell
酷 壳 – CoolShell
D
DataBreaches.Net
C
Check Point Blog
雷峰网
雷峰网
小众软件
小众软件
GbyAI
GbyAI
美团技术团队
P
Proofpoint News Feed
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
罗磊的独立博客
大猫的无限游戏
大猫的无限游戏
WordPress大学
WordPress大学
MyScale Blog
MyScale Blog
The Cloudflare Blog
阮一峰的网络日志
阮一峰的网络日志
Apple Machine Learning Research
Apple Machine Learning Research
Y
Y Combinator Blog
Jina AI
Jina AI
爱范儿
爱范儿
Last Week in AI
Last Week in AI
MongoDB | Blog
MongoDB | Blog
I
InfoQ
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 司徒正美

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How to Position Your SaaS When You're Not a Category Creator
Jake · 2026-05-09 · via DEV Community

Category creation is the positioning strategy that gets the most LinkedIn posts and works for the fewest companies.

When Drift coined "conversational marketing" in 2016, they named a problem the market had not yet labeled, built a content movement around that name, and trained buyers to evaluate the space using Drift's vocabulary. When HubSpot's co-founders coined "inbound marketing" starting around 2006, they executed the same play: defining an enemy (outbound interruption tactics), creating a term buyers adopted, and building the INBOUND conference to institutionalize it.

Both plays worked. Both required years of category education investment. Both required leadership who could function as evangelical thought leaders. And both happened when the problem genuinely had no established name.

Your product probably does not meet those conditions. That is fine. There are four other positioning archetypes that are just as effective when structurally matched to your product's DNA.

The Five Positioning Archetypes

Positioning is not a marketing decision. It is a structural consequence of what your product actually is, who it serves, and what structural advantages you hold.

1. Category Creator

You define a problem the market did not have a name for, then solve it. You teach buyers they have the problem before selling the solution.

Requires: a genuinely novel problem framing, evangelical leadership, a 3-5 year content and community investment before payoff, and funding runway to sustain education before revenue returns it.

What kills it: trying to create a category where the problem already has a name. If buyers are already searching for a solution using a competitor's vocabulary, you are not a category creator - you are a challenger who needs to win on existing terms.

Examples: Drift (conversational marketing), HubSpot (inbound marketing), Gong (revenue intelligence).

2. Challenger

You attack an established incumbent by doing what they do - but dramatically better on the specific dimensions your target buyer cares most about.

Requires: an entrenched incumbent with identifiable product weaknesses, a product that is genuinely superior on the dimensions the target persona values most, and a credible path to reach frustrated customers.

What kills it: being marginally better on many dimensions instead of dramatically better on one or two.

Examples: Figma vs. Sketch and Adobe XD. Figma launched as browser-based and multiplayer from day one, while Sketch was desktop-only and Mac-exclusive. Figma did not claim to be better on every dimension. It claimed to be structurally different on collaboration - the dimension that mattered most for distributed design teams.

Linear vs. Jira follows the same pattern: speed and opinionated workflow vs. infinite configuration overhead. For developers, Linear's positioning works because it names the specific pain - Jira's configuration complexity - and offers a structurally different approach rather than a marginal improvement.

3. Niche Dominator

You deliberately restrict your target market to a narrow vertical, use case, or workflow - and build deeper product-market fit within that segment than any generalist could match.

Requires: a target segment with distinct needs that generalist tools underserve at the product level (not just the messaging level), features deeply specific to the segment, and a segment large enough to build a real business.

What kills it: building generalist features with niche messaging. If a generalist competitor's product could serve your target segment with no modification, you are not a niche dominator - you just have narrow distribution.

Examples: Veeva in life sciences CRM (built around FDA regulatory compliance, clinical data structures, and workflows that general-purpose CRM platforms cannot address without extensive customization), Procore in construction, Clio in legal practice management.

For technical founders: niche domination is an architectural commitment, not a marketing one. If your data model, your permission system, your compliance framework, and your integration partners are all built for one vertical, a generalist competitor cannot replicate your product depth by adding a template and changing the copy.

4. Segment Specialist

You target a specific buyer segment defined by company size, sophistication, or organizational role - not vertical industry. The product is purpose-built for that segment's needs, budget, and buying behavior.

Requires: a target segment with consistently different needs from adjacent segments, pricing and packaging designed for the segment's economic constraints.

What kills it: letting your segment definition drift. Segment specialists who try to serve both SMB (small-to-medium business) and enterprise simultaneously without separate products and motions usually end up serving neither well.

Examples: HubSpot in its original form targeted SMB marketing teams - all-in-one, no-code setup, priced for SMB budgets. Gusto targets companies with fewer than 100 employees who need payroll and benefits without a dedicated HR team.

5. Platform Player

You position your product as the foundation on which other tools, integrations, and workflows are built. You are not a point solution - you are infrastructure.

Requires: a sufficiently large user base to attract third-party developers, genuine API and integration infrastructure (not just a webhook), and organizational patience for a 3-5 year platform transition.

What kills it: announcing yourself as a platform before the ecosystem exists. A platform with no third-party integrations is just a point solution with a larger vision deck.

Examples: Salesforce's AppExchange, Stripe's financial infrastructure API, Figma's plugin marketplace.

For developers: the platform play is about API surface area, not marketing. If your API docs are an afterthought, your webhook system is unreliable, and your auth implementation is non-standard, you do not have a platform - you have an API endpoint. Platforms are built by making it easier to build on your product than to build around it.

How to Choose: The DNA Alignment Map

Your positioning archetype should match your product's structural properties:

  • PLG motion pairs with Challenger or Category Creator - both require mass-market appeal and clear differentiation
  • Sales-led growth (SLG) pairs with Segment Specialist or Niche Dominator - SLG justifies the CAC (customer acquisition cost) only with high ACV (annual contract value), which requires segment-specific ROI
  • Community-led growth pairs with Category Creator - a community that owns a category's vocabulary is the most durable defense
  • Data moat points to Category Creator or Niche Dominator - the data asset defines the category or makes the vertical solution irreplaceable
  • Workflow moat points to Segment Specialist or Niche Dominator - workflows are segment-specific

If your positioning archetype contradicts your growth motion and moat type, you have a structural mismatch. It will show up as messaging that does not convert, content that does not resonate, and sales cycles where the rep spends the first call re-explaining what the product actually is.

What Makes Positioning Credible

Positioning is a claim. Claims require evidence. Three tests:

Test 1: Specificity. Can a competitor claim your positioning statement verbatim without lying? "We help teams work better" is a description, not positioning. "We are the only CRM built around FDA Part 11 compliance requirements for pharmaceutical commercial teams" is a claim a competitor cannot copy without restructuring their product.

Test 2: Provability. Can a buyer verify your key claim before they pay you? For Challengers, the structural difference must be demonstrable in a trial. For Niche Dominators, the vertical-specific features must be visible in the product, not just the messaging.

Test 3: Durability. Can a well-funded competitor copy your position in 6-12 months? Price-based positioning is least durable. Workflow-depth positioning is more durable. Network-effect and data-moat positioning are most durable - they accumulate advantages that compound over time.

The diagnostic question: Ask your last five prospects "how did you describe this product to your colleague when you were trying to get buy-in?" Their answer is your actual positioning - the words that stuck, the framing that traveled. If those words do not match your intentional positioning, the gap is the problem to fix.

Five Questions to Ask Right Now

1. Is your positioning archetype chosen or inherited? Can you name the moment your team made an explicit decision - or did the positioning accumulate from early sales calls?

2. Does your positioning make the comparison explicit? Challenger positioning requires naming what the buyer currently uses and explaining exactly why you are structurally different.

3. Can a skeptical prospect verify your primary claim without talking to a salesperson? If the proof requires a 45-minute demo, your positioning is not doing its job.

4. Does your positioning archetype match your growth motion? A Niche Dominator trying to run viral PLG will find that vertical depth and mass-market mechanics pull in opposite directions.

5. When you lose deals, what reason does the buyer give? If the loss is consistently "the other product had a feature we needed," you may be a Challenger who has not built the decisive capability yet. If the loss is "we decided to stick with what we have," your category education may not be reaching the buyer before the incumbent's status quo wins.


This is Article 7 of 8 in the SaaS Product DNA series. Next: the strategy mismatch audit - how to find the contradictions killing your growth.

If you found this useful, follow for the rest of this series. I am also building a classification toolkit that walks through all 10 dimensions with decision trees and a strategy implications matrix - details at [DNA_LANDING_PAGE_URL].