Category creation, rebranding, and opinionated software in B2B SaaS

Executive overview

Most B2B startups face a binary-seeming choice: compete in an existing category or build a new one. The answer hinges on three signals — whether customers have budget against the category, the words they use to describe their pain, and whether competitors already exist.

Building a category is not a one-time decision. Companies often operate inside an existing category while quietly constructing a bigger one in parallel.

The strongest brands fuse company values directly into visual identity and language — so every customer touchpoint reinforces the brand without training.

When to create a new category — and when not to

• New category is worth pursuing when: no existing category captures the product's scope, customers lack a budget line but can be educated to create one, or the product is genuinely disruptive.
• Validate against three signals: existing analyst/directory classification, the words customers use unprompted, and whether a budget line already exists.
• Greenhouse tried "recruiting optimization platform" — customers kept calling it an ATS regardless; they abandoned the new category and instead elevated the value of the existing one.
• Competition entering a new category is a signal of validation, not a threat — a category doesn't exist until multiple companies claim it.
• Once a company is well-established, category creation rarely generates new business; it's a growth-stage lever, not a mature-stage one.
• If you're squarely inside an existing category with little differentiation, category creation effort won't be fruitful.

How to build a category in practice

• Start with intensive customer conversations — listen for how buyers describe their pain, not how you'd describe your solution.
• Run parallel tracks: stay optimized for existing categories while building thought leadership around the new one.
• Engage analysts (Gartner, Forrester) and directory sites (G2, Software Advice) early — they shape enterprise buyer perception and must be persuaded to recognize the new category.
• Invest heavily in content marketing and PR to test whether positioning resonates and to educate buyers that a budget-worthy category exists.
• Category creation follows market inflection points (e.g., COVID accelerating distributed work) more than individual company strategy.

Rebranding: when and how

• Rebrand before scaling too far — the cost of changing a brand grows with headcount, contracts, and market recognition.
• The trigger: if the name is too literal or too small for the product's potential, it will cap growth (RealtimeBoard → Miro).
• Preserve brand equity by nodding to original elements — Miro's yellow M echoed the yellow post-it of RealtimeBoard.
• Treat rebranding as a product development process: sprint teams, owners per workstream, Agile cadences, customer feedback loops.
• Involve the whole company — at ~100 people, everyone has a stake; transparency prevents resistance.
• Name changes are significantly harder than visual refreshes: legal, contracts, URLs, product, all collateral must move simultaneously.
• Luck is a real factor — Miro's domain transferred 48 hours before launch with all materials already printed.

Building a durable brand

• Brand and product are co-equal — a strong brand cannot save a weak product, and a great product without brand investment leaves loyalty on the table.
• Build a brand system, not just a logo: logo, color palette, typography, illustration style, photography guidelines, voice and tone.
• Embed company values directly into visual identity so brand behavior is automatic, not trained — Miro's four letters each mapped to a distinct value and visual behavior.
• Values must be simple, memorable, and non-generic; too many or too long and no one internalizes them.
• The aspiration: a "lovemark" — a brand people feel emotionally committed to, not just aware of.

Opinionated software

• Opinionated software enforces best practices or structured workflows rather than offering unlimited customization.
• Two origin paths: (1) digitize an existing best practice that lacks tooling (Atlassian + Agile), or (2) teach a better way of working the market hasn't yet adopted (Greenhouse + structured recruiting).
• Structured recruiting at Greenhouse built a specific pipeline and interview kit format — reducing bias and improving transparency because the system required it.
• Pando (Gago's current startup) takes the same stance on performance management: requiring transparent leveling, competency frameworks, and mutual accountability between managers and employees.
• Fixing pay gaps at the compensation layer is a symptom fix; the root cause is biased evaluation and progression — opinionated software addresses that root.