1. Executive Summary
AIG is designing a purpose-built, single-tenant CRM for its team with multi-client capability. The system must support multiple logins with role-based access, deploy on a Hostinger VPS, include an AI assistance layer, unify the Proposal → SOW → Invoice workflow, provide a customer portal, manage multi-client social media (Content 360) and email campaigns (Rackspace), generate client dashboards/reports, and integrate with Slack for proactive team messaging.
Core recommendation: Build the foundational data model, authentication, and the commercial workflow first. Layer AI assistance, client portal, and Slack-driven proactive messaging next. Defer complex multi-platform social and advanced reporting until the core is stable and adopted.
This approach reduces risk on a VPS-hosted custom system, delivers internal value within the first month, and creates a single source of truth that eliminates scattered tools and manual handoffs.
2. Recommended Priorities
Priority 1: Foundation
- Role-based authentication and multi-login (Admin, Team Member, Client)
- Client and contact master records
- Core data model: Clients → Proposals → SOWs → Projects/Tasks → Invoices
- Hostinger VPS environment (Docker, PostgreSQL, Redis, automated backups)
Why first: Single source of truth and secure multi-user access are required for every other feature.
Priority 2: Consistent Commercial Workflow
- Proposal creation (templates + AI assist)
- Convert approved Proposal → SOW (with version control)
- Trigger Invoice generation from SOW milestones or retainers
Why second: Highest-value internal process; eliminates revenue leakage and inconsistent handoffs.
Priority 3: Team Collaboration & Proactive Messaging
- Slack integration (notifications, digests)
- Task assignment, ownership, automated daily/weekly/monthly reminders
- Simple internal “My Tasks” dashboard
Priority 4: Customer Portal MVP — login, uploads, status visibility, messaging.
Priority 5: AI Layer (incremental) — drafting assistance, task suggestions, report narratives.
Priority 6: Marketing Campaign Modules — email (Rackspace), social (Content 360), client reporting dashboards.
3. Suggested Missing Elements
- 2FA, audit logs, role-based permissions, encryption, automated backups + restore testing
- Document versioning and template library for proposals/SOWs
- Recurring tasks, dependencies, client-visible milestones
- Overdue alerts, invoice aging, renewal reminders (60/30/14 days)
- Internal analytics: utilization, pipeline velocity, revenue by service line, client health
- Client onboarding checklists and service-line playbooks
- Calendar, payment processor, and accounting export integrations
- Responsive design and Slack-first mobile experience
- Campaign calendar, approval workflow, and performance snapshots for social
- Background job queue, AI rate limiting, and VPS monitoring
4. Three-Month Build Plan & Expectations
Month 1: Foundation & Core Workflow (Weeks 1–4)
Build: VPS + Docker + DB, authentication/roles, client records, proposal creation, basic Proposal→SOW, Slack alerts, simple My Tasks view.
Expectations: Team can create and track client records and proposals; first SOWs generated; Slack alerts live; usable daily on limited real clients.
Month 2: Workflow Completion, Portal & AI (Weeks 5–8)
Build: Full Proposal→SOW→Invoice, customer portal (uploads + status), AI drafting assistance, task ownership + daily/monthly Slack digests, invoice tracking.
Expectations: End-to-end commercial workflow in use; clients access portal; proactive messaging active; AI reducing drafting time.
Month 3: Marketing Modules, Reporting & Polish (Weeks 9–12)
Build: Email campaigns + Rackspace, social tracking + Content 360, client report dashboards + PDF export, advanced proactive rules, security hardening, training materials.
Expectations: Single CRM is system of record; reliable daily/monthly proactive messages; clients see status and reports; production-ready for current services.
Overall 90-Day Outcome: One internal CRM supporting the full commercial lifecycle, proactive task visibility for every team member, a simple client portal, and the foundation for multi-client marketing operations—all under AIG control on Hostinger VPS.
5. Architecture Notes
- Recommended stack: Docker Compose (app + PostgreSQL + Redis + worker + reverse proxy)
- VPS: 8 GB RAM / 4 vCPU recommended
- Practices: Off-VPS daily backups, monitoring, staging/production separation, secret management
- AI: External API with caps/logging or self-hosted, depending on data policy