# WhatsApp Channel as a Service — Business Plan

## Executive Summary

**Product**: A managed WhatsApp integration service for AI agent platforms. Not another messaging API — a purpose-built WhatsApp runtime for AI agents that handles bidirectional messaging, access control, multi-session management, group intelligence, and admin tooling out of the box.

**Core insight**: Every AI agent platform building WhatsApp support reinvents the same 80% — webhook handling, name resolution, media processing, group filtering, session health, admin UI. This product eliminates that entirely.

**Current state**: v1.16 in production, battle-tested with 100+ actions, React admin panel, SQLite-backed directory, rate limiting, multi-session support, and access control policies. Licensed CC-BY-NC-4.0 (non-commercial).

---

## 1. Market Analysis

### 1.1 Target Customer Segments

| Segment | Description | Pain Point | Willingness to Pay | Volume |
|---------|-------------|------------|--------------------|----|
| **AI Agent Platforms** | OpenClaw, AutoGen, CrewAI, LangGraph, Semantic Kernel | Need channel integrations but WhatsApp is complex (webhooks, JID resolution, media, groups). Build vs. buy decision. | High ($200-2000/mo) | Low (50-200 platforms globally) |
| **Chatbot SaaS** | Botpress, Voiceflow, Chatfuel, ManyChat competitors | Already have WhatsApp but via Twilio/360dialog — expensive per-message costs eat margins | Medium ($100-500/mo) | Medium (500-2000) |
| **AI Dev Agencies** | Boutique shops building AI assistants for clients | Need WhatsApp for client projects, don't want to maintain infra per-client | Medium ($50-300/mo per project) | High (5000-20000) |
| **Enterprise AI Teams** | Internal AI assistant projects at companies | Need WhatsApp for employee/customer comms, require admin controls and audit | High ($500-5000/mo) | Medium (1000-5000) |
| **Solo AI Builders** | Indie devs building personal AI assistants | Want WhatsApp integration without learning WAHA, JIDs, webhooks | Low ($0-30/mo) | Very High (50000+) |

**Primary target (Year 1)**: AI Agent Platforms and AI Dev Agencies. These segments have the clearest pain point (building WhatsApp from scratch is 3-6 months of work) and can evaluate quickly.

### 1.2 Competitive Landscape

| Competitor | Model | Pricing | Strengths | Weaknesses |
|-----------|-------|---------|-----------|------------|
| **Twilio WhatsApp** | Per-message API | $0.005-0.08/msg + WhatsApp BSP fees | Massive scale, enterprise trust, global reach | Expensive at volume, no AI-native features, requires WhatsApp Business API approval, no built-in admin panel |
| **MessageBird (Bird)** | Per-message API | $0.005-0.05/msg | Omnichannel, good API docs | Same per-message model, no agent features, complex pricing |
| **WATI** | SaaS platform | $49-299/mo | Built for WhatsApp, good UI | Focused on marketing/support, not AI agents, limited API extensibility |
| **Respond.io** | SaaS platform | $79-349/mo | Multi-channel inbox, team features | Human-agent focused, not AI-native, overkill for AI-only use cases |
| **360dialog** | WhatsApp BSP | Per-message + monthly | Direct Meta partnership | Raw API, no agent features, requires BSP onboarding |
| **Self-hosted WAHA** | Open source | Free (WAHA Core) / $49/mo (WAHA Plus) | Full control, no per-message fees | Must build everything: webhook handling, name resolution, admin UI, access control, media processing, health monitoring |
| **Baileys (raw)** | Open source lib | Free | No server needed | Unstable, no admin UI, no agent features, breaks frequently with WhatsApp updates |

### 1.3 Differentiation — Why This Wins

**We are not a messaging API. We are an AI agent WhatsApp runtime.**

| Capability | Us | Twilio | WATI | Self-hosted WAHA |
|-----------|-----|--------|------|------------------|
| AI agent action dispatch (100+ actions) | Yes | No | No | No |
| Fuzzy name-to-JID resolution | Yes | No | No | No |
| Multi-session (bot + human listener) | Yes | No | No | Manual |
| Group activation policies (mention/always) | Yes | No | No | No |
| DM access control (pairing, allowlist, open) | Yes | No | Partial | No |
| Built-in admin panel (React) | Yes | No | Yes | Basic |
| SQLite contact directory with DM settings | Yes | No | No | No |
| Rate limiting with token bucket | Yes | N/A | N/A | No |
| Webhook dedup + health monitoring | Yes | Yes | Yes | No |
| Per-message cost | $0 | $0.005-0.08 | Included | $0 |
| Time to integrate | Hours | Days-Weeks | Days | Weeks-Months |

