top of page

Consumer & Commerce

MarTech

Customer Experience Management

Charles

Built a European conversational-commerce position by turning WhatsApp from a support channel into a consent-based revenue and retention channel, despite platform dependency on Meta and competition from message-marketplace alternatives.

1

MODEL

BUSINESS MODEL

SaaS

- Built a WhatsApp Business Platform layer combining messaging, campaigns, automation and commerce workflows. - Connected chat APIs with Shopify, Klaviyo, Salesforce, SAP, Zendesk and other commerce/CRM systems. - Used click-to-chat ads, QR codes, pop-ups and welcome flows to acquire consented contacts. - Added AI agents for recommendations, FAQs, abandoned carts, replenishment and service escalation. - Monetized through fixed platform fees plus conversation and revenue-linked charges.

1. Identify a high-engagement communication channel where commerce workflows remain manual. 2. Operate the end use case first to learn the customer’s real workflow. 3. Build the integration layer between the messaging channel and commerce systems. 4. Design consent, brand safety and human escalation before scaling automation. 5. Price on platform access plus the variable conversation activity that creates value. 6. The common mis-build is treating a messaging channel as a broadcast tool before solving consent, deliverability and two-way service.

Charles began in 2019 as a WhatsApp-first sustainable fashion brand, but its founders could not find suitable conversational-commerce software. In 2020, they pivoted from operating a store to building the software layer for brands, connecting WhatsApp APIs with Shopify, SAP and HubSpot.

HOW THEY BUILT IT

HOW TO ARCHITECT IT

DISTRIBUTION MODEL

Direct Sales, Partnerships, Content Marketing, Paid Advertising

HOW THEY OPERATIONALIZED

HOW TO REPLICATE WHAT WORKED

dm

- Direct sales: Charles sells to DTC and enterprise brands through demos, onboarding and customer-success-led implementation. - Meta/WhatsApp Solution Provider status: Its BSP position gives it credibility and technical access to the WhatsApp Business Platform. - Commerce and CRM partnerships: Shopify, Klaviyo, Salesforce, SAP and Zendesk integrations embed Charles in existing brand stacks. - Paid and click-to-chat campaigns: Brands use Meta click-to-chat ads and QR codes to start consented conversations, creating demand for Charles’s orchestration layer.

What worked: Sell the outcome of a new channel—higher conversion and retention—while using platform partnerships and commerce integrations to reduce implementation risk. Trap if copied blindly: Channel-led distribution fails when the underlying platform changes pricing, policy or API access; the vendor must own workflow value beyond simple message delivery.

|  PATTERNS OF THIS MODEL

PATTERNS IN CHANNEL-NATIVE COMMERCE SAAS: 1. CHANNEL POLICY RISK. Vendors built on a host messaging platform inherit its pricing, API and compliance changes. 2. CONSENT AS RETENTION. Opt-in conversational channels produce higher engagement but require strict permission and frequency management. 3. COMMERCE-DATA COMPOUNDING. Purchase, browsing and chat history improve recommendations, segmentation and lifecycle messaging. THE WEAKNESS: A messaging vendor can become a thin layer if the channel owner, CRM or commerce platform adds native conversational commerce.

What companies with this model reveal

|  OPPORTUNITY INTELLIGENCE

GOLDMINE 1 — CONVERSATIONAL COMMERCE OPERATING SYSTEM. The opportunity is not another campaign sender but a system that coordinates product discovery, cart assembly, payment, fulfillment, returns and service in one conversation. GOLDMINE 2 — AI AGENT WITH BRAND GOVERNANCE. Brands need agents that use approved product data, tone, policies and escalation rules; generic chatbots fail when they invent answers or violate brand safety. GOLDMINE 3 — CONSENTED FIRST-PARTY DATA ACTIVATION. WhatsApp conversations can create preference, intent and lifecycle data that improves email, ads and retention—provided consent and privacy are designed in. THE PIT — CHANNEL DEPENDENCY WITHOUT MULTI-CHANNEL VALUE. A WhatsApp-only tool is exposed to Meta’s pricing, policy and product decisions. THE SECOND PIT — AUTOMATION WITHOUT HUMAN ESCALATION. AI-only service can damage trust when complex or emotionally sensitive customer issues arise. MOVE WITH CAUTION — Do not build on a single messaging platform without a portable customer-data and workflow layer; otherwise the host platform controls both distribution and economics.

