Concourse — GTM one-pager (draft, pre-launch)

One line: Concourse turns your API estate into governed Databricks agent tools — certified, audited, and composable in one round-trip.

Buyer and pain

• Buyer: platform/agent-estate owners on Databricks (enterprise + partner-built solutions); secondary: ISVs exposing APIs to agent ecosystems.
• Pain: every API an agent needs is today a hand-written UC function or an unmanaged MCP server — ungoverned, uncertified, unaudited. Estates of dozens of APIs don't get tooling at all.

What we sell

1. Factory: spec in → governed UC tools out (idempotent registration, grants-ready, AI-Gateway-visible).
2. Certification: per-tool evals (fidelity, safety, determinism) with signed evidence in a UC Volume ledger.
3. Code mode: sandboxed composition with a gated invoker — agents get multi-tool programs; owners get an audit ledger and fail-closed policy.

Why Databricks-first, why now

• UC + Unity AI Gateway + managed MCP made governance native; the missing layer is supply (estates → tools) and composition (tools → programs). Concourse is exactly that layer.
• Drives consumption: generated tools and compose runs execute on serverless — the augment-not-compete story for the Brickbuilder program.

Differentiation

• No parallel policy plane — we map to UC, never replace it.
• Evidence-backed: every claim in the pack is a signed envelope from a live free-plan run, not a demo script.
• Family stack: governed server, MCP client, evals, approvals (Tower), SLOs (Radar) — assembled, not rebuilt.

Launch gates (open)

• Name/trademark sweep (Concourse CI exists in a different category).
• External security review.
• Brickbuilder program criteria confirmation.