Noah Labhart

Back in 2016, when I was building my own tech startup, I went on a hunt for that elusive dot com.

Looked high, looked low, and guess what I found?

Nothing.

What I did find cost me an arm and a leg.

So I did what every founder does under pressure.

Threw in extra letters, settled for the less than optimal name.

And here's what I wish someone had said to me back then.

You get the idea.

So take it from someone who learned it the hard way.

If you're building a tech startup, don't overthink it.

Secure your .tech domain today from any registrar of your choice.

Okay, so you got that that MVP built that first piece of the platform, and you're iterating quickly, I hear that and you decided to pull that first part of the of the platform, but at some point, you're getting the traction that you want, or you're getting you're heading in the direction you want.

How did you go about maturing and progressing the entire platform?

And I think, you know, it's going to be interesting to hear based on how how many problems you're solving, how you build your roadmap, how you decide what is the next most important thing to build?

So then I'm curious about team.

How did you build your team?

What do you look for in those people to indicate that they are the winning horses to join you?

This episode is sponsored by Mesmo.

If you're responsible for reliability, performance, or platform architecture, you already know the problem.

Telemetry volume is growing faster than teams can manage it.