# Contract Pricing > Draft, approve, assemble, sign, and amend, with every transition logged. Source: https://revomo.ai/product/contract-management/ --- Contract Pricing alpha ## The Agreement Is the Economics. The Contract Binds It. Draft, approve, assemble, sign, and amend, with every transition logged. In alpha with design partners. Shown here so you can see where it is going, not because it is generally available. [See it on your data](https://revomo.ai/contact/?plan=Contract%20Pricing)Common questions → ### From Negotiated Terms to Binding Instrument An agreement is the negotiated economics. A contract is the executed legal instrument that wraps a specific version of those economics, and only an executed contract can touch the books. - 01 **Draft the Construct** Configure the economics before anything is committed or accrued. - 02 **Approve the Economics** Sign-off on the numbers routes by projected liability, not by job title alone. - 03 **Assemble the Instrument** Standard terms from a template library wrap the approved construct. - 04 **Render Exhibit A** The commercial construct is generated from the same engine configuration. - 05 **Redline the Clauses** Individual terms can be edited before anyone signs. - 06 **Sign Both Sides** A contract cannot execute until every party has signed. - 07 **Go Active on Date** On execution it becomes binding on its effective date. - 08 **Amend With a Trail** A live contract changes only through a versioned, re-signed amendment. - 09 **Quarantine the Unsigned** Anything before execution is kept out of accruals, payouts and the portal. ### Draft, Review, Approved, Out for Signature, Active Five states, one direction, and a log of every transition between them. **States and Gating** Only an executed contract reaches the books. - Submitting from the builder creates the contract in review; it does not accrue, settle or appear in the portal. - Approval routes by projected liability: at or above the ceiling to the executive, below it to the CCO. - Approval signs off the economics only, moving the contract to approved rather than active. Contract lifecycle · only the last state reaches the books demo data - 01 **Draft***Economics configured* - 02 **In review***Submitted, not accruing* - 03 **Approved***Economics signed off* Liability ≥ ceiling → CEO - 04 **Out for signature***Both parties* - 05 **Active***Binding, and on the books* Accrues Draft, in review and approved are quarantined from Accruals, Payouts and the portal. A liability appears when the instrument creating it is executed. **Assembly and Terms** The approved construct becomes something a counterparty can sign. - Assembly attaches standard terms from a template library plus the commercial terms: effective date, expiry, cadence, scope, minimums. - The construct is rendered as Exhibit A, generated from the same engine configuration that will compute the accrual. - Individual clauses can be redlined before signature. Assembly · terms plus Exhibit A demo data **Summit Q3 Commercial Program***CTR-4417 · v1 · effective Oct 1, 2026* - 1 **Term and territory***Jul 1 to Sep 30, 2026. Northeast distributor channel.* Template - 2 **Commercial terms***Quarterly settlement, net 45. Minimum qualifying volume $2.0M.* Template - 3 **Audit and reporting***Partner supplies POS sell-through monthly.* Redlined - A **Exhibit A · rebate construct***Three lines: base revenue rebate, growth kicker, assortment breadth.* Generated **Signature and Execution** Binding means both sides signed, not that someone marked it done. - Each party signs through eSignature. - The contract cannot be executed until all parties have signed. - On execution it goes active on its effective date and becomes the binding system of record. Execution · binding means everyone signed demo data **Summit Q3 Commercial Program***CTR-4417 · executed Sep 28, 2026* - — **Cannot execute until all parties sign***The contract stays out for signature while any signer is outstanding.* - — **Active on the effective date***Execution sets it binding from Oct 1, not from the signature date.* - — **Becomes the system of record***Accruals, payouts and the partner portal all read this version.* **A. Hoff***CCO, Revomo* **D. Marchetti***VP Supply, Summit* **Amendments and Versioning** A live contract changes in the open or not at all. - You pick which layers are changing, and each selection reveals an editor scoped to that layer: tier rates and bands, commercial terms, or clause text. - Editing the construct recomputes projected liability live, and an amendment with no changes cannot be drafted. - The amendment carries its own approval and signature cycle, and the version trail survives it. Version trail · what changed, and what it cost demo data Layer All layers Construct Commercial Ts & Cs Version | Change | Layer | Projected liability | State | v1 | Executed as negotiated | Construct | $184K | Superseded | v2 | Growth tier raised to 6.5% | Construct | $212K | Superseded | v3 | Minimum volume lowered | Commercial | $196K | Active | v3 | Audit clause redlined | Ts & Cs | $196K | Active | - **One Source, Two Documents** The economics a rebate manager configures and the exhibit a counterparty signs are generated from the same configuration. There is no second spreadsheet to reconcile, and no gap between what was agreed and what will accrue. - **Nothing Accrues Unsigned** Draft, in review and approved contracts are quarantined from Accruals, Payouts and the partner portal. A liability appears on the books when the instrument that creates it is executed, not before. ### Bind It, Track It, Amend It Keep the paper and the economics in step, from first draft through the third amendment. - **Remove the Reconciliation** The signed exhibit and the accrual engine read one config. - **Make Changes Auditable** Every amendment carries a diff, an approval and a signature. - **Keep Unsigned Off the Books** Only executed contracts create liability. ### Common questions What is the difference between an agreement and a contract? An agreement is the negotiated economics. A contract is the executed legal instrument that wraps a specific version of those economics. The agreement can be configured and re-configured; once the contract is executed it changes only through an amendment. What states does a contract move through? Draft, in review, approved, out for signature, then active. Every transition is logged, and only an active contract appears in Accruals, Payouts and the partner portal. Can a contract accrue before it is signed? No. Anything earlier than executed is quarantined from the books. Submitting from the builder creates a contract in review, which does not accrue, settle or show in the portal. How is approval routed? By projected liability. At or above the approval ceiling it routes to the executive; below it, to the CCO. Approval signs off the economics only and moves the contract to approved, not to active. What is in the contract besides the economics? Assembly attaches standard terms and conditions from a template library plus the commercial terms: effective date, expiry, cadence, scope and minimums. The commercial construct itself is rendered as Exhibit A from the engine configuration. Can the legal terms be edited? Yes. Individual clauses can be redlined before signature. How do amendments work? You choose which layers are changing, and each selection reveals an editor scoped to that layer, whether that is tier rates and bands, the commercial terms, or clause text. Editing the construct recomputes projected liability live, and the amendment diff is built from the fields that actually changed. Can an amendment be drafted with no changes? No. An amendment with no changed fields cannot be drafted, which keeps the version trail meaningful rather than noisy. ### The Future of Pricing, Today! From possibility to reality in days, not months or years! [See Revomo in action](https://revomo.ai/contact/?plan=Contract%20Pricing)[The whole platform](https://revomo.ai/platform/)