Staff needed to manage customer-specific contracts and rates while continuing to use an existing pricing engine. The work had to connect commercial records, pricing requests and the documents used by the team.
Illustrative photograph
What we built.
Contract workspaces
Salesforce components and workflows supported customer contracts and rate-management tasks.
Pricing requests
An API integration submitted work to the existing pricing engine and tracked asynchronous job results.
Documents and handoffs
Rate and contract information supported document generation and the next steps in the commercial workflow.
How the pieces connect.
Salesforce connected to the legacy pricing engine through REST APIs. Tracking request status mattered because a pricing response could arrive after the initial request. The work supported the commercial team’s contracts and rates, with existing pricing logic kept in the connected system.
Start with the handoff that causes the most work.
Show us where information is re-entered, what your team waits for and which systems must stay. We can then discuss an approach and the information needed for an estimate.
In a 30-minute discovery call, we will walk through the problem, the systems involved and what a useful result looks like. Then we agree the next step toward a scoped approach and estimate.
With your permission, we use Google Analytics to understand visits and completed enquiries. Forms and bookings work either way. Read our privacy notice.