From 0edf8f83576858f7e0ec9e2456ca1c4056eff1f7 Mon Sep 17 00:00:00 2001
From: Michael Victory <michael@opencommunications.consulting>
Date: Wed, 5 Aug 2026 07:45:45 -0700
Subject: [PATCH] Process steps: discovery credits toward "the full cookbook"
 (Mike's line); stage 3 proposal -> "Writing the cookbook" (capture day + AI
 ingestion + quarterly-gathering; fixed-scope promise folded in)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---
 index.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index de6da89..7b873f3 100644
--- a/index.html
+++ b/index.html
@@ -313,11 +313,11 @@
         </li>
         <li>
           <h3>A paid discovery session</h3>
-          <p>If there's a fit, a focused few hours working together where we map how work really moves through your business — who holds what, where the judgment sits, what would break first if someone left. You leave with a written map and recommendation, yours to keep whether or not we go further: the first rough table of contents of your cookbook. Fixed fee, agreed up front — and if a project follows, every dollar of it comes off the bill.</p>
+          <p>If there's a fit, a focused few hours working together where we map how work really moves through your business — who holds what, where the judgment sits, what would break first if someone left. You leave with a written map and recommendation, yours to keep whether or not we go further: the first rough table of contents of your cookbook. Fixed fee, agreed up front — and if a project follows, every dollar of it comes off the full cookbook.</p>
         </li>
         <li>
-          <h3>A fixed&#8209;scope proposal</h3>
-          <p>You know exactly what gets built, what it costs, and what you own at the end — before any work begins. Written in plain language, not jargon. Scope changes are a conversation, not a surprise invoice.</p>
+          <h3>Writing the cookbook</h3>
+          <p>Once scope and price are agreed — written in plain language, before any work begins — we spend a day or so with the people who hold the know&#8209;how, drilling into the recipes: how a quote really comes together, what gets checked before a job ships, the calls only experience knows how to make. The methods, the ingredients, the why behind each one. Then the cookbook is loaded into your AI tools, so the systems we build cook from the real thing — and quietly gather what changes between quarterly reviews. Scope changes along the way are a conversation, not a surprise invoice.</p>
         </li>
         <li>
           <h3>A deliverable you own</h3>