“If you are not embarrassed by the first version of your product, you’ve launched too late.” – Reid Hoffman

I’ve seen a ton of founders and even experienced product people in large organizations delay the release of an app, site, or whatever because it’s not perfect. Here’s the deal: Perfection is a mirage, a tantalizing but ultimately unreachable goal that can keep you trapped in a never-ending cycle of tweaks and refinements. Enter the phenomenon I like to call “Brain Crack” – not my original idea (of course), but one that came from the amazing Ze Frank and his profanity laced video of the same title.

Brain Crack: The Addiction to Perfection

Brain Crack is what happens when you see a product evolve, and with every improvement, you come up with new ideas to make it even better. It’s that addictive feeling of always having the perfect product just within reach, but never actually releasing it because it lives in your head in a future perfect state. You can live off the crack—the IDEA of perfection—without ever facing the reality of launching.

The Reality Check of Launching

When your product is barely ready for launch, it’s real. This is when the hard work starts. You’ll start comparing it to actual mature products in the market—products that have taken years and millions of dollars to get to their current state. You’ll want your brand new product to look as good and have as many features as something backed by 100 engineers and $50 million. But guess what? It won’t. And that’s okay.

The Myth of the Perfect Launch

People forget that you will almost never launch the right product. Even if it’s for an internal audience, a system will never survive its first encounter with end users unscathed. Products and systems pivot every single time. They are created by a few people with great ideas, doing the best they can with their brains. But when you have a lot more brains looking at something, they will always find things the system can do better or differently, or they’ll use it in ways you never thought about.

Embrace the Ugly Baby

You need to get your product to users as soon as possible so you can start working on the REAL product—the one you don’t know about yet because you haven’t let your ugly baby out of the house. You’ll never know that it’s not ugly or that it is actually a super-powered email replacement rather than a baby in the first place.

Conclusion

The key to building a successful product isn’t about getting it perfect before launch. It’s about getting it out there, letting users interact with it, and learning from their feedback. Your product will evolve in ways you could never predict, but only if you have the courage to release it into the wild, warts and all. So, take a deep breath, let go of the brain crack pipe, and launch that imperfect product. You’ll be embarrassed by the first version, but you’ll also be on your way to creating something truly amazing.

Previous ArticleNext Article
I help companies turn their technical ideas into reality.

CEO @Sourcetoad and @OnDeck

Founder of Thankscrate and Data and Sons

Author of Herding Cats and Coders

Fan of squash, whiskey, aggressive inline, and temperamental British sports cars.

Leave a Reply

Is Anyone Working on Agentic Authentication?

Everyone is building AI-powered tools, even people who shouldn’t be. Agents seem to be the next obvious (and big?) step. But these little bots need a secure way to act on behalf of users without causing chaos.

Richard Dulude at Underscore VC wrote about the lack of identity standards for AI agents in this LinkedIn article. I don’t know Richard or Underscore VC (sorry). But, he’s right, traditional authentication assumes either a human or a machine with static credentials, and that doesn’t work for AI agents that need to make decisions and take actions. Companies want accountability (and probably liability), and users need control of what their potentially psychedelic robot is doing on their behalf. This balance doesn’t exist yet.

This is probably for another blog post, but right now, everyone, including the bots, are using human interfaces as a stopgap. OpenAI’s Operator is a great example, agents pretending to be humans to interact with systems that weren’t built for them. That’s fine for now, but eventually, the human interfaces will be an afterthought. Like how “mobile-first” design took over, we’ll be doing “agent-first” design with human-accessible backups. Having a dedicated standard for agentic authentication might be a good first step in that machine-to-machine way of thinking and designing systems.

Agentic Proxy Credentials (APC): A Solution (A Term I Totally Made Up)

I made this up. It’s probably a bad term, but naming things is fun. This doesn’t exist… if you are a large battery and power supply company, don’t sue me. I’m spitballing here.

One possible fix is the “sucked out of my thumb” Agentic Proxy Credentials (APC). This would let users grant their AI agents secure, limited permissions to interact with systems while making sure the right level of oversight are in place. There are things that I wanted to do this very week, but I don’t trust my bots with my actual usernames and passwords:

Stop me talking to Airline Idiot Bots

Talking to airline chatbots is painful. Right now, they can only regurgitate FAQ answers. With an APC, my AI assistant could log into my airline account, check flights based on my loyalty status, and rebook me without you having to touch anything. This would make AI actually useful instead of just a slightly smarter help page.

Paying for small things without having to deal with entering my ACH data AGAIN

I don’t want to give an AI full access to my bank account. But I wouldn’t mind letting it handle small transactions in a controlled way. With APCs, I could grant my assistant time-limited access to approve payments or move money within strict limits. The AI does the work, I stay in control, and my bank account doesn’t mysteriously empty overnight… unless I’m Ambien shopping again.

AI Dungeon Master’s Assistant

D&D is great, but session prep is a time sink. I want an AI that logs into my D&D Beyond account, manages stat blocks, generates lore-friendly content, and even takes session notes. The AI handles the boring admin work, and you get to focus on making your players cry (or cheer, if you’re nice). Yes, serious stuff here.

How It Could Work

There are a few ways to make this happen, I think. I’m no longer allowed to do actual engineering at my own companies I founded, so this blog is my outlet. Everyone needs a hobby.

Is Someone Already Building This?

Honestly, I wouldn’t be surprised if Okta, OAuth, or OpenAI are already working on this and I’m just ranting for no reason. But if they aren’t, they should be. The pieces are all there, someone just has to put them together.

I need this, but I can’t find it. If anyone is working on it, let me know. I’m too busy trying to solve employee gifting at scale at Thankscrate, implementing AI into every existing business at Sourcetoad, and making sure passengers can watch TV and book dinner reservations in the middle of nowhere at OnDeck.