Mapping the Customer Journey: A Full-Lifecycle CRM Schema

There's a question most RevOps leaders can't answer cleanly: "Show me the complete journey of a customer, from first anonymous visit to multi-product renewal, in a single system view."

Most CRM architectures can't do this because they were designed for Sales and then extended to handle everything else. The result is an Account record carrying data it was never designed to hold — and a reporting environment where every cross-functional question requires a custom export.

The fix isn't a single mega-object. It's a properly-structured multi-object schema where each entity maps to a distinct relationship type with its own lifecycle, owners, and operational logic.

The Core Objects

Lead — The anonymous or partially-identified entry point. Converted to Contact on L2A match.

Account — The legal entity anchor. Parent-child hierarchy lives here. See Unified Account Record.

Contact — The individual. Owns communication history. May be associated with multiple Accounts.

Opportunity — The commercial event. Line Items attached for multi-product deals.

Campaign — The marketing touchpoint record. Powers multi-touch attribution.

Engagement — Custom object for meaningful interactions: demos, meetings, key calls. Captures quality, not just channel.

Workspace — The product instance. Source of product telemetry via Reverse ETL. See PLG schema design.

Subscription — The active contract. ARR, plan tier, billing cadence, seat count, start/end date.

Entitlement — Which features the Account can access. Enables feature-gated expansion triggers.

Feedback — NPS, CSAT, and support ticket patterns at the Account level. Feeds the customer health score.

Partner — Tracks referral or agency partner relationships for accurate channel attribution.

Renewal — A distinct Opportunity type for the recurring commercial event, with expansion, contraction, and risk indicators.

Why This Structure Matters

Each object has its own lifecycle, owners, and automation logic. Collapsing them into fewer records destroys your ability to query and automate them independently. With this schema, you can answer: "Which acquisition channel produces the highest-retention, highest-expansion customers?" Without it, that's a hypothesis. With it, it's data.