outperosys/outpero-crm

1. This is a monolithic Next.js App Router CRM application. The UI, server-side data access, mutations, and a small set of API endpoints all live in one repo rather than being split into separate frontend/backend services.

2. The application is organized around two route groups: an auth area under app/(auth) and the main CRM workspace under app/(crm). The CRM group contains the product’s major screens: dashboard, leads, pipeline, activity, meetings, follow-ups, tasks, services, settings, and financial documents.

3. Authentication appears to be built around Supabase, with both client and server helpers in lib/supabase/*, plus lib/auth.ts and proxy.ts likely enforcing session-based route protection and redirecting unauthenticated users to /login.

4. The main data layer uses Prisma. prisma/schema.prisma, the migration history, lib/prisma.ts, and prisma/seed.ts indicate a relational database-backed domain model with seeded reference data and incremental schema evolution for leads, activities, tasks, follow-ups, proposals, meetings/transcripts, invoices, receipts, services, tags, and settings.

5. User actions are concentrated in the actions/ folder. These server actions are the primary mutation boundary for the app: they handle CRUD and workflow operations for leads, activities, notes, tasks, meetings, follow-ups, invoices, receipts, proposals, proposal templates, services, tags, settings, dashboard data, auth, and AI-assisted features.

6. The frontend is split into route-level pages and reusable feature components. Pages in app/(crm)/* assemble feature-specific components from components/*, with many client-side interactive pieces for dialogs, tables, boards, forms, and quick actions. components/ui/* is the shared design-system layer.

7. The lead domain is the central business object. Lead detail screens pull together related subdomains: activities, notes, tasks, meetings, follow-ups, proposals, and financial documents. This suggests the architecture is lead-centric, with other modules attached to a lead as contextual records rather than isolated workflows.

8. Dashboard and pipeline are analytics-heavy read surfaces. lib/dashboard/* contains scoring and insight logic, while dashboard components show pipeline snapshots, hot leads, financial overview, team snapshot, and AI insights. These screens are derived views over the core CRM data rather than separate datasets.

9. Financial documents are treated as first-class generated artifacts. Invoices and receipts have dedicated create/view/update screens, plus API routes under app/api/financial/.../pdf that generate downloadable PDFs. Supporting code in lib/pdf/* and lib/invoice/utils.ts indicates document rendering is handled server-side from structured business data.

10. AI is an explicit subsystem, not just an incidental helper. lib/ai/* contains OpenAI wiring, prompts, context builders, and placeholder handling; feature components such as follow-up generators, proposal generators, and meeting transcript tools indicate AI is used for drafting, summarization, and document assistance.

11. Proposals and proposal templates form a separate document-authoring workflow. Template management, section editing, and the proposal workspace imply a structured content model for reusable sales/proposal content, with lib/proposal/* and lib/pdf/proposal-document.tsx supporting rendering and export.

12. The app has a strong validation boundary. lib/validations/* centralizes schema checks for each domain entity, which likely protects server actions and keeps form inputs, mutations, and database writes consistent across the feature set.

13. Overall data flow is: authenticated user enters the Next.js app, server-rendered pages fetch domain data through Prisma-backed helpers/actions, interactive client components submit mutations through server actions, and a few specialized API routes generate PDFs or other exportable outputs. The important architectural boundaries are auth/session handling, domain actions, database persistence, AI services, and PDF/document generation.