School & Kura Pathway

A light rollout path for schools, kura, and departments

Te Kete Ako is not selling a heavy enterprise platform in this phase. The school lane is simple: let kaiako prove the workflow, then widen access with support, onboarding, and a sensible rollout conversation.

What the school lane is for

Use this path if you are a principal, HOD, kaiārahi, or small team who wants to adopt the premium teacher workflow without waiting for full institution tooling.

Start with real teacher value

Lead with the workflow teachers will actually use: Te Wānanga for first drafts, Creation Studio for refinement, and saved/exportable outputs for classroom use.

Roll out in small steps

Begin with a few kaiako, gather feedback, and widen access only once the value is clear. This is a rollout conversation, not a procurement maze.

Keep the public library open

The free library remains part of the offer. School access adds a premium workflow layer on top of that open resource base.

Choose the right starting point

The school lane works best when the starting point matches the scale of the problem you are actually trying to solve.

Individual kaiako

Start with the self-serve workflow

If one teacher needs drafting, adaptation, and export help right now, start with Te Wānanga, Creation Studio, and the Kaiako Pro path.

Compare plans

Small team or department

Run a real pilot first

Start with the kaiako carrying the heaviest planning load, test the workflow in ordinary planning conditions, and widen only if it is saving real time.

See Te Wānanga

School or kura leadership

Use the school lane when rollout support matters

If staff access, onboarding, invoicing, or equity pricing need a conversation, use this lane early instead of trying to force an enterprise process that does not exist yet.

Start the conversation

A simple rollout pathway

What we can support now, before full school administration tools exist.

  1. Trial with a small group. Start with Kaiako Pro access for the staff who need the workflow immediately.
  2. Map your planning process. We help you work out where Te Wānanga and Creation Studio fit your current planning and export flow.
  3. Widen only when it earns its place. Expand once the value is obvious for your department, syndicate, or kura.

What the first 30 days can look like

The school lane should feel practical from the first conversation onward: one cohort, one clear workflow, and one honest check on whether the value is real.

Week 1: choose the kaiako who need it most

Start with the teachers already carrying the heaviest planning load, not a whole-school mandate. That is the fastest way to see whether the workflow earns its place.

Week 2: run the real workflow

Use Te Wānanga for the first draft, Creation Studio for refinement, and My Kete for continuity. The point is to test the whole planning thread, not a single flashy demo.

Week 3-4: decide whether to widen access

If the workflow is saving real prep time, widen the cohort. If not, keep the rollout small and honest instead of forcing a school-wide commitment too early.

What happens next if you enquire

We want the first school conversation to feel practical, not like a procurement maze.

1. We clarify the use case

Who needs access first, what planning pain you are trying to solve, and whether the free library or Kaiako Pro workflow is the right starting point.

2. We map a light rollout

We keep the first phase small: a few kaiako, a clear workflow, and straightforward support while the school lane stays intentionally light.

3. We sort pricing and support clearly

That includes staff access expectations, onboarding support, and any equity or kura pricing conversation that should happen before rollout.

What support can look like in this phase

The current school lane is intentionally light, but it should still feel real and useful once a pilot begins.

Workflow setup around your existing planning habits

We help the first pilot cohort work out where Te Wānanga, Creation Studio, and My Kete fit their real planning sequence instead of asking staff to adopt a completely new system all at once.

Simple access and onboarding support

The early support focus is practical: who needs access, what the first tasks should be, and how to keep the premium workflow moving without a full institution dashboard.

Rollout decisions tied to actual teacher value

We want the widening decision to come after the workflow has saved real prep time, not before. That keeps the school lane credible and low-drag.

What a successful pilot should prove

The point of a first cohort is not just usage. It is evidence that the workflow is worth widening.

Teachers reach a useful first draft faster

Te Wānanga should shorten the distance between an idea and a workable lesson draft, especially for kaiako carrying the heaviest planning load.

The workflow stays continuous after generation

Creation Studio, My Kete, and export should feel like one connected planning thread rather than a collection of disconnected tools.

Leadership can widen access with confidence

A good pilot should make the next decision clearer: keep the cohort small, widen to a department, or start a fuller kura conversation with real evidence in hand.

What a school is actually paying for

The point is not to buy a bigger resource archive. The point is to give staff a planning workflow that saves time, holds drafts in one place, and can scale only after it has proved itself.

Teacher workflow, not generic AI access

The commercial value is in a teacher-facing sequence that starts with drafting, continues through editing, and ends in something staff can keep and reuse.

Support that matches rollout size

A small pilot cohort should not have to pretend it is an enterprise programme. We keep onboarding and support proportionate to the stage you are actually in.

Confidence before admin overhead

We are intentionally earning trust before we build heavy procurement or admin machinery. That keeps the school lane practical instead of bloated.

What you do not need yet

The point of this lane is to reduce institutional drag, not add it.

No full procurement project

You do not need a heavy enterprise process just to test whether the workflow helps your kaiako plan faster and better.

No whole-school commitment

You can start with a few staff, a department, or one pilot cohort. The rollout should widen only after the workflow earns its place.

No admin dashboard promise

We are not pretending a full institution console exists yet. This phase is about staff access, onboarding, support, and pricing clarity first.

School & kura questions

The current lane is intentionally light, but it should still answer the questions a decision-maker actually has.

Can we roll this out without a full admin dashboard?

Yes. This phase is about staff access, onboarding, support, and pricing clarity first. We do not need a heavy admin console for the initial rollout to be real.

How does support work?

Support is conversation-led. If your staff need onboarding or workflow help, we handle that directly while the lane stays light.

Can kura Māori or low-decile schools ask about flexibility?

Yes. Equity pricing is part of the school lane. Raise it early and we will work through the rollout path with you rather than treating it as an exception.

What should an HOD or principal look at first?

Start with the pricing page, then look at Te Wānanga and Creation Studio as the practical premium workflow. If that value is there, the rollout conversation makes sense.

Do we need to commit the whole school at once?

No. The current lane is designed for phased rollout. A smaller kaiako pilot is the normal way to start before any wider commitment.

What if billing or invoicing needs to be simple?

That is exactly why this lane stays light. We handle the conversation directly instead of forcing schools into a self-serve enterprise flow that does not fit this phase yet.

What to include in your first message

The fastest school conversation is a practical one. A short message with the right context is more useful than a long formal enquiry.

  • Who is in scope: one kaiako, a department, or a wider school/kura rollout.
  • What problem you want to solve: faster first drafts, better workflow continuity, shared planning, or export/publish support.
  • What matters operationally: onboarding, invoicing, equity pricing, or a phased rollout.

We aim to respond with the next sensible step, not a generic sales sequence.

Keep it simple

Te Kete Ako does not need to become a heavy school platform to be useful. The current school lane is about giving kaiako a better workflow and giving schools a credible way to adopt it.