I built a lot this month, and honestly I've been unsure why. So I asked eight AIs to look at all of it — and not one of them agreed. Now I'm asking you, because you actually know me. Go through it however you like, and at the end, tell me what you really see. I'll read every word.
"Hey, I'm Kunal. This past month, I built more than I ever have — nineteen products, millions of lines of code — and honestly, I couldn't tell you why. So I asked a few people who know me to look at all of it, and tell me what they saw. None of them agreed. What you're about to step into is a map of me, in their words. Take your time with it. And at the end, tell me — which version of me did you actually meet?"
Then scroll — eight AIs looked at my last month of activity, and not one of them could agree on why.
And don't just read — I want you to weigh in as you go. Rate, choose, react. Your answers build a note you can send back to me at the end.
Line them up and they're not a product line. They're a map of a life — every part of him, rebuilt in software. The numbers establish scale. They cannot establish motive.
Thirty-one days, and the pulse rarely dropped — the spike is 1,008 commits in a single day. Read it as capacity and attention, not as a measure of value or completion.
The real mystery is not “how did one person build so much?”
It is “what was all that building trying to make possible?”
Most of these names won't mean much without context. They're ordered by where his time actually went this past month — tap any to open it.
Builder mediaAn editorial and tooling home for people building with AI.
MediaA daily five-point AI-news briefing and media engine, with a large, real audience.
Personal OSA daily operating system for memory, reading, tasks, and assistant workflows.
FinanceAn AI finance and research terminal — portfolios, markets, and analysis.
ReflectionA calm app for annual words, monthly intentions, and journaling toward what matters.
HealthA personal AI longevity tracker — labs, sleep, exercise, nutrition, and wellness.
StudioKunal's blogs, books and bots — what he is putting out there in the world.
MemoriesA digital time capsule for collecting and preserving the moments that matter.
CommunityA social app for gathering friends around real-life brunches and dinners.
The harness behind everything above — a fleet of AI workers that ships software end to end. Not a product anyone visits; the AI system that builds the products, aimed at an autonomous organisation run by one person.
He meets a complex system, becomes fascinated, and builds a better map. Advertising became Nova. Markets became Pulse. Information became Pivot. Memory became Noto. Reflection became Circa. Health became Healthspan. Giving became Spark. Even relationships, travel, and rituals become objects of intentional design.
He has already reached the version of success that makes “what should I do?” harder, not easier. Survival no longer supplies the answer. A title and operating role no longer concentrate his attention by default.
AI arrives at exactly this moment, offering something seductive: the return of scale without the return of bureaucracy.
At 21, he built an institution. Now he may be trying to build an institution that fits inside one person.
His AI agent harness — a fleet of AI workers that ships software end to end, aimed at one thing: an autonomous organisation run by one person.
A better way to build software with agents.
Institutional-scale agency without dependence on a large organization.
Each reading is placed by what it believes the building is for. Tap a star to step inside it — then mark how true it rings to the Kunal you know. Your ratings shape the perspective you'll send at the end.
They agree completely on the facts. On what the facts mean, they don't agree at all. Tap the side you come down on.
For each tension, drag the green marker to where you think he is today, and the orange marker to where you think he needs to move. The starting positions are one interpretation, not the answer.
Six theories about what really drives him. Each one has a case and a pushback — two sides. Tap the side that rings true to you.
Perhaps the systems guard against regret: missed chances, forgotten ideas, avoidable decline, neglected relationships, time spent without intention.
Counter-read: This may simply be wisdom. He takes compounding seriously because he's seen how decisions shape decades.
Capability may be doing emotional work achievement can't finish — settling worth, significance, the fear of becoming ordinary after an extraordinary first act.
Counter-read: Mastery can be intrinsically satisfying. Not every ambition hides a wound.
After a 15-year company, AI offers a way to prove his ability wasn't tied to one era, one industry, one team.
Counter-read: Reinvention is exactly what a serious builder does when the substrate changes.
The portfolio may keep investor, author, founder, philosopher, philanthropist, and builder alive as simultaneous possibilities.
Counter-read: A portfolio is rational when build costs collapse. Variety need not be avoidance.
AI-mediated sovereignty can remove the mess of employees, waiting, persuasion, and compromise.
Counter-read: Sensible leverage after years of organizational responsibility. Independence can make room for better relationships, not replace them.
Motion can postpone the naked question that remains once money, status, and freedom no longer explain the drive.
Counter-read: Building may be how he discovers desire, not how he avoids it. Action reveals what contemplation can't.
Kunal told his AIs that despite building all of this, he feels bored.
His sharpest hours go in before the world wakes up. Whatever the boredom is, it isn't laziness.
Pick the two reasons you think ring most true.
Once the architecture is visible and feasibility is proven, the stimulating part is over. Implementation becomes transcription.
Polish, support, distribution, reliability, repetition aren't beneath him. They simply reward patience more than insight.
In most projects he's builder, user, operator, and judge. Only another person can introduce desires he didn't author. Pivot and Vibin are the exception.
His capability may have outrun the scale of his questions. He may need a problem he can't already see himself solving, with stakes beyond his own interest.
The nervous system can rename fear as disinterest. A project can turn boring exactly when it's ready to be judged or depended on.
Premature focus can destroy the value of exploration. The right answer may be better portfolio rules, not forced monogamy with one product.
He may be building a second self — something with the output of a whole company, kept at the freedom of one person.
The actual apps — for memory, health, money, media, and reflection.
How he builds — AI does the work, he steers the ideas.
What he gets from it — control, options, and a way to not fall behind himself.
The deepest why — making a short life feel deliberately led.
AI can help him make almost anything.
It still can't tell him what's worth making.
Choosing one thing means letting the others go. He's been building faster than he's been choosing — more ability than reasons to use it.
Seven directions he could take next. Read each — then pick your top three. Which feel most right for him? 0 / 3 selected
Let one real thing reach one real person. Not for praise — only someone outside his own head can truly surprise him, and that is the one thing he keeps avoiding.
Stop asking every tool to become a startup. Build one private, integrated intelligence system that improves his own memory, health, investing, reflection, and creative work.
Agency, coherence, privacy, institutional capability without bureaucracy.
External scale and a conventional company's validation. Some products stay personally valuable but commercially small.
Pick three daily loops across the suite; measure whether they improve decisions, energy, or time.
Find a problem still larger than his capability that matters to people with real stakes. Build less from curiosity, more from obligation to a mission.
Difficulty, consequence, service, a problem that can genuinely surprise or defeat him.
Freedom to switch when fascination fades. A worthy problem may be slow, political, human, and resistant to elegant systems.
Interview ten people living inside one serious problem; commit to an outcome before choosing a product.
Accept that many bets are the strategy. Replace guilt about focus with explicit stages, maintenance budgets, traction metrics, and unemotional kill rules.
Breadth, experimentation, option value, the economics of cheap bets.
The simplicity of one mission. Portfolio discipline must be harsher than founder intuition.
Give every project a stage and a proof metric; nothing advances without it; archive the rest.
Choose one commercial product, build a real team, and accept that depth, customers, and organizational life are the price of consequence.
Focus, market feedback, external stakes, another enduring institution.
Sovereignty, variety, some of the freedom earned by leaving daily CEO life.
Pick the product with the strongest lived advantage; recruit one operator who can disagree with him.
Lean into Vibin and Pivot — the builder-media and daily-news engines already pulling real audiences. Make the product taste and a trusted relationship with those readers; let the software serve the editorial mission.
Reach, thought leadership, recurring external feedback, distribution that feeds every other product.
The fantasy that infrastructure alone is the work. Publishing cadence becomes non-negotiable.
Ship one unmistakably Kunal-led format whose audience response can be measured.
Declare the building practice an artistic and intellectual lab. Stop pretending every experiment needs product-market fit; publish the discoveries and let the body of work be the output.
Curiosity, aliveness, mastery, honesty about what he may enjoy most.
The identity of founder building toward a conventional outcome. Work must be curated into insight, not merely accumulated.
Build freely, but every experiment must yield an essay, a method, an artwork, or a clear decision.
Let relationships, marriage, future family, health, friendship, travel, and presence become the central project. Software returns to its proper role: support, not meaning.
Embodiment, intimacy, enoughness, the chance the next chapter is lived rather than built.
The stimulation of constant creation and the comfort of measurable progress. It asks him to trust a life he can't fully instrument.
Cap building hours, remove output metrics, and watch whether life feels diminished, relieved, or newly available.
You've seen what eight AIs made of Kunal. Now it's your turn — tell him what you actually see. He reads every response.
You've seen a map of everything he built. The territory is which self he actually becomes next — and that's not a thing he has to settle alone.
What deserves this much of him?
What is the AI for?
And what becomes possible if he stops asking capability to answer a question only choice, relationship, and lived consequence can answer?