Crowdfunding On-the-Ground Judgment ① | Is It Okay to Launch Once the Page Is Ready? My Criteria for Delaying a Launch
機械翻訳 / Machine-translated
When a crowdfunding page is finished, it's easy to assume,
"Now we can go live."
The title is set.
The main image is done.
The body copy is complete.
The rewards are registered.
The review has been approved.
But for me,
Just because the page is finished doesn't mean I always launch it right away.
Depending on the situation, I'll say,
"Let's do a little more preparation before we go live."
Why? Because
a finished page and being ready for support to move are two different things.
What I look at before launch isn't just how polished the page is.
I ask myself: "Who will take action the moment this goes live?"
I make my launch date decision only after considering that.
This way of thinking comes from my own failure.
In 2017, I ran a crowdfunding campaign myself.
My goal was 1,000,000 yen.
The result was roughly 30,000 yen.
It wasn't that I had absolutely no connections at the time.
But I figured,
If I build the page, launch it, and spread the word on social media, the support will come.
Before launching, I hadn't thought through:
Who would be the first to back it?
Who would I reach out to directly?
How far did I want to get on day one?
I hadn't mapped any of that out.
That experience strengthened a belief that's now central to how I work:
Crowdfunding doesn't start when you launch — it starts long before.
These days, I put a great deal of weight on the preparation that happens before you press the launch button.
The first thing I check is whether there are
clear candidates for the first wave of backers.
Family.
Friends.
Existing customers.
Business partners.
Past clients.
Local companies.
People you're connected with on social media.
The candidates vary by project.
But it's not just about numbers.
What matters is whether you can see specific people — people you've already spoken to before launch, people who've shown interest, people you can contact the moment you go live.
I would rather see
100 people you can personally reach out to on launch day than 10,000 followers.
Even if the page is complete, if you can't answer
"Who are you going to tell when this goes live?"
I won't rush to launch.
The benchmark I use on the ground is:
30% of goal on launch day.
50% by day three.
100% of the first milestone within one week.
This isn't an official CAMPFIRE success metric — it's a benchmark I use based on my own experience supporting campaigns.
And it doesn't mean hitting 30% on day one means you can relax.
Ideally,
you prepare so thoroughly before launch that reaching your first milestone the moment you go live wouldn't be surprising.
That's the level of readiness I aim for.
For example, if the first milestone is 3,000,000 yen,
that means 900,000 yen on launch day.
And for that 900,000 yen, I want to know:
Who will it come from?
How many backers?
Which rewards?
Will any corporate sponsors be included?
I look for whether you can picture this in concrete terms.
If you've just set numbers and your plan is
"We'll push hard after we launch,"
then I consider you still in the preparation phase.
Even if the page looks complete, I may hold off on launching if the reward design is weak.
Who would actually choose each reward?
Which reward will be the centerpiece?
Does the price point give people a reason to back it?
For high-value rewards, who are the potential backers?
Can you deliver if demand exceeds expectations?
I go through all of this.
In particular, if someone says,
"We have ten 100,000-yen corporate sponsorship tiers, so that's 1,000,000 yen right there,"
I ask who those ten companies actually are.
If there are no specific companies in mind yet,
the numbers exist on paper, but the rewards are just placeholders.
What I care about is this:
Don't build rewards around a price point — build the price around the people.
Rewards, too, need to be connected to real backers before you go live.
A crowdfunding campaign isn't just one announcement on launch day and done.
Launch day.
A few days in.
The midpoint.
Hitting the goal.
The final week.
Each of these moments calls for communication.
So before launch, I also think through what will be shared:
The appeal of the product or service.
Behind-the-scenes development stories.
The founder's passion and vision.
Use cases.
Backer testimonials.
The rewards themselves.
Progress updates.
What will you post, and when?
At least a rough plan for this should exist before you go live.
If you find yourself asking "What should I post today?" from scratch every single time after launch, it becomes much easier for your communication to stall.
It's not just about the page itself —
do you have the material to sustain momentum throughout the campaign?
That's another part of my launch assessment.
This one is critically important.
The page is done.
But —
the person in charge is too busy to make calls.
No one can keep the social media accounts active.
There's no one to respond to inquiries.
Every internal decision takes days to get approved.
If that's the situation, you'll run into serious trouble after launch.
A crowdfunding campaign is not something you put up and wait for.
While it's live, you need to:
Keep posting.
Reply to backers.
Publish activity updates.
Reach out to companies.
Assess the situation and adjust.
That's what running a campaign actually looks like.
So I ask:
Who will be doing all of this during the campaign period?
If there's no capacity to actually run the campaign, I won't set a launch date just because the page is finished.
When I consider delaying a launch, it's not just because the page isn't perfect yet.
More often, it looks like this:
The page is finished.
But —
there are no clear candidates for first-wave backers.
day-one momentum looks weak.
corporate sponsors haven't been approached yet.
there's no plan for ongoing posts.
the team isn't in a position to execute.
That's when I'll recommend waiting.
Because keeping to a planned launch date matters far less than
launching when support is actually ready to move.
Of course, there are cases where the launch date can't be moved — for example, when it's tied to an event with a fixed date.
In those situations, I help figure out what to prioritize given those constraints.
But when there's no pressing reason to launch today, simply saying
"The page is done, so let's go live now"
is not how I think.
When a launch is pushed back, it can feel like
"We fell behind."
But I see it this way:
As long as you haven't launched yet, things can still be fixed.
It's much harder to realize after you're live:
"We had no one to reach out to first."
"The rewards weren't compelling enough."
"We never talked to any companies."
Crowdfunding has a deadline.
Once you launch, the remaining days only decrease.
So sometimes, it's better to take an extra week in preparation
in order to make those 30 days after launch stronger.
What I look at before a crowdfunding campaign goes live:
Are there clear candidates for the first wave of backers?
Can you picture what launch day will look like?
Are the rewards connected to actual people who will back them?
Is there material ready to post throughout the campaign?
Are the founders / company able to actively run the campaign during the live period?
The writing and design of the page matter too, of course.
But a campaign won't move on those alone.
When I failed in 2017, I thought of crowdfunding as
something you build, launch, and then hustle through.
Now I see it the opposite way.
Do as much as possible before launch to get support ready to move.
And the launch date is simply
the day you release that preparation into the world.
That's why, for me,
finishing the page isn't the finish line — it's just one piece of the launch preparation.
You don't launch a crowdfunding campaign because the page is done.
You launch because support is ready to move.
That's the order of operations I hold on to.
What to Prepare Before a Crowdfunding Launch | Success Begins Before You Go Live
What to Do on Crowdfunding Launch Day | What to Do for a Strong Start
If you'd like to talk about crowdfunding, please visit my profile page for more information.