What Am I Building?

People ask founders what they are building, and founders give answers. The answers are usually accurate as far as they go — the product, the market, the problem being solved — but they are not quite the full answer.

The full answer is harder. It requires saying something about what you believe and why, not just what you are making.

The easy answer and the honest one

The easy answer to "what are you building?" is a description of the product. I am building a platform for X. A system that does Y. Infrastructure for Z. This answer is useful for pitches and introductions. It is not the answer you need to have for yourself.

The honest answer is closer to: what kind of change am I trying to make real, and why does that change matter to me specifically?

This version of the answer matters because it is what determines what you do when the easy path diverges from the right one. When a customer wants you to build something that would grow revenue but dilute your focus. When a potential partner offers distribution in exchange for compromising what the product is. When a competitor is succeeding with a version of your idea that you believe is ultimately worse for users. In all of these moments, the product description does not tell you what to do. The honest answer does — and for me, that honest answer is explored in what I am actually building.

What I am building and why

I am building two things, and they are connected by a single thesis.

The first is Majhi Group — a retained executive search firm. The thesis here is specific: most organizations hire senior leaders using processes designed for much lower-stakes decisions, and the results reflect that mismatch. The consequences of a bad executive hire are not just expensive. They are propagating — they affect the teams those leaders build, the strategy those leaders set, the culture those leaders model. Getting executive hiring right is worth significant investment.

The second is Majhi OS — infrastructure for hiring operations. The thesis here is that the problems with hiring are not primarily about finding candidates. They are about the absence of observability and execution infrastructure that would tell you, in real time, whether your hiring system is working or failing. Most organizations know they have hiring problems. Very few have the instrumentation to diagnose those problems systematically.

Both of these are connected to something bigger: the belief that the hiring system, as currently constituted, produces outcomes that are worse than they need to be — for organizations and for the individuals who are evaluated, advanced, or excluded by those outcomes. Broken hiring blocks opportunity. It blocks the wrong people from advancing and promotes the wrong people. The consequences are not contained to the organization.

What building from this place feels like

Building from a thesis — from genuine belief that the problem matters — feels different from building from market opportunity alone.

It feels more sustainable in the difficult periods, because the difficulty is in service of something you care about, not just something you invested in. It feels more focused, because the question "does this move us closer to solving the actual problem?" is a useful filter that market opportunity framing does not provide. It feels more honest in conversations with customers, because you are not performing enthusiasm — you genuinely believe that what you are building matters.

It also creates its own risks. Conviction can shade into stubbornness. Belief in the importance of the problem can make it harder to update on evidence that a particular approach to solving it is not working. The same thing that keeps you going in the hard periods can make it harder to pivot when pivoting is right.

The discipline is in holding both: staying committed to the why while remaining genuinely open about the what. The problem is stable. The solution is a hypothesis.

The question worth asking

If you are building something and you find yourself unable to explain it without using the product as the answer — if "what are you building?" only has a technical response — it is worth spending time on the deeper version of the question.

Not what. Why. And for whom. And what changes in the world if you succeed.

The answers will make the building harder in some ways and easier in almost every way that matters.