You are here
AIramp Workshop
Half a day. One team. Two artifacts. Behaviour change in a single session.
From $8,500Detail pageServicesAIramp Workshop
Most chosen
AIramp Workshop
A half-day, hands-on session. Your team walks in with the licenses, the meetings, and the backlog. They walk out with two workflows on rails, one automation already running, and a prompt library built against their own documents.
Who this is for
Three teams who book AIramp.
If one of these sounds like the email you'd send your boss tomorrow, you're in the right place.
- 01
If you're paying for the licenses
You bought Claude or ChatGPT for the team six months ago. Usage data says half the seats are dormant. AIramp turns the seats you’re already paying for into the habits you wanted when you bought them.
- 02
If a single team is the bottleneck
One function, ops, sales, legal, support, is drowning in repetitive work. You don’t need a five-week program. You need them to leave Friday with two workflows on rails. AIramp is built for that.
- 03
If leadership wants proof, fast
You’ve been asked to bring back a "win" before the next QBR. AIramp produces a saved prompt library, a built automation, and a pre/post skills delta you can put in a deck. In one calendar slot.
What we actually do
Five beats. Four hours. One automation running by lunch.
- 9:0030 min
Beat 01
Reset and align.
- We open with the pre-assessment results. Named gaps, not vibes.
- We pick the two workflows we’ll target. You vote, we facilitate.
- We agree on what "done" looks like before lunch.
- 9:3045 min
Beat 02
Tools, side by side, on your real documents.
- Live demo across Claude, ChatGPT, Copilot, Gemini. Same prompt, four answers, side by side.
- We use a real document you sent us a week ago. Not a generic demo.
- The team sees where each tool earns its license, and where it doesn’t.
- 10:1575 min
Beat 03 · Build session 1
Each person leaves with three saved prompts.
- Each person picks a real deliverable from this week’s queue.
- They write, test, and refine three prompts against it. We pair, we critique.
- The winners get saved to a shared prompt library that travels home with the team.
- 11:3075 min
Beat 04 · Build session 2
One automation, end to end, running on real data.
- Pick the bottleneck the team voted on. We design the automation as a group.
- We wire it up live, usually in Claude Projects, Make, or Zapier, depending on your stack.
- It runs against real data before we close. Documented handoff, not a demo.
- 12:4530 min
Beat 05
Commit and close.
- Each person commits to two habits. On their calendar. Before they leave the room.
- We schedule the two-week Slack check-in and the post-assessment.
- Adoption starts the next morning, not next quarter.
What you leave with
Five artifacts. Tailored to your stack.
Below is what every AIramp produces. The exact contents depend on your tools and the bottleneck you bring. We agree on this list before the workshop, not after.
- 01
A shared prompt library
Twelve to twenty saved prompts, written against your real documents and ready to drop into the team’s daily work. Stored in whichever workspace you already use.
Volume varies by team size and use case.
- 02
One automation, built and running
Wired up in the workshop, ran on real data before close. Built in the platform that fits your stack: Claude Projects, Zapier, Make, or n8n.
Tooling depends on what your team already pays for.
- 03
A pre/post skills assessment
Ten-minute baseline before the session, the same instrument after. You get a per-person and per-team delta, plus the named gaps that closed and the ones that didn’t.
Anonymised by default. Named per-person available on request.
- 04
A workflow recording and slides
The full session recorded, indexed by beat, plus the slides. For people who couldn’t make it and for the team to revisit when a habit slips.
Hosted on your platform of choice.
- 05
Two weeks of Slack support
A shared channel with the practitioner who ran the workshop. Real questions, working hours, two-business-day reply window. Closes after two weeks unless you continue with Partner.
Or your messaging tool, if you don’t run Slack.
Tools you'll use that day
Four tools. Side by side. We lead with whichever you already pay for.
We train on all four every day, so we can speak honestly about where each one wins and where it loses. The team learns when to reach for which.
Strongest at long-context reasoning. We use it for contracts, briefs, and multi-doc analysis.
Broadest plugin and integration ecosystem. We use it for image work and quick code prototypes.
Lives where your team already works: Excel, Outlook, Teams. We use it where the data already is.
Native to Workspace. We use it for Docs, Sheets, and anything tied to your Google data.
We also wire up the workshop's automations using the platform you already run: Zapier, Make, n8n, or Claude Projects. We don't ask you to add a new vendor.
Pricing detail
One fixed price. Here's exactly what's inside it.
No tiers within the tier. AIramp is one number. Custom scoping is part of it, not extra.
From$8,500/ workshop
Pricing scales with team size and tool count. Most engagements land at the listed rate; complex multi-tool setups or custom data preparation can move it.
What's included
- Pre-workshop scoping. One 60-minute call plus a written proposal in three business days.
- Custom prompt rewriting against documents you send us a week prior.
- The half-day workshop. On-site or live remote, practitioner-led, no handoff.
- One built automation, running on real data by close of session.
- Pre/post skills assessment with team and per-person deltas.
- Recording, slides, and the prompt library, all stored in your workspace.
- Two weeks of Slack support with the practitioner who ran the workshop.
What's not
- License costs for Claude, ChatGPT, Copilot, or Gemini. You bring those.
- Travel for on-site sessions outside the Bay Area or NYC. Billed at cost.
- Ongoing automation builds after the workshop. That's what AI Partner is for.
- Role-specific multi-track sessions. That's AI Immersion.
Before you book
Four things teams ask about an AIramp.
Not the company. The workshop itself.
- 01
Why not stretch it to a full day?
Because the marginal hour stops landing. We’ve run AIramps as full days. The team’s energy drops after lunch and the second automation gets built but doesn’t get used. Half a day, two artifacts, real adoption. The full-day version is called Immersion and it’s structured differently for a reason.
- 02
What if my team isn't technical?
Most aren’t. AIramp is written for ops, sales, legal, support, finance, the people whose work AI actually changes. We use Claude Projects, Zapier, and Make precisely because they don’t require code. If your team can build a spreadsheet formula, they can build the automation we build together.
- 03
Can we run two AIramps back to back, one per team?
Yes. We do this often. Two AIramps in one week, different teams, different bottlenecks. We discount the second by 15% because the scoping work overlaps. If you’re thinking three or more, Immersion is usually a better shape.
- 04
How much prep do we actually need to do?
About two hours, spread across three weeks. One scoping call (60 min). One round of document sharing (real briefs, contracts, inbox samples, whatever the team works on). One ten-minute pre-assessment per attendee. That’s it. We do the prompt rewriting; you bring the work.
A question we haven't answered? Bring it to the call.
If AIramp isn't the right shape
Three tiers. One differentiator each.
We'd rather route you correctly than book the wrong engagement. Here's the honest comparison.
Ready to scope it?
Tell us the work. We’ll scope your AIramp.
Thirty minutes with a practitioner. We map your tools, the team, and the bottleneck. A written proposal in three business days. No pitch deck, no follow-on calls to extract the price.