juno journey
Book a demo

Your vendors ship every month. Your teams keep up.

Seats in March, a spreadsheet in June, four vendor releases since. Your LLM reads each vendor's changelog, and Juno briefs every role on what changed in your setup, then shows you who is current in each tool.

Book a demo

4.7 / 5G2

Example data

Trusted by teams at

Global-eCellebriteeToroJFrogGongCintJobber

The tool went live in March. In June, the job is done in a spreadsheet.

The vendor has shipped four releases since, the launch demo was the only training, and nobody knows which roles use it the way you set it up.

How it works

1Trigger & Signal

  • SalesforceRelease notes
  • Microsoft CopilotRelease notes
  • DatadogRelease notes
  • ClaudeRelease notes

2Knowledge Design

Your LLM + Juno MCP

    • Mission-critical
    • Important, not urgent
    • Nice to know
    Human approval

    3Delivery & Adoption

    • AEsThe new opportunity page
    • Sales managersThe new forecast view
    • RevOpsThe new fields

    4Measure

    Who is current on each tool's latest release

    One vendor release, briefed to each role in your setup

    Salesforce's Winter release changes the opportunity page. Brief each role on what changes, by Friday.

    Claude

    Example data

    Give each role the job it actually does in the tool

    Example data

    • Your setup, not the default

      Each path teaches your fields, your stages and your approval chain.

    • One job per role

      An AE, a sales manager and RevOps each learn the part they use.

    • Untouched roles left alone

      A release that changes nothing for SDRs sends SDRs nothing.

    • Generated, not hand-built

      The matrix is generated from Company Context and stays attached to it.

    Interactive lesson · SCORMWhat's new: the opportunity page · 3 minStep 1 of 6

    What's new · Salesforce

    The new opportunity page

    Where stages, our close plan and discount approvals now live, the way we set them up.

    3 min3 steps1 checkPass 80%

    Press Start to beginSCORM · tracking

    Example data

    Hold the line while somebody else's roadmap moves

    Example data

    • Updated in place

      The course is revised where it stands. Nobody deletes and re-uploads it.

    • Versions kept

      Each publish keeps the version before it.

    • Only the roles it touches

      Each release re-briefs the roles it changes. Everyone else keeps working.

    • Vendor certifications, with expiry

      A vendor certification carries its expiry date, and Juno alerts before it lapses.

    The licence and the capability have different owners

    • Two budgets, one gap

      IT owns the tool and the licence. L&D owns whether people can use it.

    • Written for L&D

      This page is for the team that owns capability, with IT as co-owner.

    • Policy becomes behaviour

      Where the tool is an AI assistant, each role learns your usage policy.

    • People approve

      The system executes, people approve. Drafts stay invisible until published.

    • Pushed, not searched for

      People hear what moved in their tool before they need it.

    • The AI lane, per role

      An AE, a manager and an analyst each get the prompts their job needs.

    See who is current in each tool, and which tool moves fastest

    Example data

    • Current on the latest release

      People current on each tool's latest vendor release, per tool and per role.

    • Workflows validated by doing

      Each person walks the workflow in the tool, not a quiz about it.

    • Certifications valid

      Vendor certifications count while they are valid, not once they are earned.

    • The app owner confirms

      The person who owns the tool confirms their users are current.

    • Release velocity

      Which of your tools change most often, from the change stream you already read.

    Who works in which tool is the list you give us. Juno does not discover, meter or reclaim licences.

    Try it

    • Turn a release into a click-through lesson

      Your new screens rebuilt from your screenshots, with hotspots, a quick check and SCORM tracking.

      Your AI asks you

      Where the release note lives, screenshots of the new screens, who it's for, the pass mark

      New to Juno? See it in a demo
      The prompt

      I want to turn a product release into a click-through lesson in Juno Journey: people practice the new flow, answer a quick check, and the score reports back to Juno. 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. Where the release note lives (or I’ll paste it) 2. Screenshots of the new screens (I’ll attach them) 3. Who the lesson is for 4. The pass mark Ask these in one message, then wait for my answers. If the release note lives in another tool, check it’s connected in this chat; if not, I’ll paste it. Rebuild each screen in HTML to match my screenshots; never invent UI. Search Juno first for training on this feature, and update it if it exists. Then outline 4-6 steps that mirror the real clicks, with hotspots and short coaching, plus a knowledge check. After I approve, build it as an interactive HTML lesson with SCORM tracking and preview it. Saving it to Juno puts it live in our catalog, so save only when I say so; don’t assign it.

    • Find training that's out of date

      Claude checks your courses against your source of truth and lists what to fix first.

      Your AI asks you

      Where your source of truth lives, which topics matter most, what counts as a recent change

      New to Juno? See it in a demo
      The prompt

      I want to find training in Juno Journey that no longer matches how things actually work today. 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. Where our source of truth lives (product docs, release notes, policies) 2. Which topics or courses matter most 3. How recent a change must be to count Ask these in one message, then wait for my answers. Check that source is connected in this chat; if not, I’ll connect it or upload the documents. Only flag drift you can show evidence for. Read the relevant Juno courses, quizzes and journeys, compare each claim to the source, and give me a table: course, what it says, what the source says now, severity, suggested fix. This is a review, not an edit: change nothing yet. Offer to draft updated versions of the top items; after I approve, save them as drafts and don’t publish until I say so.

    • Add a 5-question drill with a deadline

      A quick check on the key facts after a launch, with a due date and a nudge drafted for you to send.

      Your AI asks you

      The topic or course, who takes it, the deadline, the pass mark and attempts

      New to Juno? See it in a demo
      The prompt

      I want a quick 5-question drill in Juno Journey that locks in the key facts after a launch, with a due date so it actually gets done. 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. The topic, or the course it should reinforce 2. Who should take it 3. The deadline 4. The pass mark and how many attempts Ask these in one message, then wait for my answers. Find that course or lesson in Juno first and base every question on it. If the material lives outside Juno, check it’s connected here; if not, I’ll paste it. No questions you can’t trace to the source. Show me the 5 questions with answers and one-line explanations. After I approve, build the quiz as a draft and prepare the assignment with the deadline as its due date. Tell me plainly what Juno reminds people about on its own; you can’t schedule repeats or reminders from this chat. Draft a nudge I can send later. Show me who would get the assignment and the nudge, but don’t assign or send anything until I explicitly say go.

    • A completion heatmap by team and topic

      Teams down the side, topics across the top, so the gaps show up before the deadline does.

      Your AI asks you

      Which groups and topics, which courses count, what "done" means, the date range

      New to Juno? See it in a demo
      The prompt

      I want a completion heatmap: groups down the side, topics across the top, and each cell showing how far along that group is. 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. Which groups (departments, roles, locations) 2. Which topics, and which courses count for each 3. What “done” means (completed, passed, above a score) 4. The date range Ask these in one message, then wait for my answers. Pull everything you can from Juno; if you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. If a grouping lives outside Juno (e.g. an HR system, if we use one), check it’s connected in this chat; if not, I’ll upload a CSV. Never guess anyone’s group. Confirm definitions with me, then build an interactive artifact: the heatmap with counts per cell, a click-through to the people in each cell, and the three weakest spots with suggested next steps. State definitions, show sample sizes, and grey out cells too small to judge. Don’t assign or notify anyone.

    Every prompt

    When the thing that changed is not the tool

    Release & Product Update

    When the product that changed is yours.

    CS, Sales & Support

    When what changed is what a rep says. The tool they say it in stays here.

    Your product is the tool your customers have to stay current on

    You have just read a page from the receiving end of a vendor's roadmap. Your customers and partners are on the receiving end of yours.

    • CustomersMeasured on adoption, ticket deflection and renewal.
    • PartnersMeasured on certified partner capacity and partner-sourced pipeline.

    Questions people ask.

    How do you get employees to actually use the software you pay for?

    Teach each role the job it does in the tool, the way your company set it up, and keep that current. Juno builds a path per application and per role from your fields, stages and approval chain, briefs only the roles a vendor release touches, and shows you who is current in each tool.

    We rolled out Copilot or ChatGPT and nothing changed. What now?

    Treat the assistant as a tool rollout with roles. Most people do not know what to ask it. Juno pushes each role the tasks and prompts its job needs, with your data rules attached, instead of waiting for people to go looking. Where your usage policy asks for a person, the system executes and people approve.

    What is internal tool enablement?

    Internal tool enablement is training people on the software your company bought, per application and per role, tied to the real workflow. In Juno it runs as an application-driven journey: who works in which tool, what each role does in it, and a path that is updated when the vendor changes the tool.

    Isn't the vendor's own training enough?

    Vendor academies are good, they are free, and Juno does not compete with them. They teach the product as the vendor built it. They cannot teach how your company does the job in it, with your fields, your stages and your approval chain, and they cannot decide which of your people need which part. That layer is yours.

    We already run a tool that shows people where to click. Where does Juno fit?

    Beside it, as a different layer. A click-level tool answers where to click right now. Juno answers whether each person is current and capable in the tool, per role, as the vendor changes it, through knowledge rather than on the screen, for employees and customers alike. The two run side by side.

    How do we keep training current when the vendor changes the tool?

    Let the vendor's release start the update. Your LLM reads the vendor's release notes and drives Juno, which finds the course that release affects, updates only the sections it touches and re-briefs only the roles it changes. Each publish keeps the version before it, and nothing goes out before you approve it.

    How do we measure software adoption?

    Juno measures people, not seats. Per tool and per role: who is current on the latest vendor release, who has validated the workflow by doing it, which certifications are still valid, and whether the app owner confirms it. Who works in which tool is the list you give us. Juno does not read licence or seat data.

    Who owns tool adoption, IT or L&D?

    Both, which is why it falls between them. IT owns the tool, the licence and the usage policy. L&D owns whether people can do the job in it. Juno is built for L&D to run the enablement, with the policy IT sets attached to each role's path.

    Does this work for customers and partners too?

    Yes. The same journey runs for all three audiences, and only the last mile changes. For customers, your product is the tool they stay current on, measured on adoption, ticket deflection and renewal. For partners, it is your portal and tooling, measured on certified partner capacity. See Push Product Updates to Customers and Certify Your Partners.