I didn't start out trying to build a company. I started out noticing patterns I couldn't stop seeing.
For most of my tech career, I've worked inside systems that are supposed to turn intent into products — enterprise loyalty, B2B platforms, consumer experiences, product strategy layers sitting between ideas and execution.
On paper, these systems are different. In practice, they feel remarkably similar. Different industries. Same shape.
There is always a stated goal — improve engagement, increase retention, simplify experience, drive value, optimize outcomes. And then there is what the system actually optimizes for — alignment, scale, conversion, internal agreement, measurable outputs.
Those two things are not always the same.
Over time, I became more interested in that gap than in any single product category. Not in a cynical way. In a technical one.
If you build enough products, you start to notice that design decisions are rarely just design decisions. They are expressions of incentives. Of constraints. Of what a system is allowed to prioritize.
I saw it in enterprise loyalty systems where “engagement” often meant navigating layers of complexity that made sense internally but not always externally. I saw it in product planning processes where the hardest part wasn't building the thing — it was translating between what users needed and what organizations were structurally able to understand. And I saw it in consumer apps too — especially in food, wellness, and lifestyle products — where the user is often asked to adopt an identity before they can get value.
Be a planner. Be a tracker. Be a cook. Be a version of yourself that fits the system.
But most people aren't trying to become a new identity at 6pm on a weekday. They're just trying to solve a moment in front of them.
Girl Dinner Mode came from that shift. Not as a conclusion. But as a small experiment around a larger question I keep running into:
What happens if you design for what people actually do, instead of what systems assume they should become?
People don't always behave like the models that are built around them. They save recipes they never make. They abandon apps that ask too much of them too early. They bounce between tools that assume more intention, more time, more energy than they currently have.
I don't think that's a failure of the user. I think it's often a mismatch between lived experience and system design.
Girl Dinner Mode is my attempt to work inside that mismatch instead of ignoring it.
I don't think of it as a finished answer. I think of it as a way to see whether the patterns I've been noticing actually hold up when you try to build directly from them.
I still don't know if it will work. I still don't know how big the problem is. But I no longer think certainty is the requirement for starting. Only attention is.