Grow a Business to $1,000 MRR

Proof required

Submit a one-paragraph problem statement and a paragraph per conversation. Each covers who it was, what they said and what you learned. Each must say how they solve the problem today. End with your decision to build or pivot, and why.

What gets checked

• Ten conversations with ten different people, not repeat talks with the same few.
• Each summary says how the person solves the problem today. Behaviour beats opinion.
• At least one pivot or scope change came from the conversations.

Common mistakes

• Asking 'would you pay for this?' People misjudge future behaviour; ask what they do today.
• Only talking to encouraging friends. They won't tell you the problem isn't real.
• Moving on before 3 people say 'I want this now'. Enthusiasm without urgency isn't validation.

Resources

What a verifier looks for

• Count the conversations. Fewer than 10 isn't complete, whatever the quality.
• Check diversity. If all 10 are the same type of person, the submitter should name that risk.
• Look for the pivot. If none, ask what changed and what stayed the same.

You'll sign in first, then come straight back here.

Proof required

Share the public URL or payment page, plus a landing page screenshot. Link a launch post in a relevant community, not just a tweet. The post must describe the real problem and solution.

What gets checked

• A public URL with a working payment step. A waitlist or PDF doesn't count.
• The launch post is findable and names the specific problem and solution.
• Clicking pay reaches a real payment step, not 'coming soon'.

Common mistakes

• Building for 3 months first. By then you're too attached to act on feedback.
• Adding a second feature before the first has users.
• Launching where your customers aren't. An accounting tool may not need Product Hunt.

Resources

What a verifier looks for

• Open the URL at review. Don't rely on screenshots.
• Click pay and confirm it reaches a real payment step.
• The launch post must be linked and public. Replies or upvotes add weight.

You'll sign in first, then come straight back here.

Proof required

Screenshot your Stripe dashboard or equivalent. Show one successful payment from an email you didn't already know. Include date, amount and status; it must say 'Succeeded', not 'Pending'. A customer quote on why they paid is optional.

What gets checked

• The payer is a real outside customer. A friend paying to help doesn't count.
• Status is 'Succeeded', not pending, refunded or disputed.
• The email isn't a personal address of someone the founder knows.

Common mistakes

• Waiting for inbound. Reach out personally to your Milestone 1 list.
• Not following up after launch. A personal email within 24 hours converts people who said 'later'.
• Underpricing out of fear. Low prices signal low value for recurring products.

Resources

What a verifier looks for

• Check the email. If it's someone the founder knows, ask whether it was organic.
• Confirm status is 'Succeeded', not refunded or disputed.
• Amount isn't the signal. A $1 payment from a stranger beats $99 from family.

You'll sign in first, then come straight back here.

Proof required

Screenshot your Stripe or ChartMogul MRR showing at least $100, with today's date visible. Or show 3+ active subscriptions with their amounts. The timestamp must match the claimed date.

What gets checked

• MRR comes from active subscriptions. One $100 purchase isn't $100 MRR.
• The figure comes from Stripe, ChartMogul or similar, not your own spreadsheet.
• At least 2 customers contribute. One customer is too fragile to count.

Common mistakes

• Counting annual plans at full value. A $360 annual plan is $30 MRR.
• Counting trials. MRR means money charged and settled.
• Ignoring failed payments. Follow up on failed cards within 24 hours.

Resources

What a verifier looks for

• The figure must come from Stripe, ChartMogul or a connected tool. Ask the source if unclear.
• Count active subscriptions. Fewer than 2 unique customers needs clarification.
• Check the screenshot date matches the claimed date.

You'll sign in first, then come straight back here.

Proof required

Submit two dated MRR screenshots 30 days apart, both showing at least $1,000. Give your monthly churn rate and how you calculated it. A high churn rate is fine; not measuring it isn't.

What gets checked

• Two screenshots 30 days apart, both at $1,000+. One screenshot doesn't meet the hold.
• Churn is disclosed with its method. High churn is accepted; hidden churn isn't.
• At least 5 distinct customers contribute. Fewer is concentration risk.

Common mistakes

• Hitting $1K for one day, then losing customers. The 30-day hold is the standard.
• Discounting heavily to reach $1K. It wrecks unit economics.
• Ignoring churn while chasing new revenue. Losing 3 per 4 gained never reaches $2K.

Resources

What a verifier looks for

• Both screenshots must be present and dated 30 days apart.
• Churn must be disclosed. If unknown, ask them to calculate it before approving.
• Fewer than 5 customers is fragile. Note it in your review, but don't block on it alone.

You'll sign in first, then come straight back here.