Enablement at roadmap speed.

Releases, pricing, and policies reach the people they affect.

How Journeys work

Your CRO focuses on revenue, not training completion. Drive the behavioral change behind revenue.

Attendance and completion are what most systems can measure, so that is what gets reported. The real question is different: are your customer-facing teams up to date on this quarter's changes, and where are they falling behind?

“Don't tell me who completed training. Tell me what changed.”
  • Team readiness rate

    The share of your customer-facing people who are up to date on the last period's changes, by team and role.

  • Change-to-ready lead time

    The median time from detecting a change to the affected teams confirming they are ready.

  • Closed with a validation

    The share of changes closed with a knowledge check or an agent validation.

  • A manager confirmed it

    The share of teams whose team lead signed off on readiness for the changes that required it.

  • Business signals, as direction

    Tickets, quotes, and calls move alongside this. We show the trend and never claim the cause.

Teams running Juno today

Global-eWalkMeCellebriteeToroJFrogGongCintJobber

A release ships Thursday. Sales is current by Friday.

Release 4.2 is in Jira. Get Sales and CS up to speed on it by Friday, and give reps a way to practice the pitch.

Claude

Connect what you teach to what they do

Catch the change at its source

The announcement is the moment everyone plans for, and by then it is already late. By the time it is written, the change has been live in a ticket, a pull request, or a wiki page for a week. The journey starts in those systems instead, on the day the change happens.

  • Ship day

    A release appears in your tracker, and the work to get people ready starts from that ticket.

  • Everyday changes

    A price change, a new pitch, a process update in the wiki. No ship date, but the same impact.

  • Vendor updates

    Salesforce, Datadog, NVIDIA, and Claude ship on their own schedules, in the middle of your teams' week.

  • Connected sources

    Jira, GitHub, Confluence, or any other app with an MCP server, scoped to your permissions.

  • You approve first

    Every write action shows an approval card, and drafts stay invisible until you publish.

Reach the person before they think to ask

Search assumes the person knows there is something to look for. Most do not: they were not in the room when it changed, and they keep working from the version they learned. The change has to reach the people it affects, addressed to them by name.

  • Who it affects

    Target by role, department, or location, written once as a rule.

  • Sized to the change

    A heads-up, a short piece, a full module, or a live session, depending on how big it is.

  • Into Slack and Microsoft Teams

    Channels post into Slack and Microsoft Teams, one way, and the record stays in Juno.

  • Confirm it was understood

    A knowledge check or an agent validation confirms the change was understood.

  • Search is still available

    Knowledge Hub search covers published content by topic, keyword, or skill, for anyone who does come looking.

Edit once, and it updates everywhere it is assigned

Content goes out of date faster than anyone can maintain it, and your reps notice before you do. Once a rep opens two things that contradict each other, they stop opening either one.

  • Edit in place

    Change the content itself. No delete, no re-upload, no second version to reconcile.

  • Already assigned, already updated

    Everyone who has it gets the corrected version without being reassigned.

  • In every language you use

    The correction appears the same way in every language.

  • Built where it is delivered

    Authoring and delivery happen in the same place, so a fix does not need a second tool.

Try it on your own Juno

