FOR SCHOOL AUTHORITIES

Adopting AI is an organizational decision.

Teachers are already using AI. The question for a school authority is whether that happens deliberately, with curriculum fit, teacher control and a proper privacy review, or by default. We help you choose deliberately.

ONE DECISION, FIVE PERSPECTIVES

What adoption looks like, role by role

Senior leadership

A clear, defensible position on classroom AI: one your authority chose deliberately, with a named partner, instead of inheriting whatever tools arrive on their own.

Curriculum leaders

Workflows that start from your programs of study, so AI-drafted materials begin aligned with the curriculum rather than being checked against it after the fact.

Technology leaders

One accountable vendor, a documented review path for privacy and security questions, and a product teachers access through a standard web login.

Principals

A consistent, school-sanctioned way for staff to use AI, with expectations everyone can point to, instead of a patchwork of personal accounts.

Teachers

Faster first drafts grounded in the curriculum they already plan from, with every output reviewed, edited and approved by the teacher before it is used.

THE SCHOOL-READY AI MODEL

Not general-purpose AI with a school logo.

Starts from the curriculum

Workflows are built around curriculum outcomes, not a blank prompt box. The starting point is the material teachers already plan from.

Keeps teachers in control

AI drafts; teachers decide. Nothing reaches a classroom, a report card or a family without a teacher reviewing and approving it.

Built for school procurement

Designed from the outset for school-division privacy, security and procurement expectations, not adapted to them afterwards.

Co-designed with educators

Built with Canadian educators, in real school workflows, rather than designed in the abstract and handed over.

HOW AN ENGAGEMENT RUNS

An engagement, from consultation to support.

  1. Consultation

    We start with a conversation about your authority’s goals, constraints and current position on classroom AI.

  2. Review

    Your privacy, security and procurement teams get the documentation and answers they need to evaluate the engagement.

  3. Rollout

    We plan the rollout with you: which schools, which workflows, and how teachers are introduced to the tools.

  4. Support

    A named support path for your staff, and an ongoing relationship rather than a licence and a logout.

TWO WAYS TO WORK TOGETHER

Products, custom builds, or both

The Honeybee Toolkit

Subscription

Lesson Planner is available today, the Report Card Assistant is in pilot with a partner school, and the IPP Assistant is in development. One product, growing with the workflows schools actually run.

Custom software builds

Paid engagement

When your authority has a workflow the products don't cover, we build paid custom software for school divisions and education organizations, co-designed with your teams.

PRIVACY, SECURITY & PROCUREMENT

Built to pass your review, not avoid it.

We expect your privacy, security and procurement teams to ask hard questions. That's their job. Our job is to answer them directly:

  • Privacy by design: workflows built for school-division privacy expectations from the start.
  • Procurement-ready: documentation and direct access to us during your review process.
  • A named support path: your staff know who to contact, and so do we.

COMMON QUESTIONS

Frequently asked questions

What is available today?

Honeybee Logic Lesson Planner, our teacher-led AI lesson planner, is available now through the Honeybee Toolkit. Report Card Assistant is in pilot with a partner school — a working version is in use and being refined before wider release, not yet open for sign-up. IPP Assistant is in development. Research, administrative and teaching-material platform work is on our roadmap.

How is student and teacher data handled?

Privacy and security are treated as procurement requirements, not afterthoughts. During review we work directly with your privacy and technology teams and provide the documentation your process requires.

Do teachers still control what the AI produces?

Yes. Every workflow is built so the teacher reviews, edits and approves outputs before they are used. AI drafts; the professional judgment stays with the teacher.

Can you build something specific to our authority?

Yes. Beyond our subscription products, we take on paid custom software engagements for school divisions and education organizations.

Where are you based?

Calgary, Canada. Our products are built around provincial curriculum (starting with Alberta) and real school workflows, in partnership with local educators.

Start with a conversation, not a contract.

Tell us where your authority stands on classroom AI. We'll bring what we've learned building with Canadian schools.

Book a consultation