From da6fc39ebd187724649c83ebfc395f1e0bd7a085 Mon Sep 17 00:00:00 2001 From: Ty Date: Fri, 7 Aug 2026 00:16:29 +0000 Subject: [PATCH] Restructure outline: intro value-prop + triage; #1 website monitoring only; #2 listings/public presence (incl content consistency, RACI, AI sampling); #3 packaging --- docs/DOP-BusinessReview_ty_grok_Aug062026.md | 344 +++++++------------ 1 file changed, 118 insertions(+), 226 deletions(-) diff --git a/docs/DOP-BusinessReview_ty_grok_Aug062026.md b/docs/DOP-BusinessReview_ty_grok_Aug062026.md index fa6d04a..c9b40b9 100644 --- a/docs/DOP-BusinessReview_ty_grok_Aug062026.md +++ b/docs/DOP-BusinessReview_ty_grok_Aug062026.md @@ -23,243 +23,132 @@ AI chatbots are built to give **helpful** answers. Helpful requires public infor That is not a new AI rule. It is the same foundation that made local discovery work in 2017. In 2027 it does not get replaced; it gets **amplified**. When AI is the interface, weak or conflicting public facts hurt harder. Strong, consistent, trustworthy facts become more valuable, not less. -AI chatbots are also a **moving target**. Their ranking logic and product behavior will keep shifting. You cannot lock in a permanent “optimize for ChatGPT” playbook. What *is* stable: every major system still builds discovery and recommendations on top of the same fundamentals that make human discovery possible. Own those fundamentals. Stay ready as the assistants stabilize. +AI assistants are also a **moving target**. You cannot lock in a permanent “optimize for one chatbot” playbook. What *is* stable: every major system still builds discovery and recommendations on top of the same fundamentals that make human discovery possible. Own those fundamentals. Stay ready as the assistants stabilize. **One-line value prop:** > We keep your business’s public information trustworthy, consistent, and discoverable — the same foundation that has always driven local success, and the one AI systems need to treat you as a helpful answer. -The operating documents are strong on philosophy, evidence rules, and process. What is not finished is the hard line between what you will actually check and fix, what you will only recommend, and what you will not touch. Until that line is sharp *and* the advisor standard is explicit, every engagement risks confusion or a relationship that feels transactional instead of trusted. +### How the top 3 chatbots triage local answers (mid-2026) -This document lists the open decisions in plain language. +By market share the top three generative chatbots are **ChatGPT**, **Gemini**, and **Claude**. (Siri / Apple Intelligence matters for Apple-device local discovery via Apple Business Connect, but it is not a top-3 chatbot.) + +| Assistant | How local answers tend to be built | Highest-leverage public signals | +|-----------|-------------------------------------|----------------------------------| +| **Gemini** | Heavy use of Google’s local graph | **Google Business Profile**, Maps/Places, reviews, categories, hours | +| **ChatGPT** | Bing web index + partner place data + public web | **Foursquare** places data, **Bing**-visible consistency, **business website**, directory NAP alignment (not a primary GBP pipe) | +| **Claude** | Tools/APIs + web; often Google Places when looking up locals | Google Places/Maps-aligned data, clear website, consistent public facts | + +**MVP implication:** Own the fundamentals hard — GBP craft, website facts, NAP/hours consistency, temporary-hours discipline. That serves all three. ChatGPT specifically requires not ignoring aggregators (including Foursquare) and the website. Apple Business Connect is important for Siri/Maps users but is post-MVP relative to chatbot top-3 optimization unless your market is heavily Apple-primary. + +**MVP investment focus:** GBP integrity + exposure craft · website content consistency · cross-directory NAP awareness · temporary-hours process · light AI diagnostics on ChatGPT + Gemini. +**Post-MVP:** Deeper Foursquare/Bing Places/citation hygiene · Apple Business Connect · richer site FAQ/structure · tighter sample→fix loops. + +Until the operating line is sharp (what you check, fix, only recommend, or never touch), engagements risk confusion. The sections below are the open decisions. --- -## 1. What does “we check your website path” actually mean? +## 1. Website monitoring (standalone) + +This is operational observation of the **website as a system** — not the same job as keeping website *content* consistent with listings (that sits under section 2). ### The problem -It is easy to say “we make sure customers can reach you.” -It is harder to say exactly what that includes. +“We make sure customers can reach you” is vague. Checking that a booking link loads is one thing. Testing a full booking or watching server logs is another — and that becomes a different product. -Checking that a booking link is not dead is one thing. -Confirming that a customer can finish a booking or successfully submit a contact form is something else entirely. Those deeper checks start to look like professional website monitoring products — and that is a different business. +### Practical Version 1 +Visible, explainable checks only: -Most local owners also cannot (or will not) give you server logs or complex technical access. Asking for that creates friction you do not need. +- Main booking/contact link resolves (page loads, no obvious error) +- Expected form, button, or booking widget is still present +- Primary “call us” / “book now” CTA present and pointed correctly +- Light technical health signals (e.g. robots.txt, sitemap.xml, canonicals, accidental noindex) if included in the standard checklist -### What looks practical for Version 1 -Stick to checks that are visible and explainable: - -- Does the main booking or contact link still work (page loads, no obvious error)? -- Is there still a form, button, or booking widget where there should be one? -- Does the phone number and address on the website match Google? -- Do the hours on the website match Google? -- Is the main “call us” or “book now” button present and pointed at the right place? -- Are the basic “can Google find this page?” signals in reasonable shape? - -Do **not** promise in Version 1: -- That you tested a full booking from start to finish -- That you are watching the server for errors -- That you are running a full website uptime or performance product +**Not in Version 1:** end-to-end form/booking completion testing, server-log monitoring, full uptime/performance product. ### Decisions still needed -1. Write the exact “always checked / never checked” list in language an owner understands. -2. Decide whether basic technical health items belong in the standard check (robots.txt, sitemap.xml, canonical tags, accidental “do not index”). -3. When you find a problem on the website, who fixes it — you (with access), the owner with your instructions, or a separate quote? -4. How do you prove a finding is real so you do not over-claim in the report? +1. Exact always-checked / never-checked list in owner language +2. Whether table-stakes indexability items are standard checks +3. Remediation: DOP fixes (with access), owner fixes from guidance, or separate quote +4. Evidence standard so reports do not over-claim -**Until these four are decided, the website part of the service is not engagement-ready.** +**Until these are decided, website monitoring is not engagement-ready.** --- -## 2. Listings: integrity, temporary changes, and real platform expertise +## 2. Listings and public presence + +One operating area: the public facts about the business across platforms **and** on the website as a content surface — plus how those facts show up when customers ask AI assistants. + +### 2.1 Stable vs temporary facts + +**Stable facts** (set once, then watch for drift): name, address, phone, website URL, core weekly hours, main categories. + +**Temporary / variant facts** (need a real process): holiday hours, special hours, temporary closure, reopening date, seasonal hours. Conflicting “open” vs “closed” across surfaces is exactly the quiet failure this service prevents. + +### 2.2 Process for temporary changes + +1. Owner notifies once (text, email, or short form) — not five platforms. +2. DOP updates in-scope surfaces (and flags website hours if published); records end date. +3. Restore on end date — remove temporary notice, restore normal hours. +4. Report what changed, where, when, and when it reverses. + +Without access, prepare exact changes for the owner — or obtain access first. + +### 2.3 Exposure craft (trusted advisor, not field clerk) + +Integrity is the floor. **Exposure craft** is the advisor layer: category strategy, guideline-safe description, useful attributes, service lists that match customer language, profile completeness, temporary hours handled so they help rather than confuse. Knowledge must stay current; platforms change. + +**In scope (V1 direction, with access and approval):** clear listing improvements on agreed platforms — categories, description, attributes, services, hours including temporary, core completeness. +**Out of scope or separate:** ongoing social posts, ads, full brand rewrite, photography, broad content marketing. + +Competitive context (what nearby businesses claim on their profiles) may **inform** drafts — light, local, evidence-based. It is an input, not a standalone competitive-intelligence product in V1. + +### 2.4 Website content consistency (under public presence) + +The website is another surface for the same public facts. Name, address, phone, hours, and what the business does should match the listings story in normal text (and in structured form where practical). + +This is **not** website monitoring (section 1). It is consistency of content with the rest of public presence. Especially important for ChatGPT-class systems that lean on the open web. + +### 2.5 Responsibility (RACI) — one model for facts and wording + +| Role | Responsibility | +|------|----------------| +| **Owner** | Supplies true facts; notifies temporary changes; **approves** wording and material listing changes | +| **DOP** | Monitors; drafts recommendations and listing copy (informed by craft + light competitive context); **implements** on in-scope platforms when access is granted | +| **Access** | Prerequisite for implementation — not for diagnosis or recommendations | + +Default for listing copy: **DOP drafts → owner approves → DOP implements (access required).** +Same access philosophy covers field corrections and temporary hours. + +### 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 +4. End-date restore as hard rule +5. Confirm RACI default above (draft / approve / implement / access) +6. Website content consistency: standard in public-presence work? How deep (visible text vs structured data)? +7. AI sampling method, frequency, owner language +8. Foursquare / Bing Places hygiene: MVP awareness vs post-MVP depth + +--- + +## 3. Ongoing value and packaging ### The problem -“Keep the listings consistent” is not one job. There are related jobs, and the service only works if they are clear. +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. -### Two kinds of facts - -**Stable facts (mostly set once, then watch for drift)** -Business name, primary address, primary phone, website URL, core weekly hours, main categories. -Once correct and aligned, the ongoing work is confirming they still match and catching accidental or third-party changes. - -**Temporary / variant facts (need a real process)** -Holiday hours, special event hours, temporary closure for repairs or vacation, “reopening on [date],” seasonal hours. -If Google says closed for a week but the website and other listings still show normal hours, customers get conflicting answers. That is the quiet failure this service is meant to prevent. - -### Process for temporary changes (must be spelled out) - -1. **Owner notifies you once** — simple channel (text, email, short form). They should not log into five platforms. Example: “Closed July 14–20 for flooring. Normal hours resume July 21.” -2. **You act on the platforms in scope** — update (or draft) the listings you manage; update or flag website hours if published; record the change and the end date. -3. **Restore on the end date** — every temporary change carries a return date and a follow-up to put normal hours back and remove the temporary notice. -4. **Report what was done** — what changed, where, when, and when it is scheduled to reverse. - -If you lack access, prepare the exact changes; either the owner applies them or access is granted first. - -### Exposure craft (trusted advisor, not field clerk) - -Integrity (correct, aligned facts) is the floor. -**Exposure craft** is what a trusted advisor sells: category strategy, a strong guideline-safe description, useful attributes, service lists that match how customers search, profile completeness, and temporary hours handled so they help rather than confuse. - -Owners can tell the difference: one vendor “updates the hours”; the other knows how the major platforms work in 2026 and can explain why one setup is better than another. That knowledge must stay current. Platforms change. - -### Scope boundary still required - -**In scope when access and approval exist (Version 1 direction):** -Clear, guideline-safe listing improvements — categories, description, attributes, services, hours (including temporary), core profile completeness on platforms you have agreed to manage. - -**Still out of scope or separately quoted:** -Ongoing social posts, ad campaigns, full brand rewrite, photography shoots, broad content marketing. - -Judgment recommendations should come with a short plain-language rationale so the owner can decide with confidence. +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. ### Decisions still needed -1. Which platforms are in scope for Version 1 for integrity and temporary-hours updates? -2. Is handling owner-reported temporary changes part of the standard retainer? (Recommendation: yes.) -3. Notification method for closures and special hours. -4. End-date discipline — every temporary change has a return date and a restore step. -5. State in operating docs that listing work includes exposure craft, and that current platform knowledge is an operating requirement. -6. Exact edge of craft for Version 1 (ties to sections 4 and 7). - ---- - -## 3. AI assistants and how the top 3 triage local answers - -### Landscape (mid-2026) - -By chatbot market share, the clear top three are: - -1. **ChatGPT** (still dominant) -2. **Google Gemini** (clear #2) -3. **Claude** (established #3) - -**Siri / Apple Intelligence** is important for local discovery on Apple devices (Maps, Siri, Spotlight, CarPlay) via **Apple Business Connect**, but it is not a top-3 generative chatbot. Treat Apple as a platform/local-data surface, not as a peer to ChatGPT/Gemini/Claude in chatbot rank. - -### How the top 3 triage local business answers (open-source picture) - -This is directional, based on public product behavior and partner disclosures — not internal ranking specs. It will move. - -**Gemini (Google)** -Primary path: Google’s own local graph. Local answers lean heavily on **Google Business Profile**, Maps/Places data, reviews, categories, attributes, and hours. For “near me” / local service questions, GBP completeness and accuracy are first-class inputs. Strong GBP craft is the highest-leverage investment for Gemini. - -**ChatGPT (OpenAI)** -Does **not** appear to read Google Business Profile as a primary system of record the way Gemini does. Public signals point to: -- **Bing’s web index** for real-time retrieval -- **Foursquare** place/POI data (OpenAI has a public partnership; Foursquare’s places graph feeds local results in ChatGPT search) -- Business websites and other public/verified web sources -- Cross-checks across directories; **inconsistencies** (mismatched NAP, hours) reduce confidence - -So ChatGPT is more sensitive to consistent NAP across the web, a clear website, Foursquare/Bing-visible place data, and non-conflicting public facts. GBP-only optimization is incomplete for ChatGPT. - -**Claude (Anthropic)** -When it needs local place data, public examples show use of **Google Maps / Places API** (and similar connectors) plus web retrieval. It does not appear to have a Foursquare partnership like OpenAI’s or Google’s first-party GBP integration like Gemini. Strong Google Places/GBP-aligned data and clear websites still help; fewer unique optimization levers than the other two for a typical local SMB. - -### Investment areas that roll up to the top 3 - -| Investment area | Gemini | ChatGPT | Claude | -|-----------------|--------|---------|--------| -| Google Business Profile (accuracy + craft) | Direct, highest leverage | Indirect (ecosystem / consistency) | Strong when Places tools are used | -| NAP + hours consistency across web & directories | High | Very high | High | -| Business website (clear facts, basic structure) | High | Very high | High | -| Foursquare / major place aggregators | Secondary | Material (partner data) | Secondary | -| Bing Places | Low–medium | Relevant via Bing index | Secondary | -| Reviews (especially Google) | High | Medium (via web/listings) | Medium–high via Places | -| Categories, description, services clarity | High on GBP | High on site + listings | High on site + Places | -| Apple Business Connect | Low for these three chatbots | Low | Low | - -**Foundation that serves all three (MVP):** -Trustworthy, consistent, discoverable public facts — GBP done properly, website that matches, NAP/hours aligned across major surfaces, temporary hours handled cleanly. That is the 2017-era foundation, still the right base in 2026. - -**ChatGPT-specific gap:** -Foursquare visibility, Bing-visible consistency, and website clarity matter more than a pure “perfect the GBP” strategy admits. - -### MVP vs post-MVP (tied to top-3 optimization) - -**MVP — optimize for top 3 via fundamentals:** -- GBP integrity + exposure craft -- Website NAP/hours/services clarity + basic technical health -- Cross-directory NAP consistency (including awareness of Foursquare / Bing Places where practical) -- Temporary hours process with restore discipline -- Light sampling on ChatGPT + Gemini (optional Claude) as diagnostics — not ranking claims - -**Post-MVP:** -- Deeper aggregator/citation hygiene (Foursquare, Bing Places, key vertical directories) -- Richer site FAQ + structured data aligned to service language -- Apple Business Connect (for Siri/Maps users — important locally, not for chatbot top-3 rank) -- Tighter loops from AI samples → specific signal fixes -- Only then experimental assistant-specific work — once the base no longer moves under you - -### AI sampling in the service - -Sampling a few realistic customer questions remains useful as a **diagnostic**. It is soft evidence (Tier 2): a handful of test questions does not prove a lost customer. Method, frequency, and owner-facing language still need to be fixed so it is not oversold. - -### Decisions still needed -- Exact sampling method (which tools, query templates, how results are recorded) -- Frequency on retainer -- How it is described to the owner -- Whether Foursquare / Bing Places hygiene is in MVP or post-MVP for your first markets - ---- - -## 4. Who writes the better content? - -### The problem -Fixing a wrong phone number is clear. Choosing better categories, rewriting the description, writing service lists, or improving Q&A is content and positioning work. The plan does not yet say who is responsible for creating that material. - -This is tightly linked to section 2’s exposure craft. If DOP is the trusted advisor on listings, someone still has to produce or approve the words. - -### Decision still needed -- Owner supplies the words and choices; you implement -- You draft; owner approves; you implement -- Richer content work is out of scope or quoted separately - -Also still open: making “you must give us access to make changes” an explicit condition when you are expected to do the correcting (not just recommend). - -*(Not yet fully discussed — informed by craft decisions in section 2.)* - ---- - -## 5. What is the owner paying for every month? - -### The problem -Many of the biggest problems are closer to “fix once” than “watch forever.” A report that mostly says “nothing broke this month” will not feel valuable to a lot of owners — especially before they have seen a clear win. - -Stronger ongoing angles: platforms and AI change under the business; competitors move; temporary hours and reopenings; new small failures appear; you take the monitoring burden off the owner; you bring ongoing judgment so public facts stay trustworthy, consistent, and discoverable for both people and AI. - -### Decision still needed -- How the monthly service is described and priced so it does not rest only on “we watch for drift” -- What a clean monthly report looks like when there is little to fix -- Whether some clients should be project + light follow-up instead of full retainer - -*(Not yet fully discussed.)* - ---- - -## 6. Making the website tell the same story as the listings - -### The problem -Search engines and AI systems notice when the website says one thing and Google says another. The same core facts should appear on the site — in normal text, in structured data where practical, and in simple FAQ answers where they fit. - -For ChatGPT especially, the website is a first-class signal. For Gemini and Claude it reinforces Places/GBP data. - -### Decision still needed -- Is “make the website facts match the listings” part of the standard service? -- How deep (visible text only, or also structured data)? -- Who supplies or approves new wording? - -*(Not yet fully discussed.)* - ---- - -## 7. Packaging and boundaries - -### The problem -The mission is broad (full path from discovery to engagement). The paid recurring service is intentionally narrow (monitor, diagnose, prioritize, low-risk fixes). - -That split is good. It is not yet sharp enough on website and content. When a finding needs more than a simple field change, the owner needs a clear answer: included, recommendation for you, or separate quote. - -### Decision still needed -- A short, plain list of what is always included vs always separate - -*(Not yet fully discussed.)* +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) --- @@ -268,26 +157,29 @@ That split is good. It is not yet sharp enough on website and content. When a fi | Topic | Decision | |-------|----------| | Full booking/form completion testing | Not in Version 1 | -| Watching server logs | Not in Version 1 | -| Website monitoring level | Surface checks and consistency only; language must match that | +| 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 | | llms.txt | Optional; not required for Version 1 | -| Partnership tone | Trusted advisor — platform expertise and judgment are part of the offer | -| Core value prop | Keep public information trustworthy, consistent, and discoverable — foundation for human discovery and for AI “helpful answers” | -| AI strategy | Fundamentals first; assistants are a moving target; do not chase chatbot tricks on a weak base | -| Top 3 chatbots for MVP optimization | ChatGPT, Gemini, Claude (Siri/Apple is a local-data surface, not top-3 chatbot) | -| Gemini triage | Heavy reliance on Google Business Profile / Maps | -| ChatGPT triage | Bing index + Foursquare places data + websites + directory consistency; not primary GBP pipe | -| Claude triage | Often Google Places/Maps tools + web; fewer unique levers | +| Partnership tone | Trusted advisor | +| Core value prop | Trustworthy, consistent, discoverable public information — foundation for humans and for AI helpful answers | +| 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 / closures | Explicit process: notify once → update in-scope surfaces → restore on end date | -| MVP investment focus | GBP craft, website clarity, NAP consistency, temporary-hours discipline, light AI diagnostics | -| Post-MVP | Deeper aggregators (incl. Foursquare/Bing Places), Apple Business Connect, richer site structure/FAQs, tighter AI feedback loops | +| Temporary hours | Notify once → update in-scope → restore on end date | +| Content / facts RACI (direction) | Owner supplies facts & approves wording; DOP drafts & implements with access | +| Competitive intel | Light input to drafts; not a V1 product | +| AI sampling | Sub-bullet under public presence; diagnostic only | +| 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 | --- ## Suggested next step -Lock remaining open decisions under sections 1 and 2 (website path checklist, platforms in scope, temporary-change as standard, notification method, edge of craft), then continue through content ownership, monthly packaging, and website parity the same way: one clear decision at a time, in language a non-technical owner can understand. +Lock the open decisions under **§1** (website monitoring checklist and remediation) and **§2** (platforms, temporary process, RACI confirmation, website content depth, AI sampling method), then finish **§3** packaging so included vs separate is unambiguous. ---