01 / CASE STUDY

Product Happenings

Implementation of generative AI into a current sales opportunity funnel.

Role / Product Design + Motion

Miro, Figma, Adobe CS

01 / CONTEXT

Problem to be solved

Sellers do not have product inventory insights where they work.

Sales teams lack timely, easy -to-understand product inventory nformation within their normal Salesforce workflow. This forces sellers to leave CRM and interpret a separate Product Happenings source, making it harder to quickly identify inventory risks when researching customers, preparing for calls, or building opporunities.

02 / PROCESS

The Timeline

01

Listen

Discovery has focused on understanding how Sales currently uses Product Happenings, validating the Salesforce proof of concept, and identifying the information sellers need at the point of decsion. Sessions with Sales, Category, and CRM partners surfaced needs around inventory-status terminology, data freshness, search/ filtering, opportunity-level alerts, and visibility of products at inventory risk.

02

Map

The current As-Is Path is:

  • Find Product Happenings - a shared Excel document

  • Review Inventory

  • Interpret status/ timing

  • Connect it to the customer/ opportunity record

  • Return to Salesforce

  • Decide what to do

Sales currently relies on the Product Happenings Excel-based information source for inventory information. Inventory intelligence exists, but the seller needs to leave the selling workflow, interpret it, and manually connect it back to the opportunity record.

03

Frame

Key findings are to move Product Happenings from a separate information-retrieval task to contextual decision support within Salesforce. Surface inventory risk where sellers already work, translate source data into clear sales language, maintain visibility throughout the opportunity lifecycle, and progressively reveal the detail needed to make the next selling decisions.

04

Prototype

Designed motion studies to test pacing, hierarchy, and handoff moments.

05

Ship

CX CRM handed off the validated Product Happenings experience along with the design specifications to DTS (engineering) for grooming and implementation, followed representative Sales validation and Sprint refinement. Formal UAT was validated by checking the sellers journey, data accuracy, inventory visibility and opportunity integration before the product was released. The shipment occurred with all boxes checked and limited refactoring of the original design.

06

Learn

We have learned that the opportunity is not simply to move Product Happenings into Salesforce, but to redesign how inventory information supports the seller. Sellers need clear, current, and actionable inventory insights within their existing CRM workflow, using sales-friendly terminology and maintaining visibility as products move into an opportunity. The experience should reduce the need to locate and interpret a separate source and instead provide the right inventory context at the point a selling decision is being mad.

03 / IMPACT

Outcomes

What changed

Integrated Product Happenings into Salesforce has begun making the sales teams more proactive, informed and efficient by putting timely inventory intelligence directly into the selling workflow. Sellers can identify product risk earlier, make more confident recommendations, and spend less time searching for information, ultimately enabling better customer conversations and more informed opportunity decisions.


-8.1%

Time to Close

+2.1

Opportunity Close-Won Rate

71

System usability (previously 54)

Back to selected work