Skip to content
ServicesOur WorkAbout
Let's Talk
NavigateMENU / 04
01About
02Our Work
03Services
StrategyCreativeWebsite DevelopmentSoftware DevelopmentBusiness Automation
04Contact
More
BlogFlight Program
Elsewhere
Productized engagement

The AI Fluency Sprint

Measure the spread. Move the floor. Then measure it again.

Four to six weeks with your team, from a scored baseline to a report that shows the distribution before and after. Fixed scope, one price, and everything we build is yours at the end of it.

Price

From $4,950

Scoped on team size. The discovery call settles it in twenty minutes.

Duration

4 to 6 weeks

Remote by default. We're Calgary-based and happy to travel.

Book a call →
Schedule

Eight touchpoints, ten weeks.

The sprint schedule, from the week one baseline to the week ten check-inWeek 1: Baseline. Scored questionnaire, whole team Week 1: Build. 2 to 4 tools against your real work Week 2: Workshop I. Streamed by fluency, tools handed over Week 2: Leadership. 45 minutes with whoever funds it Week 3: Practice. Assigned work, posted where the team can see it Week 4: Workshop II. Your people demo, then we go deeper Week 5: Re-measure. Same instrument, written report Week 10: Check-in. Thirty minutes, after the relapse pointWK 1BaselineWK 1BuildWK 2Workshop IWK 2LeadershipWK 3PracticeWK 4Workshop IIWK 5Re-measureWK 10Check-in
  1. WEEK 1

    Baseline

    Scored questionnaire, whole team

  2. WEEK 1

    Build

    2 to 4 tools against your real work

  3. WEEK 2

    Workshop I

    Streamed by fluency, tools handed over

  4. WEEK 2

    Leadership

    45 minutes with whoever funds it

  5. WEEK 3

    Practice

    Assigned work, posted where the team can see it

  6. WEEK 4

    Workshop II

    Your people demo, then we go deeper

  7. WEEK 5

    Re-measure

    Same instrument, written report

  8. WEEK 10

    Check-in

    Thirty minutes, after the relapse point

Scope

What you're buying.

Included
  • A scored fluency questionnaire, run across your whole team at the start and again at the end.
  • Two to four working tools, built against tasks your team actually does, handed over as yours.
  • Workshop I, split into two groups by fluency so nobody is bored and nobody is lost.
  • A separate forty-five minute session with the people who approve the budget.
  • Assigned practice between sessions, landing somewhere your team can see each other's work.
  • Workshop II, opening with your own people demonstrating what they built.
  • A written report: what moved, what didn't, what your team said, and who should own this internally.
  • A thirty minute check-in about a month after the report lands.
  • The questionnaire itself, so you can re-run it in six months without us.
Not included
  • Production software. If the sprint surfaces something worth building properly, that's a separate project with a separate quote.
  • Ongoing maintenance of the tools we hand over. You own them, which also means you own them.
  • Your Claude licences. You buy those directly, and we'll tell you which tier you actually need rather than the one that looks impressive.
  • Deep integration into your systems. MCP servers, data pipelines and agent tooling are engineering work, and they live in the field guide.
  • Anything resembling a motivational keynote.
The awkward questions

Asked and answered before you have to ask them.

What if half my team doesn't engage?
Some won't, and the baseline tells us who before we start. That's what the streaming is for. The people at the bottom of the distribution usually aren't resistant, they've just never been shown one thing that touches their actual job. If someone genuinely doesn't want to be there, the report will say so plainly rather than average them into a number that looks fine.
We already did an AI training day. Why is this different?
A training day measures nothing, builds nothing for you specifically, and ends the moment everyone closes their laptop. The three things that make this stick are the tools built against your work, the practice with a deadline and an audience, and the second measurement. Take those away and you've got a training day.
What if we're not a fit?
We'll say so on the discovery call and you'll have lost twenty minutes. We turn down work that isn't consolidating on Claude. We've also told teams small enough to sort this out in a single conversation to go and do exactly that, which is a worse business decision and a better answer.
Who owns what we build?
You do, outright. Part of Workshop II is your people editing those tools in front of us, because a tool nobody on your team can change becomes dead weight the first time your process does.
Does this need our leadership to be bought in already?
No, and if it did we'd have a much smaller business. Plenty of these start with one person who can see what's possible and can't get anyone to move. Part of what the discovery call is for is working out how to make that argument, whether or not you end up hiring us to run it.
Start here

Twenty minutes to find out if it's a fit.

Bring your situation rather than a brief. Where your team sits, what's stuck, and who's already three years ahead of everybody else. We'll tell you honestly whether this is the right engagement, a different one, or nothing at all.

Book a call →How the consulting works
Paper Crane / Studio
CALGARYVANCOUVER·© 2026

A digital transformation studio building considered, durable web work for ambitious operators.

Services
  • Creative
  • Strategy
  • Website Development
  • Software Development
  • Business Automation
  • ─AI Automation
  • ─Workflow Automation
Navigate
  1. 01About Us
  2. 02Our Work
  3. 03Contact Us
Elsewhere
© 2026   PAPER CRANE MEDIA LTD.
Terms & Conditions
Privacy Policy