Three horizons. Theme 0–30d: First supplier database + stable foundation. 30–90d: Automation + first clients. 90–365d: The SupplyShore procurement platform.
Guiding principle: ship the supplier-intelligence pipeline first, because it is the data asset that everything else (automation, AI, the platform) depends on.
Goal: A working, scored, desk-verified supplier database (target 100–300 suppliers) + a stable, backed-up, automated base. No new hardware.
10) + set up automated backups to object storage + test restore.001 (06-decisions/adr).scripts/espocrm/, see 03-product/crm-structure.md, ADR-014) — apply on the node with apply.sh + seed_categories.sh, then verify with verify_structure.sh.03-product/supplier-intelligence).Deliverable: the first supplier database, searchable and scored, feeding EspoCRM — the flywheel begins.
Goal: Serve real buyers with a semi-automated sourcing loop; harden operations; land first clients.
03-product/ai-agents): input company → auto dossier.Goal: A differentiated, partially self-service procurement operating system backed by proprietary supplier intelligence.
Foundation/security (W1) ─► Supplier data model ─► Seed DB (30d)
│
▼
RFQ→shortlist loop + enrichment (45–75d)
│
▼
AI research agent + client pilots (60–90d)
│
▼
Platform build: portal + backend + AI layer (90–270d)
│
▼
Scale intelligence + monetization (270–365d)
Key risks & mitigations