Three views of the same machine. First the app sitemap — every section in the left rail and what lives under it. Then the entity-relationship diagram — how Company, Deal, Engagement, Invoice and the rest connect. Finally the tech structure — a custom Next.js front end talking to a Payload backend over Postgres, with a loose link out to the production platform.
The left rail of the custom Warm front end (CRM-1b), shown as a tree. Each top-level section is a destination; the chips under it are its sub-pages / views. Built means a Payload collection already backs it (shipped in CRM-1a); Planned means designed but not yet built. The rail on the left mirrors what a team member sees; the pane on the right expands each node.
Company sits at the centre — the account everything hangs off. Lines show relationships with cardinality (1 → many). Solid lines are inside the CRM; the dashed plum line is the loose link out to the platform. Built entities already exist as Payload collections; planned ones are designed for later phases.
type note / call / email / meeting / systemlifecycleStage, isCustomer, billing + GSTIN, currency, platform-client link.status open/won/lost · oneOffValue/mrr · serviceLine · ownerThree tiers, one database. The team mostly lives in the custom Next.js Warm front end; it reads and writes through Payload's access-controlled Local API (so role checks run server-side, not in the browser), and Payload persists everything to Postgres. Payload's own admin UI stays available for back-office edits. A single loose link reaches out to the production platform.
Enforced in Payload access functions — the Next UI and Admin both inherit the same rules. per-role field scope: confirm
A Company stores a platform-client reference. An ads / social Engagement hands a brief to app.csoul.cloud and pulls finished creative back — no creative data is duplicated in the CRM.
Two separate apps, two databases, joined only at this link. link mechanism (deep-link vs API): confirm
This is the Architecture page — the app's information architecture, data model and stack. For the business context behind it see the Overview; for the flow a customer travels see Journey; for every stage of the boards see Pipelines; for operating procedures see SOPs; for the assist layer see AI.
Only the Built entities (Company / Contact / Deal / Pipeline / Stage / Activity, with the deal-won automation) exist today. Everything marked PROPOSED — confirm is an inference about your process or wiring and needs your sign-off before we build it.