Untapped Business Model / Gaps / Goldmines / Pits

Patterns & Insights

2

MARKET

mkt mt es

Charles entered as WhatsApp reached nearly 3 billion monthly users and European brands faced rising acquisition costs. WhatsApp commerce was already embedded in Brazil and India, creating a proven behavior pattern that Charles brought to European DTC brands.

MARKET TYPE

Emerging Market

ENTRY STRATEGY

Greenfield Entry

WHY THEY WON

European conversational commerce was emerging rather than mature: consumers used WhatsApp daily, but brands lacked a compliant way to sell, support and retain customers there. Charles’s opening was the gap between consumer messaging behavior and brand commerce infrastructure. The transferable lesson is that market timing depends on a consumer behavior that already exists in one geography and can be transferred to another with the right compliance and integration layer.

EXECUTION

Charles entered by building a new WhatsApp-first commerce platform after operating its own fashion brand on WhatsApp. Its initial bet was that European brands would adopt conversational commerce if the software solved consent, CRM integration and revenue attribution. This required WhatsApp Business API access, Shopify/Klaviyo integrations and workflow automation. The founder-level lesson: a founder operating the end use case can discover a software gap that pure B2B builders miss.

FOOTHOLD STRATEGY

Wedge Strategy

Charles’ initial wedge was WhatsApp marketing and sales for European DTC brands. The pain was low email engagement, rising paid-acquisition costs and no practical way to sell through chat. DTC brands were reachable through e-commerce communities and Meta’s ecosystem, and could pay because WhatsApp campaigns produced measurable conversion and retention. The path outward was enterprise brands, service automation and additional messaging channels.

GROWTH CAMPAIGN

CAMPAIGNS THAT WORKED

SO WHAT: Charles’s strongest campaigns convert a familiar consumer channel into a measurable revenue and service workflow. KEY LEARNING: A new channel gains adoption when the vendor supplies a specific, high-frequency use case—abandoned cart, replenishment or FAQ deflection—rather than asking brands to adopt “conversational commerce” abstractly. HOW TO USE: Launch one measurable conversational flow, prove revenue per message or ticket reduction, then expand into the full lifecycle.

KEY LEARNING

THE STANDARD: In an emerging market, the entrant must prove the behavior transfer while building the infrastructure incumbents have not yet prioritized. RULE 1 — PROVE BEHAVIOR EXISTS: Use evidence from markets where the channel already drives commerce. RULE 2 — ANCHOR TO AN EXISTING BUDGET: Position against email, SMS, paid acquisition or customer-service cost. RULE 3 — SUCCESSFUL ENTRANT BEHAVIOR: They own consent, integration and workflow depth before broadening channels. RULE 4 — COMMON FAILURE: Treating the channel as a broadcast list creates opt-outs, regulatory risk and weak retention. MARKET TYPE: Emerging Market (category).

gc

Market Context

|  MARKET INTELLIGENCE

PATTERNS IN CONSENT-BASED MESSAGING GROWTH: 1. HIGH-INTENT ENTRY POINTS. Click-to-chat ads and QR codes convert attention into permissioned conversations. 2. LIFECYCLE FLOWS DRIVE RETENTION. Abandoned cart, replenishment and win-back flows create recurring commercial value. 3. SERVICE AS A RETENTION CHANNEL. Two-way support increases trust and creates data for future marketing. 4. THE WEAKNESS: Over-messaging causes opt-outs and can destroy the channel’s long-term effectiveness.

|  MARKET ENTRY PLAYBOOK

THE STANDARD: Greenfield entry is appropriate when consumer behavior exists but no adequate commercial infrastructure serves it. RULE 1 — Operate or simulate the end use case: direct exposure reveals workflow gaps that customer interviews miss. RULE 2 — Build compliance into the core: consent, data residency and escalation rules must precede scale. RULE 3 — Integrate with the customer’s system of record: commerce, CRM and support connections determine whether the channel becomes operational. RULE 4 — Reject greenfield entry if the channel owner can easily provide the commerce layer or the behavior is not transferable. Example: Shopify built commerce infrastructure as direct-to-consumer selling shifted online. Failure pattern: A channel tool that depends entirely on host-platform policy can lose access or margin without warning.

How to enter

|  FOOTHOLD STRATEGY PLAYBOOK

