For most of my career, I didn't plan to start a company.
I liked building inside large organizations. The problems were real, the scale was real, and the constraints were real. You had to make systems work with imperfect data, shifting priorities, and decisions that actually mattered.
There is a lot to learn in those environments.
And for a long time, it was exactly where I wanted to be.
What started to change
Over time, something shifted.
Not in the work itself.
In where the most interesting part of the work was happening.
The pace of change in AI over the last few years has been different from anything I had seen before.
New capabilities emerging quickly. Entire categories of software being rethought. Problems that used to feel out of reach suddenly becoming tractable.
I had always believed in the potential of AI. That belief shaped many of my earlier choices.
But this felt different.
It wasn't incremental anymore.
And I realized I wanted to be closer to that shift.
The constraint of large systems
Inside large organizations, even very good ones, change moves differently.
Scale requires stability.
Reliability matters.
Decisions affect too many people for experimentation to be easy.
Those constraints are necessary.
But they create distance from the edge of what is changing.
I found myself wanting to experiment more, not less.
To build faster. To try things that might not work. To work directly with the new capabilities, not just design systems around them.
For a while, I thought the right move might be to join a native AI company.
That would have been a logical next step.
But it solved for proximity to the technology, not to the problem.
Starting from the problem
Around that time, I ran into a problem that made the gap more concrete.
Planning a trip.
It should have been simple.
It wasn't.
Too many options. Too many tradeoffs. Too many decisions spread across systems that didn't connect.
Every tool answered a question.
None of them stayed with the decision.
The moment anything changed, a date, a budget, who was traveling, everything reset.
I had seen this pattern before.
Not in travel.
In retail planning, supply chain, pricing, allocation.
Systems where the hard part wasn't the prediction.
It was the sequence of decisions that followed.
Once I saw travel that way, it was hard to unsee.
The decision I was already making
At that point, the options were clear.
I could stay on a well-defined path. Continue building in enterprise environments. Possibly move into a leading AI company. Work on meaningful problems within an existing system.
All of those were good options.
What I found harder to admit was that I had already made the decision months before I was willing to say it out loud.
If I really wanted to understand what this new generation of AI could do, I needed to build with it directly.
Not as a feature.
Not as a pilot.
Not as part of a roadmap.
As the core of the product.
Choosing a different environment
That meant stepping into a different kind of environment.
Less structure.
Less predictability.
More responsibility.
More freedom.
I didn't choose to build because I always wanted to be an entrepreneur.
I chose it because it was the most direct way to work on the problems I cared about, at the pace I wanted to work.
From a specific idea to a broader direction
Voyami started from a specific problem in travel.
But the underlying pattern was broader.
Real estate had the same structure: long-lived, multi-step decisions, evolving context, disconnected systems.
That led to Brickami.
And eventually to Toutami.
Not as a single product.
As a direction.
Building systems for problems that unfold over time, where the answer is only one part of the work, and what matters is what happens next.
Why this tradeoff made sense
Starting something new is not easier.
Large organizations give you scale, resources, and the ability to operate at impact.
Startups give you uncertainty, responsibility, and a lot of work that nobody sees.
But they also give you something else.
Proximity.
To the technology.
To the problem.
To the decisions that shape what gets built.
At this stage, that tradeoff felt right.
Not because the previous path stopped working.
Because I wanted to be closer to where things are still being defined.
I don't know exactly where it will lead.
But right now, building something of my own feels like the most direct way to stay close to the work I care about.