Start your trial
Start your trial

For the handoff between sales and implementation

Turn a signed deal into an owned onboarding plan.

Carry agreed scope from a deal into the onboarding records your team needs. The implementation owner reviews the plan before the workflow sends kickoff messages.

See the workflow Build your own process

From event to outcome

Follow the work through its human decision.

A closed-won event starts the workflow—either from a connected CRM or from a deal record inside a broader Bondi system. Bondi maps the agreed scope into a repeatable plan and names the first owners. Before any kickoff message goes out, the run suspends for the implementation lead to confirm the plan. You choose whether commercial truth stays in the CRM or moves into the system you build in Bondi.

Illustrative workflow
Waiting for owner
  • Salesforce or another CRM Deal and commercial scope API / HTTP
  • Bondi Onboarding plan, owners and review Bondi runtime
  • Slack + Microsoft 365 Internal kickoff and customer communication Built-in connector
  1. 01 Receive the closed-won event integrationTrigger · CRM contract
  2. 02 Create the onboarding account bondiDataCreate · account + agreed scope
  3. 03 Build the repeatable delivery plan bondiDataCreate · milestones + owners
  4. 04 Ask the implementation owner to confirm it interactiveForm · suspended until submitted or expired
  5. 05 Open kickoff and notify the team Slack / Microsoft 365 · built-in actions

Configured human task

Implementation owner

The implementation owner checks scope, owner and target date before kickoff

Context shown

Agreed scope, proposed milestones, customer inputs and target date.
  • Confirm the plan
  • Return for correction
The same run continues to the configured kickoff actions after confirmation.
sample_ops / automations / deal-to-onboarding Illustrative execution
Run inspector

Sample account · implementation plan

The plan exists, but customer-facing work cannot begin until its owner confirms the handoff.

Trigger
crm.deal.closed_won
Scope
4 milestones · 2 customer inputs
Current step
Review implementation plan
On expiry
Keep needs-review + create owned task
Illustrative data. The connection methods, node boundaries and suspended human step reflect current product capabilities; this is not a customer implementation.
If nobody responds

The account stays in needs-review and an owned task is raised; nothing is sent to the customer.

Where the records live

Run the process beside your tools or within Bondi.

Keep one authoritative home for each business record. Choose the boundary that fits the process you are building.

Beside existing systems

Keep commercial truth in the CRM

Pass only the deal identifier and fields delivery needs. Bondi runs the onboarding plan, owners and approvals without becoming a second CRM or a two-way sync engine.

Inside your Bondi system

Build sales-to-delivery in one Bondi system

When Bondi also owns the deal record, the same workflow begins internally and carries commercial context straight into implementation. Connected communication tools can still stay where the team uses them.

Connection requirements

Set up the connections this example uses.

This is a worked example of a configurable workflow. Connections and decision rules must be set up for your system.

Explore integrations

  • Salesforce or another CRM

    Reached through its API, an HTTP step or a custom integration; not a built-in CRM connector.

  • Slack + Microsoft 365

    Typed actions send only after the review step has resolved.

The wider operation

See the system around this workflow.

Explore the records, screens and other decisions that can stay connected to this process.

Start with your process

Describe one handoff you want to improve.

Name the starting event, the records involved and the decision that needs a person. Review the plan before building the workflow.

Start your 30-day trial Explore workflows & AI

No credit card required.