When to Upgrade Your Child's Robotics Kit (And What to Buy Next)

The robotics kit will not announce that it has been outgrown. There will not be a moment. There will be a kit that gets played with twice a week, then once a week, then put away in a drawer the parent will eventually find while looking for something else.

That is the upgrade signal most parents miss. By the time it is obvious, three months of play have already been lost.

A child who has fallen out of love with their robot will not fall back in love with it. The next kit is usually less expensive than the years of disengaged STEM curriculum that follow if it is not bought.

The four signs a kit has been outgrown

The child stops asking for it. Not the most reliable signal on its own, because children stop asking for almost everything for two-week stretches. But combined with the others, it matters.

Sessions get shorter. A child who used to play for twenty-five minutes now plays for ten. They are not bored of robotics. They are bored of this robot.

The child describes new things they want it to do, and the robot cannot do them. "I want it to remember where it went yesterday" or "I want to make it stop when it sees that thing" are upgrade requests in disguise. The current kit cannot deliver. The next one might.

The child can predict the robot's behaviour before they press go. This is the most overlooked signal. When a child can correctly predict where the robot will end up every time, the learning has stopped. The robot is now a toy that does a thing they already understand. Time to add something they do not.

If three of these four are present, the kit has been outgrown. Sometimes a parent waits for all four. That is usually how a six-month gap of disengagement happens.

The most common upgrade paths

From Bee-Bot to Botley 2.0 (around age 5 to 6)

Bee-Bot's eight-button interface is exhausted within a year for most children. Botley adds object detection, longer sequences, conditional logic, and the separation between programming on the remote and execution on the robot. The price step is small (£20-£25). The capability step is significant. Botley sits comfortably in the 5 to 7 range and is the safest first upgrade for most households. The full Botley 2.0 review covers what changes between using it at five and using it at seven.

From Botley to Wonder Workshop Dash (around age 7 to 8)

The signal is usually that the child has started talking about robots they have seen at school or on YouTube, and Botley does not look like those. Dash adds a tablet interface, Blockly coding, sensor integration, and voice activation. The price step is much bigger (£100-£120 over Botley). It is also the upgrade most likely to be skipped, because parents see the price and decide to wait for the "real" coding kit at ten. That waiting often kills momentum. Dash is genuinely the right kit for the in-between years, and skipping it usually means a frustrated eight-year-old with a Botley they have outgrown.

From Dash to mBot2 or SPIKE Prime (around age 9 to 10)

This is the upgrade where the child stops being entertained and starts being challenged. mBot2 is the better-value option at £130-£150 and has the Python path open. SPIKE Prime is the building-heavy alternative at £350-£420, with the caveat that LEGO is retiring the line in June 2026. If your child is more interested in coding than in building things, mBot2. If they are a LEGO Technic obsessive, SPIKE Prime. The full comparison covers the three questions that decide it.

From mBot2 to Arduino starter kits (around age 12 to 13)

This is the upgrade where the kit stops being the point. By twelve or thirteen, the most engaged children want hardware they can wire up themselves. Arduino starter kits run £40-£80 and come with breadboards, LEDs, motors, sensors, and the open ecosystem that has been the entry point for hobbyist robotics for fifteen years. The 13+ guide covers what comes after the kit phase entirely.

When to skip a generation

Sometimes the right answer is to skip the obvious next kit and jump two levels.

A seven-year-old with very strong sequencing skills who already finishes Botley puzzles in minutes can sometimes go straight to Dash. The risk is that the tablet interface and Blockly editor frustrate them. The reward is that they get two extra years of useful play out of one kit.

A nine-year-old who has done Scratch at school can sometimes go straight to mBot2, skipping Dash entirely. The risk is the building step (mBot2 is a kit, not a pre-built robot) and the steeper coding learning curve. The reward is the longer growth path: a child who starts on mBot2 at nine is on Python by ten.

The test for whether to skip a generation: is the child finishing the current kit's exercises in under half the suggested time? Are they asking questions the current kit cannot answer? If yes, skipping makes sense. If no, the standard upgrade path is the right one.

Where upgrade decisions go wrong

Buying a second kit at the same developmental level as the first. A six-year-old with Botley does not need Bee-Bot too. Code & Go Mouse is a different shape but roughly the same skill level. Adding a second beginner kit produces variety without progress.

Buying a kit two ages too advanced because the child seems precocious. Most "precocious" five-year-olds are at the upper end of five, not actually eight. Dash at five is usually the parent making a bet that does not pay off. Wait the year.

Buying a kit because the older sibling has one. This is the most common parent failure mode. Robotics kits are not hand-me-downs in the conventional sense. A nine-year-old's mBot2 is not the right kit for the seven-year-old who watches them use it. The seven-year-old needs the kit that fits their year, not the older one repurposed.

Buying an upgrade the child did not ask for, then being disappointed when they do not use it. If the child has stopped asking for robotics entirely, the answer is not a more expensive robot. The answer is to ask the child what they actually want to do for the next six months, and to revisit robotics later when (or if) the interest comes back.

What to do with the old kit

Three options usually work. Pass it to a younger sibling, which works only if the gap is at least eighteen months and the younger child has not already been watching the older one outgrow it. Sell it on a local marketplace, where popular kits like Botley and Bee-Bot hold roughly 60% of their original price for two years. Donate it to a school, library, or a robotics club, which often costs the same as selling once you factor in the postage of the marketplace listing. For ideas on what to do with the time freed up by retiring the old kit, the budget guide for ages 6 to 10 covers the cheaper second-kit options if the new one is going to be expensive.

The verdict

For most children, the right upgrade timing follows the pattern: Botley around six, Dash around eight, mBot2 around ten, Arduino around twelve. The age guides in the by-age series cover what fits at each stage in more detail.

The thing parents who time these upgrades well have in common is that they trust the four signs. The child stops asking. Sessions shorten. The child describes things the robot cannot do. The child predicts the robot's behaviour without testing. When three of those four are present, do not wait for the fourth. Buy the next kit. Use the current one for sibling rotation or sell it. The window for keeping a child engaged with robotics is narrower than most parents realise, and the most common reason kits end up in drawers is not that the child lost interest. It is that the robot ran out of road and nobody changed it for one that hadn't.