194 lines
15 KiB
Markdown
194 lines
15 KiB
Markdown
# Digital Operations Partner
|
|
|
|
## Canonical Whitepaper v1.0
|
|
|
|
Status: Phase 1 (Business Definition) complete. Zero validated client engagements at time of writing. This document is a fully reasoned thesis, not a proven model. See Section 10 for what's actually been tested vs. what remains hypothesis.
|
|
|
|
---
|
|
|
|
## 1. The Core Thesis
|
|
|
|
Local service businesses are silently losing customers they already earned not because they're bad at their trade, but because the digital pathway between a customer's decision to visit and their actual arrival is full of quiet, undetected failure points.
|
|
|
|
A wrong phone number sits uncorrected for months. A canonical tag error suppresses indexing since the day a website launched. An AI assistant asked "who's a good plumber near me" doesn't mention a business that would have been a perfect fit. None of these show up as complaints. There's no error message for a customer who searched, found nothing useful, and quietly went to a competitor. The business owner never learns what didn't happen.
|
|
|
|
Digital Operations Partner exists to catch these failures before the business would ever notice them on their own, prove that the failures were real, fix or recommend fixing the ones within scope, and monitor continuously so new ones don't sit undetected the same way the last ones did.
|
|
|
|
Working definition:
|
|
|
|
> We continuously prevent silent customer loss for local businesses by making sure customers can find, trust, and engage the business, and that search engines and AI systems can find, understand, and accurately represent it, often before the business would ever notice something was wrong.
|
|
|
|
This is a working definition, not a final brand statement it's precise enough to guide scope decisions, not necessarily the sentence used in a sales pitch.
|
|
|
|
---
|
|
|
|
## 2. The Problem, Named Precisely
|
|
|
|
Silent Customer Loss is the umbrella term for customer acquisition problems that occur without the business owner clearly seeing the loss. It splits into two distinct categories, because they require different detection methods and support different strength of evidence:
|
|
|
|
### Customer Path Leakage
|
|
A customer has interest or intent, but digital friction prevents them from contacting, booking, visiting, or otherwise engaging the business.
|
|
|
|
*Examples:* incorrect phone numbers, broken booking links, wrong hours, failed contact forms, confusing service information, inaccurate listings.
|
|
|
|
### Discovery Failure
|
|
A potential customer never meaningfully encounters the business because customers, search engines, or AI systems don't find, understand, surface, or accurately represent it.
|
|
|
|
*Examples:* weak local visibility, incomplete entity signals, missing service clarity, absence from AI answer samples, poor structured information, inconsistent citations.
|
|
|
|
The distinction matters operationally: Path Leakage tends to produce strong, verifiable evidence (a wrong number either is or isn't live). Discovery Failure tends to produce weaker, sampled evidence (an AI system either did or didn't mention the business in a handful of test queries, which isn't the same as proving it never would). The evidence model in Section 4 exists specifically to keep these from being confused with each other in front of a client.
|
|
|
|
---
|
|
|
|
## 3. Mission Scope: Broad Mission, Narrow Contract
|
|
|
|
Two competing framings were seriously considered:
|
|
|
|
- Narrow mission only the path *after* a customer has already decided to engage (post-decision friction only).
|
|
- Broad mission the full pathway from discovery through action, including how AI-mediated and traditional search surface the business in the first place, and how competitors and market context affect that.
|
|
|
|
Resolution: broad mission, narrow contract scope. The company may identify any digital issue that affects customer acquisition, visibility, trust, or conversion discovery is not artificially excluded just because it happens before a customer has consciously decided anything.
|
|
But the *recurring paid service* only covers monitoring, diagnosis, prioritization, reporting, and approved low-risk optimization. Anything larger is a separate, explicitly quoted project never silently absorbed into the retainer.
|
|
|
|
This is the load-bearing distinction that prevents scope creep without pretending discovery-stage problems don't exist or don't matter.
|
|
|
|
---
|
|
|
|
## 4. The Evidence Model
|
|
|
|
This is one of the most important structural decisions in the entire business, because it's what prevents the company from becoming another agency that overclaims value it can't actually prove.
|
|
|
|
### Tier 1: Verified Evidence
|
|
Concrete, timestamped, observable, or instrument-backed findings. May be presented to a client as a confirmed issue.
|
|
|
|
*Examples:* wrong phone number, incorrect business hours, broken booking link, broken contact form, incorrect listing data, an indexing problem, a metadata or canonical tag issue, missing/incorrect Google Business Profile data.
|
|
|
|
### Tier 2: Indicative Evidence
|
|
Sampled, directional, or probabilistic findings that suggest risk or opportunity but don't prove a specific lost customer. Must be presented as directional risk or opportunity, never as confirmed loss.
|
|
|
|
*Examples:* absence from a sample of AI-generated answers, AI misrepresentation, weak entity clarity, inconsistent service descriptions, thin FAQ coverage, missing structured data, a competitor appearing more consistently in AI answer samples.
|
|
|
|
### Assignment Authority
|
|
Agents may propose an evidence tier for a finding. A human reviewer approves the final tier before it's used in anything client-facing, during Version 1. Two default rules protect against overclaiming:
|
|
|
|
- Ambiguous findings default to Tier 2 until a human confirms otherwise.
|
|
- A rejected Tier 1 proposal defaults to Tier 2, unless the reviewer discards the finding entirely or sends it back for more evidence.
|
|
|
|
The practical rule of thumb in the field: if you can point at a timestamp, a screenshot, or a specific broken link, it's probably Tier 1. If you're describing a pattern across a handful of AI queries, it's Tier 2 say so, and don't round it up.
|
|
|
|
---
|
|
|
|
## 5. Operating Rule: Reconnaissance vs. Execution
|
|
|
|
> Agents may detect and draft. Humans approve before publish.
|
|
|
|
This applies to anything that would publish to a client-facing surface: Google Business Profile edits, review responses, Q&A answers, business or service descriptions, hours, phone numbers, booking links, website changes, directory or citation updates.
|
|
|
|
Unrestricted for agents: scanning, comparing, gathering evidence, drafting recommendations or proposed fixes, summarizing, flagging.
|
|
|
|
Graduation threshold: a specific task type may only bypass human approval after a documented reliability run of at least 100 completed tasks with zero errors, *for that exact task type.* Reliability on one task never transfers to another. Until that threshold is met and documented, human approval is required before anything publishes.
|
|
|
|
Delegated access, practically speaking: for early clients, "approved low-risk optimization" does not require building OAuth integrations or API automation. It can mean literally being added as a manager on a client's Google Business Profile the agent detects and drafts, a human logs in and clicks publish by hand. Real API-level automation is a legitimate later decision, made *after* enough proof-of-concept engagements show which corrections are common and low-risk enough to be worth automating not before.
|
|
|
|
---
|
|
|
|
## 6. Service Domains
|
|
|
|
### 1. Customer Path Integrity
|
|
Ensures customers can find, trust, contact, book, visit, or otherwise engage the business without preventable digital friction. GBP accuracy, listings/citations, booking and contact pathways, service clarity, reviews and reputation signals.
|
|
|
|
### 2. AI Visibility Integrity / AEO
|
|
Ensures search engines and AI systems can find, understand, and accurately represent the business entity clarity, structured information, AI-answer representation.
|
|
Explicit non-guarantee: this domain improves the clarity, consistency, and trust signals AI-assisted discovery systems may use; it does not guarantee placement, citation, ranking, or recommendation by any AI system.
|
|
|
|
Client-facing term: AI Visibility or AEO (Answer Engine Optimization). GEO (Generative Engine Optimization) is the more common internal/technical term. This is not a novel category the company invented it's an already-emerging, moderately crowded market (GEO/AEO agencies, audit tools, "Share of Model" tracking already exist). The differentiator is delivery discipline, evidence standards, local proof, and human-reviewed execution not the underlying concept.
|
|
|
|
### 3. Local Competitive Awareness
|
|
Built into every client relationship not a standalone product or SKU. Competitor visibility, positioning, review movement, AI-answer comparison. Depth and frequency vary by tier, but every client gets some level of it, because once the mission includes the full acquisition pathway, competitive context is supporting intelligence for that pathway rather than an optional add-on.
|
|
|
|
---
|
|
|
|
## 7. Version 1 Scope Exclusions
|
|
|
|
The company is deliberately not a general-purpose marketing agency. Out of scope for V1 unless separately quoted as distinct project work:
|
|
|
|
- Social media production
|
|
- Paid advertising
|
|
- Website redesign
|
|
- Branding projects
|
|
- Content marketing
|
|
- Full SEO campaigns
|
|
- CRM / email marketing
|
|
|
|
These exclusions were fought for specifically and should be defended aggressively commercial pressure from satisfied clients wanting "more" is the most likely force that erodes this discipline over time.
|
|
|
|
---
|
|
|
|
## 8. Go-to-Market Strategy
|
|
|
|
Proof-of-concept first, retainer second. Given commodity GEO/SEO agencies and DIY tools already serving this market at low price points, competing on price is a losing position for a solo or small operation. The durable advantage is local, provable, before/after value plus warm-referral trust not being the cheapest provider.
|
|
|
|
Motion: Initial Assessment Evidence Classification low-risk Proof-of-Concept Fix Before/After Report Retainer Offer Ongoing Monitoring. Engagements can be one-shot if the client never converts to a retainer that's an acceptable, even expected, outcome for some fraction of prospects, not a failure of the model.
|
|
|
|
Geographic concentration: launch in a single small town or tight geographic area, leaning on warm referrals a satisfied trades business telling three others is worth more than any cold outreach at this stage.
|
|
|
|
First-client selection should deliberately span buyer psychology, not just convenience:
|
|
1. A high-trust, high-LTV category (dental or veterinary)
|
|
2. An urgency-driven, booking-friction category (HVAC, plumbing, electrical)
|
|
3. A skeptical or previously burned owner
|
|
|
|
---
|
|
|
|
## 9. Vertical Sequencing
|
|
|
|
Launch now (lower compliance overhead): home services (HVAC, plumbing, electrical, garage door), auto repair, salon/spa (non-medical claims), boutique fitness/gym.
|
|
|
|
Add later, once vertical-specific guardrails exist: dental, veterinary, med spa/aesthetics these carry real FTC/health-claims and outcome-claim constraints not present in the launch-now set.
|
|
|
|
Excluded for the foreseeable future: attorney/legal. Bar-regulated advertising rules vary by state, and several states restrict or flatly prohibit solicited testimonials outright a materially heavier compliance category than dental/vet/med spa, not a "same bucket, add later" item.
|
|
|
|
---
|
|
|
|
## 10. Validation Status What's Actually Proven
|
|
|
|
Being direct about this matters, because it's the same evidence discipline the business sells to clients.
|
|
|
|
Proven / real: technical remediation work has been completed on one business (Phoenix Salon + Spa) a canonical tag fix, Search Console setup, structured data implementation, sitemap submission. These are real, completed actions.
|
|
Not yet proven: the actual before/after impact of that work (pending a real Search Console data pull), the business's own economic numbers (LTV, repeat frequency, online-discovery rate pending a structured intake conversation), and critically the entire commercial model. No prospect outside personal relationships has been shown a before/after report, offered a retainer, or converted. The 4070% proof-of-concept-to-retainer conversion figure sometimes cited in strategy discussions is unsourced and should not be treated as a target until real engagements produce real numbers.
|
|
|
|
Everything in this whitepaper above this section is a well-reasoned, internally consistent thesis. It has not yet been tested against a real prospect who isn't already personally invested in the outcome.
|
|
|
|
---
|
|
|
|
## 11. Field Audit Framework
|
|
|
|
For use running audits across verticals. This operationalizes Client Lifecycle Stages 34 (Initial Assessment, Evidence Classification) into a repeatable field process.
|
|
|
|
What to check, every time:
|
|
- Google Business Profile: NAP accuracy, hours, categories, photos, Q&A, review responses
|
|
- Website: canonical tags, indexing status, mobile usability, booking/contact pathway function
|
|
- Citations: consistency across major directories (name, address, phone)
|
|
- Structured data: presence and completeness of schema markup
|
|
- AI representation: sample 35 realistic customer queries across at least one major AI assistant, note whether/how the business is mentioned
|
|
- Competitive context: who appears instead, in both traditional search and AI answers, for the same queries
|
|
|
|
For every finding, before writing it down, ask:
|
|
1. Is this Customer Path Leakage or Discovery Failure?
|
|
2. Is this Tier 1 (I can point to a timestamp, screenshot, or specific broken artifact) or Tier 2 (this is a pattern across a sample, not a single confirmed defect)?
|
|
3. Is this inside the recurring service scope, or does it belong in Section 7's exclusion list meaning it gets named, not fixed, under this engagement?
|
|
|
|
Per-vertical notes to capture during the 10 audits (this is the actual workflow-mapping goal): What's structurally different about this vertical's digital presence? Does the standard checklist above miss anything specific to this trade? Are there compliance considerations beyond the ones already flagged in Section 9? How does urgency/decision-speed differ from other verticals already audited? These notes are what eventually populate docs/workflows/ the repository folder that's intentionally still empty, because workflows should be built from real field observation across verticals, not theorized in advance.
|
|
|
|
---
|
|
|
|
## Appendix: Personas (as of this writing)
|
|
|
|
- Ashley salon owner (launch-now)
|
|
- Jim plumber (launch-now)
|
|
- Mike roofing contractor (launch-now)
|
|
- Marco auto repair shop owner (launch-now)
|
|
- Tyler HVAC & electrical service owner (launch-now)
|
|
- Devon gym / fitness studio owner (launch-now)
|
|
- Sarah med spa owner (reclassified: add later, with guardrails)
|
|
- Dental and veterinary personas identified as strong-fit but not yet drafted
|
|
- Attorney/legal persona removed, excluded for the foreseeable future |