From e18083855a09ede4834a4963df1ed55f98abef50 Mon Sep 17 00:00:00 2001 From: Ty Date: Thu, 6 Aug 2026 23:55:58 +0000 Subject: [PATCH] Expand value prop: trusted advisor, AI fundamentals, top-3 chatbot triage (ChatGPT/Gemini/Claude), MVP investment map --- docs/DOP-BusinessReview_ty_grok_Aug062026.md | 239 +++++++++++-------- 1 file changed, 140 insertions(+), 99 deletions(-) diff --git a/docs/DOP-BusinessReview_ty_grok_Aug062026.md b/docs/DOP-BusinessReview_ty_grok_Aug062026.md index c642ce2..fa6d04a 100644 --- a/docs/DOP-BusinessReview_ty_grok_Aug062026.md +++ b/docs/DOP-BusinessReview_ty_grok_Aug062026.md @@ -11,15 +11,24 @@ You have a clear problem worth solving: local businesses quietly lose customers because their digital path is broken or incomplete, and they never find out. -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 -- What you will not touch - The tone of the whole partnership is **trusted advisor**. Success depends on that. Owners should feel they are working with someone who understands these platforms at a professional level — not a junior clerk who only copies fields from one screen to another. -Until the scope line is sharp *and* the advisor standard is explicit, every engagement risks confusion, over-promising, or a relationship that feels transactional instead of trusted. +### What “trusted advisor” means here + +AI chatbots are built to give **helpful** answers. Helpful requires public information that is: + +- **Trustworthy** — accurate, not conflicting across sources +- **Consistent** — the same identity, hours, and services wherever they appear +- **Discoverable** — present and clear in the places people and systems look + +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. + +**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. This document lists the open decisions in plain language. @@ -44,7 +53,7 @@ Stick to checks that are visible and explainable: - 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 (more on this below)? +- 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 @@ -53,16 +62,9 @@ Do **not** promise in Version 1: ### 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 (tells search engines what they may look at) - - sitemap.xml (the list of important pages) - - canonical tags and “do not index” mistakes - - These are table stakes for any serious website. The current plan mentions some of them; it does not clearly make them standard, always-on checks. -3. When you find a problem on the website, who fixes it? - - You fix it (with the owner’s permission and access) - - The owner fixes it using your instructions - - It is quoted as separate technical work -4. How do you prove a finding is real (so you do not over-claim in the report)? +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? **Until these four are decided, the website part of the service is not engagement-ready.** @@ -71,143 +73,177 @@ Do **not** promise in Version 1: ## 2. Listings: integrity, temporary changes, and real platform expertise ### The problem -“Keep the listings consistent” sounds simple. It is not one job. There are three related jobs, and the service only works if all three are clear. +“Keep the listings consistent” is not one job. There are related jobs, and the service only works if they are clear. ### 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 these are correct and aligned, the ongoing work is confirming they still match and catching accidental or third-party changes. +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 the owner tells Google they are closed for a week but Bing, Apple, the website, and the booking tool still show normal hours, customers get conflicting answers. That is exactly the quiet failure this service is meant to prevent. +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 have to 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 they are published; record the change and the end date. -3. **Restore on the end date** — this is where most systems fail. Every temporary change carries a return date and a follow-up to put normal hours back and remove the temporary notice. +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 on a platform, you prepare the exact changes and either the owner applies them or access is granted first. +If you lack access, prepare the exact changes; either the owner applies them or access is granted first. -### The deeper layer: exposure craft (trusted advisor, not field clerk) +### Exposure craft (trusted advisor, not field clerk) Integrity (correct, aligned facts) is the floor. -**Exposure craft** is what a trusted advisor actually sells. +**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. -That means professional judgment on: - -- Primary vs secondary category choices and how they affect discovery -- A strong local business description — specific, credible, guideline-safe, not keyword-stuffed -- Attributes worth completing vs noise -- Service lists that match how customers actually search -- Photos and basic profile completeness that support trust -- How temporary and special hours should be handled so they help rather than confuse -- Platform guideline boundaries (so “optimization” never becomes a suspension risk) - -Owners can tell the difference immediately: one vendor “updates the hours”; the other knows how Google Business Profile works in 2026 and can explain why one category choice is better than another. - -If the partnership is positioned as trusted advisor, the person delivering the service must hold that knowledge and keep it current. Platforms change. A static checklist from last year will quietly become wrong. +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 -Expertise does not mean unlimited marketing work. - **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 the platforms you have agreed to manage. +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. -When a recommendation involves judgment (not just “wrong phone → right phone”), it should come with a short plain-language rationale so the owner can decide with confidence. +Judgment recommendations should come with a short plain-language rationale so the owner can decide with confidence. ### Decisions still needed -1. Which platforms are in scope for Version 1 for both ongoing integrity and temporary-hours updates? (Google only? Google + website? Google + Bing + Apple?) -2. Is handling owner-reported temporary changes part of the standard retainer? (Recommendation: yes — high value, low frequency, directly prevents silent loss.) -3. Notification method — one agreed way for the owner to report closures and special hours. -4. End-date discipline — explicit rule that every temporary change has a return date and a restore step. -5. State in the operating docs that listing work includes **exposure craft**, not only field matching — and that current platform knowledge is an operating requirement for anyone delivering the service. -6. Edge of craft for Version 1 — exact list of what is included vs always separate (ties to section 4 and 7). - -### Plain-language promise to an owner (target tone) - -> You tell us once when hours change for a holiday, vacation, or temporary closure. We update the listings we manage and make sure the temporary notice is removed when you reopen. We also bring real judgment to categories, description, and profile setup — so the platforms work in your favor, not just “look filled in.” You should not have to become a Google Business Profile expert yourself. +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. Checking how AI systems talk about the business +## 3. AI assistants and how the top 3 triage local answers -### The problem -The plan includes sampling a few realistic customer questions in AI tools (ChatGPT, etc.) to see whether the business shows up and is described correctly. +### Landscape (mid-2026) -That is useful. It is also soft evidence — a few test questions do not prove a lost customer. And asking the consumer app is not the same as asking the API; the answers can differ. +By chatbot market share, the clear top three are: -Right now there is no fixed method for how this sampling is done, how often, or how it is reported. +1. **ChatGPT** (still dominant) +2. **Google Gemini** (clear #2) +3. **Claude** (established #3) -### Decision still needed -- Exact method: which tools, which kinds of questions, how results are recorded. -- How often this is done on a retainer. -- How it is described to the owner so it is not oversold. +**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. -*(Not yet fully discussed.)* +### 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: confirm the right number, change it. +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. -Choosing better categories, rewriting the business description, writing service lists, answering Q&A, or improving photos is different. That is content and positioning work. The current plan does not say who is responsible for creating that material. - -The “low-risk fix” rule is intentionally narrow (one simple field at a time). Anything richer sits in a gray zone. - -This section 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. - -### Why it matters -Without a clear rule, every non-trivial Google Business Profile improvement turns into a negotiation: “Are you writing this, or am I?” +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. +- 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 — will be informed by the craft decisions in section 2.)* +*(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 early on, before they have seen a clear win. +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. -The model has stronger ongoing angles (platforms and AI change under the business; competitors move; new small failures appear; temporary hours and reopenings; you take the monitoring burden off the owner; you bring ongoing judgment on how the platforms should be set). Those are real, but they need to be packaged honestly. +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 treated as a project plus light follow-up instead of a full ongoing retainer. +- 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 Google and the other listings +## 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 (name, address, phone, hours, what you do) should appear consistently on the site — in normal text, in the structured data search engines read, and in simple FAQ answers where they fit. +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. -The plan knows this matters. It does not yet spell out a repeatable way to check it or fix it, or who does the writing when the site is thin or inconsistent. +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 does that go (visible text only, or also the structured data behind the scenes)? -- Who supplies or approves any new wording? +- How deep (visible text only, or also structured data)? +- Who supplies or approves new wording? *(Not yet fully discussed.)* @@ -216,13 +252,12 @@ The plan knows this matters. It does not yet spell out a repeatable way to check ## 7. Packaging and boundaries ### The problem -The mission is broad (help the whole path from “customer is looking” to “customer reaches you”). -The paid recurring service is intentionally narrow (monitor, diagnose, prioritize, fix low-risk things). +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 the website and content side. When a finding needs more than a simple field change, the owner needs a clear answer: “This is included,” “This is a recommendation for you,” or “This is a separate quote.” +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. +- A short, plain list of what is always included vs always separate *(Not yet fully discussed.)* @@ -235,18 +270,24 @@ That split is good. It is not yet sharp enough on the website and content side. | 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 | -| llms.txt (special file for AI) | Optional; not required for Version 1 | -| Partnership tone | Trusted advisor — platform expertise and judgment are part of the offer, not optional polish | -| Listing work | Includes both integrity (correct, aligned facts) and exposure craft (categories, description, attributes, services, hours done with professional judgment) | -| Temporary hours / closures | Require an explicit process: owner notifies once, DOP updates in-scope surfaces, restore on end date | +| 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 | +| 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 | --- ## Suggested next step -Either lock the open decisions under section 2 (platforms in scope, temporary-change process as standard, notification method, end-date rule, exact edge of craft), or finish the four open decisions under section 1 (website path). - -Then continue through the remaining sections the same way: one clear decision at a time, written so a non-technical owner (and a future team member) can understand the boundary. +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. ---