Meadow Arc At the start, the work was very simple.
I needed Caligo Relief to feel like something you could actually speak to, not just something you filled in.
A lot of the earliest progress was about getting the first loop to work: onboarding, early chat, a sense that the product could take in a little context and give something back that felt connected to the day instead of generic. That may sound small, but it changed the shape of the whole project.
A product like this does not become useful because it has many features. It becomes useful when the first interaction makes sense.
The first interaction had to feel believable
The early bar was not polish. It was believability.
Could the product take in a little context, respond in a way that felt connected to the day, and make the next step feel slightly clearer instead of more abstract?
That question shaped more of the first version than any feature list did.
Responsiveness matters more than cleverness
The harder part was not adding more surface area. It was getting the basics to stop feeling brittle. Replies had to feel less awkward. Delays had to feel less visible. The whole thing needed to feel a little more steady, especially in the moments when someone is already tired before they open the app.
That early phase taught me something I keep coming back to: when the problem touches health or daily capacity, responsiveness matters more than cleverness.
People do not need a system that sounds advanced. They need something that meets them without adding drag.
Early usefulness comes from holding a thread
So the first real milestone was not a launch-shaped one. It was simpler than that.
It was the point where the product started to answer back in a way that felt believable. And for now, that still feels like the right place to have started.