Marketing Management

BC-400 Level 1 Cross-Industry 73 providers 451 API surfaces 41 rated strong or better

Brand, market intelligence, demand generation, marketing operations.

Marketing Management (BC-400) is a level-1 business capability in the Cross-Industry model. The catalog holds 451 API surface(s) from 73 provider(s) that can perform some part of it, 41 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Marketing Strategy Management BC-400.10

Marketing strategy, positioning, go-to-market planning.

1 provider, 1 API surface

Brand Management BC-400.20

Brand strategy, identity, equity, governance.

2 providers, 2 API surfaces

Market Intelligence Management BC-400.30

Market research, competitive intelligence, customer insights.

7 providers, 24 API surfaces

Demand Generation Management BC-400.40

Lead generation campaigns, lifecycle marketing.

10 providers, 13 API surfaces

Marketing Operations Management BC-400.50

Marketing budget, technology, processes, measurement.

12 providers, 22 API surfaces

Digital Marketing Management BC-400.60

Web, SEO, paid media, social, marketing automation.

54 providers, 324 API surfaces

Content Marketing Management BC-400.70

Editorial planning, content production, content distribution.

17 providers, 29 API surfaces

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Marketing Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →