Day 35 of building MeetDone.
One signup objection I keep coming back to is:
"Wanted to see the output first."
I think that is one of the fairest objections a user can give.
If the whole promise of the product is the transformation,
asking for signup before showing the result might be backwards.
With MeetDone, the promise is simple:
messy meeting notes in,
send-ready follow-up email out.
If I ask for an account before someone can see that output,
I am asking them to trust 3 things up front:
- that the result will be good
- that setup is worth it
- that this is different from every other AI tool they have already ignored
That is a lot of trust before proof.
So I think there are really 3 options here:
1. Keep signup first
2. Show a sample output first
3. Show one real output first, then ask for signup
Right now I think option 3 is the most interesting.
A sample shows the category.
A real output shows the value.
And if the product is easiest to understand by seeing what it does,
moving the proof later in the flow may just be bad onboarding.
I think this applies to a lot of products, not just MeetDone.
Sometimes the best onboarding fix is not better copy.
It is showing the result earlier.
My working rule now is:
if the product promise is output quality,
show the output before you ask for commitment.
Would you gate the first result, or the second one?