Who is affected?
The customer
Name the intended users or buyers and explain the problem in terms of their daily experience.
A place to begin
Bring the problem you care about.
We can explore the next step.
You do not need a perfect pitch. You do need a clear account of what you are trying to solve, what you have learned and why the idea matters.
Who this is for
Builders at different
stages of the journey.
An aspiring founder with a specific problem, a creator with a working product and an operator seeking a better business model may all have a reason to start a conversation. We value thoughtful people who are willing to test, learn and do the work.
Independent projects should retain a recognizable identity. We value founders who understand their customers, accept feedback and are prepared to contribute to the work ahead.
Make the first email useful
Six things that
help us understand.
A thoughtful first introduction can be short. Useful specifics matter more than a large attached deck.
What is your proposed answer?
The solution
Show what would be different for the customer. A link or short example may help more than a long slogan.
What exists today?
Current stage
Describe prototypes, tests, customer conversations, sales or operating activity honestly. “Not yet built” is a valid answer.
What have you learned?
Evidence
Separate observations from assumptions. Include concrete evidence you can share without revealing sensitive material.
What is difficult now?
The bottleneck
Identify the one or two obstacles that are stopping meaningful progress.
What would you like to explore?
The next step
State the kind of contribution you think would help, while staying open to a different approach.
What to expect
A focused introduction,
not a promise of acceptance.
Please start with non-confidential information. Do not send passwords, customer records, unpublished source code, sensitive personal information or detailed trade secrets in an unsolicited first email. If further discussion is appropriate, the parties can agree how to exchange additional materials.
Read the project journeyQuestions worth asking
For founders.
Clarity helps everyone decide whether a conversation is worth taking further.
Is an early-stage idea welcome?
Yes. Explain the problem, intended customer and a testable next step.
Should I prepare financial forecasts?
Only if relevant and grounded. A simple explanation of potential revenue and likely costs is more useful than unsupported growth projections.
Will you sign an NDA before reviewing my email?
Do not assume an NDA is in place. Send a non-confidential summary first; any confidentiality arrangement requires separate mutual agreement.
Start a conversation
Show us what matters most.
An honest introduction about the customer, the work already done and the immediate obstacle is the best start.
Introduce your idea