# Original CRM Improvement Opportunities

1. Make tenant context unmistakable with color-neutral labels, breadcrumbs and a persistent workspace switcher.
2. Replace module sprawl with nine outcome-based client destinations and seven agency destinations.
3. Use one unified contact workspace: identity, consent, current work, communications and chronological history.
4. Make Kanban changes reversible and accessible; add keyboard/explicit move controls and stage-change reasons.
5. Offer a universal quick-create drawer for contact, deal, task and appointment.
6. Separate role templates, data scope and dangerous actions; show effective-access previews.
7. Turn workflow building into Trigger → Conditions → Actions → Test → Publish, with simulation and rollback.
8. Replace “snapshots” with versioned Workspace Templates including manifests, dependencies and diffs.
9. Separate platform billing, client billing, plans/entitlements and add-on catalog.
10. Provide a notification preview before sends, bookings, invitations, publishes or charges.
11. Default dashboards by role; avoid empty ad/analytics widgets until integrations exist.
12. Use progressive disclosure for secondary fields and advanced marketing features.
13. Design mobile as task-oriented views rather than squeezing desktop Kanban and sidebar navigation.
14. Provide human-readable audit diffs and export governance.
15. Treat consent, channel health and delivery state as first-class data, not incidental contact fields.

## External services likely required

- Transactional email provider; SMS/voice carrier and number provisioning; push notifications.
- Calendar adapters for Google/Microsoft and video meeting providers.
- Payment processor, tax support and webhook infrastructure.
- Object storage/CDN, malware scanning and media transformations.
- Identity/MFA, secrets management, observability, queues and scheduled jobs.
- Address/time-zone normalization, email/phone validation and optional enrichment.

## Cloudflare-oriented architecture risks

- D1 consistency/scale boundaries for high-volume multi-tenant CRM workloads; test sharding and durable coordination early.
- Workflow timers, retries and idempotency need Durable Objects, Queues and scheduled triggers designed together.
- Analytics/reporting may need a separate event/warehouse path rather than transactional queries.
- Provider webhooks arrive out of order and duplicate; preserve raw events and idempotency keys.
- Tenant isolation must exist at authorization, query, caching, storage, export and logging layers.