# Stakeholders: who signs, who uses, who blocks, handed over as a map

Handoff Checklist, item 2 of 12, read 10 Nov 2026

**The short answer.** Stakeholders are the people on the buyer side with a role in the decision and the rollout. Trumpet says a stakeholder map goes to Customer Success at handoff, and Flowla says its agent adds a name to the map and tags the role when it comes up on a call.

02

- **Who hands it over:** Account executive
- **When:** At handoff, before the kickoff call

## What passes

- Each person's name, title and role: signer, user, blocker, payer, technical owner.
- Who is the day-to-day contact.
- Who was involved late or came from a forward.
- Who has been quiet since the last meeting.
- The source for each entry: call, email or room view.

## When it does not pass

The onboarding team emails the wrong person, misses the technical owner until week three, and learns of a blocker from the blocker.

## Which portals carry it over

5 of 13 portals show this item carried over without re-entry: Flowla, Dock, Trumpet, GetAccept, Accord; 3 in part.

| Portal | Carried over | Evidence |
| --- | --- | --- |
| [Flowla](/platforms/flowla/) |  yes | The same summarizer prompt drafts the stakeholders from the call and meeting transcripts on the CRM deal. ([source](https://www.flowla.com/workflow-templates/sales-to-cs-handover-workflow)) |
| [Dock](/platforms/dock/) |  yes | The guide lists "Team dynamics: Key stakeholders" as captured in the workspace that is reused for onboarding. ([source](https://www.dock.us/library/sales-to-customer-success-handoff)) |
| [Trumpet](/platforms/trumpet/) |  yes | The onboarding page says to "Give CS a stakeholder map of who was involved in the sale". ([source](https://www.sendtrumpet.com/use-cases/customer-onboarding)) |
| [GetAccept](/platforms/getaccept/) |  yes | The guide says the room holds the stakeholder list, "including people added after the sale". ([source](https://www.getaccept.com/blog/sales-to-customer-success-handoff-process-with-digital-sales-rooms)) |
| [Aligned](/platforms/aligned/) |  none found | None found on 10 Nov 2026 in the home page, the onboarding software, client onboarding portal, Customer Success Hub and onboarding flow pages and the Zapier and Meetings tab help articles: a statement that the stakeholder list carries from the deal into onboarding. ([source](https://alignedup.com/customer-onboarding-software/?utm_source=whichclientportal.com&utm_medium=referral&utm_campaign=checklist)) |
| [Accord](/platforms/accord/) |  yes | The page says Accord "preserves all deal context, stakeholder relationships, and promised outcomes" and shows "who's involved" (vendor claim). ([source](https://inaccord.com/use-case/implementation)) |
| [HubSpot Sales Hub](/platforms/hubspot/) |  none found | None found on 10 Nov 2026 in the onboarding plans article, the deal plans article and the deal progression article: a statement that the stakeholder list carries from the deal into onboarding. ([source](https://knowledge.hubspot.com/customer-success/create-and-manage-customer-onboarding-plans)) |
| [GUIDEcx](/platforms/guidecx/) |  partial | The Salesforce page says customer records and assigned team members are mapped from Salesforce into GUIDEcx. ([source](https://www.guidecx.com/products/integrations/salesforce/)) |
| [Rocketlane](/platforms/rocketlane/) |  none found | None found on 10 Nov 2026 in the HubSpot and Salesforce help articles and the integrations page (the HubSpot mapping lists deal name, owner, company, create and close dates and a template): a statement that the stakeholder list carries from the deal into onboarding. ([source](https://help.rocketlane.com/support/solutions/articles/67000715492-rocketlane-s-integration-for-hubspot)) |
| [Arrows](/platforms/arrows/) |  partial | The same story says forms collect "key contacts" at onboarding and sync them to HubSpot; they are asked again, not carried from the sale. ([source](https://arrows.to/customers/automating-customer-onboarding-using-arrows-and-hubspot/)) |
| [OnRamp](/platforms/onramp/) |  partial | The FAQ says CS inherits accounts with "customer details"; contacts and roles are not named. ([source](https://onramp.ai/onboarding-visibility)) |
| [Moxo](/platforms/moxo/) |  none found | None found on 10 Nov 2026 in the customer onboarding page, the client portal page and the product page: a statement that the stakeholder list carries from the deal into onboarding. ([source](https://www.moxo.com/workflow/customer-onboarding)) |
| [Salesforce Sales Cloud](/platforms/salesforce/) |  none found | None found on 10 Nov 2026 in the Sales Cloud page, the Sales AI page and the revenue orchestration page: a statement that the stakeholder list carries from the deal into onboarding. ([source](https://www.salesforce.com/sales/)) |

## Sources

- Trumpet: Vendor onboarding page says closing and onboarding happen on the same link, with a stakeholder map handed to: https://www.sendtrumpet.com/use-cases/customer-onboarding (read 10 Nov 2026)
- Flowla: Vendor Stakeholder Mapping page says REX adds a name to the map and tags their role the moment it comes up on: https://www.flowla.com/stakeholder-mapping (read 10 Nov 2026)
- Trumpet: Vendor org chart page says the AI maps every contact in a deal into a buying committee and a second AI scan: https://www.sendtrumpet.com/product/org-chart (read 10 Nov 2026)
- https://www.flowla.com/workflow-templates/sales-to-cs-handover-workflow (read 10 Nov 2026)
- https://www.dock.us/library/sales-to-customer-success-handoff (read 10 Nov 2026)
- https://www.sendtrumpet.com/use-cases/customer-onboarding (read 10 Nov 2026)
- https://www.getaccept.com/blog/sales-to-customer-success-handoff-process-with-digital-sales-rooms (read 10 Nov 2026)
- https://inaccord.com/use-case/implementation (read 10 Nov 2026)
- https://www.guidecx.com/products/integrations/salesforce/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://whichclientportal.com/checklist/stakeholders/
