Written for: IT and system owners, commercial directors planning a change of quoting tool
Contents
Your sales team works in Salesforce or Dynamics. Breakbulk quotes sit in a separate spreadsheet, and accepted offers are typed into a booking system. Moving the quoting process raises a practical question: which system owns each part of the work during the transition?
The transition is where most quoting projects stall. Keeping the CRM in place and moving only the quote takes most of that risk away. Answer the ownership question before deciding what to synchronise.
Decide who owns what
Who owns what during a transition
Existing CRM
Owns accounts, contacts, opportunitiesCargoVerse
Owns the agreed quoting scope and its commercial rulesBooking system
Owns confirmed bookings, unless explicitly movedERP
Owns invoices and payments- CRMCargoVerseCustomer identifiers and contacts
- CargoVerseCRMQuote status and value on the opportunity
- CargoVerseBooking systemAccepted quote as a booking request
- Booking systemERPConfirmed booking data for invoicing
A typical starting point:
- The existing CRM stays the source for accounts, contacts and opportunities.
- The new quoting capability handles the agreed scope and its commercial rules.
- The booking system stays authoritative for confirmed bookings unless that is explicitly moved.
- The ERP stays authoritative for invoices and payments.
Contract and allocation ownership need explicit decisions too. They may stay in an existing system during the first phase. Separate the authoritative record from copies used to support a workflow.
Keep the first exchange focused
Start with the information the chosen process needs. That may be customer identifiers flowing into quoting, quote status returning to the opportunity, and accepted quotes becoming booking requests.
Define what happens when a record changes, a message fails or the same request arrives twice. Settle the handoff to booking before deciding when finance receives data. An accepted offer is not automatically a confirmed booking or an invoice instruction.
Treat integration as scoped work
For an organisation already on Dynamics, the integration design depends on the applications, environments, data model and security set-up in place. Sharing a technology platform does not by itself remove the need for data mapping.
For Salesforce, test the required interfaces and any proposed connector against the real workflow. A connector being available does not mean the full quoting, booking and error-handling process works out of the box.
Set an exit condition for the first phase
Choose a defined cargo segment and one authoritative quoting process. Measure quote turnaround, re-entry and corrections before you start, and agree how the new process will be judged. Compare margin only where the cost basis is the same.
Review the result before widening the scope. Keep ownership, reconciliation and support clear for as long as both systems run.
Why this capability matters
Many carriers delay better quoting because they think it means replacing the CRM first. It does not. A quoting capability that works next to the existing CRM delivers value sooner, with less risk, and leaves the larger system decisions for later, when the results are known.
Map who owns what today
Map which systems own customers, contracts, rates, quotes, allocations and bookings today. Bring that map to a conversation, and we will look together at what a first phase could cover.
Cartagena builds these capabilities together with each customer, as tailored solutions on the Microsoft platform.
Discuss a first phase