ServicesAI Immersion

Program

AI Immersion

Five weeks. A small program. Role-specific tracks. The deepest skill transfer we run, designed for teams who are past the workshop phase and ready for actual production-grade work.

See the five weeks

Who this is for

Three teams who book Immersion.

Immersion isn't a first step. It's where teams go when the workshop phase has run its course and they need the skills to actually stick.

  • 01

    If you're past the workshop phase

    Your team has done an Ignite. Maybe an AIramp. People know what AI can do; they're not yet doing it at production quality. Immersion is the structured skill build that closes the gap between awareness and habit.

  • 02

    If your team needs to ship, not just understand

    You're past the point where one prompt library is enough. You need every role on the team using AI in their actual workflows, with production-grade quality and the judgment to know when not to use it. That takes weeks, not hours.

  • 03

    If you want measurable adoption

    You need to walk into a board meeting with numbers, not vibes. Immersion ends with a pre/post skills assessment, role-level adoption analytics, and a dashboard you can share with leadership. The methodology produces evidence, by design.

The five weeks

The arc of an Immersion program.

One live session per week. Async work between. Each week ends with something built or assessed, not just discussed.

  1. W1

    Week 01 · Foundations

    Same room, different starting points.

    • Live session: tool landscape, prompt anatomy, the four moves every prompt makes. Everyone in the program, regardless of role.
    • Async work: baseline skills assessment, document drop (each person uploads three real artifacts from their job).
    • Ends with: a tailored prompt template assigned per role, ready to use Monday.
    BaselineWhole program
  2. W2

    Week 02 · Tracks split

    Role-specific tracks begin.

    • Live session: tracks split. Each track works on its own use case with a track lead.
    • Async work: each participant scopes one workflow from their week they'll automate by Week 4.
    • Ends with: a written automation spec per participant, reviewed by the track lead.
    Tracks splitScoping
  3. W3

    Week 03 · Build

    First workflow goes live.

    • Live session: guided build of workflow #1, paired in tracks. We sit alongside while you wire it up.
    • Async work: ship the workflow into your actual environment. Run it on real data for at least two days.
    • Ends with: one production workflow per participant, running in your stack.
    Build sessionProduction
  4. W4

    Week 04 · Refine

    Second workflow, with what you learned.

    • Live session: debrief on workflow #1 in tracks; design workflow #2 with the lessons baked in.
    • Async work: build workflow #2 yourself. Track leads available for unblocking only, no pairing.
    • Ends with: a second workflow shipped without the safety net. The independence test.
    Independent buildTrack debriefs
  5. W5

    Week 05 · Reconverge

    Tracks rejoin. Program closes out.

    • Live session: all tracks reconverge. Each track presents one workflow to the program. Cross-pollination is the point.
    • Async work: post-program skills assessment (same instrument as Week 1) and adoption dashboard review.
    • Ends with: per-team and per-person deltas, a shared prompt library, two production workflows per participant, certificate of completion.
    DemosAssessment

Role-specific tracks

Four named tracks. One concrete build each.

Starting Week 2, participants split into tracks based on their daily work. Below is what each track ships, by name. We add or customise tracks if a client's mix needs it.

  • Track 01

    Operations

    Build: an SLA-monitoring agent in Claude Projects that watches your support queue and surfaces breaches with full context, not just alerts.

    Focus: structured-data extraction, multi-step reasoning, internal escalation logic.

  • Track 02

    Sales

    Build: a discovery-call summariser in ChatGPT plus CRM webhook that turns a 45-minute call into a deal-ready brief with next steps named.

    Focus: conversational-AI prompting, CRM integration, sales-stage tagging.

  • Track 03

    Marketing & Comms

    Build: a content-velocity workflow combining Claude for long-form drafting and Gemini for SEO refinement, with a single editor's voice preserved across both.

    Focus: voice consistency, multi-tool handoffs, content QA loops.

  • Track 04

    Leadership & Strategy

    Build: a board-prep workflow that turns your last quarter's metrics into talking points, scenarios, and risk callouts. Designed for review, not authorship.

    Focus: analytical reasoning, scenario generation, executive summarisation.

Need a track for engineering, legal, HR, finance? We add named tracks on request when there are at least three participants. Custom tracks are scoped during Week 1.

What you leave with

Five tangible deliverables. Per person, per team.

These are the artifacts every program produces. They're concrete by design, so leadership can review evidence after the program ends.

  • 01

    Two production workflows per participant

    One built with track-lead support in Week 3, one built independently in Week 4. Both running in your actual stack by Week 5.

    Quality varies by participant; not every workflow ships to full production for every role.

  • 02

    Role-specific prompt library

    Scoped during Week 1, populated through the program. Each track ends with a library tuned to its own document types and workflows.

    Volume varies by track size and role complexity.

  • 03

    Pre and post skills assessment

    Same instrument at Week 1 and Week 5. You get per-person and per-track deltas, named gaps closed, named gaps that need follow-up.

    Anonymised by default. Named per-person available on request.

  • 04

    Adoption analytics dashboard

    Per-track usage, prompt-library hit rates, workflow run counts. The dashboard you can put in front of leadership when they ask whether this worked.

    Tracks usage we can instrument; we can't read inside vendor consoles you don't share.

  • 05

    Certificate of completion

    A signed certificate per participant. Recognition, not accreditation. For internal LinkedIn posts and team performance reviews. We're not an accredited body.

    Issued by RipplLabs. Has no academic or CPE credit weight.