Each card opens Claude with the prompt ready. It asks before it builds, and nothing goes live without your OK.

  • Build a Product Hub channel from our release notes

    Your releases become short lessons and videos, filed by product area.

    The prompt

    Your AI asks you

    Where your release notes live, who it's for, your product areas, how far back

    I want a Product Hub channel in Juno Journey: one place where people learn what we ship, easy to refresh from our release notes whenever I ask. 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 release notes live (a tool, a docs site, or I paste them) 2. Who the channel is for (customers, our own staff, both) 3. Our product areas, to use as topics 4. How far back to go 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 paste/upload the notes. Never invent a release. Search Juno first for lessons on these features and any existing product channel, and reuse what fits. Then propose the channel: a topic per product area, existing content filed in, and a draft lesson for each gap. Build it as a new private channel and preview it. Adding content to a channel with members notifies them, so ask before touching an existing one. Don’t publish or notify anyone until I approve.

  • Create a sales enablement channel

    Pitch, product, and competitive material in one place reps open.

    The prompt

    Your AI asks you

    Whether you have playbooks or recorded calls, which roles, the skills and deals to win

    I want a sales enablement channel in Juno Journey where reps find pitch, product and competitive material in one place. 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. Whether we have playbooks or recorded calls, and which tools hold them 2. Which sales roles and segments this is for 3. The skills or deal types we most need to win Ask these in one message, then wait for my answers. Check each tool I name is connected in this chat; if not, I’ll connect it or upload exports. Never guess what’s in a playbook or a call. Look in Juno first for existing sales courses, quizzes and channels, and reuse them. Then propose topics (e.g. by deal stage), file existing content in, and suggest 3 new pieces for the biggest gaps (one from a strong call, if we record calls). Build it as a new private channel with drafts and preview it. Adding content to a channel with members notifies them, so ask before touching an existing one. Don’t publish, assign or notify reps until I approve.

  • 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.

  • Build a learning → impact funnel for a launch

    Learned, discussed, used: one dashboard from Juno and the tools you connect.

    The prompt

    Your AI asks you

    The launch and team, whether and where you record calls and track usage, the outcome

    I want a learning → impact funnel for one of our launches. 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 launch, its date range and the team that learned it 2. Whether and where we record or take notes on customer calls 3. Whether and where we track product usage, and which event means “used it” 4. The outcome to end on, where it lives, and how accounts map to people Ask these in one message, then wait for my answers. Check each non-Juno source is connected in this chat; if not, I’ll connect it or upload an export. Never invent data. Start in Juno: this launch’s training and who completed it. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Confirm definitions with me, then build an interactive artifact: the funnel (learned → talked about it → used it → outcome) in total and per person, the biggest drop-off, and suggested next steps. Show sample sizes and gaps. Don’t claim causation; don’t assign or message anyone.

All promptsNew to Juno? See it in a demo

In the words of the people using it

“The journeys with automations really helped me make sure my support agents were being kept up to date on our product on a daily basis.”
Salome M.Customer Experience Training & AI Enablement Manager, Moon ActiveG2
“Speaking from my experience, Juno is the perfect combination of functionality and flexibility. Juno is really intuitive to use, and allows me to quickly build courses, create high-quality journeys, and maintain them all easily in one place.”

From the Hunters case study

“Designed role-based, highly scalable, and ROI-positive onboarding certification programs in Juno for sales, partners and customers.”

Meagan D.Director of Sales Enablement, Hunters

The same reach, for the people who don't work for you.

Frequently asked questions

What is revenue enablement?

Revenue enablement is the work of making sure customer-facing teams can act on a change the day it matters. Releases are one source of change. Everyday changes such as pricing, positioning, and process are another, and the vendors your teams depend on are a third. Enablement means maintaining readiness across all three.

What is the difference between knowledge management and enablement?

Knowledge management makes the answer findable. Enablement brings the change to the people it affects and checks they understood it.

Is a sales enablement platform the same as an LMS?

No. A sales enablement platform is built around content, calls, and coaching for one revenue team. A People Readiness Platform carries structured training, records, and certifications for everyone, including customers and partners. Juno is a People Readiness Platform, and it runs enablement for revenue teams inside the same platform rather than in a separate tool.

Does this run for customers and partners too?

Yes, in a separate workspace for external audiences: product updates for customers, certifications that stay valid for partners. See Customer and Partner Training.

How do you measure whether a company is up to date?

By the share of customer-facing people up to date on the last period's changes, by team and role, and the time from a change to those teams confirming they are ready.

Does it read our systems, and is it secure?

Your LLM connects to Juno over MCP, using OAuth rather than API keys, and it is scoped to the permissions that person already has. It reaches your other systems through their own connections. Juno is ISO/IEC 27001 certified, and GDPR and CCPA details are in our Trust Center.

What does it cost?

What each plan includes is on the pricing page. For a quote, talk to sales.