Chris Farhood
c7db1dd8b6
- Replace GRO-920 reference with Path C (niche domination strategy) - Document completed messaging and homepage refresh work - Refocus follow-up work on Path C pillars: time recapture, workflow fit, data ownership - Remove competitive positioning page task (Path C doesn't compete on feature parity) - Remove wellness positioning task (GRO-920 pillar; Path C focuses on workflow fit) - Update content calendar to align with three content pillars - Add explicit anti-customer list (NOT for large commercial/franchise shops) - Emphasize data ownership as key differentiator and moat Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
128 lines
4.9 KiB
Markdown
128 lines
4.9 KiB
Markdown
# Marketing Follow-Up Work — Path C Strategy (GRO-1057)
|
||
|
||
## Summary
|
||
|
||
CEO approved Path C strategy (GRO-1055 research, finalized in GRO-1057): **Niche domination for solo/small operators in 2026, AI roadmap for 2027+.**
|
||
|
||
This document tracks the follow-up work to execute Path C messaging and positioning. See MESSAGING-PATH-C.md for the authoritative messaging framework.
|
||
|
||
---
|
||
|
||
## Completed (GRO-1057 — May 5, 2026)
|
||
|
||
### ✅ Path C Messaging Framework
|
||
- **File:** MESSAGING-PATH-C.md
|
||
- **Includes:**
|
||
- Lead message: "Stop missing client calls. Book 24/7, groom all day."
|
||
- Team message: "Automate the admin. Your team focuses on grooming."
|
||
- Anti-customer positioning (NOT for large commercial/franchise shops)
|
||
- Three content pillars: time recapture, workflow fit, data ownership
|
||
|
||
### ✅ Homepage Refresh
|
||
- **Hero message:** Updated to Path C lead message
|
||
- **Feature section:** Reframed around time/revenue benefit for solo groomers (not generic features)
|
||
- **"Built for Your Reality" section:** Replaced feature-parity comparison table with workflow-fit positioning
|
||
- Emphasizes: mobile capability, offline-first, 24/7 booking, data ownership
|
||
- Removes: competitive feature checklist (Path C doesn't compete on breadth)
|
||
- **Anti-customer language:** "Built for solo/mobile, not franchises"
|
||
|
||
### ✅ Blog Post Validation
|
||
- "The Mobile Groomer's Time Problem" (already published) aligns perfectly with Path C messaging
|
||
|
||
---
|
||
|
||
## In Progress (Next 2 Weeks)
|
||
|
||
### 1. Ad Templates & Outbound Messaging
|
||
**Goal:** Update all marketing collateral to reflect Path C positioning
|
||
|
||
**Scope:**
|
||
- Update ad copy (if any exist) to lead with "Stop missing client calls"
|
||
- Ensure all outbound messaging emphasizes solo/small-team focus
|
||
- Remove any feature-parity language vs. Gingr/MoeGo/Fresha
|
||
- Add anti-customer messaging where relevant (e.g., "We're built for mobile groomers, not franchise chains")
|
||
|
||
**Ownership:** CMO (Pawla Abdul)
|
||
|
||
---
|
||
|
||
### 2. Landing Page for Mobile Groomers
|
||
**Goal:** Deepen positioning around offline capability and mobile workflow
|
||
|
||
**Scope:**
|
||
- Already exists (mobile-groomers.html) — good positioning; validate alignment with Path C
|
||
- Potential updates: emphasize "no vendor lock-in," data ownership more explicitly
|
||
- Consider separate landing for "Small Teams" segment
|
||
|
||
**Ownership:** CMO (Pawla Abdul)
|
||
|
||
---
|
||
|
||
### 3. Content Calendar for Pillar Topics
|
||
**Goal:** Create 3–4 blog posts addressing Path C's three content pillars
|
||
|
||
**Topics:**
|
||
- **Time Recapture:** "Stop missing client calls — the math" (already published)
|
||
- **Workflow Fit:** "Why breed-specific grooming data matters" or "Coat type profiles vs. generic fields"
|
||
- **Data Ownership:** "Open source means you own this software, fully" or "Self-hosted vs. SaaS: what matters for small operators"
|
||
|
||
**Ownership:** CMO (Pawla Abdul)
|
||
|
||
---
|
||
|
||
## Medium-Term Content (Next Month)
|
||
|
||
**Content pillars (from MESSAGING-PATH-C.md):**
|
||
|
||
| **Pillar** | **Blog Topics** | **Ownership** |
|
||
|---|---|---|
|
||
| **Time Recapture** | "Stop missing client calls — the math" (published) | CMO ✅ |
|
||
| **Workflow Fit** | "Why breed-specific grooming matters" (draft) | CMO |
|
||
| **Workflow Fit** | "Coat type profiles let you charge more" (draft) | CMO |
|
||
| **Data Ownership** | "Open source means you own this software" (draft) | CMO / CTO |
|
||
|
||
**NOT publishing (outside Path C scope):**
|
||
- ❌ Competitive positioning page (Path C doesn't compete on feature parity)
|
||
- ❌ "Wellness Grooming Positioning" (was GRO-920; Path C focuses on workflow fit + revenue)
|
||
- ❌ "Zero Double-Bookings" detailed post (feature explainer; save for 2027 AI roadmap)
|
||
|
||
---
|
||
|
||
## Path C Anti-Customers
|
||
|
||
**Who we are NOT marketing to:**
|
||
- ❌ Large commercial multi-site salons
|
||
- ❌ Franchise operations
|
||
- ❌ High-volume shops competing on features with enterprise software
|
||
|
||
**Who we ARE marketing to:**
|
||
- ✅ Mobile groomers (basement, garage, van)
|
||
- ✅ Solo operators (1 groomer)
|
||
- ✅ Small teams (2–5 staff)
|
||
- ✅ Groomers who want to own their data
|
||
|
||
---
|
||
|
||
## Success Metrics
|
||
|
||
- Homepage CTR to demo/GitHub (measure vs. baseline)
|
||
- Blog traffic from "Time Problem" post → demo signups
|
||
- Demo signup source tracking (homepage vs. blog vs. search)
|
||
- Engagement metrics: feature cards (feature order change impact)
|
||
|
||
---
|
||
|
||
## Blockers / Dependencies
|
||
|
||
- **CTO input** on any technical positioning claims (offline capability, data migration, etc.)
|
||
- **Customer validation** needed: Do solo groomers actually care about data ownership? (assumption to test)
|
||
|
||
---
|
||
|
||
## Notes
|
||
|
||
- **Path C = Niche Domination:** We win by being laser-focused on solo/small operator pain, not by competing with enterprises on breadth.
|
||
- **Messaging voice:** Warm but direct. Lead with benefit. For groomers with five minutes, not engineers with fifty.
|
||
- **No feature arms race:** We're not saying "we don't have X feature that Gingr has." We're saying "we solve the pain you actually have."
|
||
- **Data ownership is a moat:** Open source + self-hosted is a key differentiator that enterprises can't match. Lean into it.
|