the energy to keeep building

there is a moment you sometimes notice in certain founders.

it is hard to describe, but once you see it, it is unmistakable. a certain intensity in the way they talk about what they are building. not excitement exactly. something quieter. more stubborn. like the outcome is already decided in their head and the rest of the world just has not caught up yet.

i met someone like that recently.

we were talking about his company. the conversation itself was not dramatic. no big announcements. no fundraising stories. no exaggerated visions about changing the world. but there was a spark in his eyes when he talked about the work. not the idea. the work.

the long nights. the things that broke. the parts of the system that no one else noticed but kept him awake anyway. the way he described it made it clear that this was not a phase for him. this was just the direction his life had taken.

and strangely, that conversation did something to me. it reminded me why people build things in the first place.

the quiet side of ambition

entrepreneurship gets packaged in strange ways online.

a lot of it revolves around outcomes. funding rounds. growth charts. big milestones. all of those things matter, but they are not the engine that keeps people moving. the real engine is something quieter. a kind of internal stubbornness.

you wake up, and the problem you are working on still feels important. you go to sleep, and your brain is still trying to solve parts of it. not because someone told you to. not because it is fashionable. but because something about the problem feels unfinished in your head.

when i met that founder, i recognized that feeling immediately.

it was the same energy that pushed us to start building things in the first place. the same reason we ended up spending weeks obsessing over systems that most people would consider invisible.

seeing that spark in someone else had an unexpected effect. it made me want to work ten times harder. not out of competition. more like a reminder of the standard.

something i have been reading

around the same time, i have been reading leaders eat last by simon sinek, that was recommended to me by someone i know.

the book talks a lot about leadership, but underneath that it is really about trust and responsibility inside groups. why some organizations feel safe and collaborative while others slowly fall apart even when they have talented people. one idea that stayed with me is the concept of the “circle of safety”.

the basic argument is simple:

in environments where people feel protected by leadership, they stop spending energy protecting themselves. that energy then gets redirected toward solving problems, helping teammates, and building things that last. in environments without that safety, the opposite happens. people optimize for survival instead of progress.

it is interesting to think about this in the context of startups.

because early stage companies are almost the opposite of safe. everything is uncertain. the runway is limited. every decision feels consequential.

and yet the responsibility still exists.

if you are building a team, your job is not just to build products. it is to create a small pocket of stability inside chaos. a place where the people around you can focus on the work instead of constantly worrying about the ground beneath them. that idea has been sitting in my head a lot lately.

leadership in small teams

when a company is small, leadership does not look like it does in large organizations. there are no layers. no distance between decisions and consequences. if something breaks, everyone feels it immediately. in that environment, leadership becomes less about authority and more about responsibility.

responsibility for the direction. responsibility for the pace. responsibility for making sure the team’s energy goes into building instead of unnecessary friction.

the phrase “leaders eat last” is symbolic, but the underlying idea is practical. if things go wrong, the leader absorbs the pressure first. if things go well, the team benefits first.

it sounds obvious when written out. in practice it requires constant attention.

the founder’s mind

the longer i build things, the more i realize that the founder’s mind is a strange place. half of it is engineering logic. systems. tradeoffs. constraints. the practical mechanics of making something work. the other half is something closer to belief.

belief that the work matters. belief that the system you are building will eventually find its place in the world. belief that the long nights and uncertain months are part of a larger trajectory.

most days these two halves coexist quietly.

every now and then, something reminds you why the belief part exists. for me, that reminder came from a simple conversation with another founder who clearly had that same stubborn energy in him.

moving forward

after that conversation, i went back to work with a slightly different mindset. the problems were still the same. the systems we are building still need refinement. the roadmap is still long.

but something about the energy shifted.

sometimes inspiration does not come from books or speeches or dramatic events. sometimes it comes from seeing the same fire in someone else’s eyes and realizing that the spirit that started all of this is still very much alive. and when that happens, the only reasonable response is to work harder.