How data is organized
The data model
One connected record from first touch to recognized revenue — leads, contacts, accounts, deals, quotes, orders, contracts and revenue, all linked.
The core entities
Everything in Muntri hangs off the same chain. A lead becomes a contact at an account; that account has opportunities; a deal produces a quote, an order and a contract; and a won deal creates a revenue schedule.
-
Lead
An unqualified inbound. Converts into a contact (and optionally an account and deal).
-
Contact
A person you work with, usually tied to an account, with a lifecycle stage.
-
Account
A company. The hub that opportunities, contacts and contracts hang off.
-
Opportunity
A deal in your pipeline — an amount, a stage, a close date, contact roles.
-
Quote
A priced proposal for an opportunity, with line items and approvals.
-
Order
The confirmed purchase created from an accepted quote.
-
Contract
The signed agreement — dates, total value, e-signature.
-
Revenue
The recurring revenue schedule created when a deal is won.
How they relate
erDiagram
ACCOUNT ||--o{ CONTACT : "has"
ACCOUNT ||--o{ OPPORTUNITY : "has"
ACCOUNT ||--o{ CONTRACT : "signs"
LEAD ||--o| CONTACT : "converts to"
OPPORTUNITY }o--o{ CONTACT : "contact roles"
OPPORTUNITY ||--o{ QUOTE : "priced by"
OPPORTUNITY ||--o| ORDER : "confirmed as"
OPPORTUNITY ||--o| CONTRACT : "executed as"
OPPORTUNITY ||--o| REVENUE : "recognized as"
QUOTE ||--o| ORDER : "becomes"
ORDER ||--o| CONTRACT : "produces"
CONTRACT ||--o| REVENUE : "backs"What each entity carries
A quick tour of the fields you'll use most. Custom fields and objects (below) let you add your own.
| Entity | Key fields |
|---|---|
| Lead | name, email, company, source, status, score, owner |
| Contact | name, email, title, account, lifecycle stage, role, owner |
| Account | name, domain, industry, employees, annual revenue, lifecycle stage, owner |
| Opportunity | name, account, stage, amount, close date, forecast category, contract dates |
| Quote | opportunity, status, line items, subtotal, total, discount, valid-until |
| Order | opportunity, quote, status, payment status, total |
| Contract | opportunity, account, status, total value, start/end dates, e-signature |
| Revenue | opportunity, contract, stage, ARR / MRR / TCV, active flag, renewal link |
Contact roles
An opportunity's buying group is modelled explicitly: each contact on a deal gets a role — decision maker, champion, economic buyer, evaluator, influencer, end user, blocker or executive sponsor — with one marked primary. This is what powers buying-group coverage and gap analysis.
Extend it: custom fields & objects
The eight core entities are only the starting point. You shape Muntri around your business without leaving the platform.
-
Custom fields
Add your own fields to any core entity — text, number, date, select and more — and they behave like built-in fields everywhere.
-
Custom objects
Model entities Muntri doesn't ship — assets, projects, partners — with their own fields and records, related to the core chain.
Kept honest automatically
Every relationship in this model is validated as records are created, and you can run a full data-integrity report to confirm the whole chain is intact.
Next: see how these entities move through the revenue lifecycle, including the booking gate.