In part one, we talked about how Stan's entrepreneurial journey began and how the idea for Multilogin came to life.

Now we turn to what happens after the first success. How many attempts does it take to find a working model? Which mistakes actually teach you something, and which ones just lead you astray? And what's the one piece of advice everyone thinking about starting a company should hear?

Looking back, what were your biggest mistakes early on, and what's the most valuable lesson you took from them?

The main conclusion I've reached over the years is that we learn far more from our successes than from our failures. That might sound strange, because conventional wisdom says the opposite.

But when a product doesn't take off, you can rarely say with any confidence what actually caused it. The market? The timing? The product itself? The team? It's usually some combination of factors.

When a product does start to work, though, everything becomes much clearer. Users show up, analytics come in, you have real data. You can talk to customers and understand why they're buying. That's why success gives you more practical knowledge about building a business than failure does.

The second big lesson: execution is everything. You have to keep testing hypotheses, launching new ideas, and moving through validation cycles quickly. Entrepreneurship is largely a numbers game. The more quality attempts you make, the better your chances of finding something that genuinely works.

How many of those cycles did Multilogin take before you hit even a minimum level of revenue?

Before Multilogin, we tested a lot of ideas. I couldn't give you an exact count anymore, but somewhere around 8 to 10 different hypotheses, definitely. Some were small experiments, others grew into fully developed services.

Multilogin itself kept evolving too. We tried different organizational models, management approaches, growth directions. NodeMaven, for instance, eventually grew out of experiments within the Multilogin ecosystem.

Speaking of NodeMaven, what decisions had the biggest impact on scaling it? Was your approach different from the first product?

In many ways we applied the same principles we'd already proven with Multilogin.

• One of the key tools was OKRs. They help the whole team understand shared goals and see their own contribution to results through concrete metrics.

• With NodeMaven we also moved to market very quickly and made marketing a core competitive advantage.

• Influencer and affiliate marketing turned out to be among the most effective channels.

  A lot of entrepreneurs underestimate this, even though it works in almost any space. Influencers don't just bring in customers; they help explain your product's value, educate users, and build trust in the brand.

Probably the most common question from aspiring founders: what advice would you give someone who wants to launch their first product? What matters most at the start — the idea, the team, or execution?

Execution, always. Launching products today is easier than it's ever been. With AI, you can quickly build prototypes, test hypotheses, and validate demand.

My advice: don't get fixated on a single idea. Launch, test, validate, and move on. The faster your hypothesis validation cycles, the sooner you'll find what the market actually needs.

I'd also recommend looking at niche markets. There's often less competition there, and a better chance of building something sustainable. The idea matters but on its own it's worth nothing without quality execution.

Let's end on a lighter note — if your life were a movie, what would it be called?

If You Win, I Win. Because real victories happen when it's not just you winning, but the people around you too.

Genre-wise, it'd be a sci-fi thriller in anime style, with elements of comedy.

Over the years, Stan has arrived at a simple conclusion: a sustainable business is rarely built around one lucky idea. Far more important is the ability to learn quickly, test hypotheses, and keep moving forward consistently.

That's how Multilogin came to be, and later NodeMaven. And it's exactly why we're always glad to meet people who ask questions, look for new solutions, and never stop learning. If that sounds like you, we'd love to connect :)