WizzlyTry Wizzly free

Why we built Wizzly this way

The short answer

Wizzly was built by Amit, a parent and software developer, after his 3.5-year-old asked him what to do when she gets angry and he realised he had only learned the answer at 36. It is screen-free because conversation is the skill being taught, and the learning is hidden inside stories because children resist lessons and absorb play.

The question that started it

During an evening walk, my daughter and I passed a little boy in the middle of a full meltdown — screaming, hitting his parents, the whole thing. She watched it quietly, taking it in, and then looked up at me.

"Dada, I love you. I will not hurt you, but tell me what I do when I get mad?"

I froze. Not because it was a hard question, but because I was 36 years old and I had only worked out my own answer a few years earlier — slowly, awkwardly, mostly by getting it wrong in front of people who deserved better. Nobody had taught me. I had assumed, like most of us, that this was something you simply pick up.

Some of us do pick it up. Many of us do not, and pay for it for decades in careers and marriages and friendships. The thing that struck me on that walk was that she was asking at exactly the right age — and that there was nothing I could hand her.

Why screen-free, and not another app with videos

Conversation is not a subject you can learn by watching. It is a motor skill for the mouth and the ear: you get better at it by doing it, badly, many times, with something patient on the other end.

Almost every "educational" product for young children puts a screen in the middle and makes the child a spectator. That is the opposite of practice. Wizzly is voice-first for a reason that has nothing to do with screen-time politics and everything to do with pedagogy — the child has to actually speak, and has to actually listen, or nothing happens at all.

The side effect is that the phone can lie face-down across the room while it works. In the car, at bedtime, on a walk.

Harvard's Center on the Developing Child describes "serve and return" — the back-and-forth of an adult responding to a child's babble, question or gesture — as one of the core interactions that builds brain architecture. What matters is the return, not the broadcast.

Center on the Developing Child, Harvard University

Why the learning is invisible

Every story Wizzly tells carries one hidden objective — an emotion to name, a social situation to navigate, a handful of words to meet in context. The child never hears about the objective.

This is not a gimmick. The moment a child can tell they are being taught, two things happen: they perform rather than engage, and they resist. Ask any parent who has tried to turn a car journey into a teachable moment. The lesson has to be underneath the thing the child actually wants, or it does not land.

So the design rule we hold ourselves to is blunt: if your child can spot the lesson, we have failed. You see the skills in the parent dashboard. Your child sees a slightly ridiculous wizard.

What Wizzly is not

  • Not a general-purpose chatbot. Wizzly is one character with one personality and hard boundaries, not an open-ended assistant with a kid-friendly coat of paint.
  • Not a therapy or diagnostic tool. If you are worried about your child's speech, language or development, that is a conversation for your paediatrician or a speech and language therapist — not an app.
  • Not a replacement for you. It is built for the gaps: the car ride, the wind-down, the third "tell me a story" when you have run out. The dashboard hands you conversation starters so the stories flow back into your own conversations.
  • Not ad-supported. Your child is not the product, and there is no version of this where they become it.

Who is building it

Wizzly is built by Amit — a software developer who has spent a career on complex technical problems, and a parent who found the hardest problem at home. Early versions were written at night, after bedtime.

It is early. The 3–6 tier is live, the older tiers are in build, and the families using it now are genuinely shaping what it becomes — which is why early access is free. If you use it and something is wrong, I would rather hear it than not.

Where things stand today

The Wonder Years tier for ages 3–6 is live and free during early access — no waitlist, no download, it runs in the browser. The Social Years (7–10) and Depth Years (11–15) are in development.

If your child is older, it is worth starting anyway: the account carries over, and early-access families keep their pricing when the older tiers land.

Try Wizzly free →

Wizzly is completely free during early access — every story, no card required. Runs in the browser — no download.

Common questions

Who made Wizzly?

Wizzly was built by Amit, a software developer and parent, after his 3.5-year-old asked him what to do when she gets angry. It is an independent product, not a division of a larger company.

Is Wizzly based on research?

The approach draws on established developmental work — Harvard's Center on the Developing Child on "serve and return" interaction, and the broad evidence base behind social-emotional learning. Wizzly itself has not been the subject of a published efficacy study, and we will not claim otherwise.

Is Wizzly free?

Yes, completely free during early access — every story, the full parent dashboard, no credit card. Paid plans will arrive later, and early-access families will get notice and a permanent discount.

Related guides

Is ChatGPT safe for kids?ChatGPT requires users to be 13+ and is not designed for children. What the risks actually are, what the age rules say, and safer alternatives built for kids.Screen-free learningAudio-first and screen-free ways for children to learn — what the categories are, what to look for, and why interactive audio beats passive listening.Wizzly for ages 3–6Wizzly for 3 to 6 year olds: short screen-free audio stories that teach naming feelings, turn-taking, apologies and asking for help. Available now, free during early access.
Written by Amit, founder of Wizzly. Last updated July 27, 2026.