Tony_tech/veripath
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

§2.5 stewardship/cadence under Phase B; consolidate §2.7 decisions; rewrite §3 ongoing value as appropriate freshness SME

Browse Source
This commit is contained in:
Ty
2026-08-07 00:51:25 +00:00
parent d44c302713
commit 9bae276cf0
1 changed files with 42 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/DOP-BusinessReview_ty_grok_Aug062026.md
+42 -36
View File
@@ -126,7 +126,9 @@ After setup, most changes are seasonal or one-off: holiday hours, a temporary cl
The owner should not manage five platforms. They notify once. You handle the rest on the surfaces you manage, including putting normal hours back when a temporary change ends.
The plan acknowledges temporary hours in spirit but does not yet define intake, handoff, or speed. **Work items:** one primary way for the owner to notify you; what a complete notice includes (especially end dates); and written turnaround expectations so a holiday change does not go live a day late.
Ongoing work is **not** “edit often.” It is stewardship: update when reality changes, refresh where it builds confidence, and leave alone what should stay stable. Hours and services move when the business does. Description and empty posts should not be rewritten for activity’s sake — constant change can weaken confidence. The operating plan still needs a simple **by-element cadence** so the team does not treat every surface the same.
The plan acknowledges temporary hours in spirit but does not yet define intake, handoff, or speed. **Work items:** one primary way for the owner to notify you; what a complete notice includes (especially end dates); written turnaround expectations so a holiday change does not go live a day late; and a clear Phase B boundary (facts/hours/services only vs also posts, review replies, photo refresh).
**Who does what (after the shape is clear)**
@@ -135,48 +137,53 @@ The plan acknowledges temporary hours in spirit but does not yet define intake,
| **Owner** | Confirms true facts during setup. Approves the correction plan and material wording. Later: sends a short notice when something must change. Approves only when the change is more than a straightforward factual or temporary update. |
| **DOP** | Builds the correction plan with the owner. Monitors. Drafts and, with access, publishes on agreed surfaces. Restores temporary changes on the end date. Reports what was done. |
**Still open (so this section is not half-finished)**
1. Exact Correction Plan template fields and definition of done for Phase A
2. Primary notify channel for Phase B (and what “complete enough to act” means)
3. Turnaround targets: acknowledge, draft, execute, restore
4. Which changes, after Phase A, can run without per-item approval when the notice is complete
5. Whether website content updates stay inside ongoing public presence or are always separate
Until those are decided, control is documented; owner-facing pacing is not.
### 2.6 AI sampling (sub-bullet under public presence)
Light checks against ChatGPT and Gemini (optional Claude): a few realistic local/need queries to see whether the business appears and is described correctly.
**Diagnostic only** — soft evidence, not proof of a lost customer, not a ranking claim. Method, frequency, and owner-facing language still need to be fixed so it is not oversold.
### 2.7 Decisions still needed
1. Platforms in scope for V1 (integrity + temporary hours)
2. Temporary-change handling as standard retainer work? (Recommendation: yes)
3. Notification method (ties to Phase B intake)
4. End-date restore as hard rule
5. Correction Plan template + Phase A definition of done
6. Phase B turnaround targets
7. Standing authority after Phase A (what runs without per-item approval)
8. Website content consistency: standard in public-presence work? How deep (visible text vs structured data)?
9. AI sampling method, frequency, owner language
10. Foursquare / Bing Places hygiene: MVP awareness vs post-MVP depth
### 2.7 What still needs deciding in this section
Grouped so the open work is easy to act on:
**A. Scope**
- Which platforms are in Version 1?
- Does Phase B cover only facts, hours, services, and attributes — or also posts, review responses, and photo refresh?
- Is website content consistency part of ongoing public presence, and how deep (visible text only vs structured data)?
- Foursquare / Bing Places: light awareness in MVP, or deeper hygiene later?
**B. Phase A (setup)**
- Correction Plan template: required fields and definition of “setup is done.”
**C. Phase B (ongoing)**
- How the owner notifies you (one primary channel).
- What a complete notice must include (especially end dates for temporary changes).
- Turnaround targets: acknowledge → draft → execute → restore.
- After setup, which changes can run without per-item approval when the notice is complete.
- Simple edit policy by element (when to change, temporary vs permanent tools, when restraint is better).
**D. AI sampling**
- Method, how often, and how it is described to the owner so it is not oversold.
Until A–C are decided, control is documented; owner-facing pacing and freshness rules are not.
---
## 3. Ongoing value and packaging
### The problem
Many high-impact issues are closer to “fix once” than “watch forever.” A monthly report that only says “nothing broke” will not feel valuable — especially before the owner has seen a clear win.
Many of the biggest wins are closer to “fix once” than “watch forever.” A monthly report that only says “nothing broke” will not feel valuable — especially before the owner has seen a clear win.
Real ongoing angles: platforms and AI change under the business; temporary hours and reopenings; competitors’ public claims shift; small failures appear; you carry the monitoring burden; you keep public facts trustworthy, consistent, and discoverable for people and AI. Honest packaging should also reflect the two-phase shape in §2.5: real attention during setup, light touch after.
**What the owner should be paying for ongoing** is stewardship of public presence: accurate, consistent, and **appropriately fresh**. That includes knowing when *not* to touch something. Drift watching is part of it. SME judgment about cadence — update hours immediately, refresh photos when needed, leave the description alone unless the business has truly changed — is what makes a quiet month still worth the fee.
Honest packaging should also reflect the two-phase shape in §2.5: real attention during setup, light touch after.
### Decisions still needed
1. How the monthly service is described and priced so it does not rest only on drift watching
2. What a clean monthly report looks like when there is little to fix
3. When a client should be project + light follow-up instead of full retainer
4. Short plain list: always included vs always separate (ties to website monitoring remediation and any work beyond low-risk listing fixes)
1. How the monthly offer is described so it rests on stewardship and appropriate freshness — not only “we watch for drift.”
2. What a clean monthly report looks like when there is little to fix (stewardship summary, not an empty repair list).
3. When a client should be project + light follow-up instead of full retainer.
4. Short plain list: always included vs always separate (website monitoring remediation; posts/reviews/photos if those stay outside core Phase B; anything beyond low-risk listing fixes).
---
@@ -186,20 +193,19 @@ Real ongoing angles: platforms and AI change under the business; temporary hours
|-------|----------|
| Full booking/form completion testing | Not in Version 1 |
| Server-log monitoring | Not in Version 1 |
| Website **monitoring** | Standalone; surface path/technical checks only; language must match method |
| Website **content consistency** | Part of listings & public presence — same facts story, not monitoring |
| 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 — foundation for humans and for AI helpful answers |
| 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 |
| Gemini / ChatGPT / Claude triage | GBP-heavy · Bing+Foursquare+web · Places/web |
| Siri / Apple | Local-data surface via Apple Business Connect — not top-3 chatbot |
| Listing work | Integrity + exposure craft |
| Temporary hours | Notify once → update in-scope → restore on end date |
| Owner pacing (direction) | Two phases: Phase A structured correction plan (heavier, joint); Phase B ongoing change management of public presence (owner notifies once; DOP executes). Control exists in the plan; pacing, intake, SLAs, and Phase A template are still gaps. |
| 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 | Sub-bullet under public presence; diagnostic only |
| 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 |
@@ -207,7 +213,7 @@ Real ongoing angles: platforms and AI change under the business; temporary hours
## Suggested next step
Lock the open decisions under **§1** (website monitoring checklist and remediation) and **§2** (platforms, Phase A Correction Plan template, Phase B intake and turnaround targets, standing authority, website content depth, AI sampling method), then finish **§3** packaging so included vs separate is unambiguous.
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.
---