arv1production

byinfo 369

Build a production-oriented SaaS MVP called RetEdge. RetEdge is a Recovery Operating Layer for Indian B2B distributors. IMPORTANT: Do not build a generic AR dashboard. Do not build an accounting system. Do not build a generic CRM. Do not build a generic WhatsApp reminder application. The core product is a daily recovery decision and execution workflow. ================================================== CORE PRODUCT PROMISE ================================================== "RetEdge tells a distributor which customers their collection team should act on today, why, and what to do next — then tracks what happened and reprioritizes the account." ================================================== TARGET CUSTOMER ================================================== Indian B2B distributors. Initial vertical: Electrical and electrical-industrial-supplies distributors. Typical company: ₹10–50Cr revenue 100–300 active credit buyers Tally/BUSY/Excel/manual collection workflows Economic buyers: Owner Managing Director CFO Finance Head Finance Manager Daily users: Accountant Collections Executive Collections Manager ================================================== CORE WORKFLOW ================================================== Receivables ↓ Recovery Audit ↓ Recovery Intelligence ↓ Priority ↓ Today's Recovery Actions ↓ Action Execution ↓ Customer Response ↓ Payment Commitment ↓ Payment / Outcome ↓ Broken Promise Detection ↓ Escalation ↓ Re-prioritization ↓ New Today's Recovery Actions This workflow is the heart of the product. ================================================== MVP INPUT ================================================== The first version accepts CSV/XLSX receivables data. Do NOT build Tally/BUSY integrations in the first implementation. Supported fields: Customer Name Invoice Number Invoice Date Due Date Invoice Amount Amount Paid Outstanding Balance Days Overdue Optional: Promise Date Promise Amount Notes Collector Salesperson Customer Phone Customer Email ================================================== RECOVERY AUDIT ================================================== After upload, calculate: Total Outstanding Total Overdue Overdue % Ageing buckets Top overdue customers Largest exposures Oldest overdue accounts Broken promises if available Data quality problems Customer concentration Priority recovery exposure Show the audit before showing the recovery queue. ================================================== RECOVERY INTELLIGENCE ================================================== Create a deterministic and explainable scoring engine. Every score MUST have: Priority Score Priority Level Reason Codes Evidence Recommended Action The system must never invent financial facts. AI may explain or summarize. Financial calculations must be deterministic. Example: ABC Electrical Outstanding: ₹8,40,000 Days overdue: 62 Broken promises: 2 Latest promise: ₹3,00,000 Friday Payment received: ₹0 Output: Priority: CRITICAL Why today: High outstanding exposure + 62 days overdue + Repeated broken promises + Latest promise failed Recommended action: Owner escalation + Call + WhatsApp follow-up ================================================== TODAY'S RECOVERY QUEUE ================================================== The primary home screen must be: TODAY'S RECOVERY ACTIONS Each item shows: Customer Outstanding Days overdue Priority Why today Evidence Recommended action Last interaction PTP status Next action Example: 🔴 ABC Electrical ₹8.4L overdue 62 days 2 broken promises WHY TODAY: High exposure + repeated broken PTP ACTION: Owner escalation + call ================================================== RECOVERY ACTIONS ================================================== Users can: Call Open WhatsApp Create follow-up Record customer response Create payment promise Record partial payment Record full payment Record dispute Record no response Escalate Snooze with reason Every action creates a recovery event. ================================================== PAYMENT PROMISE STATE MACHINE ================================================== States: NO_PTP PTP_CREATED PTP_DUE PAYMENT_PARTIAL PAYMENT_COMPLETED PTP_BROKEN ESCALATED NEW_PTP Only valid transitions are allowed. Example: PTP_CREATED ↓ PTP_DUE ↓ NO_PAYMENT ↓ PTP_BROKEN ↓ ESCALATION When a promise becomes broken: Increase priority Create BROKEN_PTP event Generate next recommended action Return account to Today's Recovery Actions ================================================== RE-PRIORITIZATION ================================================== The queue must change when new information is recorded. Examples: Payment received → lower outstanding → lower priority New PTP created → update recovery state PTP broken → increase priority Customer dispute recorded → change recommended action No response → increase follow-up priority according to rules ================================================== USER ROLES ================================================== Owner/CFO Finance Manager Collections Manager Accountant/Collections Executive Each role should see an appropriate view. ================================================== OWNER/CFO VIEW ================================================== Show: Total overdue Priority recovery amount Payments received Broken promises PTPs due today High-risk accounts Accounts requiring escalation Cash currently trapped Do NOT create dozens of charts. ================================================== DATABASE ================================================== Use PostgreSQL. Core entities: organizations users roles customers invoices receivables payments payment_promises recovery_cases recovery_actions recovery_events escalations audit_logs The application must be multi-tenant. Tenant data must never be visible across organizations. ================================================== SECURITY ================================================== Implement: Authentication Authorization Tenant isolation Row-level security where supported Audit logging Secure file uploads Server-side validation Secret management Never expose API secrets in frontend code. ================================================== UI ================================================== Mobile responsive. Simple Indian B2B business software. Do not make it look like a consumer AI application. Primary navigation: Overview Recovery Audit Today's Actions Customers Receivables Recovery History Reports Settings Today's Actions should be the primary screen. ================================================== MVP EXCLUSIONS ================================================== Do NOT build: Tally connector BUSY connector QuickBooks connector Marg connector Xero connector AI voice calling Mass WhatsApp campaign engine SMS automation Email automation Mobile native application Complex predictive ML Generic chatbot Accounting functionality ERP replacement These are future phases. ================================================== TECHNICAL REQUIREMENTS ================================================== Use a maintainable full-stack architecture. Prefer: TypeScript React/Next.js PostgreSQL Tailwind/shadcn or equivalent component system Use automated tests. Use realistic seed data representing an Indian electrical distributor. ================================================== CRITICAL DEVELOPMENT RULE ================================================== Do not generate the entire application blindly from this prompt. First create: 1. Requirements 2. User flows 3. Database architecture 4. Recovery engine specification 5. Action policy specification 6. Technical architecture 7. Implementation plan STOP. Ask for human approval before implementation. After approval: Build in vertical slices. Each completed feature must have: Unit tests Integration tests where appropriate UI tests for critical workflows Error states Empty states Loading states Security checks The final MVP must be deployable and usable with a real CSV/XLSX file. The most important test is: Can a distributor upload real receivables and immediately see a trustworthy list of customers that the collection team should act on today? If not, the MVP is not complete.