When you can ship but can't invoice

The realization didn't hit me all at once, it built up over a week of small confirmations.

I'd been targeting a soft launch around June 1st, then a hard launch July 1st. About 4 weeks between them, tight but doable. Then Firstbase, the service I'm using to handle my US incorporation and the IRS paperwork, faxed my SS-4 to the IRS and the timeline came back: Day 21 if everything will go smoothly, ~30 business days if you don't have an SSN. After the EIN, another 1-5 business days for the business bank to verify. After that, another 1-4 weeks for Stripe Connect production verification. Suddenly, June 1st wasn't realistic anymore. Realistically - late June, maybe even early July.

Here is the frustrating part: the bottleneck isn't engineering (The retry engine/the cohort onboarding flow/the dashboard/the dunning emails). I probably could ship by June 1st. The real bottleneck is the bureaucracy involved. Without the EIN, the LLC can't open a US bank. Without the bank, Stripe Connect can't go live. Without Stripe Connect verified, the platform can't process a single charge. Nothing I can speed up by working harder.

The first move I considered was holding the July 1st hard launch and absorbing the slip into a 1-2 week soft window, which was reasonable on paper.

Then I thought about what 1-2 weeks would actually mean to me.

The founding cohort phase was supposed a special phase during the launch. Time to onboard customers by hand, watch the engine make its first steps and handle real Stripe failures (not test data), do 1:1 onboarding calls about the good, the bad, and the ugly, write Recovery Reports with actual numbers, gather permissioned testimonials, and (this is the part I usually don't say out loud) build some confidence as a first-time founder before the hard-launch traffic spike.

A 1-2 week soft window doesn't enable any of that. It becomes a sprint to launch, not a learning phase, and the cohort feels like a meaningless checkbox.

So I slipped both: Soft launch June 22-29, hard launch August 1st, with 5-6 weeks between them. Cost: about a month of pre-launch revenue I could have been earning.

There's a freedom in being pre-public for this kind of decision. No waitlist had been told a date, no tweet was pinned, no "launching in July 1st" badge to walk back. Slipping was genuinely free of reputation cost, the only audience I owed an explanation to was myself. I think that's underrated. The pressure to hit a date you announced before you knew what you were committing to is a real reason founders ship cohorts as checkboxes instead of phases. Being a few weeks "behind" with no audience is a much cheaper place to learn than being on time with an audience that wasn't ready for what you actually built.

I might be wrong about needing 5-6 weeks specifically. Either way, I'd rather find that out with a real cohort onboarded than skip the tests entirely pretending 1-2 weeks was enough.

The lesson if you're facing the same call? Being agile and planning accordingly is key to moving forward. Being a stickler to the rules of your plan usually keeps you stuck way too long.

Currently working on the banking applications.

What's the longest you've intentionally delayed a launch, and did the extra time deliver what you hoped?