Black and white photo of Daniel Pokorny seen from behind, sitting alone at a wooden table on a mountain overlook, looking out across a long alpine lake toward a row of snow capped peaks under a heavy overcast sky.
All Reality Checks
Founder's Reality Check · Entry 011

The Problem With Building Alone.

Daniel Pokorny · Solo founder, Atom Foundry

One of the hardest parts of building Atom Foundry alone is that there is nobody sitting next to me who can simply tell me what they think I should do.

The funny thing is that I actually do not need someone to tell me what to do.

I am the founder, and I want to make those decisions myself.

I usually make decisions very quickly, mostly based on intuition, and then I watch what happens.

If the results show me that I made the wrong decision, I change it and move forward.

What I miss sometimes is having someone who can challenge the way I think.

Someone who can look at what I am building and tell me that they see it differently.

That is much more valuable to me than someone simply telling me what to do.

The biggest decision I have made with Atom Foundry so far was probably the change in direction from where I originally started.

The company was supposed to do something completely different in the beginning.

At some point I realized that I was looking at the problem from the wrong angle.

There was no team meeting where we discussed it for three hours and voted on what to do next.

I went for a walk, thought about it, trusted my intuition and changed the direction.

That decision eventually led me to everything we are doing today.

I still think about those kinds of decisions after I make them, especially when I do not yet have enough evidence to know whether they were right or wrong.

But I have learned not to keep changing things simply because I feel uncertain.

Until I see something in the results that tells me a decision was wrong, I leave it alone and keep moving.

My wife is probably the person who challenges my thinking the most, even though she knows very little about AI or technology.

That is actually what makes her opinion so useful.

She looks at things from a completely different perspective than I do.

I tend to look at numbers, research, systems and data.

She looks at things more like a normal person who has not spent the last several hours thinking about AI commerce.

Sometimes I show her something I have written on LinkedIn and she tells me that nobody will understand what I am actually doing.

My first reaction is sometimes that she does not understand it because she is not inside the subject.

Then I look at it again and realize that she is right.

That is exactly the kind of person I need around me.

I do not need someone who agrees with everything I say.

I need someone who can look at something from the outside and tell me when it does not make sense.

There have also been situations where someone strongly disagreed with what I am researching.

I remember a conversation on LinkedIn with a respected SEO specialist who was completely convinced that AI visibility and citations were the main things that mattered when it came to AI recommendations.

He was so confident in that view that he did not even want to look at our data.

I disagreed with him, but not because I believe that I am always right.

I disagreed because we had actually measured the problem.

That distinction has become very important to me.

People can have strong opinions about where AI commerce is going, and I can have strong opinions too.

But opinions are still opinions.

When we have data that tells us something different, I want to follow the data instead of protecting my original idea.

We experienced this ourselves during one of our research projects when we tested whether characteristics such as the apparent gender of the person asking a question, age, message length and other factors might influence AI recommendations.

I expected the results to show something much more interesting.

They did not.

The numbers were not strong enough to support what I had expected to find, and I was honestly disappointed.

But that is exactly why I like research.

You do not get to decide what the answer should be.

You have to accept whatever the data gives you, even when it is not the answer you wanted.

Being alone also means that when I make a mistake, there is nobody else to blame.

My usual reaction is actually pretty simple.

I look at what happened and tell myself, Pokorny, you are an idiot, and then I try to figure out what I missed.

It sounds harsh, but I think it is better than spending time looking for someone or something else to blame.

The same thing applies when something goes well.

I know exactly how much work went into it, and I also know that the next problem is probably already waiting somewhere else.

That is just the reality of building something alone.

There is also a very good side to it.

Atom Foundry is exactly the way I want it to be.

I do not have to convince a team that something should be built in a certain way.

I do not have to wait for approval before changing direction.

When I have an idea and believe it is worth pursuing, I can simply start working on it.

That freedom is one of the things I enjoy most about being a solo founder.

The problem is that there is only one of me.

There are so many things I want to build, so many research projects I want to run and so many ideas that I would like to turn into real products that sometimes the only thing stopping me is time.

Something that could probably be done by a small team in one week might take me three weeks because I have to do everything myself.

I know what needs to be done, but I cannot be in five places at the same time.

That is becoming one of the biggest limitations of building alone.

I know that at some point I will need a team.

Not because I want someone to tell me what Atom Foundry should be, because I already have a very clear idea of what I want to build.

I want people around me who can challenge my thinking, bring perspectives that I do not have and take things that need to be done and make them happen much faster than I could do them myself.

I am not there yet, so for now I am still the entire team.

I do the research, build the systems, work on the product, write the content, handle sales, fix the bugs and spend far too much time thinking about things that probably could have been solved much faster by someone else.

But I am okay with that for now.

I do not think building alone means that you have to believe you are always right.

For me, it means accepting that the final decision is mine while still being willing to listen when someone sees something I do not.

I trust my intuition because it has served me well so far, but I also trust data enough to change my mind when the evidence tells me that I should.

That is probably the balance I am still learning.

I make the decision.

I live with the result.

I change it when necessary.

And then I keep building.

Because the hardest part of being a solo founder is not that there is nobody there to tell you what to do.

It is knowing that when the decision matters, there is nobody else who can make it for you.

From time to time, I will share a Founder's Reality Check. Not startup advice. Not growth hacks. Just honest stories from the journey of building something from nothing.

All Reality Checks · Previous entry · Next entry