Tools across the program

Four tools. Taught by track, not by lecture.

Every participant works in two of these by Week 5. Which two depends on the track. We train on all four every day, so we can speak honestly about where each one wins and where it loses.

  • Long-context reasoning. Ops and Leadership tracks use it heavily for multi-doc analysis and structured output.

  • Broadest integration ecosystem. Sales and Comms tracks use it for CRM webhooks and content prototyping.

  • Native to Excel, Outlook, Teams. Ops and Finance-adjacent participants use it where the data already is.

  • Native to Workspace. Marketing and Comms tracks use it for Docs, Sheets, and SEO-tuned refinement.

We wire automations using the platform you already run: Zapier, Make, n8n, or Claude Projects. We don't add new vendors to your stack mid-program.

Pricing detail

One fixed program fee. No per-seat pricing.

Immersion is priced per program, not per participant, so you can send the full team without rounding up the bill. Cap is 25 participants.

From$28k/ program

Pricing scales with program size above 15 and custom-track count. Most engagements land at the listed rate. Multi-region or asynchronous-only programs can move it.

What's included

  • Pre-program scoping: a 60-minute call plus a written program brief in five business days.
  • Five live sessions, each practitioner-led, 90 minutes per session.
  • Track leads for each named track (up to 4 tracks per program).
  • Async support across all five weeks via shared Slack channel.
  • Two production workflows per participant, built and shipped during the program.
  • Pre/post skills assessment and adoption analytics dashboard.
  • Two weeks of post-program Slack support after Week 5 closes.
  • Certificate of completion per participant.

What's not

  • Ongoing retainer after the program. That's what AI Partner is for.
  • License costs for Claude, ChatGPT, Copilot, or Gemini: you bring those.
  • Custom-track development beyond the four named tracks; we charge for additional named tracks at scoping time.
  • External tooling licences like Zapier or Make. We use what your team already runs.
  • Academic or CPE credit: the certificate is recognition, not accreditation.
Program brief in five business days. No pitch deck.

Before you book

Five things teams ask before committing to five weeks.

It's a real commitment. These are the questions that decide it.

  • 01

    Five weeks is a big commitment. What if we lose people halfway?

    We design for that. Each week ends with something built or assessed, so a participant who drops at Week 3 still leaves with a working workflow and a baseline skills delta. That said, completion rates matter to us; if a program starts losing people, we ask why and adjust live.

  • 02

    Can remote teams join?

    Yes. Most programs are remote or hybrid. Live sessions are video; async work happens in your team's normal tools (Slack, Loom, shared drives). We split the program by timezone if it spans more than four hours.

  • 03

    What's the assessment actually testing?

    Three things: prompt construction quality (can you write a prompt that gets the answer in one shot?), tool selection judgment (do you reach for the right tool?), and workflow design (can you decompose a real task into AI-assisted steps?). Same instrument before and after. We share the rubric upfront.

  • 04

    Can we send five participants instead of twenty-five?

    Yes, but be honest with us at scoping. A five-person program is structurally different: fewer tracks, more practitioner attention per person, different price (we discount roughly 30%). If you're between five and twenty, we'll tell you whether Immersion is the right shape or whether two back-to-back AIramps would land better.

  • 05

    What happens to our prompts and workflows after the program?

    They stay with you. Everything is built in your stack, in your accounts, with your data. We don't host or own anything. Two weeks of post-program Slack support is included for handoff questions; after that, you can engage AI Partner for ongoing builds, or you're independent. Either is fine.

A question we haven't answered? Bring it to the call.

If Immersion isn't the right shape

Three tiers. One differentiator each.

We'd rather route you correctly than book the wrong engagement. Immersion is a real commitment. Here's how to know if it isn't the right one.

If you want a shorter format

AIramp Workshop

Half a day. One team. Two artifacts. Behaviour change in a single session.

From $8,500See AIramp

You are here

AI Immersion

Five weeks. Role-specific tracks. The deepest skill transfer we run.

From $28kDetail page

If you want ongoing support

AI Partner

Monthly retainer. Pair after Immersion for sustained adoption, or stand alone for slower-burn engagement.

From $6k / moSee Partner

Or if you haven't done a workshop yet, AI Ignite is the sixty-minute on-ramp most programs start from.

Interested?

We start a new group when there's enough fit.

Tell us about your team and what you're trying to change. We'll map you against the next program opening, or scope a private one if your team alone justifies it. Either way, you get a written program brief within five business days.

or email hello@rippllabs.io →
  • Program brief in 5 business days
  • Private programs available for teams of 8+
  • Practitioner on the line, not a sales rep