Turn real founder progress, setbacks, or stalled experiments into lessons other builders can use. Share the evidence, the decisions, and what you will try next.
Founder journey templates
For a real build decision, technical experiment, or milestone with evidence to share.
Founder journey templates
For a progress check-in, including stalled work or zero revenue, with no success story required.
Why founder journey posts earn attention
A strong founder journey post turns your backstory into something readers can borrow for their own decisions. Start with a dated observation, explain what you tried, and separate what the evidence shows from what you still suspect. A stalled experiment can be as useful as a milestone. Communities such as r/startups, r/SaaS, and r/Entrepreneur are research starting points; check their current rules and permitted formats before sharing your own project.
Jump to product
Use the template page as the entry point, then move into subreddit discovery, timing, and safer execution paths.
Customization
Use a date range and a source such as an experiment log, changelog, or shareable measurement. Mark estimates and uncertainties. Do not invent a failure or breakthrough to complete the arc.
A milestone is optional. Explain a stalled build, zero revenue, or an unresolved decision with enough context for another founder to learn from it.
Explain which constraints made the lesson useful and where it might not apply. End with one focused question and a next step you can revisit.
How to use
Pick one decision or reporting period. Read the community rules first; do not use a journey story to promote where promotion is prohibited.
Record the starting point, dates, action, and observed result. If nothing changed, say so and explain what you can and cannot conclude.
Check every metric and anecdote against your records. Omit a failure or success that did not happen and remove private customer details.
Keep paragraphs short. After posting where allowed, keep a simple comment log: question, your answer, evidence to check, next action, and next update date. Separate suggestions from things you have actually tested.
Examples
Avoid
We just launched [Product] after 6 months of hard work! It's the best tool for [Feature]. Check it out!
Better
During [date range], we tried [actual action] to address [problem]. Our [evidence source] shows [observed result, including no change]. Here is the tradeoff we learned about and the question we are testing next.
This illustrative structure asks for evidence and a useful decision rather than a manufactured struggle or victory. Replace brackets only with your own facts.
Mistakes
Name the actual constraint, action, and observation. Specificity helps readers learn; invented detail undermines the story.
Keep the focus on learning. A reader asking for a link does not override community rules, and moving promotion into comments does not make it allowed.
Related reads
FAQ
Related templates
Move into adjacent template types so this page links into the broader Reddit template cluster instead of ending at a single example.
Use Reddit to research real frustrations and current workarounds. Record supporting and conflicting evidence without treating replies as a complete business validation.
Use a Reddit feedback request template to ask for specific landing-page observations, while respecting community rules and recording what to test next.
Share an open source project on Reddit with the right level of transparency, realistic positioning, and subreddit fit for developer communities.
Plan a Reddit AMA as a real expert by proving your credentials, narrowing the topic, coordinating with moderators, and showing up ready to answer hard questions.
Next step
Draft a post that resonates with other builders.