Market pillar · v0.17.1

competitor Competitor

Competitor profile.

$id · https://corpospec.com/schemas/v0.17.1/competitor.schema.json

Fields

Field Type Required Description
as_of IsoDate yes ISO 8601 date (YYYY-MM-DD).
category string yes
description string yes
id PathRef yes Path-based cross-reference relative to .corpospec/ root. Pattern: `^[a-z0-9_-]+(/[a-z0-9_.-]+)+$`
layer integer yes Competitive tier in this company's layered market model. A lower number denotes closer competition; `1` is typically the direct head-to-head layer, `2` adjacent, `3` aspirational reference, etc. The exact meaning is company-specific.
name string yes
relationship CompetitorRelationship yes Relationship classification of a competitor.
sources string[] yes
website string yes Primary public website URL.
acquirer string? —
category_representative boolean? — `true` when this competitor is the canonical representative of its category — the name an investor or customer reaches for first. At most one competitor per category should set this to `true`.
competitive_advantages string[] —
core_features string[] —
custom CompetitorCustom? —
founded string? — Year (or year-month) the company was founded. String rather than `IsoDate` because sources report at mixed precision (`"2013"`, `"2026-02"`, `"2024-10-09"`).
funding CompetitorFunding? —
github string? —
headquarters string? —
integration_opportunity string? —
legal_name string? —
notes string? —
planned_features string[] —
pricing CompetitorPricing? —
product CompetitorProduct? —
shutdown_date string? — Year-month (or full date) the company shut down, if applicable. String for the same mixed-precision reason as `founded` (e.g. `"2024-12"`).
status string? —
strategic_relevance string? —
strengths string[] —
target_market CompetitorTargetMarket? —
team_notes string? —
team_size integer? —
technology object? — Technology stack — keys are layer names, values are descriptions.
threat_level ThreatLevel? — How severe a threat this competitor poses to the company's wedge. Separate from `layer` (which measures closeness) because a distant competitor can still be highly threatening, and a close competitor can be strategically irrelevant.
traction CompetitorTraction? —
weaknesses string[] —
why_we_win string? — Short statement of the structural reason the company wins against this competitor. Contrast with `strategic_relevance` (which explains *why* we track them) and `competitive_advantages` (which is a feature-level list). One sentence; pitch-ready.

Definitions

Shared types referenced within this schema.

CompetitorCustom
Typed custom extension data for `Competitor`.
type: object
CompetitorFunding
Competitor funding information.
type: object
CompetitorFundingRound
Funding round details for a competitor.
type: object
CompetitorPricing
Competitor pricing model.
type: object
CompetitorPricingTier
A pricing tier in a competitor's pricing model.
type: object
CompetitorProduct
Competitor product information.
type: object
CompetitorRelationship
Relationship classification of a competitor.
CompetitorTargetMarket
Competitor target market.
type: object
CompetitorTraction
Competitor traction metrics.
type: object
EuDataResidency
EU data residency offering details for a competitor.
type: object
IsoCurrency
ISO 4217 currency code.
pattern: ^[A-Z]{3}$
IsoDate
ISO 8601 date (YYYY-MM-DD).
type: string
PathRef
Path-based cross-reference relative to .corpospec/ root. Pattern: `^[a-z0-9_-]+(/[a-z0-9_.-]+)+$`
pattern: ^[a-z0-9_-]+(/[a-z0-9_.-]+)+$
ThreatLevel
Threat level a competitor poses. Ordered from least to most urgent.

Reference in your YAML

# yaml-language-server: $schema=https://corpospec.com/schemas/v0.17.1/competitor.schema.json