A ramp for every role.

Each person ramps up on their own job until a manager confirms it.

Same onboarding, different jobs.

Your support engineer sat through the CRM demo, your account executive learned the ticket queue, and neither was ready on day 30.

Two roles, two ramps, from day 3

Lina (support) and Omer (AE) finish orientation Tuesday. Start their ramps Wednesday, with a manager check on day 30.

Claude

Two ramps, one start date

The tools

Lina, support engineerThe ticket queue, the knowledge base, the product's admin console

Omer, account executiveThe CRM, the call recorder, the pricing sheet

The processes

Lina, support engineerTriage, escalation paths, the response time a priority ticket needs

Omer, account executiveDiscovery, qualification, the handoff to customer success

What is expected

Lina, support engineerResolve a standard case alone, escalate the rest with the right context

Omer, account executiveRun a first call alone and log a qualified opportunity

The first real task

Lina, support engineerA live case, worked end to end

Omer, account executiveA discovery call, run end to end

The check

Lina, support engineerDay 7 and day 21: the product and the escalation paths

Omer, account executiveDay 7 and day 21: the product and the qualification criteria

The manager's question

Lina, support engineerCan she take the queue on her own?

Omer, account executiveCan he run a first call on his own?

The first 30 days, on the calendar

  1. Wedday 3

    Role ramps start

    Support engineerAccount executive
  2. day 7

    First check

    • Lina
    • Omer
  3. day 12

    First real task

    A live caseA discovery call
  4. day 21

    Second check

    • Lina
    • Omer
  5. day 30

    Confirmed

    Manager: can she do the job?

  6. day 30

    Not yet: two steps added

    Omer
  7. day 34

    Confirmed

    Omer

Build it once, for the role

  • One ramp per role

    The support ramp and the sales ramp are built separately, each one once.

  • Assigned by criteria

    Role, department, location, and employee type decide who gets which ramp.

  • Assigned automatically

    A new hire who matches the criteria gets the ramp automatically.

  • Built from existing content

    Your LLM and Juno assemble it from the courses you already have.

The sign-off

It asks if they can do the job, not if they finished the ramp.

  • One question

    The manager answers one question, not a form: can this person do the job?

  • The evidence alongside it

    Both checks and the first real task appear next to the question.

  • “Not yet” adds steps

    A “not yet” adds the missing steps and schedules the next check.

  • Confirmed, with a date

    A yes records the day this person could do the job, and who said so.

Try it

  • Build a 30-60-90 day onboarding journey

    Three phases for one role, a checkpoint quiz per phase, your courses reused.

    The prompt

    Your AI asks you

    The role, what "ramped" looks like at 30/60/90, any existing material, who signs off

    I want a 30-60-90 day onboarding journey in Juno Journey for one role, so new hires ramp on a clear path instead of a pile of links. 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 role and the team 2. What “ramped” looks like at day 30, 60 and 90 3. What material we have outside Juno, if any, and where 4. Who signs off at each milestone Ask these in one message, then wait for my answers. For material outside Juno, check that source is connected in this chat; if not, I’ll connect it or upload files. Don’t invent our processes. Search Juno first and reuse existing courses and quizzes wherever they fit. Then propose the journey: three phases, the courses in each, a checkpoint quiz per phase, and the gaps you’d fill with short new courses. After I approve the outline, build the new pieces and the journey as drafts. Don’t publish, assign or notify anyone until I say so.

  • Spin up a new-hire channel for one role

    Week 1 to day 90 in topics, with a short lesson for every gap.

    The prompt

    Your AI asks you

    The role, day 30/60/90 goals, any onboarding docs outside Juno, when new hires start

    I want a new-hire channel in Juno Journey for one role, so a new person knows exactly what to learn and when. 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 role 2. What they should be able to do by day 30, 60 and 90 3. Whether we keep onboarding docs outside Juno, and where (or I’ll upload them) 4. When the next hires start Ask these in one message, then wait for my answers. If the docs live in another tool, check it’s connected in this chat; if not, I’ll connect it or upload the files. Don’t make up our processes. Search Juno first for onboarding courses and journeys we already have for this or similar roles. Then propose topics like Week 1, Month 1, Tools and People, filled with existing content, with short draft lessons only where there’s a gap. Show me the outline, then 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, assign or notify anyone until I approve.

  • A learning digest for every manager

    One view per manager: who finished, who's overdue, and one suggested nudge.

    The prompt

    Your AI asks you

    Which managers or teams, which numbers matter, the period, anything from outside Juno

    I want a learning digest for every manager: who on their team finished what, who’s overdue, and one thing to follow up on. 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 managers or departments to include 2. Which numbers matter (completions, overdue, scores, time spent) 3. The period it covers (e.g. the last 7 days) 4. Whether to add anything from outside Juno, and from where Ask these in one message, then wait for my answers. Check anything outside Juno is connected in this chat; if not, I’ll upload an export. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Never fill in numbers you can’t read. Build an interactive artifact: one view per manager with their team’s progress, overdue items and a suggested nudge. State definitions, data gaps and counts. Show me a sample for one manager first. Nothing runs on a schedule; tell me how to refresh it. Don’t send it to anyone or notify learners.

All promptsNew to Juno? See it in a demo

Sales Onboarding: Saved the company $950K over two years, or $577/person/day by shortening sales ramp time.

HuntersFrom the Hunters case study
“Juno Journey makes it so much easier to build and manage upskilling programs for our teams. I love how quickly I can develop learning paths, it saves a lot of time and effort.”
Gal V.Talent Acquisition Partner, CYMOTIVE TechnologiesG2

The ramp curve

  • Track each person

    Each hire's ramp: where they are, what they passed, when they were confirmed.

  • Compare by role

    The same confirmations, gathered across every hire in a role.

  • Improve the next ramp

    What the “not yet” answers had in common feeds back into the ramp.

  • EmployeesOne person, one role, to the day a manager confirms they can do the job.
  • CustomersA new user of your product, to the day their CSM confirms they work on their own.
  • PartnersA new partner rep, to certified competence and the pipeline they bring.

Frequently asked questions

How do you know when a new hire can work independently?

Their manager confirms it on the date you set, with the person's checks and first real task beside the question. A yes records the day and who said it.

What is the difference between onboarding and a role ramp?

Orientation introduces every new hire to the company: the culture, the policies, and the tools everyone uses, the same for everyone. It is covered in Company & Department-Wide Orientations. The role ramp follows, per job: the tools this role uses, the processes it follows, what is expected of it, and a manager who confirms the person can do it.

What happens if a new hire is not ready yet?

The manager answers “not yet,” and the ramp adjusts instead of a report turning red. The ramp does not end when the courses are complete; it ends when a manager confirms the person can do the job.

How do you build a ramp for each role without building one per person?

Build the ramp once for the role. Juno assigns it to every new hire who matches its criteria: role, department, location, and employee type.

How do you test whether a new hire can actually do the job?

You ask them to do it: a live case for a support engineer, a discovery call for an account executive. By the sign-off, the manager is not guessing; they are looking at what the person did.

How long should a role ramp take?

As long as the role requires. Each ramp ends on the day a manager confirms the person can do the job, and Juno records that date for each person. Export the dates to compare roles; a built-in view of ramp time by role is next.

Can I ask ChatGPT or Claude where a new hire is in their ramp?

Yes. With Juno's connector in ChatGPT, Claude, GitHub Copilot, or Cursor, you ask in plain words: where is Omer in his ramp, which checks has he passed, and what is left before the sign-off. The answer comes from Juno, within the permissions you already have, and nothing is sent or assigned without your OK.