Readiness review

What actually happens on the call

Forty-five minutes, technical, no slides. It ends in one of three ways and one of them is us telling you not to buy this yet.

Last updated 20 September 2026 · Protocol v9.3

Agenda

  1. Your agent (10 min). Which warehouse, which agent framework, what it is used for, and who acts on its answers without re-deriving them.
  2. Definition ownership (10 min). Whether a named Business Definition Owner exists for the metrics in scope. This is the single strongest predictor of whether an engagement is worth running.
  3. Access (10 min). Whether we can read INFORMATION_SCHEMA and the dbt manifest, and which evidence mode fits your data constraints.
  4. The deliverable (10 min). We walk through a real report and you tell us whether it answers the question you actually have.
  5. Scope and price (5 min). A written scope follows within two business days, or a written decline with the reason.

How it can end

Scoped

You get a written scope, a fixed price and a start date. No success fee, no hourly billing.

Too early

No definition owner, or the agent has no consequential use yet. We say so, and suggest what to fix first.

Declined

Out of scope, unsupported dialect, or a conflict under the Independence Charter. In writing, with the reason.

Worth bringing

Before you book

Everything you would normally need a demo to see is already public: the report, the method, the rubric, where it fails and a verifier you can run right now. If reading those answers your question, you do not owe us a call.

Request a readiness review → Other ways to reach us

Response within one business day. target