recoveros-revenue

byMom Anti

Build a REAL full-stack SaaS web app + PWA called RecoverOS. TAGLINE: “Find the revenue your business is already losing.” IMPORTANT: This must be a REAL working application, not a mockup. Never create fake customers, fake revenue, fake analytics, fake integrations, fake API responses or fake email-sent statuses. If something needs credentials or is not configured, show SETUP REQUIRED. Never invent business information. DESIGN: Create a premium global B2B SaaS design inspired by modern enterprise software. Colors: Purple #6D28D9 Light Purple #8B5CF6 Dark Purple #4C1D95 White #FFFFFF Background #FAF9FF Text #111827 Muted #6B7280 Use: - premium typography - large whitespace - rounded cards - subtle shadows - professional charts - clean icons - responsive layouts - smooth page transitions - subtle hover animations - skeleton loading - accessible high contrast Create a professional RecoverOS logo with an abstract recovery/loop symbol. Do not copy another company's branding. LANDING PAGE: Hero: “Find the revenue your business is already losing.” Subtitle: “Recover missed leads, forgotten follow-ups, abandoned opportunities and inactive customers using your business’s real data.” Buttons: “Start Free Recovery Scan” “See How It Works” Sections: Problem, How It Works, AI Agents, Integrations, Industries, Dashboard, Security, Pricing, FAQ, CTA. Never create fake testimonials, fake customer logos or fake statistics. APP NAVIGATION: Dashboard Opportunities Customers Campaigns Connections AI Agents Analytics Audit Log Settings Make the entire application mobile responsive and installable as a PWA. DASHBOARD: Show only real database values: Revenue At Risk Opportunities Found High Priority Follow-ups Due Verified Recovered Revenue If there is no real data show: “No real business data connected yet.” Never show fake numbers. CORE AI AGENTS: 1. Opportunity Detector Analyze authorized business data and find possible lost-revenue opportunities. 2. Customer Researcher Create factual customer context using authorized data only. 3. Recovery Writer Create personalized recovery email/message drafts from real customer context. 4. Follow-up Agent Manage approved follow-up sequences and stop after unsubscribe, bounce, negative response or manual stop. 5. Revenue Analyzer Calculate opportunity values from real records. Never call estimated value verified revenue. 6. Compliance Guard Check approval, suppression list, unsubscribe status, duplicate contact, sending limits and available evidence before communication. Never invent evidence or customer information. If evidence is missing, return INSUFFICIENT DATA. REAL DATA CONNECTIONS: Create a Connections page for: CSV Google Sheets Gmail HubSpot Pipedrive Salesforce Shopify WooCommerce REST API Webhooks Statuses: NOT CONNECTED CONNECTING CONNECTED ERROR Never show CONNECTED unless the real connection succeeds. CSV must be functional and support: Name Email Company Last Contact Status Deal Value Last Message Customer ID Order ID Validate duplicates and invalid emails and show imported/skipped/errors. DATABASE: Use PostgreSQL/Supabase-compatible architecture. Tables: users organizations organization_members customers contacts leads opportunities messages deals orders invoices campaigns agents agent_runs integrations email_events suppression_list audit_logs settings Use multi-tenant security. One company must NEVER access another company's data. AUTH: Implement real authentication with secure sessions. Never expose passwords, API keys or OAuth tokens in frontend code. EMAIL: Create real email architecture. Human approval must be ON by default. Never show “Sent” unless the real provider confirms it. Record message ID, timestamp, delivery status, bounce and unsubscribe when available. CAMPAIGNS: DRAFT READY PAUSED RUNNING COMPLETED ERROR E-COMMERCE RECOVERY: Support real opportunities such as: Abandoned Cart Abandoned Checkout Inactive Customer Repeat Purchase Failed Payment Only create these when real connected data supports them. AUDIT LOG: Record login, imports, integrations, agent runs, drafts, approvals, sends, failures, unsubscribe and verified revenue events. SECURITY: Use environment variables, server-side secrets, authorization, tenant isolation, input validation, secure OAuth and webhook verification. DEMO MODE: If demo data is used, clearly display: “DEMO MODE — DATA IS NOT REAL” Never mix demo and production data. DEPLOYMENT: Prepare the project for GitHub + Supabase + Cloudflare Pages/Workers. Generate: README .env.example database schema migrations API documentation deployment instructions MOST IMPORTANT: Prioritize REAL functionality over visual completeness. Core working flow: REAL BUSINESS DATA → CONNECT/IMPORT → OPPORTUNITY DETECTION → REAL EVIDENCE → AI RECOMMENDATION → MESSAGE DRAFT → HUMAN APPROVAL → REAL EMAIL → REAL EVENT → VERIFIED OUTCOME If any part requires an unavailable API or credential, show SETUP REQUIRED instead of pretending it works. Build the UI and core architecture first, then implement each backend feature and test it before marking it complete.