What Ages 10–13 Want to Build: Survey Evidence
Students ages 10–13 rarely arrive asking to learn entrepreneurship, financial literacy or design thinking. They arrive wanting to make something: a product they wish existed, a website people might use, a brand that reflects their taste or a solution to an annoyance they already recognize.
The survey received 25 responses. This page examines the 18 respondents who reported being ages 10–13, the current age range for Build Week. Within that age-filtered group, product design and website building drew the most initial interest.
What 18 Students Told Us
Among the 18 students ages 10–13, each student could choose two Build Week activities they most wanted to try. Because this was a multiple-selection question, activity totals exceed 18 and percentages do not add to 100%.
- Designing a product
- 12 of 18 67%
- Building a website
- 10 of 18 56%
- Making ads, photographs or videos
- 4 of 18 22%
- Calculating costs, prices and profits
- 3 of 18 17%
- Presenting and selling an idea
- 3 of 18 17%
- Creating a logo and packaging
- 2 of 18 11%
- Writing a product story or sales pitch
- 1 of 18 6%
- Interviewing customers
- 1 of 18 6%
The same age-filtered responses showed that 10 of 18 students (56%) already felt comfortable working with numbers and prices, while 11 of 18 (61%) selected working with one or two other people as part of how they like to work.
This is a small first-party sample, not a representative population study. It is useful because it shows what this group of students said before a build-focused summer experience.
They Want to Make Something They Can Point To
Adults tend to describe learning through subjects.
Financial literacy.
Entrepreneurship.
Design thinking.
Market research.
AI.
Students tend to describe what they want through things.
A product.
A game.
A website.
A clothing idea.
A service.
Something for pets, sports, school, food, family life or a problem they encounter every day.
Those ideas can look scattered, but they often share four characteristics.
The starting point is familiar.
Students are more likely to notice opportunities in parts of life they already understand. They know what frustrates them at school, what their friends talk about, which products they want, what their families buy and where everyday experiences feel inconvenient.
They do not need to discover a problem no one has ever seen before.
They need to recognize something clearly enough to investigate it.
The idea leaves room for identity.
At this age, the name, appearance and personality of a project can matter as much as its function.
That is not necessarily superficial. Choosing the visual direction, audience or tone gives students a visible form of authorship. It helps transform an adult-assigned activity into something they feel responsible for.
The design still has to communicate clearly and support the product. But personal expression can be the door through which more demanding work enters.
The result is visible.
“Learn about business” is abstract.
“Create a product, calculate what it costs and build a website explaining it” produces something students can see.
A visible result gives the week a destination. It also makes gaps harder to hide. If the product cannot be explained, the price does not work or the website confuses people, the team has something concrete to improve.
Someone outside the team can react to it.
Students care differently when another person will eventually see, use, question or reject the idea.
The audience does not need to be large. It may consist of other students, instructors, parents or a few potential users.
What matters is that the project leaves the imagination and encounters another person.
The stronger signal is about project design, not universal preference.
Among students who responded, the most selected activities were product design and website building. Lower-interest activities, including presenting, selling and customer interviews, still matter because they make the idea meet another person.
Students were not simply looking for freedom. They responded to the chance to make consequential decisions about something they could recognize as their own.
Students Need Choice—But Not an Empty Page
There are two easy ways to remove ownership from a student project.
The first is to prescribe everything.
Every student receives the same instructions, follows the same sequence and produces a slightly different version of the same result. This can teach a defined skill efficiently, but students are executing the adult’s idea.
The second is to provide no structure at all.
“Build anything you want” sounds empowering. For many students, it creates a blank-page problem. They choose the first idea that comes to mind, spend too long debating possibilities or focus on a name and logo because the harder decisions remain unclear.
The stronger approach is bounded choice.
Adults establish the process, time, available tools, materials, and safety boundaries. Students make the decisions inside those constraints.
A practical sequence might ask students to:
- notice a problem or opportunity;
- identify who experiences it;
- examine what people currently do or buy;
- compare several possible responses;
- select an idea that can be tested;
- build a product, service, website or prototype;
- calculate the likely costs;
- decide how the idea should be explained;
- show it to other people;
- and revise it after receiving evidence.
The structure tells students which decision comes next.
It does not make that decision for them.
This distinction becomes especially important when students use AI.
AI can produce business names, product concepts, images, research summaries and polished marketing copy almost immediately. That speed is useful, but it can also create the appearance of progress before the student understands the idea.
A student should still be able to explain:
- What problem are we trying to solve?
- Who experiences it?
- What evidence do we have?
- Why did we choose this approach?
- What will it cost?
- What did AI help us do?
- Which decisions did we make ourselves?
- What changed after someone tested the idea?
AI should help students investigate and build. It should not quietly become the author of the project.
Team structure matters for the same reason.
A group of six children can produce one polished result while several students remain observers. Smaller teams and defined responsibilities make it easier to see who is researching, calculating, designing, building and explaining.
Ownership is not created by telling students that the project belongs to them.
It is created by giving each student decisions whose consequences become visible.
How Build Week Turns an Interest Into a Project
The Money Club.Org publishes this guide and operates Build Week, a five-day product-building experience for students ages 10–13. The Build Week curriculum uses the student-facing sequence: Design it. Build it. Price it. Test it.
Build Week does not promise that students will turn their first idea into a successful business.
The first idea is a starting point.
Students may discover that the problem is not important enough, the audience is too narrow, the product costs too much, the price is unrealistic or another solution already works better.
That discovery is part of the work.
Each student works in a small team to:
- identify a problem;
- investigate what people already do and buy;
- select a product or service idea;
- build a website or prototype;
- calculate costs and pricing;
- create the materials needed to explain it;
- test the idea with real people;
- and decide what should change next.
Financial literacy, market research, design thinking, communication and AI sit underneath the project.
Students encounter those subjects because the build requires them.
Market research helps them determine whether other people experience the problem.
Design thinking helps them understand those people before choosing a solution.
Financial literacy reveals whether the costs, price and demand can work together.
Creative tools help them make the idea understandable.
AI helps them research, organize, calculate and produce—but the judgment remains with the students.
The final product does not need to be perfect.
A student should be able to explain what the team wanted to build, why it made particular decisions, what happened during the test and what it would do differently next time.
That is the deeper pattern behind what students ages 10–13 in this survey wanted to build.
They do not necessarily need a revolutionary idea.
They need an idea close enough to understand, open enough to shape and real enough to push back.
For parents, the takeaway is practical: a build week should not hide the less glamorous skills. It should connect pricing, interviews, testing and explanation to a product students care enough to improve.