THE STANDARD: A wedge is a narrow, high-frequency conversational workflow that creates measurable commercial value. RULE 1 — Choose a workflow with a direct revenue or cost metric, such as abandoned cart or FAQ deflection. RULE 2 — Make the first flow easy to launch with existing product and CRM data. RULE 3 — Expand only when the first flow produces consented contacts, revenue and retention evidence. RULE 4 — Failure occurs when the workflow is generic, low-frequency or easily handled by email. Example: Attentive built SMS retention around cart recovery and lifecycle messaging before expanding into broader consumer engagement. Failure pattern: Expanding into every messaging channel before mastering consent and deliverability creates operational complexity without better outcomes.

How to get the first strong position

MARKET PATTERNS & PLAYBOOK

3

MONEY

money rev pri

Charles charges an annual fixed fee plus a per-conversation fee, while WhatsApp Business Platform API charges also scale with conversations. This structure requires Charles to manage Meta’s variable messaging costs, AI inference and support costs as customer usage grows.

REVENUE MODEL

Subscription, Usage-Based, Service Fee

PRICING MODEL

Custom Enterprise Pricing, Usage-Based Pricing, Value-Based Pricing

WHY THEY WON

Brands pay a fixed platform fee for access, onboarding and workflow software, plus variable fees tied to conversations and revenue generated in chat. Revenue expands with contacts, campaigns, AI automation and commerce volume. Margins depend on WhatsApp API fees, AI compute, integration support and customer success.

Charles uses sales-led, custom pricing with an annual fixed fee plus a per-conversation charge. Earlier non-custom plans were reported at €349–€1,599 per month plus variable conversation/revenue fees; current enterprise pricing is quote-based and rises with message volume and WhatsApp API costs.

TARGET AUDIENCE

European DTC brands (fashion, beauty, food; WhatsApp campaigns and cart recovery); mid-market consumer brands (CRM-integrated lifecycle messaging); enterprises with high service volume (AI FAQ, fulfillment updates and human escalation); brands with repeat-purchase products (replenishment, win-back and referral flows).

CUSTOMER BUYING BEHAVIOUR

The trigger is usually rising CAC, weak email engagement, high support volume or a need for a direct customer channel. Brands evaluate WhatsApp ROI, GDPR compliance, Shopify/CRM integration, deliverability and AI safety; CMOs, e-commerce leads and CX leaders participate in the decision.

|  PRICING INTELLIGENCE

What makes this model effective & make customers pay 

Brands pay for revenue and retention from a channel customers actually open, not for another messaging inbox. RULE 1 — PRICE THE CONVERSATION, NOT THE CONTACT. Conversations represent engagement, service cost and commercial opportunity. RULE 2 — ANCHOR TO DISPLACED SPEND. WhatsApp competes with paid retargeting, email discounting and support headcount. RULE 3 — MONETIZE LIFECYCLE VALUE. Abandoned cart, replenishment and win-back flows make the channel recurring rather than campaign-based. RULE 4 — WATCH THE API-COST TRAP. Meta’s conversation pricing and AI inference can rise faster than platform fees if messaging volume is unmanaged. The buyer is really buying higher revenue per customer relationship; the conversation-based budget proves that value.

PRICE & REVENUE

|  Revenue Risk - The biggest threat to revenue stability

Meta dependency: WhatsApp pricing, API rules, template approvals and policy changes directly affect Charles’s product and margins. Messaging fatigue: Excessive promotional messages cause opt-outs and reduce long-term channel effectiveness. Privacy risk: GDPR, consent management and data residency requirements constrain European conversational marketing. Commerce-platform competition: Shopify, Klaviyo, Zendesk and CRM vendors could add native conversational workflows. AI reliability risk: Incorrect recommendations or automated answers can damage brand trust and increase human escalation costs. Funding/valuation: Charles raised $20 million in Series A funding in 2022, led by Salesforce Ventures; current revenue, ARR and profitability are not publicly disclosed.

Where the model can break

4

MOTION

motion ge cs

Charles uses its Meta/WhatsApp Solution Provider status, Shopify and Klaviyo integrations, and Salesforce Ventures backing to reach DTC and enterprise brands. Its customer-success-led onboarding converts platform access into operational adoption.

GROWTH EXPANSION MODEL

Platform Expansion, Geographic Expansion

HOW THEY EXPAND

