Business problem
Why this system exists
Client-service work becomes hard to operate when sales, onboarding, delivery, approvals, and support lose a shared source of truth.
CRM and client operations
Agency Operations OS
Functional Prototype / In Development — Local Only; Not DeployedA local prototype for lead intake, owner qualification, client and project records, approvals, change requests, support, and organization-scoped client access.
Verified media
Rendered application evidence, labeled at its actual stage.
Role evidence
What the repositories support
Repository evidence supports the application architecture, persisted CRM and portal workflows, authorization boundaries, database tests, and end-to-end browser validation.
Repository group
- Pwarner96/agency-operations-os — canonical repository; intended private
System architecture
Verified boundaries from interface to accountable data.
This diagram summarizes repository-supported components and controls. It does not imply that disabled providers or undeployed services are active.
- Role-specific surfacesLead intake · operator CRM · organization-scoped client portal
- Application workflowsQualification · projects · approvals · change requests · support
- Authorization boundaryAuth claims · server-side role checks · organization membership
- Data boundarySupabase/PostgreSQL · row-level security · database validation
Core workflow
A controlled path from source to accountable action.
- 01Capture and qualify a lead
- 02Convert approved work into client and project records
- 03Coordinate milestones, tasks, files, and decisions
- 04Expose only organization-scoped records in the client portal
AI boundary
Assistance without invented authority
No AI runtime is verified in this checkpoint. This system is represented as an operations and integration prototype, not as an AI product.
Human approval points
- Explicit lead-conversion confirmation
- Client approval and change-request records
- Owner-controlled access and workflow transitions
Security controls
- Supabase Auth claims and server-side role checks
- Organization membership boundaries
- Database row-level security as the final boundary
Reliability controls
- 161 application tests and 254 database tests at the audited checkpoint
- Three core browser workflows passed locally
- Clean dependency audit, lint, typecheck, and build
Current limitations
- The application is local-only and not deployed.
- No public registration or production provider configuration is represented.
- The marketing surface is implementation evidence, not proof of customers or consulting outcomes.
Evidence before adjectives