When I was a teenager, my father bought me an Apple II computer.
At the time, it was a serious investment. The computer, printer, and software cost thousands of dollars. My father was a Greek immigrant who had built a manufacturing business, and he did not buy it because computers were trendy. He bought it with a very practical instruction: do something useful with it.
So I did.
At his plastics factory, engineers were spending 20 or 30 minutes at a time running calculations by hand. I started experimenting with the Apple II, taught myself enough to write a simple program, and eventually turned that same task into something that took about 30 seconds.
That was the moment I understood why technology mattered.
It was not because it was new. It was not because it was impressive on its own. It mattered because it removed real friction from real work.
That idea has stayed with me through every phase of my career: early internet marketplaces, enterprise software, energy analytics, and now AI-native company building. It is also central to how we build at Nexus3.
The tools change. The pace changes. The opportunities get bigger. But the fundamentals of building a company do not change nearly as much as people think. Durable companies tend to start in the same place: with a painful, specific problem that customers are already motivated to solve.
Put another way: build painkillers, not vitamins.
A vitamin can be smart. It can be useful. It can even be obviously good for the customer. But it is still easy to defer. When budgets tighten or priorities shift, vitamins are often the first things people push off.
A painkiller is different. A painkiller solves a problem that is urgent, expensive, and hard to ignore. It addresses something the customer already knows they need to fix.
I learned this lesson the hard way.
In energy analytics, we initially sold directly to individual businesses. The product helped companies understand their utility bills, identify savings, and make better decisions around energy spend. The value was real, but for many customers it still felt like optimization: helpful, but not always urgent.
The business changed when the customer changed.
Utilities had a much sharper problem. They needed better ways to serve large numbers of business customers, manage demand, and respond to regulatory and market pressure. For them, the same product was not a nice-to-have. It solved a real operating problem.
That shift taught me something important: company-building is not just about inventing something clever. It is about staying close enough to the market to understand where the pain really lives, then shaping the company around that pain.
This is also why I think capital should be treated as fuel, not proof.
During the dot-com era, capital was abundant. The instruction from the market was simple: raise more, spend more, grow faster, and capture the market before anyone else does. At the time, it felt rational. Everyone was moving quickly. Everyone believed the window would stay open.
Then the market turned.
IPO windows closed. Plans that looked inevitable suddenly became impossible. Companies that had been built around permanent access to capital had to face a different reality.
That experience left a mark on me. It did not make me anti-capital. Capital can be an incredibly useful tool. But it has to come in the right order. Find the pain. Prove the value. Earn the right to scale. Then use capital to accelerate what is already working.
That discipline matters even more now, because AI is creating another major platform shift.
I believe AI is on the same level as the PC, the internet, and the cloud. The long-term implication is enormous: the cost of cognition is falling. Work that once required teams of people, consultants, analysts, or coordinators can increasingly be handled by intelligent systems.
But AI does not excuse vague products. If anything, it raises the bar.
The winning companies will not be the ones that simply add AI to an existing workflow. They will be the ones that use AI to solve painful, specific, high-value problems in ways that were not possible before.
That is the conviction behind Nexus3.
We are building AI-native operating companies around real industry pain. We start with the problem. We stay close to the customer. We use technology as leverage, not decoration.
The phrase "AI-native" matters to me because it is not just about adding a chatbot or automation layer. It means rethinking how work gets done when intelligent systems can reason, coordinate, research, draft, analyze, and execute across a workflow. It means building companies where AI is not a feature. It is part of the operating model.
At the same time, the human side of company-building matters as much as ever.
My own leadership style has evolved over time. Earlier in my career, I leaned heavily on delegation. I still believe deeply in putting the right people in the right seats and giving them room to run. But I have also learned where founder judgment matters most: product, customers, and the decisions that shape the direction of the company.
The broader philosophy is servant leadership. Build around people's strengths. Give them clarity. Create a shared purpose that makes the work matter beyond the numbers.
That last part matters.
When I think about legacy, I do not think first about valuations or exits. I think about my father. At his funeral, person after person came forward with stories about how he had helped them, given them a chance, or offered a kind word when they needed it.
That is the kind of legacy that lasts.
The measure of a builder is not only what they build. It is how they build, who they build with, and what they leave behind in people.
Markets will change. Technologies will turn over. AI will reshape the cost structure of entire industries. But the fundamentals stay stubbornly human:
Solve real pain. Keep learning. Lead with character. Build something useful enough to last.
