Founders & Ideas
Typical stages for founders & ideas creators
The stages below reflect what many founders & ideas creators experience. Every journey is different — use this as a general reference, not a prescription.
The Idea
Every venture begins with an observation — a problem worth solving, a gap in the market or a better way of doing something familiar. Capturing that initial idea, even roughly, gives you a starting point to refine and return to.
What this stage means
Every venture begins with an observation — a problem worth solving, a gap in the market, or a better way of doing something familiar. The clearest version of that initial insight is often the most valuable guide for everything that follows. Capturing it early gives you a starting point to return to when the complexity of building begins to obscure the original purpose.
Questions to consider
- Can you articulate the core problem this idea solves in a single sentence?
- Who specifically experiences this problem, and how often?
- Is this idea genuinely new, or a better version of something that already exists?
- Have you documented this idea at this stage?
Practical ideas
- Write the idea down in its simplest form before developing it further
- Create a Creative Record to timestamp this moment
- Talk about the problem with people who experience it — before talking about your solution
- Keep a single document that tracks how the idea evolves from this starting point
Pro tip
The most durable ventures usually begin with a problem the founder personally experienced — that kind of understanding is hard to replicate.
Reached a meaningful milestone? Create another Lyricsmit Record and continue building your Creative Record Archive.
Research
Understanding the space before building in it is one of the most valuable investments a founder can make. Research often reveals something unexpected about the problem — or the people experiencing it — that changes the direction of the work.
What this stage means
Understanding the space before building in it is one of the most valuable investments a founder can make. Research often reveals something unexpected — about the problem, the market, or the people experiencing it — that changes the direction of the work before a significant commitment of time or money has been made.
Questions to consider
- Are you researching with genuinely open questions, or confirming assumptions?
- Have you spoken directly with people who experience the problem you're solving?
- Do you understand the competitive landscape honestly?
- Have you identified the key unknowns that your research hasn't resolved?
Practical ideas
- Conduct at least ten conversations with potential users before reaching any conclusions
- Look for successful analogies in adjacent markets
- Document what surprises you during research — those moments usually matter
- Identify the one assumption your venture depends on most — and test it directly
Pro tip
The most useful research is often the conversation that challenges your assumptions rather than confirms them.
Validation
Testing the core assumption with real people before committing to a full build helps founders learn faster and build with greater confidence. The simplest version of the idea is often enough to discover what matters most.
What this stage means
Validation tests the core assumption before a full commitment of resources. The simplest version of an idea is usually enough to learn whether it has real traction — and learning early, even if the answer is no, is almost always more valuable than discovering the same thing after months of building.
Questions to consider
- Have you identified the single most important assumption to test first?
- Is the validation approach as simple as it can be while still being meaningful?
- Are you measuring genuine demand, or interest that doesn't translate into commitment?
- Have you created a record of your validation findings?
Practical ideas
- Test demand before building — a landing page, a pre-order, or a simple prototype can reveal a great deal
- Define success criteria before you start — what would a positive result look like?
- Be willing to invalidate your idea — it's valuable information
- Create a Creative Record of your validation evidence
Pro tip
Validation that confirms the idea feels satisfying but teaches little — the failures are where the real learning is.
Reached a meaningful milestone? Create another Lyricsmit Record and continue building your Creative Record Archive.
Build
Building the first version means making a series of difficult choices about what to include and what to leave out. At this stage, deciding what not to build is often as important as deciding what to build.
What this stage means
Building the first version requires making a series of difficult decisions about what to include and what to leave out. The smallest version that delivers real value to a real user is almost always the right place to start. At this stage, deciding what not to build is as important as deciding what to build.
Questions to consider
- Have you defined the minimum scope clearly, and are you staying within it?
- Is every feature you're building serving the core problem?
- Are there dependencies or technical decisions that will be difficult to reverse?
- Is there a target date for the first version that creates appropriate urgency?
Practical ideas
- Define three tiers of scope: must-have, nice-to-have, and later — build only the must-haves first
- Create a Creative Record when the first working version exists
- Show the first version to potential users as early as possible
- Build for one specific person — what would delight them?
Pro tip
The features that feel essential before you've shipped often feel unnecessary once you have real users.
Reached a meaningful milestone? Create another Lyricsmit Record and continue building your Creative Record Archive.
Feedback
Early users rarely want what you think they want. The most useful insights often come from observing how people actually use what you've built, rather than how you imagined they would.
What this stage means
Early users rarely use what you've built the way you imagined they would. The most useful insights at this stage come from observing how people actually experience the product — not just from reading their responses to it. What users do is more informative than what they say.
Questions to consider
- Are you listening to what users do as much as what they say?
- Is there a consistent pattern in the feedback, or is it scattered?
- Are you distinguishing between feedback that reflects the core problem and feedback that reflects individual preference?
- Are you acting on feedback systematically, not reactively?
Practical ideas
- Watch someone use the product without guiding them — take notes on what confuses them
- Identify the top three problems users consistently experience
- Separate feedback into: fix now, consider, and won't fix — with reasons
- Create a record of feedback that led to significant product decisions
Pro tip
The feedback that stings the most is often the feedback that matters the most.
Iterate
Iteration is the discipline of making meaningful improvements based on what you learned. A consistent cycle of shipping, observing and adjusting tends to produce better outcomes than waiting for the perfect feature.
What this stage means
Iteration is the discipline of making meaningful improvements based on what has been learned. A consistent cycle of shipping, observing, and adjusting tends to produce better outcomes than waiting for a complete solution. Each iteration is a hypothesis — the result is data.
Questions to consider
- Is each iteration addressing a specific, identified problem?
- Are you moving forward or cycling — making the same changes without real progress?
- Have you set a specific goal for each iteration?
- Is the product meaningfully better after each cycle?
Practical ideas
- Set a specific, measurable goal before each iteration
- Time-box iterations — a week of focused improvement is more productive than open-ended refinement
- Document what changed and what the result was — it builds institutional memory
- Celebrate meaningful improvements, even small ones — iteration is a long game
Pro tip
Iteration without measurement is just activity — define what better looks like before you start.
First Customer
The first customer — someone who chooses your product without being asked — is one of the most meaningful milestones in any venture. It confirms that what you've built has value beyond your own belief in it.
What this stage means
The first customer — someone who chooses your product without being asked or incentivised to do so — is one of the most meaningful milestones in any venture. It confirms, more clearly than any other signal, that what you've built has value beyond your own belief in it.
Questions to consider
- Do you understand why the first customer chose you?
- Is there a genuine relationship with this customer that can inform future development?
- What did acquiring this customer reveal about how people discover you?
- Have you documented this milestone?
Practical ideas
- Create a Creative Record to mark this milestone
- Reach out to the first customer personally — their story is valuable beyond the transaction
- Ask how they found you and what made them choose you
- Use the first customer story as a reference point for future marketing — real specifics are more persuasive than general claims
Pro tip
The first customer tells you more about your product than a hundred potential customers who only considered it.
Reached a meaningful milestone? Create another Lyricsmit Record and continue building your Creative Record Archive.
First Revenue
First revenue marks the point at which the venture becomes self-sustaining in some small way. It's a milestone worth acknowledging — the business has moved from idea to something real.
What this stage means
First revenue marks the point at which the venture becomes self-sustaining in some initial way. The number matters less than what it represents — the business has moved from idea to something that has real value to real people, proven by an exchange of money.
Questions to consider
- Do you understand what drove the first purchase?
- Is the revenue consistent with the pricing model you intended?
- What does first revenue tell you about the unit economics of the business?
- Have you acknowledged this milestone to yourself and your team?
Practical ideas
- Create a Creative Record to mark first revenue
- Analyse the first sale as thoroughly as possible — it contains a great deal of information
- Reinvest the first revenue into the thing most likely to generate the next
- Celebrate the milestone — it is significant, even if the number is small
Pro tip
First revenue is not proof of a business, but it is proof of a product — that distinction matters for what you build next.
Reached a meaningful milestone? Create another Lyricsmit Record and continue building your Creative Record Archive.
Public Launch
A public launch takes the product beyond your early circle and into the world. For many founders, a quiet early launch with a small audience provides valuable learning before a wider public announcement.
What this stage means
A public launch takes the product beyond the early circle and into the world. For many founders, a quiet early launch with a small, well-targeted audience provides more useful learning than a large public announcement — and creates a better foundation for growth.
Questions to consider
- Is the product ready for people who discover it without context?
- Have you identified the specific audience for the launch?
- Is there a clear plan for the week after the launch, not just the day itself?
- Are you prepared to respond to the response — positive or negative?
Practical ideas
- Define what a successful launch looks like before the day — what would a good result be?
- Prioritise depth over breadth in the first wave — ten engaged users are more valuable than a thousand passive ones
- Prepare a landing page that explains who the product is for and what problem it solves
- Create a Creative Record to mark the public launch
Pro tip
The quietest launches often have the most durable outcomes — the goal is users, not attention.
Reached a meaningful milestone? Create another Lyricsmit Record and continue building your Creative Record Archive.
Grow
Sustainable growth is built on a foundation of real value. Continuing to improve the product, listening to users and making it easier for people to discover what you've built tends to produce more durable results than any single growth tactic.
What this stage means
Sustainable growth is built on a foundation of real value. The most durable growth tends to come from making the product genuinely better for existing users — improvements that make the product more shareable and more worth returning to.
Questions to consider
- Are existing users returning and referring others?
- Do you understand which growth channels are producing the most valuable users?
- Is growth creating operational or product challenges that need to be resolved?
- Are you maintaining the quality of the user experience as volume increases?
Practical ideas
- Identify the one lever most likely to drive growth right now — and focus on it
- Talk to your best users about what would make them refer you more often
- Measure retention as carefully as acquisition — both matter equally
- Document what's working and why — the lessons won't always be obvious in retrospect
Pro tip
Growth that outpaces the product's ability to deliver on its promise is not growth — it's debt.
Things to Consider
- Have you reached a meaningful milestone?
- Is this a version you’d like to remember?
- Have you organised your project files?
- Are you ready for the next stage of your creative journey?
What You Could Do Next
Once this stage of the work is complete, these are some possible directions to explore. Choose what fits your project.
- Customer discovery conversations
- MVP refinement and testing
- Developing a brand identity
- Registering the business formally
- Preparing for investment conversations
- Building partnerships
- Planning a product launch
- Developing a marketing strategy
Reached another meaningful milestone? Create another Lyricsmit Record and continue building your Creative Record Archive.
Lyricsmit Compass provides general information about common creative workflows. Every project is different. Creators should make decisions appropriate to their own circumstances.