saascode
marketing & growth·run 241 · Jun 2026

Curatewell

A marketing context-governance cockpit that versions business definitions and taxonomies, binds them to source systems and owners, tests sampled agent answers against approved fixtures, detects semantic drift, and routes conflicts and corrections without claiming a gold set is permanent truth.

Genesis score7.06/10
Make Curatewell real.0/500
500 more votes and Curatewell is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
1Confirmed adjacent observability products
1Confirmed semantic-layer platforms
0Combined curation cockpits found
The case

The research confirms a raw data-observability product and an open semantic-layer platform, but no reviewed product joining definition ownership, versioning, LLM gold-set scoring, and semantic drift QA for marketing operations. Two of three proposed interfaces remain unverified and no structural incumbent copying cost is evidenced.

Curatewell cannot decide what an MQL, campaign, customer, attribution event, CAC, qualified opportunity, or revenue metric means. Those are organization-specific decisions with owners, effective periods, inclusions, exclusions, source hierarchy, and downstream consequences. A gold set is a versioned fixture approved for a particular question and context, not universal truth.

Schema health, semantic definition, source data quality, agent retrieval, generated answer, human interpretation, and business decision remain separate. Tests must cite the context version, permissions, dataset state, model and retrieval configuration, tolerance, reviewer, and known coverage.

Who pays — and why

Marketing operations, analytics, data-governance, and AI enablement teams responsible for shared definitions used by people and agents.

What it unlocks
A definition record with term, meaning, owner, steward, source authority, formula, dimensions, inclusions, exclusions, examples, effective period, permissions, consumers, approval, expiry, and correction
A taxonomy and context graph with campaigns, channels, audiences, products, lifecycle stages, brands, relationships, aliases, provenance, access controls, conflicts, and supersession
A versioned fixture with question, expected evidence and answer shape, permitted sources, dataset state, tolerance, prohibited inference, reviewer, rationale, coverage tag, and no permanent-truth claim
A drift case separating source-schema change, source-data anomaly, definition change, taxonomy conflict, retrieval failure, answer deviation, model variability, human disagreement, downstream impact, disposition, remediation, and retest
How Genesis scored it
7.06across seven criteria
tension 7temporal 8blindspot 5buyer 7leverage 9convergence 5why-not 7
9
Asymmetric leverage

Customer-approved definitions, fixtures, and drift history become sticky.

8
Temporal window

Growing agent use makes context ownership urgent.

5
Convergence

Several context-quality signals support the thesis without a combined product category.

Why it scored well

Confirmed observability and semantic substrates, explicit definition owners, versioned fixtures, drift cases, provenance, and downstream impact create a useful governance wedge.

What's holding it back

The buyer is broad, two interfaces are unverified, business semantics need continuing human ownership, gold sets are expensive, and data or observability incumbents can copy.

Signals detected3 sources crossed
SignalGenesis research

SignalGenesis research

SignalGenesis research

Direction briefcuratewell.md
curatewell.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.