Cohort vs. solo: which is right for our family?

The two paths, in one sentence each

The solo path: you buy the software, your kid installs it on the family computer, and from then on your kid is making games or stories or sites or short films at their own pace. The studio runs in the background of your week. Your kid opens it when they want to, ships when they ship, and shows you when there is something to show.

The cohort path: every Saturday morning for four weeks, your kid joins a small group of five other kids and one mentor on a 75-minute video call. They work on their own project, but they work on it during the call, with the mentor present, and on week four they demo it to the group. The software is included; the AI is included; the structure and the audience is what you are buying on top.

Both end the same way: a kid with a published project and the experience of having built it. The middle is different.

What the cohort actually does

The cohort works because of two ingredients that don’t exist in the solo path: a more knowledgeable other in the room (the mentor) and a peer audience.

Lev Vygotsky’s zone of proximal development was the original argument for why a more knowledgeable other matters.¹ A kid can do some things on their own and some things they can’t do yet. In between is a zone where they can do the thing with a small assist from someone slightly ahead of them. That zone is where most of the learning happens, and the cohort mentor lives there. The mentor is not teaching from a script; they are watching what each kid is making and offering the next-step nudge at the right moment.

The peer audience is the second ingredient. Mitchel Resnick’s 4 Ps framework names Peers as one of the four creative-learning engines, alongside Projects, Passion, and Play.² A kid who knows five other kids will see what they made on Saturday tends to make different choices during the week. Sometimes more polished. Sometimes weirder. Either way: more deliberate. The demo night is not a performance, it is a deadline that makes the work feel finished.

The cohort also has a less visible benefit: it reframes what the kid is doing. A kid working alone on a game might describe what they did this week as "I played Tell and Show." A kid in a cohort describes it as "I worked on my game with my group." The cohort upgrades the activity, in the kid’s own self-description, from playing to making. Kafai and Burke’s work on connected learning communities makes the same observation: kids in a group with shared making and shared audience develop richer identities as creators.³

What the solo path actually does

The solo path is the studio without the social wrapper. Your kid opens it when they want to. There is no Saturday morning standing appointment. There is no mentor watching. There is no demo deadline.

The cohort gives the kid a deadline. The solo path gives the kid forever. Both are gifts. They are different gifts. From the cohort intake calls

For some kids, that is exactly the right shape. The kid who already has momentum, who already makes things in their own time, who already has a notebook full of ideas they want to build, will treat the cohort as scaffolding they do not need. The studio software gives them the tools and gets out of the way. Inkie is the AI partner; the parent is the audience; the gallery is the publish point. That can be enough.

The solo path also works for kids who are more introverted, who would find a weekly group call draining, or who simply have crowded weekends with sports or music or other commitments. We have parents who tell us their kid would have loved the cohort but the schedule didn’t fit, and they have done extraordinary solo work over six months because the solo path was the only path the calendar permitted.

What the solo path asks of the parent is a small amount more presence. Not supervision in the surveillance sense, but presence. Someone needs to be the audience the kid is making for, because Inkie is a tool, not a friend. The parent dashboard is built to make that easy: approval prompts when the kid is ready to ship, the family gallery when something is published, the option to look at the trace together when the kid wants to show you what changed.

Three questions that decide it for most families

If you are stuck between the two, work through these. Most families have a clear answer after question two.

The most common mistake we see is parents picking the cohort because it sounds more impressive and then watching the family schedule make it half-attended. A half-attended cohort is worse than a well-used solo path. If the Saturday morning is not actually free for four weeks in a row, choose solo and run a cohort later.

The second most common: parents picking solo because it’s cheaper, when the kid is clearly in the "needs a deadline" camp. Six months later the kid has installed the studio, opened it twice, and the parent feels like the software didn’t take. That is a fit problem, not a software problem. If the kid needs a deadline, buy the deadline.

The money math, honestly

Solo path: $99 single track or $149 all-four bundle, one time. AI add-on $30/mo or $300/yr is optional; without it Inkie still works in scoped mode, just slower and with fewer model choices. So the floor is $99 for one kid forever, with no recurring fees if you skip the AI add-on.

Cohort path: $299 Private (one-on-one mentor), $496 Single (5 kids + 1 mentor, your kid’s slot), $695 Builder (mentor + builder-track focus), $780 Studio (full studio cohort with all-four tracks). Each tier includes the software license for all four tracks and two months of AI access. So if you were going to buy the all-four bundle plus two months of AI anyway, the Studio cohort delta over solo is roughly $480 for four weeks of mentor time plus the peer group.

Whether that delta is worth it depends entirely on the answers above. For a kid who needs the deadline, $480 for the structure is one of the best educational dollars we have watched a family spend. For a kid who would have shipped solo, the cohort is a nice-to-have that didn’t move the needle.

One last note: you can do both. Run the solo path for two months, then enroll in a cohort once the kid has some momentum and a project to bring to demo night. We have run cohorts where every kid arrived with an existing project, and those tend to be the deepest weeks. Solo first, cohort to finish, is a real path.