**Key differentiator**: A Twilio customer building an AI WhatsApp bot still needs to build name resolution, group filtering, access control, admin UI, session management, and action routing. We ship all of that.

### 1.4 Market Sizing

**TAM (Total Addressable Market)**: Global WhatsApp Business API + chatbot market
- WhatsApp Business API market: ~$2.1B by 2027 (Grand View Research)
- AI agent platforms market: ~$5.1B by 2027
- Overlap (AI agents needing WhatsApp): ~$800M
- **TAM: $800M**

**SAM (Serviceable Addressable Market)**: AI platforms and dev agencies that would use a managed WhatsApp-for-agents service
- ~25,000 potential customers globally
- Average revenue per customer: $150/mo
- **SAM: $45M/year**

**SOM (Serviceable Obtainable Market)**: Realistic Year 1-3 capture
- Year 1: 200 paying customers, $80 avg MRR = **$192K ARR**
- Year 2: 800 paying customers, $120 avg MRR = **$1.15M ARR**
- Year 3: 2,500 paying customers, $150 avg MRR = **$4.5M ARR**

---

## 2. Subscription Plans & Pricing

### 2.1 Pricing Philosophy

**Hybrid model**: Flat monthly subscription + usage-based overage for messages. This gives customers cost predictability (unlike pure per-message Twilio pricing) while protecting against abuse.

No per-message fees within tier limits — this is our biggest competitive advantage vs. Twilio/MessageBird.

### 2.2 Tier Structure

| | **Sandbox** | **Starter** | **Pro** | **Enterprise** |
|--|------------|------------|---------|---------------|
| **Price** | $0/mo | $29/mo | $149/mo | $499/mo+ (custom) |
| **WhatsApp Sessions** | 1 | 1 | 3 | Unlimited |
| **Messages/month** | 1,000 | 10,000 | 100,000 | Unlimited |
| **Overage** | Hard cap | $0.003/msg | $0.002/msg | Custom |
| **Actions available** | Send, receive, basic | All 100+ actions | All 100+ actions | All + custom |
| **Admin Panel** | View-only | Full | Full + analytics | Full + SSO |
| **Directory (contacts)** | 50 max | 500 | 5,000 | Unlimited |
| **Groups monitored** | 2 | 10 | 50 | Unlimited |
| **Multi-session** | No | No | Yes (bot + listener) | Yes + custom roles |
| **Access Control** | Basic (allowlist) | Full (pairing, policies) | Full + God Mode | Full + audit log |
| **Media** | Images only | All media types | All + 100MB limit | Custom limits |
| **Webhook delivery** | Best-effort | Guaranteed | Guaranteed + retry | Guaranteed + SLA |
| **Rate limit** | 5 msg/sec | 15 msg/sec | 30 msg/sec | Custom |
| **Support** | Community (GitHub) | Email (48h) | Email (24h) + Slack | Dedicated + SLA |
| **Data retention** | 7 days | 30 days | 90 days | Custom |
| **API** | REST only | REST + webhooks | REST + webhooks + WS | Custom |
| **Hosting** | Shared | Shared | Dedicated pod | Dedicated + region |

### 2.3 Pricing Rationale

- **$0 Sandbox**: Developer acquisition. Low limits prevent abuse. Enough to build a proof-of-concept. Convert to Starter when they go to production.
- **$29 Starter**: Price point below WATI ($49) and Respond.io ($79). Targets solo builders and small agencies. 10K messages covers a personal AI assistant comfortably.
- **$149 Pro**: Sweet spot for agencies and small platforms. Multi-session unlocks the "human monitor + AI bot" use case. 100K messages handles 5-10 active client deployments.
- **$499+ Enterprise**: For platforms integrating us as infrastructure. Dedicated resources justify the price. Custom pricing for high-volume deals.

### 2.4 Add-ons (a la carte)

| Add-on | Price | Notes |
|--------|-------|-------|
| Additional WhatsApp session | $19/mo | For multi-number setups |
| Dedicated WAHA instance | $49/mo | Isolation, custom config |
| Priority webhook delivery | $29/mo | < 100ms delivery SLA |
| Extended data retention (1 year) | $19/mo | Compliance use cases |
| Custom domain for admin panel | $9/mo | White-label |
| Backup & disaster recovery | $39/mo | Daily SQLite backups, failover |

