← Back to blogBehind the Build

Building Smart Syllabus Assistant: what teachers actually told me

5 February 20266 min read

I did not start with a product spec. I started with a question.

"What is actually eating your time?"

I asked that question to every teacher and school leader I could get in front of. Over coffee, over Zoom, in school hallways, at networking events. The answers were remarkably consistent.

What they told me.

"Planning takes longer than teaching." One early-career teacher described spending 5 hours preparing a single lesson — then delivering it in 50 minutes. The preparation-to-delivery ratio was 6:1.

"I already use ChatGPT. It is not good enough." Teachers are not anti-AI. Most already use it. The problem is that ChatGPT does not know the NSW syllabus, does not build term sequences, and invents outcome codes. Teachers spend as long verifying the output as they would have spent planning from scratch.

"I do not need another app. I need fewer hours." This was the most common sentiment. Teachers are exhausted by tools that promise to help but add another login, another system, another thing to learn. They want the planning burden reduced, not redistributed.

"Differentiation is the hardest part." Every class has students with different needs. Writing individualised adjustments for every instructional phase of every lesson is what turns a 30-minute plan into a 3-hour one. Generic AI advice like "provide scaffolding" is useless.

"The scope is more important than the lesson." Experienced teachers told me that the real value is not in generating a single lesson — it is in having a coherent term plan where skills build, outcomes are tracked, and each week connects to the next.

What I built from those conversations.

Every feature in Smart Syllabus Assistant traces back to something a teacher told me:

  • **Scope-first planning** — because teachers said the term plan matters more than any single lesson.
  • **Verified NESA outcome codes** — because teachers said ChatGPT invents codes and they waste time checking.
  • **Learner profiles** — because teachers said differentiation is the hardest, most time-consuming part of planning.
  • **Phase-level differentiation** — because teachers said "a differentiation box at the bottom is not differentiation."
  • **Word export** — because teachers said every other tool makes them reformat before submitting.
  • **Inline editing** — because teachers said "I do not want AI to write my lesson. I want it to give me a strong starting point I can shape."

What I learned about building for teachers.

Teachers are the most underserved professional users of technology I have ever encountered. They are highly skilled, deeply committed, and working with tools that were not designed for them.

The mistake most EdTech companies make is building for administrators and hoping teachers will follow. I built for teachers first. The admin dashboard came later. The school licence came later. The product started with one question: does this save a teacher time without compromising their professional judgement?

If the answer is yes, ship it. If the answer is no, go back to the conversations.

What happens next.

Smart Syllabus Assistant is now in early access. Teachers can sign up for free and generate their first scope and lessons today. I am actively talking to schools about structured pilots — 5 to 10 teachers, 30 to 90 days, with clear metrics on time saved.

If you are a teacher, try it. If you are a principal, let us talk.

The tool was built from what you told me. Now I want to see if it delivers.


Smart Syllabus Assistant — built from real teacher conversations. Try it free or book a pilot conversation.

See how it works for your classroom

Generate your first NESA-aligned scope and lesson plan in minutes. Free to start.