Should I launch a product or event before I have a full plan?

"Always launch things before you make the full plans."

I mean that literally. I've done a lot of making the full plans and then realizing I wasted my time.

For an AI 101 event for local business owners, I built a polished registration site: hero section, why-attend cards, and a pricing page that looks like a million-dollar business would use it. I didn't have a venue. The site said "venue upon registration," and I'd deal with that if people signed up.

What do I build first, and what do I leave open?

• Build what creates the decision. The page, the offer, the price.
• Leave costly commitments open. The venue, in that case.
• Commit money only after signups.

The exception: anything other work depends on. If a build is a foundation for other things, it gets a brief and acceptance criteria first.

How much does a launch-first test cost?

Less than people think. When we talked about a new B2B newsletter, my take was to just launch it. Worst case, it doesn't work and we lost $300 or $500. If it works, that changes everything. Buy the domains right away, since they're about $10.

About 80% of what we try fails. That's exactly why we have to keep trying things quickly and keep the ones that work.

For a new newsletter niche, my test plan looks like this:

1. Set up the basics. A landing page, a few issues written, and the signup survey ready.
2. Put about $1,000 into Meta ads over one to two weeks. Watch what subscribers cost and how many people fill out the survey.
3. Compare it to what you expected. I expect under $1 a subscriber, hopefully 50 cents or less. Way worse means back to the drawing board. Way better changes the plan.
4. Try to break even. We don't want to be spending our own money, so the goal is to make some of it back quickly.

Why launch before pitching partners or investors?

An idea is hard for people to grasp. A working product isn't. For one niche newsletter, my plan was to run it ourselves for a month or two and bail if it didn't work. If it got 600 or 1,000 people with high engagement, we wouldn't be taking an idea to bigger partners anymore. We'd be taking them a working concept.

Same with selling. One December, a few hours of real calls with advertisers taught us more about our advertising plan than two weeks of planning would have. Taking action beats sitting around figuring out a plan.

Do I need the local person before I launch a newsletter?

Not at the start. I've launched this model about 30 times, and a brand takes about a day to set up. We launched a set of town newsletters with no local person in all but one, and their numbers were almost as good as my home newsletter, where my wife customizes everything. One VA writes six of them, my manager reviews them, and I usually review them too.

Long term, you do need that person: a local face for content, social, advertisers and events. You can find them after you launch.

Does it need to be perfect first?

No. Make sure it's good enough and everything works, then change it later. With 300 subscribers, imperfection barely matters. If your welcome page says every Wednesday and you send on Thursdays, nobody's going to notice. It matters more as the audience grows.

The same goes for a product site. When we launched the site for my software, the people finding it at first were the ones I was messaging directly. We needed it live so we could talk about it. A good enough demo of a newsletter made in three or four minutes beat a perfect one, because we could fix it in a week or two.

In a July 2026 campaign review I applied a "good enough to learn" rule: launch a $10-a-day follower test despite minor imperfections, while keeping real product defects listed as separate blockers. Polish shouldn't become a substitute for learning. A first version still has to clear the bar, though: I treat 7 out of 10 as minimum competent.

Why do some launch-first experiments fail?

Because nobody sees them. A year to eighteen months before that AI event, I was serious about the same idea and started a Facebook page. It went nowhere. I had no audience because I had no local newsletter, and I didn't know how to run Facebook ads. With no way to get the word out, I stopped.

Launching first only gives you a signal if you can put the launch in front of people.

Isn't jumping in early a mistake?

It can be, and it's burned me. One of my problems as an entrepreneur type is jumping in way too early, before it's there. In September 2025 I was in a holding pattern: massive potential, but nothing proven yet. My plan was to prove the model with partners before scaling.

My earlier software company failed partly because we went too big. Start small and make it viable short term before you chase the grand vision.

The way I square it: launching a page is cheap, and committing staff and money before the idea is proven isn't. Launch early. Commit late.

What if I don't have all the answers?

Ready, fire, aim. Pursue the hard thing and figure it out later. We know we're on to something; we just don't know exactly what it is yet. And when you pitch someone, don't show up with ideas. Build a template or a simple version so they can see it. That's how I pitch publishers on my newsletter system.

Treat all of this as a guide, not gospel. Somebody is doing the opposite of what I'm saying and crushing it.