The standard path is Discovery Call -> Workshop -> Retainer -> First Outcome -> Operating Mode. The call confirms whether there is a real fit; the workshop turns a qualified target into a package recommendation and written assessment.
Free / 15 minutes
A short call on one named business problem: a vendor to replace, a workflow to fix, a report to trust, or a decision surface to clarify.
Free or low-cost / 2 hours
A live or Cairn-mediated working session on a qualified target. The goal is to decide what should be bought next, not to turn qualification into open-ended implementation.
Starts at $8k/month
A recurring cadence for teams that need AI decisions, outcome priorities, and small follow-through work to keep moving between larger builds. The retainer keeps context, receipts, and next-step decisions current without making activity the product.
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 that need security review, client-side operation, or a path to long-term internal ownership.
Implementation partners that have buyer access and delivery capacity but need CMD+RVL methodology, evidence patterns, and QA.
Choose the outcome first, then choose the operating mode. Mode answers where data lives, who hosts and operates the workflow, and whether the proprietary CMD+RVL stack is involved.
CMD+RVL hosts, processes, and operates the workflow in our environment, with the outcome and receipt delivered back to the client.
Fastest path when the client can share approved data and wants the lowest internal IT lift.
Requires an approved data-transfer or processing boundary before client data moves into CMD+RVL-operated systems.
The CMD+RVL stack runs inside a client-approved cloud, Databricks, Azure, or on-prem boundary where feasible.
Best when sensitive data, internal adoption, or long-term client-side operation matters.
Requires a Foundation Build, stack license, support terms, security review, and deployment coordination.
The outcome is delivered with approved standard tools and no proprietary CMD+RVL stack operating the workflow.
Useful when procurement simplicity, client tool policy, or partner-led implementation matters most.
Usually slower and less reusable because CMD+RVL memory layers are not operating the workflow; CMD+RVL still defines the receipt, QA gates, and acceptance standard where we are involved.
This is the mental model the rest of the site should reinforce.
The commercial and delivery shapes: workshop, retainer, sprint, operated monitor, client-owned outcome setup, 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, and monitors.
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 15-minute discovery call on one concrete problem. If there is a fit, the next step is a free or low-cost two-hour workshop that produces an outcome hypothesis, recommended package, and retainer fit signal.
The retainer starts at $8k/month and is outcome-scoped, not time-scoped. It gives the team a recurring AI advisory cadence, a prioritized outcome backlog, small bounded follow-through work when scope allows, and receipts and context that carry into the next decision. Larger outcomes are scoped separately when they need their own sprint.
No. Strategic POC is an enterprise exception for prospects whose expected scope is too large for a two-hour workshop to qualify. Most prospects should use Discovery Call -> Workshop before deciding on a retainer or first outcome.
No. The package is chosen separately from the operating mode. The same outcome 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 the outcome, data hydration path, delivery cadence, data sensitivity, operating mode, hosting or operation boundary, support level, and any required stack licensing.
Yes. In channel delivery, CMD+RVL can own the methodology, receipt standard, architecture, QA gates, and acceptance rubric 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 mode that makes it safe to ship.
