Teams keep up as tools change.

Your LLM reads each changelog. Juno briefs each role in your setup.

Trusted by teams at

Global-eCellebriteeToroJFrogGongCintJobber

The tool went live in March. By June, the work was back in a spreadsheet.

Since then, the vendor has shipped four releases, the launch demo was the only training anyone got, and nobody knows which roles use the tool the way you configured it.

Brief every role on each vendor release, based on your setup

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

Claude

Teach each role the work it does in the tool

  • Your setup, not the default

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

  • Training matched to each role

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

  • Unaffected roles are left alone

    If a release changes nothing for SDRs, SDRs receive nothing.

  • Generated automatically, not built by hand

    The role-by-tool matrix is generated from Company Context and stays linked to it.

Interactive lesson · SCORMWhat's new: the opportunity page · 3 min
Step 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 begin
SCORM · tracking

Keep training current while your vendors' roadmaps change

  • Update courses in place

    The course is revised where it already lives, with no need to delete and re-upload it.

  • Keep previous versions

    Each time you publish, the previous version is kept.

  • Brief only the affected roles

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

  • Track vendor certification expiry

    Each vendor certification carries its expiry date, and Juno sends an alert before it lapses.

The software license and the ability to use it have different owners

  • Two budgets, one gap

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

  • Turn policy into everyday behavior

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

  • People approve before publishing

    The system does the work, and people approve it. Drafts stay hidden until they are published.

  • Updates pushed to people

    People learn what changed in their tool before they need it.

  • AI prompts for each role

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

See who is up to date in each tool, and which tools change most often

  • Up to date on the latest release

    Who is up to date on each tool's latest vendor release, by tool and by role.

  • Workflows validated in practice

    Each person completes the workflow in the tool instead of taking a quiz about it.

  • Only valid certifications count

    Vendor certifications count for as long as they are valid.

  • App owner confirmation

    The person who owns the tool confirms that their users are up to date.

  • Release velocity

    See which of your tools change most often, based on the vendor updates you already follow.

You provide the list of who works in which tool. Juno does not discover, meter, or reclaim licenses.

Try it

  • Turn a release into a click-through lesson

    Your new screens, rebuilt from screenshots and tracked as SCORM.

    The prompt

    Your AI asks you

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

    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.

    The prompt

    Your AI asks you

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

    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 a launch's key facts, with a due date and a drafted nudge.

    The prompt

    Your AI asks you

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

    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, gaps visible before the deadline.

    The prompt

    Your AI asks you

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

    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.

All promptsNew to Juno? See it in a demo

Your product is the tool your customers have to stay up to date on

Your customers and partners are on the receiving end of your roadmap.

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

Frequently asked questions

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

Teach each role how to do its job in the tool, the way your company configured it, and keep that training up to date.

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

Treat the assistant like any other tool rollout, role by role. Most people do not know what to ask it. Juno sends each role the tasks and prompts its job needs, with your data rules attached, instead of waiting for people to go looking.

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 and 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?

Alongside it, as a different layer. A click-level guidance tool shows people where to click right now. Juno shows whether each person is up to date and capable in the tool, by role, as the vendor changes it. It works by building knowledge rather than guiding on screen, for employees and customers alike. The two run side by side.

Who owns tool adoption, IT or L&D?

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

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

Let the vendor's release start the update: Juno updates only the sections it touches and re-briefs only the roles it affects, keeping the previous version.

How do we measure software adoption?

Juno measures people, not seats: for each tool and role, who is up to date on the latest release and who has validated the workflow. It doesn't read license data.

Does this work for customers and partners too?

Yes. The same journey runs for all three audiences; see Push Product Updates to Customers and Certify Your Partners.