Why I Build

People ask founders why they build. The answers are usually polished — mission statements, market opportunity framing, the language of investor pitches.

Here is the honest answer for me: I build because I cannot not build.

That sounds dramatic. It is also accurate.

The origin of compulsion

Three weeks in, we were behind. The search was for an Associate Partner at a management consulting firm — niche domain expertise, a limited talent pool, and a commitment we had made to the client: one qualified candidate submitted every week.

We had not delivered in three weeks.

Going back through the work, nothing was obviously wrong. The outreach was going to the right people. The messaging was correct. The role was real. But responses had stopped — LinkedIn, email, phone calls that went to voicemail. No signal. The problem only became visible when we reconstructed what had happened manually, week by week, until we found the moment the pipeline had silently stopped working.

What eventually worked was video messages — short, specific, direct. Three candidates came back. The placement succeeded.

But the three weeks of pressure, the manual archaeology, the improvised pivot — none of that was inevitable. It was the cost of operating without the infrastructure that would have shown us the pattern forming before it became a crisis.

That is what I kept running into. The tools existed for sourcing. The tools existed for tracking. Nothing existed for the thing that actually mattered: knowing whether a search was working, why it was failing, and what to do about it before it collapsed.

So I started building. Not because I planned to build a software company. Because the alternative — continuing to operate without the infrastructure I knew should exist — was intolerable.

What building actually costs

Building is expensive in ways that are hard to communicate to people who haven't done it.

It costs time in a way that is qualitatively different from working for someone else. When you work for someone else, you can leave the problem at the end of the day. When you are building, the problem follows you everywhere.

It costs certainty. Those three weeks in the consulting search — doing everything correctly, getting no signal, not knowing where the problem was — that was not an anomaly. That is the permanent condition of building. You make decisions based on incomplete information and trust that the direction is right even when the destination is unclear. The difference is that the stakes are yours.

It costs ego. The market does not care about your vision. It cares about whether what you built solves a real problem at a price people will pay. Learning this — really learning it, not just knowing it — is a process of sustained humbling.

What building returns

But here is what it returns: the experience of making something that did not exist before.

Not metaphorically. Literally. The system I am building — Majhi OS — did not exist before I started building it. The searches it recovers would have failed. The hiring velocity it creates would not have existed. The insight it generates would have been lost.

That is not nothing.

Building also returns compounding. Every problem you solve makes you better at solving the next one. Every system you build teaches you what you didn't know about systems. The learning is not linear.

The deeper answer

But the deepest answer is this: I build because I believe that the gap between how things are and how things should be is closeable.

Not through wishing. Through work. Through building the systems and tools and processes that make the better version of things possible.

The world has too many people who see the gap and despair. And not enough people who see the gap and start building.

I would rather be the second kind.