Operational records stay where they already live.
Give Marketo, Salesforce, and every AI one vocabulary.
Krel maps the fields your systems already have, helps RevOps approve what Pipeline, MQL, Revenue, and Attribution mean, and publishes one governed context contract downstream tools can consume.
Your systems keep the records. Krel governs their meaning.
Krel is the control plane between the GTM data you already own and every AI, report, and workflow that needs to understand it.
One versioned contract for GTM business meaning.
Approved context ships with lineage, owners, and definition versions.
Krel does not replace your warehouse, move customer records, or become another attribution dashboard.
See where every definition comes from—and prove when it is safe to use.
Krel connects the business map, field-level definition work, and a repeatable proof scorecard through one governed model. These are captures of the working product, not concept art.
Build a metric like a sentence.
Start with the business intent, select compatible fields from the live catalog, add plain-language conditions, and review what Krel will publish.
- Search Source → Object → Field
- Type-aware calculations and conditions
- Plain-English review before approval
Pair marketing activity with revenue authority.
Validate encrypted Marketo credentials, discover marketing structure, pair it with Salesforce opportunity authority, and review changes without exposing secrets in the browser.
- Encrypted server-only credentials
- Marketo + Salesforce metadata
- Durable sync and schema history
Make the handoff between systems visible.
See which system owns marketing activity, which one owns revenue, how Krel resolves their shared meaning, and exactly what downstream agents receive.
- Explicit marketing and revenue authority
- Inspectable metadata-to-context flow
- Approved outputs separated from drafts
Turn trust into an observable buying decision.
Fix the buyer questions up front, capture a baseline, run the governed context, and review whether each answer was grounded—or correctly refused—with field lineage attached.
- Agreed baseline and current evaluation suite
- Field-lineage references on every grounded answer
- Durable human pass or needs-work verdicts
From raw metadata to trusted answers.
Every stage remains inspectable: connect, map, define, review, and distribute.
Connect the metadata
Discover the fields, objects, and structures in Marketo and the rest of your GTM stack without retaining unrestricted customer records.
Map the business
Relate real source fields to the entities and concepts your teams use, with every connection visible and reviewable.
Define what is true
Build metrics from guided choices and actual fields. Krel generates the technical logic and keeps lineage in sync.
Prove and publish
Benchmark the questions that matter, then publish only approved context—with field lineage, ownership, and definition versions attached.
Krel learns your business language—not your customer records.
Krel connects to Marketo and Salesforce through dedicated integration users, encrypts credentials, and stores discovered metadata, schema history, decisions, and safe diagnostics. Raw lead and opportunity records are not retained by default.
Prove the value before committing to the platform.
The paid proof is fixed-scope; platform plans are annual and anchored to connected systems, governed domains, and operating requirements—not database rows or AI tokens.
Paid proof
For a RevOps team proving that governed context changes real outcomes.
- Marketo + Salesforce metadata
- 20 agreed GTM questions
- Baseline and final scorecard
- 50% credited to onboarding
Core
For one GTM domain keeping two production systems aligned.
- Marketo + Salesforce metadata
- Definitions, lineage + drift
- Context API and service keys
- Paid-proof scorecard
Scale
For teams expanding the governed-context operating model with implementation support.
- Everything in Core
- Additional managed source catalogs
- Custom evaluation suites
- Priority implementation support
Enterprise
A design-partner scope for custom connector, deployment, and governance requirements.
- Everything in Scale
- Custom connector development
- Architecture and retention review
- Contracted roadmap and support terms
Give every AI and report the same approved definition of pipeline.
Connect the systems, agree on the questions, and leave with a reviewed scorecard—not another open-ended data project.




