The Customer GP Model: Diagnosing Experience Across Silos
Updated
Knowledge on this page was mainly distilled from the following articles: The Death of "Pretty Good", Satisfied Customers Have Nothing to Say, Every Metric Is Green. The Customer Is Lost..
Most companies have specialists for every customer interaction but no generalist holding the full picture. Support sees a ticket. Marketing sees a segment. Sales sees an opportunity. Product sees usage data. Each optimizes its own metrics while the customer receives a disjointed experience from what feels like five strangers sharing a logo.
Medicine solved a version of this with the general practitioner. The GP does not run the MRI or perform surgery. The GP's job is diagnosis: understanding the full picture before anyone starts prescribing. The Customer GP model applies the same logic to business. One function, person, or system sits across departments and repeatedly asks: do we know what this person is trying to do right now?
The Diagnostic Question
The question that replaces your dashboard: What is this specific person trying to accomplish today, and are we helping or interrupting? When you can answer that, timing, channel, and content all resolve. Reach out when the answer is "helping." Stay quiet when the answer is "interrupting."
Implementation Patterns
Some companies build the GP into the product itself. Slack suppresses mobile notifications when you are active on desktop. Others make it a structural role. Amazon uses "single-threaded leaders" who own a product end-to-end with authority to coordinate across every department. Smaller companies achieve it with a lean operations team whose sole mandate is to hold the unified picture and flag when departments are about to collide.
The Support Queue as the GP's Waiting Room
The support inbox is the closest thing most companies have to a GP's intake desk. Every ticket carries two layers: the surface question and the structural intelligence underneath. "How do I export my data?" asked twenty times in a month is not twenty identical problems. It is one invisible product flaw that no dashboard surfaced. A Customer GP function treats the queue as a diagnostic stream, not a cost center to be automated away.
When AI chatbots resolve tickets silently, they strip this diagnostic layer out. The bot classifies "I keep clicking the blue button and nothing happens" as "UI Bug - Resolved" and the GP never sees that five people hit the same onboarding wall this week. Automation that filters signal before a generalist can read it undermines the entire model.
Q&A
What is the Customer GP model?
It borrows from medicine's general practitioner role: one function that holds the full picture of a customer before any specialist team acts. The GP does not replace support, marketing, or sales. It coordinates them by answering a single diagnostic question: what is this person trying to accomplish right now? This prevents individually reasonable touchpoints from combining into a disjointed experience.
Why do green metrics still produce bad customer experiences?
Each department optimizes its own KPIs in isolation. Support reduces response time, marketing improves open rates, sales hits quota. All dashboards show progress, but nobody is responsible for how these touchpoints interact from the customer's perspective. Five reasonable messages in two days can feel like harassment when the customer just wants a $12 billing fix.
Why won't a Customer Data Platform solve this?
CDPs unify data but not judgment. Industry surveys report dissatisfaction rates as high as 90%, with only 22% satisfaction for personalization. A unified profile without a diagnostic question is just a more expensive way to bother customers in unison. The bottleneck was never data integration; it was nobody asking what the data means for this specific person right now.
How does the Customer GP model apply to solo founders?
Solo founders do not need departments to create fragmentation; automation does it. Welcome emails, re-engagement nudges, and upgrade prompts each run on their own clock with no awareness of each other. The solo founder's superpower is that they can still see the full picture manually. The strategic question is how to preserve that diagnostic ability as the business scales.
What is the biggest risk of creating a Customer GP function?
The GP function can become another silo. It develops its own metrics like diagnostic accuracy rates and coordination scores, then optimizes those numbers just like every other department. The safeguard is keeping the function close to actual customer conversations, not reports or dashboards summarizing customers. The moment that distance grows, the diagnostic reflex dies.
Where is the line between helpful coordination and surveillance?
The diagnostic question is 'what is this person trying to do?' not 'what is this person doing on every screen right now?' The first earns trust; the second erodes it. Telling a customer 'we noticed you were browsing pricing while your support ticket was open' sounds like watching them through a window. As data gets richer, this distinction matters more.
What does the Chewy example illustrate about the GP model?
When a customer called to return pet food after their dog died, Chewy refunded the purchase, sent flowers and a handwritten card, and suppressed automated reorder reminders. That response required every department to share one piece of context: what just happened to this person. It looks effortless externally but demands real-time diagnostic coordination internally.
How does automating support undermine the Customer GP model?
The GP model depends on seeing the full, unfiltered picture of what customers are experiencing. AI chatbots resolve and classify tickets before anyone reads the underlying signal. A clean dashboard replaces messy but diagnostic detail, so the generalist function loses the raw input it needs to coordinate across teams.
Why is the support queue a better diagnostic source than analytics?
Analytics tell you what happened; support tells you why. A usage drop on a feature page is a data point. Twenty tickets saying the same button does not work is a diagnosis. The queue also reveals the language customers actually use, which often exposes gaps between the product's mental model and the user's expectations.
How does the medicine analogy extend beyond customer experience?
Medicine's GP-specialist split is a template for what AI is doing to every profession. The position that disappeared in medicine was "pretty good at cardiology but not a cardiologist." AI accelerates the same pattern: deep specialists own the frontier, generalists own the coordination layer, and the middle erodes. The Customer GP model is one application of a broader structural shift.