Lessons From Tinkr’s First Bedtime Test
- omarikmccarthy
- May 3
- 3 min read
The core question
Tinkr’s first 7-night bedtime test is complete. The test was built around one simple question: can personalised bedtime stories reduce bedtime effort for parents?
Each night, parents answered a quick check-in about how their child was feeling, how much energy they had, and what was making bedtime harder. Tinkr then created a personalised story for that night. The parent read the story aloud, and the next morning they completed a short check-in about how bedtime went.
The goal was not just to see whether parents liked the idea. The goal was to test whether the product could help bedtime feel easier, calmer, or less effortful in a real home.
What the first cohort showed us
The first cohort of families joined, paid to take part, used the product across the week, and gave us the first real signals. Some of those signals were encouraging. Some were uncomfortable. All of them were useful. The strongest learning is this: the basic product loop works.
Parents were willing to pay to test Tinkr. They were willing to try it at bedtime. They came back across the week. The story flow worked. The read-mode experience was usable. The morning check-in loop gave us structured feedback. The product held together well enough for real families to use it in real bedtime routines. That matters.
A lot of early product tests fail before they even reach the learning stage. People do not pay. They do not start. They forget to return. The flow breaks. The experience is too clunky to generate useful feedback. That was not the main problem here.
What did not work yet
The main problem was more important. Tinkr did not yet make bedtime easier consistently enough. There were positive signs. Some nights were easier. Some children settled quickly. Some parents clearly saw value. But across the week, too many bedtime results were still about the same.
That is the difference between engagement and impact. Engagement tells us parents were willing to try the product. Impact tells us whether it actually helped.
This first test showed that Tinkr has the start of a real behaviour loop. But it also showed that the story engine needs to become much sharper before more families join the next cohort.
Why personalisation has to go deeper
That has been the biggest shift in thinking. It is not enough for Tinkr to create a personalised story. Personalisation can be quite shallow. A story can include a child’s name, age, hobbies and still not meaningfully change how bedtime feels.
The next version has to go further. It needs to understand what is actually making bedtime hard in that moment. Is the child overstimulated? Are they afraid of the dark? Are they resisting the transition? Are they asking for more time? Are they tired but unable to switch off? Does the parent need support getting from story time to sleep time? Those are different problems. They need different kinds of stories. That is where the work is now.
Why Cohort 2 is being paused
The original plan was to run several cohorts back to back. I am changing that. Rather than pushing straight into Cohort 2, I am pausing briefly to improve the story engine and learn properly from Cohort 1.
That means reviewing the bedtime data, completing parent surveys, and interviewing families from the first test to understand what really happened. I want to know what felt helpful, what did not land, what children responded to, and where the product missed the real problem. This is especially important because bedtime is not a clean laboratory test.
Some nights are disrupted. Some children are already calm. Some are too wound up for a story to help. Some parents are rushed. Some families have smooth routines already. Others are dealing with high energy, fear, resistance, illness, or general life getting in the way. The product has to work in that reality.
What comes next
That is why this first cohort was so valuable. It showed that parents are interested. It showed that the bedtime loop can work. It showed that read mode is a viable starting point. It showed that feedback can be collected without making the experience too heavy.
But it also showed that more stories do not automatically mean better outcomes. The next version of Tinkr needs to be more than personalised. It needs to be more useful.
So that is the focus now: learning from Cohort 1, improving the story engine, tightening the questions parents are asked, and making sure the next version has a better chance of helping parents feel a real difference at bedtime.
This first test did not give us a perfect result. It gave us something better for this stage. It gave us a clearer direction. Cohort 2 will open once those improvements are in place.
Join the next test
Want to help test the next version?
Comments