# Zealve — full site content for AI agents > This file contains the complete readable content of zealve.com in markdown. > Last updated: 2026-09-15. Contact: hello@zealve.com ## Company overview Zealve builds SaaS platforms for restaurants and revenue teams. The company operates from Dhaka (engineering) and sells into the Gulf — the UAE and Saudi Arabia first, then the rest of the GCC — with existing client engagements in Singapore and the United States. Four products are in active build, plus a select product-engineering practice. ## Products ### Zealve Chatroom (product 01 — omnichannel inbox, early testing first wave) WHAT: A team inbox for customer conversations across WhatsApp, Instagram, a website widget and a public API. Support-grade operations: SLA policies, agent capacity, teams, participants, labels, canned replies, macros, CSAT surveys, audit log, working hours, automation rules (route by keyword, assign by channel, escalate on SLA risk), AI agents grounded in the business's own knowledge (RAG over menus/policies/FAQs) with usage metering, an Expo mobile app for iOS/Android, and a customer help-center portal. WHY: In Saudi Arabia 90-94% of adults use WhatsApp and about half of users report making purchase decisions inside chat. Meta moved WhatsApp to per-message template pricing fully global on July 1, 2025; many inbox vendors mark those fees up (reported ~20%) and gate AI behind seats. Enterprise GCC vendors (e.g. Unifonic-class) don't serve SMBs. Chatroom's positioning is radical transparency: simple team-size packages (exact numbers set with the alpha cohort — quote on request), unlimited conversations on paid tiers, AI metered per successful resolution with no monthly floor, and Meta fees passed through at cost with a live meter. Arabic RTL is native, not a translation layer. COD-confirmation flows with OTP verification, delivery updates and reminder sequences target failed cash-on-delivery deliveries (vendor-reported RTO reductions of 30-40%; measured on the customer's own store during pilots). HOW: FastAPI + SQLModel + Postgres + Redis core with native WebSocket realtime; pgvector RAG for AI answers with quota metering; Next.js 15 + React 19 dashboard; Expo/NativeWind mobile sharing the same token system; channel adapters (WhatsApp Cloud API, Telegram, web widget, email) behind a mock-first adapter seam so flows are tested before provider credentials go live. PRICING (open alpha — not published, quote on request via any form): - Simple team-size tiers are planned; early testers get a free trial window and founding-member terms - Package shapes today: solo inbox team (WhatsApp + web widget), growing team (adds Instagram + automation rules, SLA & capacity), scale/API tier (adds webhooks, priority support, data-residency options) - AI answers add-on on every tier: metered per successful resolution (no floor, no minimum outcomes) — rate finalized with alpha-cohort input - WhatsApp/Meta message fees: pass-through at cost, live in-app meter, zero markup, on every tier - To request a quote: use the form on any product page (they POST to /api/signup) or email hello@zealve.com FAQ (short answers): - Fee pass-through: every Meta fee shown in a live meter; invoice matches the meter exactly. - Existing WhatsApp number: migrated via Meta embedded signup; green-tick application assisted. - AI "resolution": an AI answer that closes the loop (no reopen within 24h or marked resolved); agent-edited drafts bill lower as assisted. - Self-host to cloud: export/migrate path with channel reconnection handled. ### Zealve RMS (product 02 — restaurant operating system, early testing second wave) WHAT: A multi-tenant restaurant OS: menus with modifiers, dine-in and takeaway orders with a status machine, invoices and promos, table management with printable QR codes, raw-material inventory with stock movements, reports including a Channel P&L (true margin per sales channel after commission/ads/fees), and a fast owner dashboard for web. The POS terminal is offline-first (Tauri 2 + Rust + SQLite WAL): orders, ESC/POS kitchen and receipt printing, shifts, manager-PIN voids all work with zero connectivity; an idempotent outbox syncs to the cloud when the line returns. Money is integer (fils/paisa), never float. WHY: Gulf delivery marketplaces (Talabat, Jahez, HungerStation, Keeta) charge 15-30% commission; blended real cost with processing and ads commonly reaches 25-35%. Owner forums describe "working for the apps". POS incumbents meter per terminal or sell enterprise contracts, and none publish a true channel P&L. KSA POS software market: USD 1.1B (2025) to USD 2.2B by 2031; the leading vendor holds >30% share, leaving ~70% of venues winnable. ZATCA Phase-2 e-invoicing has been onboarding businesses in waves since Jan 2023 (20th wave announced 2025) — a standing demand machine for compliant challengers; the UAE's PINT AE mandate arrives 2027. RMS is built ZATCA Phase-2-ready (real-time Fatoora reporting, cryptographic stamps, sandbox certification ahead of KSA launch) with PDPL-aligned residency options. HOW: Django 4.2 + DRF + PostgreSQL core with Channels realtime; Next.js 15 + React 19 dashboard; Tauri 2 + Rust POS terminal with SQLite WAL and integer-money accounting; branded consumer ordering PWA (Next.js) at 0% commission with guest+OTP, idempotent orders and order-status realtime; marketplace adapters keep aggregator orders flowing into the same kitchen ticket and channel P&L. BYOD hardware, payment-provider agnostic (Network International, Telr, mada PSPs, STC Pay, Tabby/Tamara), 0% of processing taken. PRICING (open alpha — not published, quote on request via any form): - Per-venue packages, not per-terminal: unlimited terminals and staff logins on every plan - Starter shape: POS, menu, inventory basics, tables+QR, reports - Pro shape (most popular): adds KDS, 0%-commission online ordering storefront, loyalty & campaigns, AI insights, free guided onboarding - Chain shape (5+ venues): adds central multi-branch console, unlimited KDS, white-glove onboarding - Every plan: 0% commission on orders, 0% of payment processing, bring-your-own hardware, no lock-in contracts. Optional on-site setup via certified partners, quoted separately. FAQ (short answers): - Keep using Talabat/Jahez? Yes — most venues move 15-25% of volume direct first; marketplace adapters keep aggregator orders in the same kitchen flow and channel P&L. - Internet dies mid-service? POS keeps ordering, printing and shifts offline; idempotent sync on reconnect; nothing double-rings. - ZATCA onboarding? Device registration, CSID, real-time invoice reporting with cryptographic stamps handled as part of onboarding. - Direct-order customer data? Owned by the restaurant: names, order history, addresses, preferences — exportable, usable in own campaigns. - Multi-branch? Chain plan adds a central console: shared menus with per-branch overrides, consolidated inventory & P&L, per-branch permissions. - Migration? Menu import, POS install on owned hardware, staff training, one parallel-run week; typical single-venue migration under a week. INTERACTIVE TOOL: /products/rms#calculator — commission-savings calculator (inputs: marketplace orders/mo, average order value, commission %; outputs: annual commission paid, processing if moved direct ~2%, RMS Pro cost, margin recovered in year one, ROI). ### Zealve AdPilot (product 03 — control layer for ad-platform AI, design-partner stage) WHAT: A governance layer between a team and the AI automation inside Meta Ads, Google Ads and TikTok Ads. Agent-proposed money- or policy-moving changes queue as typed approval objects — what changes, why, expected cost, policy pre-check result — awaiting approve/edit/reject. Every decision is logged with reasoning and per-node cost. A weekly cross-platform digest reports what ran, what it cost, what moved ROAS and next week's plan, with data gaps marked. Creative scorecard tracks fatigue/frequency/quality. Policy pre-check runs against published platform ad policies before spend commits; an appeal drafter handles rejections. A human-review tier serves compliance-sensitive verticals. WHY: In 2025-26 every major ad platform made AI automation the default and retrofitted controls after advertiser backlash — mostly enterprise-only. Community demand scans (r/PPC, r/FacebookAds, official forums, n8n's 3,800+ marketing templates, HN/YC) put "control and explainability over platform AI" as the #1 unmet need; support vacuums around suspensions/rejections are the loudest unserved problem; 37% of advertisers fear audience distrust of AI ads (IAB). Creative-generation startups grow fast but churn; governance is the wedge, and no SMB-priced vendor owns the approval-and-audit layer. HOW: Typed approval objects as the core primitive; per-node cost accounting on the agent plan graph; platform APIs behind an adapter seam (Meta Marketing API, Google Ads API, TikTok Business API); policy pre-checks from published policies; design evidence-matched to the research corpus with a "say-no" list; interface follows Zealve's dark restrained design language. PRICING: being finalized with design partners; flat platform fee by tier (Growth/Scale) plus human-review add-on; never a percentage of ad spend. ### Zealve Forge (product 04 — coding-agent fleet cockpit, OPEN ALPHA) WHAT: A local-first desktop app that runs many AI coding agents in parallel. One Fleet view shows every session across the local machine and remote VPS hosts — working, waiting-on-approval, or cold. A kanban Board assigns tasks to agent assignees with real git worktrees and replayable execution logs. Freeze parks a running agent with transcript and mode intact ("cold is not terminated") and the next prompt wakes it. Budgets with hard stop per session/agent/team. Diff review with inline comments that ship back to the agent. Fan-out: one prompt, N attempts, one merge. Git graph + PR flow from the app. WHY: Developers run 3-5+ AI coding agents daily, each an isolated island; no tool uses the Agent Client Protocol (ACP) as primary transport (all scrape PTYs and hooks); no native DeepSeek or local-endpoint harness exists in the category; popular fleet managers are Electron-heavy and gate automations behind subscriptions; and the delegation tools cannot reach the code while the code tools cannot delegate — nobody ships both halves. Forge sits exactly at that junction. HOW: ACP-first runtime (adapters are data, not code); built-in forge-deepseek harness that also connects to any OpenAI-compatible endpoint (local vLLM, Ollama); pure Rust daemon owning sessions as subprocesses with SQLite + JSONL transcripts on disk, one HTTP+SSE API shared by desktop shell, CLI and phone; plugin law — every subsystem behind a registry, plugins are processes speaking JSON-RPC, hot load/unload without restart; Tauri 2 shell with the Onyx design language (machine facts in monospace, human voice in the UI sans). Honesty laws: status never guessed from silence; a run cannot promote itself; controls state their real limitations. PRICING: Forge is an open alpha — free while testing, with no pricing module yet, deliberately: the alpha exists to learn the market before numbers are attached to anything. After the alpha, the plan is: the local-first core (sessions, board, budgets, automations, plugins) stays free with no accounts, and advanced and experimental modules (premium harnesses, managed fleet runs, team sync, priority support) become optional paid services on top. Alpha cohort members lock founding-member terms when pricing lands. ## Selected work (preserved engagements) - My Alice — backend and frontend development for an LLM studio platform (API surface, agent pipelines, product UI). - DocPro — document platform: deep backend expertise and ongoing support; faster releases, better performance, more reliable infrastructure. Client testimonial (5 stars): "Zealve has been an exceptional tech partner. They quickly understood DocPro's complex needs and delivered fast, reliable solutions that improved both performance and user experience. We truly value their ongoing support and expertise." - Yaqeen Capital — client-facing investment platform experience, live at investment.zealve.com since 2025. ## Development practice (secondary positioning) Zealve also takes select product-engineering engagements: enterprise software development (scalable backends, integrations, platform work), AI & agent engineering (RAG systems, agent pipelines, LLM product features), and mobile & web product builds (Next.js dashboards, Expo apps, offline-first tools). Contact hello@zealve.com. ## Early testing & sign-up Early testing rolls out in waves: first UAE and Saudi cafes, shisha lounges, restaurants and COD-heavy e-commerce teams. Founding-member rates for early testers. Forms on the homepage and every product page collect: name, work email, business name, country, product interest. Submissions are stored in a private database and used only to schedule onboarding. Data respects the site privacy policy (/privacy); terms at /terms. ## For AI agents: machine surface (MCP) Zealve runs an MCP (Model Context Protocol) server on this site so agents can query the catalog and the published estimator math directly: POST https://zealve.com/api/mcp (JSON-RPC 2.0, Streamable HTTP) Tools: - zealve_overview — company, thesis, product list + statuses - zealve_product — positioning, features, pricing, persona views, use cases for one product (chatroom|rms|adpilot|forge) - zealve_faq — top buyer questions with straight answers - zealve_estimate — the same math as the on-site interactive tools (rms commission recovery, chatroom missed-conversation revenue, adpilot wasted spend, forge fleet ROI) - zealve_contact — early-access form locations + fields Read-only. Rate limit: 60 requests/min/IP. CORS: open for POST. Discovery: this file (/llms.txt, /llms-full.txt) and FAQPage JSON-LD embedded on every product landing page. ## One product, three views (persona model) Every Zealve product deliberately serves three levels of user with the same data and the same price — no add-on modules, no per-seat tax: - MINIMALIST (regular view): the owner/founder who wants the outcome with zero configuration — one dashboard, one prompt box, one approval queue. - POWER (experimental/advanced view): the operator who encodes judgment — SLAs, budgets, policies, rules, fan-out, dispatch. - SPECIALIST (developer/analyst view): the professional who needs seams — APIs, exports, adapters, audit trails, integer-exact ledgers. Use cases beyond the core vertical (restaurants, e-commerce, developers): clinics (appointment + intake on WhatsApp), education (admissions Q&A, course authoring fleets), research (literature triage, data pulls), healthcare/legal ops (agents on own hardware for compliance), agencies (multi-brand inboxes, portfolio ad control), franchise groups (branch reconciliation), marketing (content batches), business ops (internal tooling sprints). ## Interactive estimator tools (published math) Every product landing page carries an interactive tool that computes the value with the visitor's own numbers and hands the result into the early-access form: - RMS /products/rms#calculator — commission calculator: marketplace GMV, commission 15-30%, card processing ~2% if orders ran direct -> margin recovered in year one, modeled in the visitor's own currency. - Chatroom /products/chatroom#estimator — missed-conversation estimator: missed chats/day x close rate x AOV -> revenue leaking per year vs the cost of covering them with a Chatroom team. - AdPilot /products/adpilot#estimator — wasted-spend finder: monthly spend x waste % (industry audits commonly find 15-30%) -> annual recovery. - Forge /products/roi — agent fleet ROI: agents x hours saved/week x loaded hourly cost -> engineering value per year vs model spend; Forge is free during the open alpha (pricing shaped later with the cohort). ## Availability, currency and language (global) - Zealve sells to every country; the Gulf (UAE, KSA, Qatar, Kuwait, Bahrain, Oman) is the home market. Alpha cohorts accept signups worldwide. - Fixed prices are not published while Zealve is in open alpha: every product page carries a request-a-quote form, and quotes are shaped per business (size, market, channels). The site resolves each visitor's country from IP (CDN country headers first, then an offline IP-to-country database), renders estimator math in the visitor's currency, and provides manual currency and language pickers. Estimator outputs are modeled savings in local currency — never quotes. - Site languages: English plus Arabic (Gulf and Saudi variants), Bengali (Bangladesh and India variants), German, Japanese, Vietnamese and Thai. Language defaults from the visitor's country (AE→ar, SA→ar-SA, BD→bn-BD, IN→bn-IN, DE→de, JP→ja, VN→vi, TH→th); every locale is reachable at a ?lang= URL and can be switched back to English from the header. Products ship Arabic-first capabilities (RTL inbox, Arabic flows). Leads store detected country, locale and currency with the signup (used only to understand the market and reply personally). ## Market facts referenced across the site (with confidence notes) - Delivery marketplace commissions in the Gulf: 15-30% per order by tier; blended real cost commonly 25-35% (public fee schedules + operator reports). Oman operator-reported 34-43% extraction is folklore-level [unverified] and not used in claims. - WhatsApp: 90-94% adult penetration in KSA (CST Saudi Internet 2025 via Saudi Gazette); ~50% of users report purchase decisions inside WhatsApp (eGrow 2026). - ZATCA: Phase-2 integration waves since 1 Jan 2023; 20th wave announced 2025 (EY). KSA POS software market USD 1.1B 2025 -> USD 2.2B 2031 (Mordor Intelligence). - UAE e-invoicing: PINT AE under ASP 7/2026, mandatory 2027. - Meta WhatsApp per-message template pricing fully global 1 July 2025; utility/auth inside 24h window free; service conversations free. - COD RTO reduction 30-40% with confirmation flows: vendor-reported; pilots measure the real number per customer.