Charles expanded from WhatsApp marketing into conversational CRM, AI agents, service automation and additional channels including Instagram, Messenger, Webchat and RCS. It expanded geographically from Germany into broader European markets and targeted larger enterprises requiring API-based WhatsApp integration.

COMPETITIVE STRATEGY

Differentiation

HOW THEY COMPETE

Against generic WhatsApp BSPs and email/SMS platforms, Charles differentiates through commerce-native workflows, Shopify/Klaviyo depth, GDPR-first design and AI agents governed by brand tone and service rules.

GROWTH ENGINE

GTM

Content Flywheel

A brand runs a click-to-chat ad or QR-code campaign → a consumer opts into WhatsApp → Charles captures preferences and connects commerce/CRM data → automated flows recover carts or answer questions → purchases and service interactions improve segmentation → the brand expands into replenishment, referrals and AI service. The loop compounds when conversation data improves personalization. It breaks if consent quality is poor, message frequency is excessive or Meta changes economics.

Charles’s GTM is sales-led with partner-assisted distribution. Direct sales targets DTC and enterprise brands, while Meta, Shopify, Klaviyo and CRM partnerships reduce implementation friction. Customer success converts onboarding into lifecycle automation and expansion. The transferable components are channel-outcome positioning, consent-first onboarding and commerce-data integration; they require platform-policy resilience and strong service operations.

SUSTAINING MOATS

High Customer Lock-In

moat

The moat is Charles’s connected conversational-commerce ecosystem: consented contacts, commerce data, CRM profiles, AI workflows and service history. As brands run more lifecycle and service flows, replacing the platform disrupts customer communication and revenue operations.

|  MOAT INTELLIGENCE

THE STANDARD: An ecosystem moat lasts when the product connects customer identity, commerce data and operational workflows. RULE 1 — CONSENTED PROFILE DEPTH: Opt-in conversations create preferences and first-party data beyond email lists. RULE 2 — COMMERCE WORKFLOW DEPTH: Cart recovery, recommendations, fulfillment and service are interconnected. RULE 3 — BRAND GOVERNANCE: Approved tone, product data and escalation rules make AI usable in customer-facing contexts. THE SIGNAL: Charles reports customers achieving over 30% lower cost per conversion, 7x higher conversion rate versus its best email segment and €12 average revenue per abandoned-cart message; the moat does not protect against Meta policy shifts, messaging fatigue or native commerce-platform features.

Why this company remains defensible

ARR & TAKEAWAY

ARR Journey - what to do at each stage

PRE-$1M ARR — OPERATE THE USE CASE. Charles began as a WhatsApp-first fashion brand in 2019, learning firsthand how conversations could drive purchase and repeat behavior. WATCH: Consent, fulfillment and customer response quality. $1–5M ARR — PIVOT TO SOFTWARE. In 2020, it launched the platform for brands, connecting WhatsApp with Shopify, SAP and HubSpot. $5–10M ARR — PROVE REVENUE PER CONVERSATION. It raised a €6.4 million seed in 2021 and showed customers generating meaningful WhatsApp revenue. $10–50M ARR — SCALE EUROPEAN DTC. It raised $20 million in 2022, expanded enterprise targeting and deepened Shopify, Klaviyo, Salesforce and Zendesk integrations. $50–100M ARR — ADD AI AND CHANNELS. It expanded into charlesAI, Instagram, Messenger, Webchat and RCS, moving from WhatsApp marketing toward conversational CRM. NOT REACHED — $100M+ ARR based on publicly disclosed evidence. Rule: Operate the end customer workflow first, then build the software layer that makes the channel commercially reliable.

COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid

THE STANDARD: Use direct exposure to a high-potential channel to discover the workflow gap, then build a consent-first software layer connected to commerce systems. SEQUENCE: 1. Operate or deeply simulate the end use case; prerequisite: access to real customer conversations and transaction data. 2. Build the consent, integration and measurement layer before scaling automation; prerequisite: commerce, CRM and messaging-platform access. 3. Add AI and adjacent channels only after one flow proves revenue or cost reduction; prerequisite: brand governance and human escalation. WORKED: Charles’s fashion-brand origin gave it practical insight into WhatsApp commerce, while Shopify and Klaviyo integrations made the platform operationally useful. CAUTION: Do not copy a single-channel strategy without a portable data and workflow layer; do not scale AI conversations without brand-safety and escalation controls.

bottom of page