# AGM Zero-License-Cost Decision File

Date: 2026-04-18  
Decision Authority: Enterprise Architecture Board  
Constraint: Platform must be free (no license fee), highly customized, and proprietary to AGM Network.

## Decision Statement
AGM will pursue an open-source, self-hosted, proprietary-control architecture for web scraping, CRM, CMS, CPQ, sales, marketing, and service workflows. SaaS commercial dependencies are excluded from the primary platform path.

## Approved Target Stack (License-Free)

## 1) Scraping and Ingestion
- Scrapy: high-volume crawler backbone.
- Playwright: JS-heavy and interaction-based extraction.
- Crawlee: orchestration and adaptive crawl flows.
- BeautifulSoup/Cheerio: deterministic parsing and field extraction.

## 2) Data and Pipeline Core
- PostgreSQL: system-of-record relational data.
- Redis: queue/cache/session acceleration.
- Python workers (Celery or RQ): scheduled and event-driven jobs.

## 3) CRM and Sales Operations
- SuiteCRM or ERPNext CRM (self-hosted).
- AGM custom lead lifecycle service in API layer for scoring, assignment, and SLA propagation.
- Vertical segmentation model with owned territories: Healthcare, Manufacturing, Private Equity.
- Deal-tier segmentation model:
	- SMB/Growth: $2.5K-$25K
	- Mid-market transformation: $50K-$100K+
	- Enterprise/full-service: $100K+
- Mandatory CRM fields: industry/vertical, revenue range, tech stack, urgency trigger, decision-maker role, deal tier.
- Sequenced automation requirement: 14-day outreach cadence with telemetry capture.

## 4) CPQ
- Odoo Community with custom CPQ modules, or
- AGM custom CPQ microservice in existing API layer (recommended if strict proprietary logic is required).

## 5) CMS and Content Factory
- Strapi self-hosted for workflow-driven content operations.
- Keep static publishing footprint for performance and SEO control.

## 6) Service and Ticketing
- Zammad or osTicket self-hosted.
- Integrate with existing SLA and acknowledgement endpoints for command-center visibility.

## 7) Orchestration and Governance
- Strategic Command Center remains control plane.
- Existing APIs under api/ remain authoritative integration fabric.

## Why This Is the Best Option Under Current Constraints
- No software licensing lock-in.
- Full source-level customization and AGM ownership.
- Direct alignment with current command-center architecture.
- Lowest long-term strategic dependency risk.

## Non-Goals
- No paid SaaS as core runtime dependency.
- No proprietary vendor CPQ/CRM lock-in for phase baseline.

## 30/60/90 Best-Practice Migration Plan

## 0-30 Days (Foundation and Hardening)

### Objectives
- Establish canonical data contracts and operational guardrails.
- Stabilize command-center controls and critical workflow paths.
- Start secrets and configuration externalization.

### Tasks
- Finalize canonical schema for lead, SLA, project, workflow log entities.
- Create ingestion adapter from CRM scraper output to command-center lead schema.
- Baseline API contract tests for KPI, lead intelligence, SLA, project pipeline, milestones, webhook, SOAP.
- Migrate hardcoded credentials to environment variables with fallback-safe loading.
- Create role/permission matrix for sensitive actions.

### Best Practices
- Enforce idempotent writes for ingestion jobs.
- Use deterministic dedup key (domain + contact + source hash).
- Require owner and due date for all manual tasks.
- Capture evidence for every FAIL in phase checklist.
- Track daily sales controls: target-account import completion, scoring threshold validation, rep assignment consistency, outreach library readiness.
- Capture daily evidence: scoring outcomes, routing outcomes, sequence step completion, reply/open rates.

### Exit Criteria
- Control buttons, tab routing, and service audit actions are stable.
- API contracts pass baseline checks.
- Secret inventory and migration backlog are approved.

## 31-60 Days (Integration and Process Unification)

### Objectives
- Unify scraping, CRM, CPQ, content, and service workflows.
- Enable end-to-end lead-to-delivery lifecycle traceability.

### Tasks
- Connect scraper ingestion to CRM records and lead intelligence APIs.
- Implement CPQ baseline objects (catalog, quote, approval, status transitions).
- Integrate ticketing system with SLA event dispatch and acknowledgement.
- Add content workflow states (draft, review, approved, published) with approval evidence.
- Add reconciliation reports for summary vs row-level consistency.
- Implement trigger-driven prospecting ingestion (funding, hiring, M&A, redesign, expansion) into scoring and queue assignment.
- Publish vertical messaging library and sales playbooks tied to offer tiers.

### Best Practices
- Version all data contracts and endpoint schemas.
- Keep business logic in AGM-owned services, not in UI scripts.
- Treat SLA breaches as event stream with immutable audit rows.
- Implement retry with bounded exponential backoff for external fetches.

### Exit Criteria
- Lead -> quote -> service ticket path is executable and auditable.
- Content workflow approvals are enforced.
- Service escalation and acknowledgement loop is deterministic.

## 61-90 Days (Scale, Intelligence, and Governance)

### Objectives
- Operationalize intelligence-driven optimization.
- Formalize governance and reliability standards.

### Tasks
- Add model-based lead scoring recalibration routines.
- Add anomaly detection for SLA/ticket and pipeline stalls.
- Implement weekly governance digest and monthly executive scorecard.
- Add policy checks for release gates, migration safety, and rollback readiness.
- Add win/loss intelligence and competitor objection taxonomy review loop.
- Add forecast variance, rep productivity, and territory penetration governance.

### Best Practices
- Define SLOs for API latency and workflow completion.
- Use canary deploy pattern for high-impact changes.
- Keep one-click rollback playbook for command-center critical scripts.
- Enforce immutable audit logs for all state-changing actions.

### Exit Criteria
- Four-week stable KPI trend with reduced SLA breach rate.
- Governance package delivered on schedule.
- Platform operations repeatable without heroics.

## Phase 1 Kickoff Actions (Initiated)
- Master Plan updated with zero-license architecture decision.
- Strategic Command Center updated with direct link to this decision file.
- Phase 1 security baseline started via secrets migration backlog.

## Governance Note
All future tool evaluations must be screened against: zero license cost, self-hostability, source control ownership, security posture, and command-center interoperability.