Replace decision log table with closing: business-level next steps + human-heavy/automation-light scalability constraint

2026-08-07 00:58:06 +00:00
parent 9bae276cf0
commit 6271632e71
1 changed files with 13 additions and 23 deletions
@@ -187,33 +187,23 @@ Honest packaging should also reflect the two-phase shape in §2.5: real attentio
 ---
-## What has already been decided in this review
+## What is left before process and code
-| Topic | Decision |
+The operating docs already give you control: evidence, approval before publish, low-risk fixes, and access before changes. This review sharpened the **offer and the gaps**: trusted-advisor tone, fundamentals that AI systems still need, two-phase owner pacing, and ongoing value as stewardship of public presence — not only “nothing broke.”
 |-------|----------|
 | Full booking/form completion testing | Not in Version 1 |
 | Server-log monitoring | Not in Version 1 |
 | Website **monitoring** | Standalone; surface path/technical checks only |
 | Website **content consistency** | Part of public presence — same facts story, not monitoring |
 | llms.txt | Optional; not required for Version 1 |
 | Partnership tone | Trusted advisor |
 | Core value prop | Trustworthy, consistent, discoverable public information |
 | AI strategy | Fundamentals first; assistants are a moving target |
 | Top 3 chatbots for MVP focus | ChatGPT, Gemini, Claude |
 | Listing work | Integrity + exposure craft |
 | Temporary hours | Notify once → update in-scope → restore on end date |
 | Owner pacing | Two phases: Phase A correction plan; Phase B ongoing change management of public presence |
 | Ongoing value (direction) | Stewardship of public presence — accurate, consistent, appropriately fresh; knowing when not to edit |
 | Competitive intel | Light input to drafts; not a V1 product |
 | AI sampling | Diagnostic only under public presence |
 | MVP focus | GBP craft, website content consistency, NAP consistency, temporary-hours discipline, light AI diagnostics |
 | Post-MVP | Deeper aggregators, Apple Business Connect, richer site structure/FAQs, tighter AI loops |
---
+**What still has to be locked at the business level** (before you write detailed process or ship product code):
-## Suggested next step
+1. **Version 1 scope** — Which platforms; whether Phase B is facts/hours/services only or also posts, reviews, and photos; how deep website content consistency goes.  
 2. **Phase A deliverable** — A Correction Plan template and a clear “setup is done” line.  
 3. **Phase B operations** — How the owner notifies you; turnaround expectations; what can run without per-item approval after setup; a simple edit policy so freshness helps and over-editing does not hurt.  
 4. **Packaging** — How the monthly offer is described and priced around stewardship; what is included vs always separate; when a client is project-only instead of retainer.  
 5. **Website monitoring boundary** — Exact always/never checks and who fixes what when something fails.
-Lock **§2.7 groups A–C** (scope, Phase A template, Phase B intake/SLA/cadence), then finish **§3** packaging so the monthly offer matches the stewardship story and included vs separate is unambiguous.
+Until those are decided, engineering and playbooks will guess at the product.
 **Important constraint:** Version 1 is **human-heavy and automation-light**. Judgment, copy, approvals, and platform work still run through people. That protects quality and the trusted-advisor promise. It also **limits how fast you can scale** client count without more skilled capacity. Do not plan growth as if this were a self-serve software product; plan it as an expert service with tools underneath. Automation can expand later — it should not be assumed as the Version 1 delivery model.
 **Suggested sequence:** Lock the five business items above → write the Correction Plan template and Phase B intake/SLA rules into the operating docs → only then invest in automation where it clearly removes load without removing judgment.
 ---