---

## 3. Revenue Model

### 3.1 Cost Structure (per customer)

| Cost Item | Sandbox | Starter | Pro | Enterprise |
|-----------|---------|---------|-----|-----------|
| WAHA hosting (shared) | $2 | $5 | $15 | $40 |
| Compute (webhook server) | $1 | $3 | $8 | $20 |
| Storage (SQLite, media) | $0.50 | $2 | $5 | $15 |
| Bandwidth | $0.50 | $2 | $5 | $10 |
| Support cost | $0 | $3 | $10 | $50 |
| **Total COGS** | **$4** | **$15** | **$43** | **$135** |
| **Gross Margin** | -$4 (loss leader) | **$14 (48%)** | **$106 (71%)** | **$364+ (73%)** |

Note: WAHA Plus license ($49/mo) covers multiple sessions. At scale, amortized cost per customer drops significantly. Self-hosted WAHA Core (free) for Sandbox tier.

### 3.2 Unit Economics

| Metric | Assumption |
|--------|-----------|
| **CAC (Customer Acquisition Cost)** | $50 (content-led, developer community) |
| **Average MRR** | $80 (blended across tiers) |
| **Gross Margin** | 65% blended |
| **Monthly Churn** | 5% (Year 1), 3% (Year 2), 2% (Year 3) |
| **Average Customer Lifetime** | 20 months (at 5% churn) |
| **LTV** | $80 x 20 x 0.65 = **$1,040** |
| **LTV:CAC Ratio** | **20.8x** (excellent) |
| **Payback Period** | < 1 month |

### 3.3 MRR Projections — Year 1

| Month | Conservative | Moderate | Aggressive |
|-------|-------------|----------|-----------|
| 1 | 5 customers / $200 | 10 / $400 | 20 / $800 |
| 3 | 15 / $800 | 35 / $2,100 | 70 / $4,500 |
| 6 | 40 / $2,800 | 80 / $6,400 | 160 / $14,000 |
| 9 | 70 / $5,200 | 140 / $11,200 | 300 / $27,000 |
| 12 | 100 / $8,000 | 200 / $16,000 | 500 / $45,000 |
| **Year 1 Total Revenue** | **~$48K** | **~$108K** | **~$270K** |

Assumptions:
- Conservative: Organic growth only, no paid acquisition
- Moderate: Content marketing + community + 1 partnership
- Aggressive: Content + partnerships + Product Hunt launch + dev evangelism

### 3.4 Revenue Mix Target (Month 12)

| Tier | % of Customers | % of Revenue |
|------|---------------|-------------|
| Sandbox | 60% | 0% |
| Starter | 25% | 18% |
| Pro | 12% | 45% |
| Enterprise | 3% | 37% |

---

## 4. Go-to-Market Strategy

### 4.1 Phase 1: Developer Seeding (Months 1-3)

**Goal**: 50 Sandbox signups, 10 paying customers, establish presence in AI agent communities.

**Actions**:

1. **Product Hunt Launch**
   - Position: "Give your AI agent a WhatsApp number in 5 minutes"
   - Timing: Tuesday/Wednesday for max visibility
   - Assets: 60-second demo video, comparison table vs Twilio
   - Target: #1 Product of the Day in AI/Developer Tools

2. **Hacker News**
   - Show HN post: "I built a WhatsApp runtime for AI agents (open-source core)"
   - Focus on technical depth — webhook dedup, fuzzy name resolution, group policies
   - Link to GitHub repo (open-source core)

3. **Dev Community Presence**
   - r/LocalLLaMA, r/ChatGPT, r/SelfHosted posts
   - Dev.to / Hashnode articles: "How I gave my AI assistant a WhatsApp number"
   - Discord servers: AutoGen, CrewAI, LangChain, AI agent builders

4. **GitHub Strategy**
   - Open-source the core plugin (current codebase, CC-BY-NC or MIT for core)
   - Managed service = the paid offering (hosting, admin panel, SLA, multi-tenant)
   - Star-farming: good README, demo GIFs, clear "Deploy in 5 minutes" guide
   - Target: 500 GitHub stars in 3 months

### 4.2 Phase 2: Content Engine (Months 2-6)

**Goal**: Establish SEO authority for "WhatsApp AI agent" keywords. 30 published pieces.

**Content Calendar**:

| Week | Type | Title | Target Keyword |
|------|------|-------|---------------|
| 1 | Tutorial | "Connect your AI agent to WhatsApp in 10 minutes" | whatsapp ai agent |
| 2 | Comparison | "WhatsApp for AI: Twilio vs. Self-Hosted vs. Managed" | twilio whatsapp alternative |
| 4 | Case Study | "How [Agency] deployed 12 WhatsApp AI assistants in a week" | whatsapp chatbot saas |
| 6 | Technical | "Webhook deduplication: Why your WhatsApp bot processes messages twice" | whatsapp webhook duplicate |
| 8 | Tutorial | "Multi-session WhatsApp: Monitor human chats with AI" | whatsapp multi device api |
| 10 | Comparison | "WATI vs. Respond.io vs. WhatsApp Channel Service" | wati alternative |
| 12 | Architecture | "How we handle 100K WhatsApp messages/day with SQLite" | whatsapp api scale |

**Distribution**: Blog (SEO), Dev.to (reach), Twitter/X (engagement), YouTube (tutorials).

### 4.3 Phase 3: Partnerships (Months 3-9)

**Goal**: 3 integration partnerships, 1 reseller deal.

| Partner Type | Target | Value Prop | Deal Structure |
|-------------|--------|-----------|---------------|
| **AI Agent Platform** | AutoGen, CrewAI, Semantic Kernel | "Official WhatsApp channel" integration | Rev share 20% or flat $5/customer/mo |
| **No-Code AI Builder** | Relevance AI, Stack AI, Flowise | "Add WhatsApp to any AI workflow" | Integration listing + co-marketing |
| **WhatsApp Infra** | WAHA (upstream) | "Recommended managed service for WAHA" | Cross-promotion, bundled offering |
| **AI Dev Agency** | Top 10 AI agencies | Volume discount for client deployments | Reseller at 30% discount |

### 4.4 Phase 4: Expansion (Months 6-12)

**Goal**: 200 paying customers, $16K MRR.

1. **Paid Acquisition** (if unit economics hold)
   - Google Ads: "WhatsApp API for AI" keywords (~$3-5 CPC)
   - Budget: $2K/mo, target $50 CAC
   - Retarget Sandbox users who haven't converted

2. **Webinars/Demos**
   - Monthly "WhatsApp AI Office Hours" — live integration demos
   - Guest spots on AI podcasts (Latent Space, Practical AI)

3. **Template Gallery**
   - Pre-built configs: "Customer Support Bot", "Personal Assistant", "Group Moderator"
   - Each template = landing page = SEO keyword

### 4.5 Open-Source Core vs. Proprietary SaaS Split

| Component | License | Rationale |
|-----------|---------|-----------|
| Core plugin (channel.ts, send.ts, inbound.ts) | MIT or Apache 2.0 | Community adoption, trust, contributions |
| Admin panel (React UI) | Source-available (BSL or SSPL) | Key differentiator, prevents cloning |
| Multi-tenant hosting platform | Proprietary | The actual SaaS product |
| Directory + access control engine | Source-available | Useful standalone but drives SaaS value |
| SDKs (Python, Go, REST) | MIT | Lower integration friction |
| Deployment tooling (Docker, Helm) | MIT | Reduces support burden |

**Strategy**: MIT core drives GitHub adoption and trust. Managed service provides the value (no ops, admin panel, SLA, multi-tenant isolation). This is the "open-core" model used successfully by Supabase, GitLab, Airbyte.

---

## 5. Marketing Materials Needed

### 5.1 Landing Page Structure

```
[Hero Section]
"Give your AI agent a WhatsApp number."
Subtitle: "100+ actions. Zero per-message fees. Production-ready in minutes."
CTA: "Start Free" | "See Demo"
Social proof: GitHub stars, customer logos (when available)

[Problem Section]
"Building WhatsApp for AI agents is harder than it should be."
- 3 pain points with icons:
  1. "Twilio charges per message. Your AI sends a lot of messages."
  2. "WAHA gives you an API. You still need to build everything else."
  3. "Name resolution, group policies, admin UI, health monitoring — that's months of work."

[Product Section — 3 columns]
Column 1: "100+ Actions"
  Send, poll, react, groups, contacts, channels, media, labels, presence...
  Screenshot of SKILL.md action table

Column 2: "AI-Native Features"
  Fuzzy name resolution, group activation policies, DM access control,
  multi-session (bot + human listener), trigger words
  Screenshot of admin panel directory tab

Column 3: "Production Infrastructure"
  Rate limiting, webhook dedup, session health monitoring, SQLite directory,
  React admin panel, configurable access policies
  Screenshot of admin panel status tab

[Comparison Table]
Side-by-side: Us vs Twilio vs Self-Hosted WAHA vs WATI
(Use the table from Section 1.3)

[Pricing Section]
4 tiers with feature comparison
CTA on each tier

[Integration Section]
"Works with your stack"
Logos: OpenClaw, AutoGen, CrewAI, LangChain, custom (REST API)
Code snippet showing 5-line integration

[Footer CTA]
"Your AI agent deserves a phone number."
CTA: "Start Free — No Credit Card"
```

