Talk
Conversation runs
Reading interviews, day check-ins, recap prompts, and proof of understanding.
chatmicexplain
For parents and educators building with AI
Bring your kid workflow to Sprout.
If you use Codex, Claude Code, Cursor, OpenClaw, Home Assistant, n8n, or your own scripts to help with school, chores, practice, routines, or lessons, we want to see what you made. Sprout is building the place where those workflows can turn into kid-ready conversations, activities, proof, rewards, and receipts.
Codex
Claude Code
Cursor
OpenClaw
n8n
Home Assistant
Shortcuts
scripts
No kid on the call. Blur anything private. Rough is fine.
The promise: your workflow can do the thinking. Sprout can give it a parent-approved place to land with the child.
What Sprout is building
Sprout can run what comes next.
Program a conversation, ask for proof, open a canvas, run a routine, set gems, and get the receipt back. Some of this is live now. Some is next.
conversation
canvas
proof
routine
gems
receipt
- Connect the signal. School email, calendar, sensor, notes, lesson plan, chore state, or your own agent.
- Give the child a place to act. Chat, canvas, routine path, proof step, reward, or unlock.
- Send the adult a receipt. What happened, what needs review, and what should run next.
Product tour
Your workflow finds the next step. Sprout can make it something a kid does.
You bring the agent, script, automation, or classroom workflow. Sprout is where a child can chat, do the activity, prove it happened, earn gems, and send the adult a receipt.
We are looking for early parent and educator builders whose real workflows can shape what Sprout opens to creators first.
Visual run
Email parser to kid checklist
The agent finds the school signal. Sprout turns it into a child-facing task, proof step, and a receipt you can review.
Signalschool email
Kid actionkid checklist
Proofexplain or photo
Receiptparent feed
Best fitschool inbox, pickup changes, spelling words
Sprout can hosttask, chat, proof, receipt
See
Proof moments
Camera proof, worksheet photos, room reset checks, and other parent-approved evidence.
phototapvideo soon
Land
Lobbies and areas
Math Tower, English practice, morning paths, and other places a workflow can land.
lobbyarearoutine
Practice
Canvas activities
Guided quizzes, tiny games, lesson follow-ups, and practice loops built around the child.
quizcanvasreward shop
Connect
Inputs from your stack
Gmail, Calendar, Slack, Khan, Home Assistant, n8n, or the agent you already use.
GmailCalendarbring your own
Close loop
Gems and receipts
Earned gems, screen-time unlocks, reward paths, and summaries that come back to adults.
gemsunlockreceipt
Examples
Your setup does not need to be impressive. It needs to be real.
The smaller and more real, the better. We care what you built, why you built it, and where the handoff still lands back on you.
School inbox parser
Pulls spelling words, permission slips, pickup changes, or teacher updates out of the school-email swamp.
Could become a kid checklist
Lesson or practice generator
Turns class notes, tutor goals, Khan progress, reading work, or sports practice into an activity a kid can use.
Could become a guided canvas
Morning or pickup helper
Turns lessons, lunches, carpools, and last-minute changes into the plan for tomorrow.
Could become a routine path
Chore or allowance flow
Records what happened around the house, then decides what needs a reminder, proof, gem, or reward.
Could become proof + gems
Practice or homework log
Turns piano, reading, sports, tutor notes, or homework into the next step a kid can act on.
Could become a practice loop
Home Assistant or n8n routine
Uses household state to trigger reminders, lights, dashboards, messages, or family nudges.
Could become a Sprout runIf kids already see the output, we want to see it. If it only lands with an adult, that is useful too.
Creator invitation
We are looking for early parent and educator builders.
Bring the thing you already made, even if it is tiny, duct-taped, or half-working. We want to learn what Sprout should let creators run first.
- Turn one repeatable workflow into a Sprout run. Map the trigger, child activity, proof, reward, and receipt.
- Test the handoff from your stack. Explore how Codex, Claude Code, Home Assistant, n8n, or your own agent should pass work into Sprout.
- Shape the first creator surfaces. Help decide what parents, tutors, coaches, and educators should be able to create first.
Paid interview
Want to show us your setup?
We are doing a small number of 30-minute screen-share calls with parent and educator builders. Show one real workflow, tell us where it still gets stuck, and help shape what Sprout should open to creators first.
We'll send a $75 thank-you for completed fit calls. No kid on the call, no identifiable student data, and you can blur anything private.
1
Bring the workflow
School email parser, lesson builder, chore flow, practice log, routine helper, Home Assistant rule, n8n flow, or script.
2
Show where it lands
Inbox, dashboard, calendar, text thread, kid screen, classroom system, paper checklist, or parent notification.
3
Tell us what Sprout should run
The conversation, canvas, proof step, reward, reminder, routine, or receipt you wish existed.
Good fit
You probably fit if a child is supposed to do something next.
It can be small. It just needs to be something you actually use or seriously tried with children in the loop.
1You work with kids age 5-12.
Your own child, students, tutoring kids, coaching group, homeschool pod, or family program.
2You use AI or automation.
Codex, Claude Code, OpenClaw, Cursor, Home Assistant, n8n, Shortcuts, scripts, or your own stack.
3The output repeats.
School, routines, chores, practice, allowance, homework, lessons, pickup, medicine, or calendar chaos.
4You can show the real handoff.
Screen-share for 30 minutes. Blur names, calendars, school details, or anything private.
90-second builder note
Tell us what you built.
No pitch deck. No polished demo. Add your name, email, and the shape of the workflow. Zeev reads each one and replies if it looks like a fit for the early creator conversations.
repeatable workflow
kids age 5-12
handoff still hurts
Fragments are fine. No prep, no kid on the call, no identifiable student data. A rough screen-share is better than a polished demo.
What happens after you send it
- Zeev reads the workflow note. This is not a mailing list.
- If the setup matches the creator conversation, he sends the 30-minute Zoom booking link.
- On the call, show one real setup. Blur anything private.
- Strong fits may help shape early creator paths in Sprout.
FAQ
A creator conversation, not a sales call.
The goal is to learn from the thing you already built and see what Sprout should make possible for families, tutors, coaches, and classrooms like yours.
Do I need to use Codex?
No. Codex, Claude Code, Cursor, OpenClaw, Home Assistant, n8n, scripts, Shortcuts, or your own local stack can all fit.
Do I need to be a parent?
No. Parents, educators, tutors, coaches, and homeschool adults can fit if they are building repeatable workflows for kids age 5-12.
Do I need to show private family data?
No. Show the shape of the workflow. Blur, skip, or describe sensitive parts.
Do educators need school permission?
No. Do not bring identifiable student data, rosters, recordings, or private school details. Use dummy examples or describe the workflow shape.
What if I only use one-off chat prompts?
This is probably too narrow unless those prompts repeatedly create work kids actually do. Join the wait list if you are just curious.
How does Sprout handle kid privacy?
Sprout is PRIVO COPPA Safe Harbor Certified. For this creator call, we are not asking you to connect a child or upload kid data.
If you built even one thing for kids, show Sprout.
Send the shape: what you made, what runs it, where it still needs you, and what you wish Sprout could run next.