How data is organized
The revenue lifecycle
From first touch to recognized revenue — how a lead becomes a customer, and how the booking gate keeps every closed deal clean.
The full flow
Every record moves along the same connected path. Nothing is stitched together across apps — it's one chain, validated at each hop.
flowchart LR
L[Lead] -->|convert| C[Contact]
C --> A[Account]
A --> O[Opportunity]
O --> Q[Quote]
Q --> Or[Order]
Or --> Ct[Contract]
Ct -->|e-sign| Ex[Executed]
Ex -->|won| R[Revenue]
R --> Rn[Renewal]
classDef n fill:#ffffff,stroke:#2563eb,stroke-width:1.5px,color:#0B1024;
class L,C,A,O,Q,Or,Ct,Ex,R,Rn n;Stage by stage
Capture & convert. A lead comes in, gets scored, and converts into a contact at an account — optionally opening an opportunity.
Qualify & progress. The opportunity moves through your pipeline stages, each gated by requirements (an amount, contact roles, a close date).
Quote & order. You price the deal in a quote; on acceptance it becomes an order.
Contract & sign. A contract is drawn up and e-signed by the required signers.
Book & recognize. Once the booking gate clears, the deal closes won and a revenue schedule is created.
Renew & grow. Revenue schedules track ARR/MRR and drive renewals and expansion.
Stage gates as you go
Each pipeline stage has entry requirements, so a deal can't skip ahead of its own facts. These run the same way no matter how the change is made — in the app, over the API, or by an AI agent.
| Reaching this stage | Requires |
|---|---|
| Qualification | An account and an amount greater than zero |
| Needs Analysis | At least one contact role on the deal |
| Proposal | A close date |
| Negotiation | A quote |
| Closed Won | Clears the booking gate (below) |
| Closed Lost | A churn reason |
The booking gate
The final gate is the important one. A deal cannot be booked (closed won) until its contract is executed and all required documents are complete or waived. This is what keeps "closed won" meaning genuinely closed.
flowchart TD
W[Attempt to close won] --> G{Booking gate}
G -->|contract executed| D1{Documents complete?}
G -->|not executed| B[Blocked]
D1 -->|yes| WON[Booked ✓]
D1 -->|no| B
B -.->|admin override + reason| WON
classDef n fill:#ffffff,stroke:#2563eb,stroke-width:1.5px,color:#0B1024;
class W,G,D1,B,WON n;-
Contract executed
The contract must be e-signed by the configured signers — customer-only, or internal-then-customer.
-
Documents complete
Every required document on the deal's checklist is complete or explicitly waived.
-
Admin override
An admin can override with a recorded reason — the bypass is audited, never silent.
-
Live status
The deal shows exactly what's blocking booking, so reps know what to finish.
Configurable per workspace
The gate is on by default, and admins tune what it enforces. Deals already won before you turn it on are grandfathered in.
How quote → order → contract → revenue tie together
The money is meant to be consistent all the way down the chain. Muntri keeps the numbers aligned as records are created:
flowchart LR
Q[Quote total] --> O[Opportunity amount] --> Or[Order total] --> Ct[Contract value] --> R[Revenue TCV]
classDef n fill:#ffffff,stroke:#2563eb,stroke-width:1.5px,color:#0B1024;
class Q,O,Or,Ct,R n;- Accepting the primary quote syncs the opportunity amount.
- Creating an order from a quote validates the totals.
- Executing the contract links it to the deal.
- Closing won auto-creates the revenue schedule with the deal's values.
After the win
A revenue schedule moves through its own lifecycle — from pending delivery, to delivered, to recognized revenue — and either renews (linking to the next schedule) or churns. This is what your ARR, renewals and customer-success views read from.
flowchart LR
P[Pending delivery] --> D[Delivered] --> Rev[Revenue]
Rev --> Rn[Renewed]
Rev --> Ch[Churned]
classDef n fill:#ffffff,stroke:#2563eb,stroke-width:1.5px,color:#0B1024;
class P,D,Rev,Rn,Ch n;Trust the chain
Run the data-integrity report any time to confirm every won deal has its contract, its revenue schedule, and matching amounts across the chain.