The handoff breaks when the information is scattered.
By the time a deal closes, your team has already collected most of what post-sales needs.
Customer goals came up during calls. Requirements were captured throughout the sales process. Commercial terms are in the contract. Account and opportunity details are sitting in Salesforce.
The problem is that all of that information lives in different places.
That makes every handoff dependent on how well someone can piece it all together. One might be thorough, while the next is missing a key commitment or implementation detail. Post-sales doesn’t always know what’s missing until they need it.
The result is an inconsistent handoff that leaves post-sales filling in the gaps.
The play: Describe the handoff. Ballet builds the workflow.
You don’t have to build the integrations or figure out how to connect the systems yourself. Tell Ballet what you want the handoff to do in plain English.
What you hand Ballet
When an opportunity moves to Closed Won in Salesforce, create a sales-to-service handoff brief using the opportunity data, contract, and sales call recordings. Include the customer’s goals, key requirements, commercial terms, commitments made during the sales process, and anything the implementation team should know. Flag anything important that’s missing.
Ballet takes it from there. It builds the integrations and workflow needed to pull the right information from the systems involved, bring it together into the handoff you’ve defined, and flag anything that needs human review.
Once the workflow is built, it runs as deterministic, reviewable code, so the same process can run consistently every time a deal closes.
You describe what needs to happen. Ballet builds the workflow to make it happen.
Here’s how the workflow runs
1. Closed Won starts the workflow
When an opportunity moves to Closed Won in Salesforce, Ballet starts the sales-to-service handoff workflow.
- Trigger: Salesforce Opportunity Stage Closed Won
2. Ballet connects the systems and pulls the information the handoff needs
The information post-sales needs rarely lives in Salesforce alone. It may be spread across your CRM, contract platform, call recordings, and sales documentation.
Ballet builds the integrations needed to connect those systems as part of the workflow, generating custom API integrations on demand. Rather than stitching together separate connectors or handing the integration work to engineering, you describe which systems Ballet should work across and what information the workflow needs from each one.
3. Ballet builds the handoff around what post-sales needs
Ballet brings the information together into the handoff structure you’ve defined, organizing customer details, goals, requirements, commercial terms, implementation expectations, and commitments made during the sales process.
The handoff is built from information your team has already captured throughout the sales process, rather than recreated manually after the deal closes.
4. Ballet flags what’s missing
You define which information is required for the handoff. If Ballet can’t find it, the workflow can flag the gap for human review rather than silently passing it downstream.
Needs review: Implementation timeline not found.
Needs review: Primary implementation contact is missing.
Your team steps in where additional information or judgment is needed, while Ballet handles the rest of the workflow.
5. Ballet moves the handoff into the next step
Once the handoff is ready, Ballet can move it into the system where post-sales works or trigger whatever should happen next.
Depending on your process, that could mean updating a record in Salesforce, creating an onboarding record, notifying the implementation team in Slack, or passing the handoff into a Customer Success platform.
From a one-line note to the full picture
Faster handoffs. Better information. Less manual work.
Post-sales starts with a clearer picture of the customer instead of tracking down details across systems or going back to Sales for answers.
That means fewer gaps at the start of implementation, less manual work between teams, and a consistent handoff every time a deal closes.
Because Ballet runs the workflow as deterministic, reviewable code, your team also has visibility into how the process executes.
Take this play and make it yours
Every sales-to-service handoff looks a little different. Before you bring yours to Ballet, answer a few questions:
- What event should start the handoff?
- Where does the information post-sales needs live today?
- What information should every handoff include?
- What should happen if something is missing?
- Where should the finished handoff go?
You don’t need to map out the integrations or design the technical workflow. Start with the process you want to run and the outcome you want post-sales to receive.
