01 · ACCOUNTSCommercial organizations
Industry, tier, and prospect or customer status establish the operating context.
Product architecture
Sales CRM holds the records that revenue teams actually hand to one another, with references that preserve how each record came to exist.
The model is broad enough for real lead-to-order work and narrow enough for a team to understand quickly.
01 · ACCOUNTSIndustry, tier, and prospect or customer status establish the operating context.
02 · CONTACTSWork email, role, status, and account keep the human relationship visible.
03 · LEADSSource, stage, estimated value, and next action date make qualification concrete.
04 · OPPORTUNITIESAccount, contact, originating lead, amount, close date, and stage travel together.
05 · PRODUCTSActive products and services carry a stable SKU and unit price.
06 · QUOTESNumber, dates, status, value, and opportunity identify the offer being considered.
07 · QUOTE LINESProduct, quantity, unit price, and discount retain the economics behind the total.
08 · SALES ORDERSThe accepted quote, account, value, date, and status become operational demand.
Sales Development, Account Executives, Sales Managers, and Revenue Operations receive different authority over the same linked model.
| Role | Primary responsibility | Control boundary |
|---|---|---|
| Sales Development | Accounts, contacts, and lead qualification | No commercial commitment |
| Account Executive | Opportunity and quote progression | Orders remain read-only |
| Sales Manager | Pipeline and pricing review | Review without rewriting line detail |
| Revenue Operations | Cross-process visibility | Read across the model |