### 5.2 Documentation Site

**Structure** (use Mintlify, Docusaurus, or Nextra):

```
/docs
  /quickstart
    - 5-minute setup guide
    - First message tutorial
    - Connect to [AutoGen/CrewAI/LangChain]
  /concepts
    - How sessions work
    - Name resolution explained
    - Access control policies
    - Group activation modes
    - Multi-session architecture
  /actions
    - Send messages (text, media, polls, locations)
    - Group management
    - Contact management
    - Channel/Newsletter
    - Labels
    - Status/Stories
    - Presence & Profile
  /admin-panel
    - Directory tab guide
    - Config tab guide
    - Filter stats guide
    - Status monitoring
  /api-reference
    - REST API (auto-generated from OpenAPI spec)
    - Webhook events
    - Error codes
  /guides
    - Build a customer support bot
    - Build a personal AI assistant
    - Build a group moderator
    - Monitor WhatsApp with AI (listener mode)
    - Migrate from Twilio
  /self-hosting
    - Docker deployment
    - Configuration reference
    - Troubleshooting
```

### 5.3 Demo / Sandbox Environment

**Interactive sandbox** (critical for conversion):

1. **Live Demo Page** (no signup required)
   - Pre-connected WhatsApp number (demo account)
   - User types a message in web UI, sees it arrive on WhatsApp and get AI response
   - Shows webhook payload, action dispatch, response — full round-trip visibility
   - Resets every 15 minutes

2. **Sandbox Account** (free signup)
   - Dedicated WAHA session on shared infrastructure
   - QR code pairing flow in admin panel
   - Pre-loaded with demo contacts and groups
   - 1,000 message limit, 7-day data retention
   - Full admin panel access

### 5.4 Video Content

| Video | Length | Purpose | Distribution |
|-------|--------|---------|-------------|
| Product demo (hero video) | 60 sec | Landing page, Product Hunt | YouTube, Twitter, landing page |
| "Zero to WhatsApp AI in 5 minutes" | 5 min | Developer onboarding | YouTube, docs |
| "Twilio vs. WhatsApp Channel Service" | 8 min | SEO + comparison shopping | YouTube |
| "Multi-session: Human + AI on WhatsApp" | 6 min | Feature highlight | YouTube, blog |
| "Admin Panel Walkthrough" | 4 min | Feature showcase | YouTube, docs |
| "Building a Group Moderator Bot" | 12 min | Tutorial/use case | YouTube, blog |

### 5.5 Comparison Pages (SEO)

Individual landing pages targeting competitor keywords:

1. **vs Twilio WhatsApp API**
   - "Save 90% on WhatsApp messaging costs"
   - Focus: per-message pricing trap, no agent features, complex setup
   - Target keyword: "twilio whatsapp api alternative"

2. **vs Self-Hosted WAHA**
   - "WAHA gives you the engine. We give you the car."
   - Focus: 3-6 months of building vs. 5-minute setup, admin panel, access control
   - Target keyword: "waha whatsapp managed hosting"

3. **vs WATI**
   - "Built for AI agents, not human support teams"
   - Focus: AI-native features, no per-seat pricing, developer-first
   - Target keyword: "wati alternative for developers"

4. **vs Respond.io**
   - "Your AI agent doesn't need a team inbox"
   - Focus: lightweight, API-first, no per-agent seats
   - Target keyword: "respond.io alternative ai chatbot"

5. **vs Building from Scratch**
   - ROI calculator: developer hours saved x hourly rate
   - "3-6 months of engineering or $29/month"
   - Target keyword: "whatsapp api integration cost"

---

## 6. Risks & Mitigations

