Partnerships · AthlyticZ

Partnerships

Put your team on state-of-the-art content.

Organizations come to us when the methods their people need are moving faster than any recorded backlog can keep up with. We run the same practitioners and the same live rooms for one group.

How a partnership runs

Four moving parts, in this order.

The shape is the same whether it is a research group, a department, or an analytics team. What changes is what the sessions are about.

At the start

Seats provision

Every seat opens from a browser into an identical, fully configured environment. No install week, no version drift across forty machines, no faculty time spent on IT tickets that were never the teaching.

Every week

Your team learns live

Sessions run for your group by named practitioners from the same roster that teaches our public masterclasses, recorded, with the code and the notes.

Between sessions

The environments carry the work

The room does not close when the session ends. People keep working in the same environment, so what was taught on Tuesday is still runnable on Friday.

Each quarter

A review

What the group has actually built, what landed, and what the next block of sessions should be about. Sessions get re-pointed rather than repeated.

Who we work with

Three kinds of group, one delivery model.

Research teams. Keeping a group current on methods that move quarterly, taught live by people working in them rather than through a course recorded two years ago. Sessions can be built around the methods your work actually turns on. 6 live tracks Weekly cadence

Universities and labs. Running a cohort where every seat opens into the same working environment, so week one is teaching rather than troubleshooting. We provide completion records for the people who finish. We are not a degree-granting or accrediting institution, and we say so to your procurement team before they have to ask. Identical seats 30-day replays

Agencies and front offices. Putting an analytics group on the tools and methods the people teaching them use in production, with dedicated sessions built around the work your team does rather than a generic curriculum. 23 practitioners Official Posit Managed Services Partner

The shape of a license

A flat fee, a number of seats, provisioned environments.

That is the whole structure. What the fee and the seat count come to depends on the group and the scope, which is why it is a conversation rather than a pricing table. Seats can carry the self-paced catalog alongside the live sessions, so people who join mid-stream have somewhere to catch up rather than falling behind the room.

The environments run on IDEalyze, our infrastructure platform and a different product of ours. We run our own entire teaching operation on it, which means it is hardened against the messiest workload we could find: our own.

How we support your team

A channel, standing hours, and a way to buy more.

Support is part of the license, not a thing you chase. What follows is the standing shape; the exact hours are set in your agreement.

Day to day

A dedicated channel

A private Slack channel with your team and ours in it, and a stated response window written into the agreement rather than implied by how busy we are.

Every month

Dedicated support hours

A standing block of hours each month for your team: questions about the platform, the content, or an environment that is misbehaving.

As needs grow

Project hour blocks

Additional hours bought in blocks against a specific project, so a piece of work that outgrows support becomes its own scoped thing rather than quietly eating the monthly allowance.

Covered by support
  • Platform questions: access, seats, provisioning, recordings
  • Content questions: what a session covered, where a resource lives
  • Environment troubleshooting: a seat that will not open, a package that is missing
  • Instructor routing: getting a technical question to the person who taught it
Becomes scoped work
  • Building something for your team rather than teaching them to build it
  • Custom curriculum written for your data or your systems
  • Integration work against your own tooling
  • Anything with a deadline attached that is not a session date

Not a refusal. These are real things we do, and they are quoted as work rather than absorbed into a support window, which is what keeps the support window worth having.

Start here

Tell us about your people.

What they do now, what they need to be able to do, and roughly how many of them. We will tell you honestly whether we can help.

Prefer to talk first? Book a call or email [email protected].

Every live room, the recordings, the code, and the environment, behind one door.

Join the Masterclass

Bring it to your organization.

One call, an honest answer about fit, and a scope if there is one.