What to build with your bright, bored kid this summer

Why I wrote this

You have a kid between 11 and 16 who is clearly capable. They pick things up fast. They have opinions about apps, games, videos, and brands. And they spend a large number of hours each week inside things that other people built, getting very good at consuming and not much practiced at making.

Most parents in your position do one of two things. They buy a class, a kit, or a camp, and watch the kid lose interest by the second week. Or they do nothing, because the alternatives all look like more screen time with a nicer logo.

There is a third thing, and it does not require you to be technical, to manage a project, or to know how any of this works. It requires one idea, held clearly, and a parent who knows how to ask two or three good questions at the kitchen table. This guide gives you both. Everything in it is something you can use this week, whether or not you ever pay me a dollar.

The reframe: maker, not consumer

Start here, because everything else follows from it. The years between 11 and 16 are the years your kid forms a self-image about what they are for. A kid who spends those years only consuming arrives at the rest of their life fluent in watching. A kid who spends even a few focused hours a week building arrives with something almost no adult you know has: proof, made with their own hands, that they can make a real thing other people use.

This is not a screen-time argument. The screen is not the problem. The question is which side of the screen your kid is on. The same device that delivers an endless feed can also be the place a 13 year old ships a tool a real person pays for. Same hours, same device, opposite outcome. The only variable is whether they are taking from it or making with it.

The cheapest, most durable thing your kid can build this summer is not a skill on a resume. It is the identity of someone who finishes and ships real things. That identity compounds for the next ten years.

The one move that matters: customer first

If your kid takes only one thing from this guide, make it this. Almost every kid who tries to build something starts with the product. They say, in some form, the following:

I want to make a fitness app.

That is not an idea. That is a category. A category is a shape an idea might one day fit inside. You cannot build a category. You can only build a specific thing, for a specific person. Watch the difference between a category and a real idea:

The first column sounds bigger. The second column is actually buildable. A 13 year old with a second-column idea ships something real. A 13 year old with a first-column idea is back where they started by the end of the month. The difference is not skill or luck. It is that one of them is thinking about a specific human and the other is thinking about a market.

A real idea answers three questions, in this exact order

1. Who is the person? Use their actual first name. Not "users." Not "people who like to draw." A name you would call out if you were yelling across a room.
2. What is the problem? Something the person already spends real time, money, or attention trying to solve, badly. If they are not already trying to solve it, the pain is not strong enough.
3. How do you know it is a problem? Did your kid watch them do it? Did the person say so? Did your kid do it themselves? A moment they witnessed beats a thing they assumed.

If your kid can answer all three, they have an idea. If they cannot, they have a category, and no amount of building will save it.

What a real idea sounds like on paper

Here is the shape to aim for. This is an illustrative example written to show the move, not a claim about any specific child.

Sarah is 17 and runs the social media for her dad's gym in San Mateo. She spends about 5 hours a week trying to turn 90 minute Zoom-recorded class footage into 60 second clips. She uses CapCut. She gets frustrated because she has to scrub through the entire 90 minute recording to find the one good moment. I watched her do it last Saturday for two hours. She muttered "this is so stupid" four separate times.

Count what is actually in there:

• A name. Sarah.
• An age. 17.
• A role. Runs social for her dad's gym.
• A specific tool she already uses. CapCut.
• A specific frustration. Scrubbing 90 minutes of video.
• A moment that was witnessed. Last Saturday, two hours, four mutters.

Now the same idea written as a category: "an app for social media managers to turn long videos into short clips." Zero people. No Sarah, no Saturday, no four mutters. Just a market shape. The kid who can write Sarah's version will out-build the adult who writes the second version, because the kid is thinking about Sarah and the adult is thinking about a market.

Your job: inspect the work, do not do the work

This is the part most parents get wrong, and it is the part that decides whether your kid learns anything. The rule is exact and it is easy to violate: you inspect the work, you do not do the work.

Your kid makes the decisions, talks to the coach, writes the thing. You read what they produce. You ask questions. You point out what they missed. You do not type their answers, edit their idea, or research their market for them. This rule exists because a project can be faked if you do it, but the skill cannot. We are in it for the skill.

You do not have to be technical to do this well. You only have to be present and willing to hold a standard. Here are the questions that do the work for you. Pick one, ask it, then listen. Do not pepper them with all five.

• "Who is the person in your idea? Describe them to me like I have never met them."
• "When did you actually watch them have this problem? Tell me the moment."
• "If you handed them your first version next Saturday, what would they do with it?"
• "What is the smallest version of this that would still solve the painful part?"
• "Why does the tool they use today not work for them?"

And three things to resist, because your instinct will be to help and helping the wrong way takes the lesson away:

• Do not optimize their answers. When the work asks "which specific kids, where, with what problem," let them struggle to answer it. The struggle is the lesson.
• Do not pre-research their idea. If they want to build for skateboarders, resist looking up skateboarding apps and presenting findings. They learn to do their own research by doing it.
• Do not rescue them from boredom. Some hours of real building are unglamorous. Sitting with that is part of it. The feeling of shipping on the other side is what they remember.

The word that does all the work: real

Most programs for kids build dioramas: a model of a thing, graded by an adult, thrown away in June. The whole point of building this summer is that the thing is real. Here is what real means, used the same way every time:

• A real customer is a specific person whose name your kid knows. Not a sibling. Not you. Someone who does not live in your house and is not in your kid's school.
• A real problem is something that person already spends real time, money, or attention on, badly.
• A real product is something a real customer would pay a real dollar to use, even if it is rough at the edges.

That is the bar. Aim there from the first day. When your kid offers to "sell" the thing to you for ten dollars so they can check a box, the honest answer is calm and standard: "That is a parent, not a customer. Try again with someone outside our family." No drama. Just the standard.

What the whole arc looks like, if they keep going

Finding the idea is the first step. If your kid wants to take it all the way, here is the path a young builder walks: idea, then a locked offer, then a working first version, then real payments wired up at a domain that is theirs, then a public launch, then the moment that changes everything, a first paying customer who is a stranger.

That first dollar from a stranger is the hinge. Before it, your kid is a kid with a project. After it, they are a builder, and the next thing they make in their life starts from a different baseline. It is the one milestone worth orienting the whole summer around. Everything before it is preparation. Everything after it is easier.

You do not need a program to start. The exercise above and your two good questions are enough to begin this week. If you want to go further today, your kid can do the real Module 1 free, with no login and no card, and write their first idea brief in a guided builder. A program helps with what comes after the idea: the structure that keeps a kid moving when motivation dips, the coaching that gets them unstuck the same day instead of quietly giving up, and the finish line of one real shipped thing. That is the gap Wright is built to fill, and it is the only reason the next section exists.