| Risk | Probability | Impact | Mitigation |
|------|------------|--------|-----------|
| Meta restricts unofficial WhatsApp API usage | Medium | Critical | Support official WhatsApp Business API as fallback channel; WAHA Plus has better compliance story |
| WAHA project abandoned or breaks | Low | High | Fork and maintain; abstract WAHA dependency behind adapter pattern |
| Twilio launches AI-native WhatsApp features | Medium | Medium | Move faster; our depth in agent-specific features is 2+ years ahead |
| Low conversion from Sandbox to paid | High | Medium | Aggressive nurture sequences; time-limited Sandbox (30 days); usage alerts |
| WhatsApp blocks numbers used by bots | Medium | High | Best practices guide; phone number warming; rate limiting defaults |
| Customer data security concerns | Medium | Medium | SOC 2 certification (Year 2); data residency options; encryption at rest |

---

## 7. Key Metrics & Milestones

### North Star Metric
**Monthly Active WhatsApp Sessions** — number of WhatsApp sessions actively sending/receiving messages through the platform.

### Year 1 OKRs

| Quarter | Objective | Key Results |
|---------|-----------|-------------|
| Q1 | Launch & seed | 500 GitHub stars, 100 Sandbox signups, 15 paying customers, Product Hunt launch |
| Q2 | Content engine | 20 published pieces, 3 SEO keywords in top 10, 50 paying customers, 1 partnership signed |
| Q3 | Growth | $8K MRR, 100 paying customers, 2 integration partnerships live, < 4% monthly churn |
| Q4 | Scale | $16K MRR, 200 paying customers, 3 case studies published, Series seed discussions |

### Dashboard Metrics

| Category | Metrics |
|----------|---------|
| **Acquisition** | Signups/week, Sandbox activations, GitHub stars, docs page views |
| **Activation** | Time to first message, QR code scan completion rate, first action success rate |
| **Revenue** | MRR, ARPU, expansion revenue, net revenue retention |
| **Engagement** | Messages/session/day, actions used per customer, admin panel DAU |
| **Retention** | Monthly churn rate, NPS, support ticket volume |

---

## 8. Immediate Next Steps

### Pre-Launch Checklist (Weeks 1-4)

1. **Week 1**: Create landing page (Framer or Next.js), set up waitlist
2. **Week 1**: Extract open-source core, create separate GitHub repo with MIT license
3. **Week 2**: Build multi-tenant provisioning (Docker-based session isolation)
4. **Week 2**: Write "5-minute quickstart" tutorial + record demo video
5. **Week 3**: Set up Stripe billing with 4 tiers
6. **Week 3**: Build Sandbox provisioning flow (signup -> QR code -> connected)
7. **Week 4**: Product Hunt submission, HN Show post, Reddit posts
8. **Week 4**: Set up docs site (Mintlify) with quickstart + API reference

### Technical Requirements for SaaS

| Requirement | Priority | Effort |
|-------------|----------|--------|
| Multi-tenant session isolation | P0 | 2 weeks |
| Signup + QR code onboarding flow | P0 | 1 week |
| Usage metering (messages, contacts, groups) | P0 | 1 week |
| Stripe billing integration | P0 | 1 week |
| Tier-based feature gating | P1 | 1 week |
| Customer dashboard (usage, billing, settings) | P1 | 2 weeks |
| REST API with API key auth | P1 | 1 week |
| Auto-scaling for shared infrastructure | P2 | 2 weeks |
| SOC 2 / compliance prep | P2 | Ongoing |

---

## Appendix A: Naming Options

| Name | Domain Available | Notes |
|------|-----------------|-------|
| wahub.io | Check | WAHA + hub |
| agentwhatsapp.com | Check | Descriptive, SEO-friendly |
| waruntime.com | Check | "WhatsApp Runtime" |
| channelkit.dev | Check | Generic but extensible |
| whatsagent.io | Check | WhatsApp + Agent |

Recommendation: **whatsagent.io** or **agentwhatsapp.com** — immediately communicates the value prop.

## Appendix B: Competitive Pricing Benchmarks

| Service | Base Price | Per-Message | Sessions | AI Features |
|---------|-----------|-------------|----------|-------------|
| Twilio WhatsApp | $0 | $0.005-0.08 | N/A | None |
| WATI | $49/mo | Included (limited) | 1 | None |
| Respond.io | $79/mo | Included | 1 | Basic AI |
| 360dialog | $15/mo | $0.005-0.07 | 1 | None |
| WAHA Plus | $49/mo | $0 | Unlimited | None |
| **Us (Starter)** | **$29/mo** | **$0 (10K included)** | **1** | **Full (100+ actions)** |
| **Us (Pro)** | **$149/mo** | **$0 (100K included)** | **3** | **Full + multi-session** |