Elizabeth Slavitt came to the project after years at McKinsey, then Khan Academy, where she led teams working on educational content and learning tools. In 2014 she was named to Forbes 30 Under 30 in Education. Shakespeers started from a simple idea: kids write more when they have a place that feels encouraging, social, and safe.
The hard part was not only building the product. Families had to trust it enough to actually use it, and Elizabeth needed a fast way to see if the idea worked with real customers. Parents needed confidence before inviting their kids in. Kids needed a reason to come back and write. And the first version had to get into production quickly, without cutting corners on safety.
Those goals can fight each other. Make the community too open and parents worry. Make it too locked down and kids stop writing. The product had to hold both.
From the start, the product had to work for four personas: first-time visitors, parents, kids, and moderators. They needed different goals and different access. Each role got its own permissions, navigation, and workflows, but they still lived on one platform so parents, kids, and moderators could interact without privacy or access getting messy.
A first-time visitor could look around, pick a plan with Stripe subscriptions, and sign up as a parent. Parents could then invite their children and keep control of who got in. Kids needed writing to feel real, so we customized an established rich text editor instead of building one ourselves. Daily prompts, a 7-day submission flow, browsing by topic, and emoji reactions gave them something to do every day. Image uploads were left out on purpose. That kept the space cleaner and lowered privacy risk for a young audience.
Moderators were there from day one too. Kids could report content, and the team got moderation alerts when something needed a look. A kids community cannot run on trust alone.
Parents stay in control while kids get into writing.
Reports and alerts, so the team does not have to watch every post.
We did not leave moderation for later. It sat in the product from the beginning. When we designed onboarding or content creation, we kept asking how kids, parents, and moderators would meet in the same place. Safety had to feel built in, not bolted on.
Existing services covered authentication, Stripe subscriptions, and serverless infrastructure. That left more room for the work that was unique to Shakespeers: the writing experience, parent confidence, role-based access for moderators, and a notification system when reports came in.
The first production release stayed small enough to ship, but still covered the path from parent signup to a child writing in a moderated space.
Families could use the platform for real: subscribe, invite kids, write, and stay in a moderated community. Moderation alerts cut down on constant manual checking. Serverless infrastructure meant less time spent running servers, so the founder could spend more time growing the product. The first version was solid enough to learn from users and add features later without starting over.
Redwood kept the app in one framework. Stripe handled subscriptions. AWS covered serverless infrastructure and moderation alerts. That mix saved time and still left room for the product to grow.
Parents could manage subscriptions. Kids could write in a moderated community. The founding team had a launch-ready platform in 3 months with room to grow from there.
OR
Write To Us At Your Own Convenience