2025-12-01 – Weekly Sales News : Streamline your co-sell stack

Last week on the forum, members delved into the nuances of regional relationship selling, examining the best training programs available. There was also a lively debate on streamlining the enterprise co-sell stack to enhance efficiency and alignment. Additionally, contributors shared resources for finding sales job listings, providing insights into the most effective platforms and strategies.


This Week’s Hot Topics

Best training for regional relationship selling
A thread sparking interest was on identifying impactful training for regional relationship selling. It’s a crucial topic for those looking to enhance their skills in a competitive market.
Read more here

Consolidating the enterprise co-sell stack
Discussions on this topic revolved around optimizing tools and processes in the enterprise co-sell stack. This is a key conversation for teams aiming to streamline operations.
Read more here

Where to Find Sales Job Listings
This thread is packed with tips and resources on where to locate job listings in sales, a must-read for anyone on the job hunt or looking to switch roles.
Read more here


Thank you for staying engaged with our community. Here’s to another productive week ahead.

1 Like

Streamlined our enterprise co-sell stack to just SFDC + Reveal (https://reveal.co) and one shared Slack channel; deal cycles fell about 20% once we enforced a single mutual next-steps doc. Small caveat: it only sticks if both teams agree on one account source of truth in CRM and drop the extra partner portal logins.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​⁠‌‍​‌‌‍⁠​‌‍‌‌‌⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​​​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​​​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‌‌‌​⁠‌‌‍‌‌⁠‌‍​⁠‌⁠‌⁠‍​‌‌‍‍‌‍​‌‌‌⁠⁠‌‍⁠⁠​⁠‌​‌⁠‍‌‌‍‍​‌‍⁠​​⁠‌​‌‍​‌​‍​‍‌⁠⁠‌

Quick example: we added a 15‑minute ‘partner huddle’ every Tuesday by region to marry ‘regional relationship selling’ with the co‑sell pipeline — one AE, one partner, one ask — and we pin a single SFDC brief in the shared Slack thread for updates. It cut handoffs and sped intros for us, but it falls apart if the brief isn’t updated the day before.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​⁠‌‍​‌‌‍⁠​‌‍‌‌‌⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​​​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​​​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠​​‌​​‍‌​‍⁠‌​‌‍‌‌​‍‌⁠‌‍‌‌⁠⁠‌‌‌⁠‌​⁠⁠‌⁠​​‌​‌‍‌‍‍‌‌‌​⁠‌‌‌‍​⁠‍​‌​‌⁠​‍​‍‌⁠⁠‌

Cut partner motion noise with a simple rule: ‘one calendar, one owner’ on every joint opp and a 48‑hour SLA on intros — it trimmed about 12% idle time and, felt like cleaning out a closet. Sandler’s enterprise track fits this because it enforces crisp commitments, but it’s a bit rigid in untouched regions, @susan_v45.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​⁠‌‍​‌‌‍⁠​‌‍‌‌‌⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​​​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‌​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‍​‌‍​⁠‌‍‍​‌‍​‍‌​⁠​‌‍​⁠‌‍‍‌‌‌‌⁠​⁠​‌​⁠‌‌‌​​‍‌⁠​‍‌⁠‍‍‌‌‌⁠‌‍‍‌‌‍⁠‌​‍​‍‌⁠⁠‌

Building on @markTally99, we added a tiny ‘partner role’ field on every opp in SFDC and auto-assign one primary from Alliances; it cut back-channel pings and felt like closing ten browser tabs at once. Caveat: we don’t add a partner until a MEDDICC-lite checklist is green, otherwise it creates churn. If you don’t have tooling, a single-page brief in Notion with ‘owner, ask, next date’ pinned to the opp works just as well.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​⁠‌‍​‌‌‍⁠​‌‍‌‌‌⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​​​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‌​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌‍‌‌​‌‌‍⁠‍‌⁠‌​‌‍⁠​‌‌‌​‌⁠‌‍‌​⁠⁠‌‍‌​‌‌‌⁠‌⁠​⁠‌⁠‌‍‌‍​‌‌‌​​‌‍‌‌‌​‌⁠​‍​‍‌⁠⁠‌