The first step should produce clarity, not a broad transformation plan. These are the two common starting points before larger scoped packages.
Free when the scope is narrow
A focused working session or tiny proof case on one real problem: a vendor to replace, a workflow to fix, a report to trust, or a decision surface to clarify.
Starts at $8k/month
An ongoing cadence for teams learning how to use AI against real operating problems. We discuss outcomes, maintain the backlog, and can use Cairn-assisted delivery for bounded lightweight work.
Each package is scoped by what the client needs to accomplish, what evidence must survive review, and how much delivery responsibility CMD+RVL should carry.
One spend line, workflow, report, or risk surface the business can evaluate quickly.
Replacing or pressure-testing a known vendor, manual process, or fragile internal workflow.
Teams that need to understand how decisions are made before automating or rebuilding the surrounding process.
Office or department files that need to become a structured data product, such as thousands of Excel files feeding comps or review workflows.
Decision-critical state that needs cadence, drift detection, alerts, webhook/API delivery, and provenance records.
Sensitive workflows where the client environment, security review, and long-term internal ownership matter.
Implementation partners that have buyer access and delivery capacity but need CMD+RVL methodology, evidence patterns, and QA.
Operating mode is separate from package choice. It answers where data lives, who operates the workflow, and how much of the CMD+RVL stack is involved.
CMD+RVL hosts, processes, and operates the workflow in our environment.
Fastest path when the client can share approved data and wants low IT lift.
Requires agreement on approved data movement and delivery boundaries.
The CMD+RVL stack runs inside a client-approved environment where feasible.
Best when data sensitivity, internal adoption, or long-term local operation matters.
Requires stack license, support terms, security review, and deployment coordination.
The work is delivered with approved standard tools and no proprietary CMD+RVL stack.
Useful when procurement simplicity or partner/subcontractor execution matters most.
Usually slower and less reusable because Cairn, memory layers, and the proprietary evidence stack are not operating the workflow.
This is the mental model the rest of the site should reinforce.
The commercial and delivery shapes: workshop, retainer, sprint, operated monitor, embedded evidence layer, or channel enablement.
The result CMD+RVL is trying to produce and defend: the workflow, monitor, report, data product, or decision surface the business actually needs.
Reusable CMD+RVL capabilities and assets used inside packages, including Signals, Data Products, Outcome API / Feature Feeds, monitors, and Cairn-assisted delivery.
Where and how the work runs: CMD+RVL-operated, client-side CMD+RVL stack, or open-source/off-the-shelf delivery.
Explore market questions before they become monitored outcomes.
Use curated, lineage-backed datasets as inputs for analytics, models, and outcomes.
Pull monitored outcomes and provenance records into downstream systems.
Browse recurring outcome examples and state-monitoring surfaces.
These are the boundaries a buyer, legal team, or delivery partner usually needs before the first scope.
Packages are how clients buy and operate work with CMD+RVL. Products are reusable capabilities and assets, such as Signals, Data Products, Outcome API / Feature Feeds, and monitors, that can power those packages.
Most clients should start with a free Outcome Workshop / POC on one real problem. If the outcome is real, the next step is usually the AI Advisory & Outcomes Retainer or a scoped sprint.
The retainer starts at $8k/month and is designed for ongoing AI learning, strategy, outcome backlog management, and bounded lightweight outcome work when the scope is small enough for CMD+RVL to handle inside the cadence.
No. The operating mode is chosen separately. Work can be CMD+RVL-operated, run with the CMD+RVL stack inside a client-approved environment where feasible, or delivered with open-source/off-the-shelf tools when that is the right procurement path.
Scoped packages are priced after discovery based on evidence surface, delivery cadence, data sensitivity, operating mode, delivery responsibility, and the level of CMD+RVL support required.
Yes. In channel delivery, CMD+RVL can own the methodology, evidence standards, architecture, and QA while a partner or subcontractor carries more of the implementation work under an agreed package model.
Bring the vendor, workflow, report, file pile, or decision surface that matters now. The first conversation is about choosing the smallest useful result and the operating model that makes it safe to ship.
