1. Typical Stuck Points (Symptoms)
- Campaigns increase, but contribution to revenue, LTV, and profit cannot be explained (cannot reproduce "what worked").
- Dashboards are in place, but frontline decision-making doesn't change (who to target, what to send, what to stop).
- Segments exist, but don't translate into trigger campaigns or "next actions".
- Optimization happens by channel, fragmenting the customer experience (email/LINE/app/ads).
- KPI improvements happen, but don't drive business growth (total demand, fan base, purchase frequency).
2. Root Causes: Common Problems in Non-Performing Companies (7 Issues)
2-1. "Growth Levers" Are Unclear, and CDP Becomes Just a "Box"
CDP/CRM is a "tool to improve efficiency"—if what to grow (demand creation, base expansion, added value enhancement) is unclear, initiatives will be scattered and eventually hit a ceiling.
- The role of official channels (owned EC/app/membership) is undefined (ambiguous differentiation from distribution/retail).
- Value propositions that work for direct brand sales—"exclusive," "early access," "lottery," "experience," "community"—are not designed.
- Launch calendars, product planning, events/community operations are not linked to CRM.
2-2. No Operational "OS" for Hypothesis → Experimentation → Validation
Even with analytics, without a system to mass-produce winning strategies (experimental design and learning cycles), you get lost as campaign volume increases.
- No hypothesis template for deciding "who," "what," "when," and "why."
- No incremental measurement (A/B test/holdout), leading to correlation-based rather than causal judgments.
- Successful scenarios cannot be "standardized," becoming dependent on individual experience.
2-3. Segments Are Created, but Scenarios (Triggers) Are Weak
- Stops at RFM or clustering without translating into specific campaigns (welcome/browse abandonment/cart abandonment/second purchase promotion/win-back).
- No design for state transitions tied to events or launch dates—"purchase reminder," "lottery loser follow-up," "re-stock waiting list."
- Personalization stops at "recommendations display," not extending to offers/content/navigation consistently.
2-4. Data Exists, but Lacks "Decision-Ready Granularity"
- ID unification (member, anonymous, app, store/event) is insufficient, causing unstable lifecycle classification.
- Event definitions (browse, search, cart, purchase, return, exit) are vague, undermining KPI foundations.
- Product/inventory/pricing/campaign information is not organized, preventing "actionable proposals."
2-5. Experience Value (Content/UGC/Live, etc.) Doesn't Connect to Purchase
Even with winning content like SNS/UGC/live streaming, growth stalls if you can't connect which content drives which customer's return/purchase.
- Content-to-purchase linking (view/click/dwell → purchase/return) is not tracked.
- Pulled only by a few voices (high-engagement community), creating bias.
- Online/offline integration (event attendance → EC purchase, purchase → participation rights) is not designed.
2-6. Organization/Partners Remain in "0→1 Mode," Unable to Transition to Growth
- Cannot transition from launch phase ("foundation building/initial campaigns") to growth phase capabilities ("experimental design/incremental measurement/creative mass production").
- Who makes decisions and who executes is unclear, slowing improvements.
- Cross-departmental consensus (product planning/marketing/EC/CRM/CS/legal) is slow, stalling initiatives.
2-7. Insufficient Compliance/Fraud Prevention Design Causes Initiative Paralysis
- Lottery/benefit/campaign terms are weak, and fear of backlash/complaints reduces risk-taking.
- Minor protections, resale prevention, identity verification are retrofitted, breaking operations.
- No design balancing "offense" and "defense," leading to frontline decision paralysis.
3. Prioritization by Growing Companies
Successful companies define "growth drivers" before CRM campaigns, then solidify the "operational OS."
- Priority ①: Business Driver Design (Increase Total Demand) — Official channel role, value (exclusive/early access/experience/community), launch/event design.
- Priority ②: CRM/CDP from "Campaigns" to "Growth OS" — KPI tree, experimental design, standard scenarios, learning cycles.
- Priority ③: Channel Design — Differentiation from distribution/retail without friction, integrated customer experience.
- Priority ④: Content Operations — Link UGC/live/editorial to customer states, reproduce winning patterns.
4. Diagnostic Checklist (Quickly Identify Stuck Points)
4-1. Growth Levers (Upstream)
- Can the role of official channels be stated in one sentence (exclusive/deep brand world/early access/fan touchpoint, etc.)?
- Is there integrated design between product planning, launch calendar, events, and CRM?
- Is it clear "whose" "what kind of experience value" to increase?
4-2. Growth OS (Midstream)
- Is there a North Star KPI (gross profit LTV, second purchase rate, etc.) and KPI tree?
- Is incremental measurement (A/B/holdout) built into operations?
- Are standard scenarios (welcome, abandonment, second purchase, win-back) in "steady-state operations"?
4-3. Implementation Quality (Downstream)
- Are ID unification and event definitions stable (no measurement fluctuation)?
- Is delivery frequency/creative production system/approval flow sustainably designed?
- Are messages consistent across channels?
5. Partner Review Considerations (Failure-Resistant Role Division)
- Strategy/Second Opinion: Growth lever design, channel strategy, initiative portfolio, decision support.
- Growth Execution: Experimental design and weekly operations, creative mass production, ad/CRM integration.
- Data/Infrastructure: Data quality, ID unification, event design, analytics standardization.
Don't "replace everything"—supplement only missing capabilities (distinguish reversible/irreversible).
6. Summary
The biggest factor causing CDP/CRM projects to stall is not lack of data or campaigns, but ①unclear growth levers, ②insufficient hypothesis→experiment→validation operational OS, and ③organizational/partner capability gaps.
By first solidifying upstream (growth drivers) and midstream (operational OS), then stabilizing downstream (implementation quality), you can reach "reproducible results" via the shortest path.