Bring a sales owner, sales operations owner and finance contact, plus the source extracts and the policies that shape configuration. These include account and territory mappings, product prices, contract templates, forecast periods, commission plans, communication preferences and the providers that must connect. Reserve time for users to rehearse their actual work and accept reconciliation differences.
Implementation
Plan the move around your sales process, customer data and commercial policies.
Start with the sales process and the information teams need to trust, then agree the acceptance evidence for the first release.
Implementation phases
- Agree the operating modelTeam and ERP.ai
- Configure authority and commercial rulesSales Manager
- Prepare the migrationSales Manager
- Reconcile existing businessTeam and ERP.ai
- Rehearse real work and exceptionsTeam and ERP.ai
- Release and support the first cycleTeam and ERP.ai
Phase 1 · Team and ERP.ai
Agree the operating model
Identify the sales teams, entities, territories and customer segments in scope. Define lead qualification, pipeline stages, required commercial evidence and ownership of accounts, service cases and renewals. Confirm which system owns invoices, cash reconciliation and recognized revenue before choosing integration boundaries.
Phase 2 · Sales Manager
Configure authority and commercial rules
Set up roles, approval limits, product configurations and effective prices. Establish quote and contract review, commission preparation and independent payout authority. Define communication preferences, campaign release, routing precedence, forecast currencies and quota periods. Review permissions with actual users, including commission privacy and manager access.
| Role | Screens |
|---|---|
| Sales Rep | 8 |
| Sales Manager | 10 |
| Sales Ops | 5 |
| Marketing Manager | 2 |
| CPQ Admin | 1 |
| AR Clerk | 1 |
| Viewer | 4 |
Role permissionsRoles and permissions →
Phase 3 · Sales Manager
Prepare the migration
Establish source identities, cutoff times and repeatable import batches. Review duplicate account, contact and lead mappings without losing suppression or historical ownership. Load dependencies first, then resolve manager, territory and commercial references in a controlled second pass. Keep accepted versions and in-flight provider requests attached to their source.
Phase 4 · Team and ERP.ai
Reconcile existing business
Preserve open opportunity history, accepted contracts, remaining order and billing scope, original invoices and effective cash or credit applications. Carry approved commission statements and their payout evidence, plus the applicable quota and plan history. Reconcile opening amounts once; importing an already-net balance and then subtracting its historical applications would reduce it twice.
Phase 5 · Team and ERP.ai
Rehearse real work and exceptions
Run a lead through qualification, offer review, customer acceptance and the agreed order/billing path. Test duplicate capture, contact suppression during a queued send, a discount exception, partial signatures, changed terms, partial fulfilment and an uncertain payout. Compare forecast rollups and commission calculations with the frozen source evidence.
Phase 6 · Team and ERP.ai
Release and support the first cycle
Launch after users accept the data, access and required connections. Historical Won, Active, Sent and Paid records must remain nonposting migration evidence rather than trigger new orders, messages or payouts. Enable new operational effects from the agreed cutoff, support the first forecast and commission close, and retire earlier tools only when their outstanding work is accounted for.
| Role | Screens |
|---|---|
| Sales Rep | 8 |
| Sales Manager | 10 |
| Sales Ops | 5 |
| Marketing Manager | 2 |
| CPQ Admin | 1 |
| AR Clerk | 1 |
| Viewer | 4 |
Role permissionsRoles and permissions →
Use Proto to propose changes on a branch and review them before release. Changes to stages, pricing, routing or commission plans need an effective date and a decision about existing work. Preserve the original accepted terms and approved earnings; a new configuration should not rewrite prior customer or employee commitments.
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.