Product Requirements (PRD)عربيPrint / PDF

Comestare — Product Requirements Document (PRD)

Scope: the core Comestare product (web platform). Audience: founder, future engineers/designers, and technical investors. Companion: SRS (system/technical requirements).

1. Overview

Comestare is a bilingual (EN/AR) web application that generates AI marketing strategies from an idea or URL and supports self-serve and done-for-you monetization. This PRD defines goals, users, features, and acceptance criteria.

2. Goals & success metrics

GoalMetricTarget
Instant value% signups generating in first session≥ 70%
Convert free → paidFree→paid rate≥ 4%
Monetize intent% hot leads contacted for done-for-you within 24h≥ 90%
Bilingual parityFeature parity EN/AR100% of funnel
Retention30-day active (SaaS)≥ 35%

3. Personas (built into the product)

vibeCoders, ideaOnly, stuckBuilders, adReady, agencies, securityAnxious. Each maps to messaging and an entry point (see Marketing & Leads).

4. User stories (core)

  • As a founder, I paste my URL and get a full marketing strategy (map + roadmap) in under a minute, so I know exactly what to do.
  • As a free user, I can generate one strategy/month and preview value (watermarked), so I'm motivated to upgrade.
  • As a Pro user, I get unlimited strategies, competitor analysis, validation reports, and exports.
  • As an SME (adReady), I can request "run it for me" (Ad Studio) without learning the tool.
  • As an agency, I can white-label and manage multiple clients.
  • As an Arabic speaker, I use the entire product natively in Arabic (RTL).
  • As the founder/admin, I manage users, pricing, routes, finance, and audit via the admin panel.

5. Functional requirements

5.1 Strategy generation (core)

  • FR-1 Accept input as free-text idea or URL; validate and normalize.
  • FR-2 Generate a marketing universe map: positioning, target audiences/personas, channels, messaging pillars, competitor context.
  • FR-3 Generate a phased roadmap: sequenced actions grouped into phases (validate → launch → scale).
  • FR-4 Render the universe as an interactive, explorable map; roadmap as phase cards.
  • FR-5 Enforce plan limits (free = 1/mo, watermark; paid tiers per pricing).
  • FR-6 Support regeneration/refinement of a strategy.
  • FR-7 Localize generation + UI for EN/AR.

5.2 Accounts, auth, plans

  • FR-8 Sign up / log in via email + OTP verification and Google sign-in.
  • FR-9 Manage subscription tier (Free/Starter/Pro/Agency); upgrade/downgrade; checkout.
  • FR-10 Gate features by tier (export, competitor report, watermark removal, seats, API, white-label).

5.3 Outputs & execution

  • FR-11 Export strategy/roadmap (PDF/roadmap) for paid tiers.
  • FR-12 Competitor analysis & validation report (Pro+).
  • FR-13 "Done-for-you" intake: request Ad Studio or a Service; capture brief + budget; route to sales/CRM as a hot lead.
  • FR-14 (Roadmap) Campaign/creative generation; roadmap task tracking.

5.4 Done-for-you operations

  • FR-15 Ad Studio: client onboarding, creative pipeline, platform connection (Meta/TikTok), weekly reporting.
  • FR-16 Services: milestone-based project tracking and billing (e.g., 30/40/30%).

5.5 Admin platform (exists)

  • FR-17 Admin auth (separate from customer auth) with roles (owner/admin/viewer).
  • FR-18 Manage users, sessions, audit events.
  • FR-19 Manage pricing tiers (public pricing served from admin-backend).
  • FR-20 Manage the gateway route registry (middleware consumes it).
  • FR-21 Finance: wallets/balances, transactions.

5.6 Leads & analytics

  • FR-22 Capture lead record (identity, source/UTM, firmographics, behavior, consent) per lead schema.
  • FR-23 Compute lead score; set lifecycle stage; route hot leads.
  • FR-24 Track funnel events (visit → signup → generate → pricing → upgrade) with attribution.

6. Non-functional (summary; full in SRS)

Performance (generation feels fast / streamed), reliability (auth + gateway hardened), security & privacy (PDPL/GDPR, consent, data regions), scalability (caching, inference cost control), i18n (EN/AR/RTL), accessibility.

7. Out of scope (now)

Native mobile apps; full CRM replacement; non-marketing services; languages beyond EN/AR (post-traction).

8. Release criteria (MVP launch)

  • FR-1–FR-12, FR-17–FR-24 working in EN and AR.
  • Payments live for all SaaS tiers; done-for-you intake routing leads.
  • Analytics, lead capture & scoring operational.
  • Auth + middleware↔backend reliability verified end-to-end (no 5xx on the auth path).
  • Acceptance: a new EN user and a new AR user can each sign up → generate → hit a paywall → upgrade → export, with the event funnel recorded.

9. Dependencies & open items

  • AI model/provider for generation (cost & quality guardrails).
  • Stripe + local GCC payment rails.
  • Email/OTP deliverability.
  • Resolve known production issues before scaling spend: middleware↔customer-backend networking, Google sign-in config/session, cross-domain refresh cookie (tracked in SRS appendix).