6 Positioning Briefs from Public SaaS Companies, Annotated

Most positioning guides cite Slack's "where work happens" and move on. The brief itself — the internal document that produced the public messaging — is treated as proprietary and the reader never sees one. Below are six reconstructed briefs from public SaaS companies, pieced together from 10-K filings, investor day transcripts, product-launch pages, and careers-page language. They're as close as an outsider can get to what the internal doc said. Each is annotated against the five-layer positioning framework. The pattern at the end is the one every durable brief shares.

1 · Datadog (as of 2024 investor day)

Category: "Observability platform." Clean noun, industry-validated, Gartner-blessed.

Audience: "DevOps, SRE, and security engineers at technology-forward enterprises."

Problem: "Modern applications produce more signal than any team can correlate manually."

Alternative: Named explicitly — Splunk (incumbent), New Relic (challenger), "in-house observability stacks built on open source."

Claim: "Single platform for logs, metrics, and traces with unified correlation. Teams running on three-plus separate tools see median incident resolution time drop 40%."

What the brief gets right: Every layer is named, including the do-it-yourself alternative (open-source stacks). The claim is falsifiable and includes a benchmark. Most companies at Datadog's scale skip Layer 4; Datadog treats it as load-bearing.

2 · Monday.com (circa 2023 S-1 amendment language)

Category: "Work operating system." Category-creation language. Still not fully validated by analysts but widely adopted by buyers.

Audience: "Cross-functional teams at companies of any size." The weakest layer.

Problem: "Work happens across dozens of disconnected tools; teams spend more time coordinating than doing."

Alternative: Jira (adjacent), Asana (direct), spreadsheets (do-nothing).

Claim: "Customizable workspace templates across departments, designed for non-technical owners."

Monday's Layer 2 is the reason the TAM story stays contested. "Any company, any team" is a pitch deck's Layer 2, not a positioning brief's Layer 2.

What the brief gets wrong: The audience layer. "Companies of any size" is a growth-story claim, not a positioning claim. The sales motion has to re-create the ICP conversation on every call because the brief doesn't anchor it.

3 · HubSpot (inferred from 2024 analyst day and careers-page language)

Category: "CRM platform." Ceded the category-creation move years ago; now competes inside the Salesforce-defined category.

Audience: "Marketing, sales, and customer service teams at companies ranging from SMB to mid-market, who want an integrated suite rather than a best-of-breed stack."

Problem: "Best-of-breed stacks produce data silos and force teams to pay for integration work they don't want to own."

Alternative: Salesforce (scale incumbent), Pipedrive (SMB challenger), stacking point-tools.

Claim: "Integrated suite with a free-tier entry point; teams using the full suite see 30% shorter ramp time than multi-vendor alternatives."

What the brief gets right: Explicit concession of category leadership to Salesforce, then differentiation on integration cost and suite economics. The claim references a shorter ramp time — a metric the buyer can verify. Layer 4 is sharp.

4 · Snowflake (inferred from 2024 proxy and investor materials)

Category: "Data cloud." Started as "cloud data warehouse" and deliberately broadened.

Audience: "Data and analytics teams at enterprises with multi-source data estates."

Problem: "Data lives in too many places; moving it for analysis is expensive and slow."

Alternative: Databricks (challenger), Redshift/BigQuery (hyperscaler alternatives), on-premise legacy.

Claim: "Separate storage and compute, pay for what you use; customers migrating from on-prem see 3–5× faster query performance."

What the brief gets right: The category pivot from "warehouse" to "data cloud" is visible in the brief's shape. It's a Layer 1 move that took three years of content and customer proof to cement. Most companies attempting a Layer 1 pivot don't sustain it for long enough.

5 · Asana (circa 2022 investor materials)

Category: "Work management." Narrower than Monday's "work OS," which limited TAM but sharpened the brief.

Audience: "Marketing, ops, and IT teams at mid-market to enterprise companies."

Problem: "Teams don't have a single source of truth for what's on deck, who owns it, and when it ships."

Alternative: Monday.com, Jira, email-and-spreadsheets.

Claim: "Goal-to-task traceability; teams using Asana for quarterly planning see a 20% reduction in missed deadlines."

What the brief gets mixed: Strong on Layers 2 and 3; weak on the durability of Layer 5. Asana's positioning has held on the customer side but eroded on the competitive side as feature parity set in. A reminder that Layer 5 needs to be rebuilt on a non-product differentiator once the product differentiator is copied.

6 · Twilio (inferred from 2024 10-K and developer-documentation framing)

Category: "Customer engagement platform." Shifted from "communications APIs" — a Layer 1 pivot that took four years.

Audience: "Developer and product teams at companies where programmatic customer communication is a core competitive surface."

Problem: "Customer communication is fragmented across channels; each channel has its own integration tax."

Alternative: Sinch, Bandwidth, in-house build on carrier APIs.

Claim: "Single API for every channel the customer prefers; developers ship multi-channel campaigns in days, not quarters."

What the brief gets right: Layer 2 is specific — "developer and product teams," not "companies." The alternative layer includes in-house builds, which is the real competitor for Twilio's ICP. Most briefs would have written "competing APIs" and missed that the buyer's default is often to build it themselves.

The pattern across durable briefs

Four things recur in every brief that has aged well (5+ years of continuity in the claim):

• Layer 2 is specific enough to disqualify. Datadog, Twilio, and Snowflake all name a specific role or team type. HubSpot names a posture ("suite-over-stack"). Monday names "any team of any size" — and that's visible in the positioning churn ever since.

• Layer 4 includes the do-nothing or do-it-yourself alternative. Datadog, Twilio, and Asana all name the in-house build or spreadsheet alternative explicitly. Briefs that skip this layer lose to "we'll build it internally" at a rate that shows up in churn data.

• Layer 5 references a specific, falsifiable outcome. 40% faster incident resolution, 30% shorter ramp, 3–5× query performance. Adjective-claims age poorly; benchmark-claims survive.

• One layer gets a deliberate pivot over 2–4 years. Snowflake pivoted Layer 1. Twilio pivoted Layer 1. HubSpot pivoted Layer 4 (from "replace Salesforce" to "integrated suite for SMB"). Durable briefs are not static — but the pivot is always one layer at a time, executed over multiple product cycles.

The brief every PMM should print out and pin to the wall is not one of these six. It is the composite — Datadog's Layer 4 discipline, HubSpot's Layer 1 humility, Twilio's Layer 2 specificity, and Snowflake's patience on the pivot. Every durable positioning brief in B2B SaaS is some version of that composite. The ones that aren't — the "any team, any size" Layer 2, the unnamed alternative, the adjective-claim — will need a refresh within eighteen months.