Data cleaning
Profile, normalize, deduplicate, and prepare the approved source data.
Expansion offer · one business domain
Operational Context Foundation
An Operational Context Foundation is a trusted data and context layer for one business domain. Croox uses it when fragmented sources, inconsistent definitions, missing lineage, or unreliable permissions begin limiting several operational systems—not as the default first purchase.
Starting scope and price
One-domain Context Foundations start at $25,000. The final scope depends on source count, data condition, permissions, refresh requirements, historical migration, and the number of systems that need governed access.
Several business domains, enterprise-wide governance, major legacy replacement, regulated-data controls, or high-volume infrastructure are scoped separately.
What the foundation includes
Standard definitions
Document shared entities, fields, metrics, meanings, and ownership.
Pipelines
Move and synchronize approved data on the required operating schedule.
Lineage
Record where operational facts came from and how they were transformed.
Permissions
Limit access by role, purpose, environment, and approved system boundary.
Quality monitoring
Track freshness, completeness, validity, drift, and known data failures.
Context access
Provide governed search, retrieval, or application access where useful.
Why this is an expansion offer
Most companies should begin with one valuable operational constraint. That first workflow shows which data actually matters, which definitions conflict, which exceptions recur, and which evidence must be controlled.
A broader foundation becomes justified when several approved systems repeatedly depend on the same unreliable domain data. Croox does not recommend a large context project simply because information is fragmented.
How the Croox Console supports it
The Croox Console can expose source freshness, quality checks, failed synchronizations, permissions, lineage, review queues, and system dependencies for the approved domain. It provides operational visibility; it does not replace the underlying governance and ownership decisions.
Foundation boundaries
One defined domain
For example: customers, service delivery, projects, proposals, or reporting—with an accountable business owner.
Approved source systems
Only the sources, fields, historical range, and refresh rules included in the agreed scope.
Observable quality
Named checks, thresholds, owners, escalation paths, and acceptance criteria.
Controlled consumers
Defined operational systems, people, or approved interfaces that may use the context.
Operational Context Foundation questions
Is this required before a Controlled Production Pilot?
No. Most pilots should validate and build around one workflow first. A separate foundation is useful only when shared data problems are already limiting several systems or make the first workflow unsafe to deploy.
Is this the same as a data warehouse?
Not necessarily. The engagement may use an existing warehouse, database, search index, or other approved infrastructure. The focus is trusted operational context, clear ownership, quality, lineage, permissions, and reliable access.
Does every foundation use AI?
No. Cleaning, synchronization, definitions, quality, lineage, and access may be deterministic. AI-assisted search or retrieval is added only when it serves an approved operating need.
How does this relate to Context Intelligence?
The Context Intelligence methodology defines the facts, rules, exceptions, relationships, evidence, and approvals that reliable actions need. The foundation implements the governed data layer for one domain.