
A learning to impact funnel for a launch
From who learned it, to who talked about it, to the accounts now using it. Every week.
- For
- Revenue EnablementL&D
- Routine
- Every week
- Setup
- Juno + 2 tools
- You approve
- every draft
What you get
Northstar
From learning it to using it
Launch: Usage alerts, shipped Sep 2
Last 30 daysExample data
Since the last update
- UpTwo more accounts connected this week
- UpTwo more people opened the training
- No changeNo new learning on the certification path
- DownFewer calls raised it than the week before
- Hours on the launch training6.8 h11 of 12 people
- Calls where it came up28/4661% of calls
- Accounts where it was raised23
- Accounts connected14+2 this week
- Accounts using it97 days of real usage
The funnel
- Opened the trainingPeople11was 9 last week
- Raised it with a customer73% of the step above8
From people to the accounts they talk to
Accounts where it came upAccounts23- Accounts connected61% of the step above14was 12 last week
- Accounts using it64% of the step above9
Learning it vs. talking about it
| Person | Training | Calls where raised | Accounts |
|---|---|---|---|
| Marta | 74 min | 80% | 5 |
| Tomás | 62 min | 67% | 4 |
| Ade | 48 min | 60% | 3 |
| Deniz | 33 min | 50% | 2 |
| Sofia | 55 min | 38% | 3 |
| Kofi | 26 min | 33% | 2 |
| Omar | 18 min | 25% | 2 |
| Lena | 41 min | 20% | 2 |
| Hana | 28 min | 0% | 1 |
| Priya | 17 min | 0% | 1 |
| Jonas | 8 min | 0% | 1 |
| Ravi | 0 min | 0% | 1 |
Correlation, not causation. 12 people, 46 calls.
Every call, by depth46 calls
- No mention 18
- Mention 9
- Explained or demoed 10
- Next step agreed 6
- Already using 3
Gaps and next steps
- Nobody opened the certification pathSend a 5-minute refresher
- 3 people learned it but never raised itDraft a coaching note
- 5 accounts connected but are not using it yetShare the setup guide with their owners
Example data. Built by your assistant from Juno, your call recordings, your product usage and your CRM.
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
I want to see whether our last launch changed the work, not just who completed the training: a funnel from the people who learned it, to the conversations where they used it, to the accounts or teams now using what we launched. Use the Juno Journey connector for anything in Juno. If it isn't connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. My role and the team I support 2. The launch: what shipped, its date, and the Juno training that went with it 3. Who should have learned it (teams, roles) and who they talk to about it (customers, prospects or internal teams) 4. What counts at each stage: talking about it (a mention, a demo, a next step) and using it (how much real usage, over how many days) 5. The date range Ask these in one message, then wait for my answers. In that same first message, also ask me which call recording or meeting notes tool, which product usage or analytics tool and which CRM we use. Then check each one is connected in this chat; if not, I'll connect it or upload an export. Never guess what is in it. Pull learning activity from Juno first: who opened or completed the launch training, and how much time they spent. If you can't read completions here (analytics may be off for our account), I'll upload an export from Juno. Then read the calls in the range, person by person: judge from the transcript whether the launch came up, who raised it, and how far it went (a mention, explained or demoed, a next step agreed, already using it). Quote at most one short line per call with its timestamp link. Never infer what was said on a call you can't read. Match accounts through the CRM, and count usage from real usage only: leave out our own staff and demo accounts. Build the view: a funnel with one stage per step, counting people for the learning stages and accounts for the usage stages, with a conversion rate only where the unit stays the same; what changed since the last run; one dot per person (time spent learning against the share of their calls where they raised it); a timeline of every call, coloured by depth; and the gaps, each with one suggested next step. Show sample sizes, label correlation as correlation, and say which numbers you could not read. If this assistant supports artifacts connected to Juno, build it as an interactive artifact that re-reads Juno each time I open it, and say so; otherwise build it static and show the date the data was read. This is a read-only report: don't message, assign or notify anyone. Offer drafts (a coaching note for a person, a short refresher lesson) for me to review. Routine: after the first run, offer to repeat this every week. If this assistant can run scheduled tasks, set one up only after I approve it; if not, give me a one-line prompt I can re-run.
Your AI asks you
- Q1My role and the team I support
- Q2The launch: what shipped, its date, and the Juno training that went with it
- Q3Who should have learned it (teams, roles) and who they talk to about it (customers, prospects or internal teams)
- Q4What counts at each stage: talking about it (a mention, a demo, a next step) and using it (how much real usage, over how many days)
- Q5The date range
The routine
- 01
Connect
Juno and the tools below
- 02
Answer
the questions, one message
- 03
Review
the draft or the view it builds
- 04
You approve
before anything goes live
Routine: Every week. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
Live viewLive view: when your assistant supports artifacts connected to Juno, the result is an interactive view that reads Juno again each time you open it.
What it connects
- JunoRequired
- Gongvia your AI assistant
- SalesforceNative
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

Find who learned it but isn't using it
Completions matched with calls, a next step for each rep.
Live viewEvery week
Ship on Monday, train on Tuesday
A release note becomes a click-through lesson for the teams it changes.
Every release
This month's “What's new” digest and video
Everything you shipped in one short course, plus a video on the biggest change.
Every month






















