Provide sales, Deal Desk and finance owners; current product and pricing files; approval and credit policies; representative quotes and signed agreements; source extracts; and access to the chosen providers. Name the people who accept each process and resolve exceptions. Missing source evidence and connector work become explicit implementation scope.
Implementation
Plan your CPQ rollout around the products, policies, connections and people who will use it.
Application configuration, provider connections and operating acceptance are still required. Agree the scope and readiness checks with your implementation team; timing depends on catalog quality, commercial policy, source records and integrations.
Implementation phases
Phase 1 · Team and ERP.ai
Map how you sell
Identify configurable products, bundles, price books, discounts, cost and floor rules. Agree which system owns accounts, fulfillment, tax, accounting and collection, and define the quoting-only or complete-process launch boundary.
Phase 2 · Team and ERP.ai
Set commercial policy
Assign discount and terms authority, independent reviewers, delegation and escalation. Resolve contract terms, renewal price basis, service dates, proration, billing triggers and credit limits before configuring templates.
Phase 3 · Team and ERP.ai
Prepare the catalog
Load products, options, bundles and pricing in dependency order. Rehearse compatible and blocked combinations, quantity bands, automatic discounts, missing costs and mixed recurring and one-time offers.
Phase 4 · Team and ERP.ai
Connect the surrounding systems
Verify CRM mappings and signature documents, then order, fulfillment, accounting and payment exchange. Test repeated events, delayed callbacks and uncertain provider outcomes as well as the successful path.
Phase 5 · Team and ERP.ai
Rehearse complete deals
Work representative quotes with the people who will run them. Check that discounts survive order creation, billing reconciles to accepted value, approvals protect the sent revision and a partial shipment does not release an acceptance milestone.
Phase 6 · Team and ERP.ai
Reconcile the migration
Preserve source identifiers, signed documents, accepted versions and outstanding obligations. Stage cyclic references, reconcile invoices and cash at the cutoff, and suppress historical messages, orders and postings while loading the baseline.
Phase 7 · Team and ERP.ai
Activate the agreed scope
A quoting-only launch keeps automatic downstream generation and billing disabled. A later cutover reconciles transferred accepted work before enabling its effects. For a complete rollout, activate only reviewed balances, schedules and connections.
Phase 8 · Team and ERP.ai
Review early operation
Investigate blocked configurations, slow decisions, unresolved deliveries and billing exceptions. Tune rules through approved releases and confirm that existing accepted agreements keep their original terms.
Use Proto to prepare configuration and application changes on a branch for review and release. An additional price book may be configuration; a different tax provider, accounting handoff or commercial model needs its own implementation and verification. Changes to accepted business follow the agreed amendment and correction process.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.