Loading…
Get studio updates
Get project updatesOur project updates, in your inbox.
Launches, updates, and articles from Alileus projects. Choose your language and unsubscribe whenever you like.
Alileus
Pitch a project to Alileus: write a brief that starts a useful conversation
Turn an early idea into a clear project introduction with a specific problem, a first useful outcome, evidence, and an honest request.
By Alileus editorial team4 min read
A project idea becomes easier to discuss when another person can understand who it serves, what problem it addresses, and what you want to learn next. You do not need a long presentation to make that possible. You need a clear starting point.
Alileus is a venture studio, and its public description includes working with promising ideas from founders. If you are considering introducing an idea, a practical brief can help the conversation begin with something concrete. The following structure is a writing guide, not a promise of funding, acceptance, or a particular response time.
Describe one person and one problem
Start with the person who experiences the problem. Be more specific than “everyone” or “businesses.” Explain the situation in which the difficulty appears and what that person does today.
For example, an imagined project might help a small event organiser collect information from contributors. The useful detail is the repeated work or confusion the organiser faces. A proposed feature list can come later.
Write the problem in two or three sentences that someone outside your field could understand. If you need a specialist term, explain it briefly.
Define the first useful outcome
Describe what a person should be able to accomplish with the first version. Keep the scope small enough to picture.
A useful outcome could be completing a task with fewer steps, finding relevant information, or keeping a process in one place. Explain the change in the user's experience. You do not need to promise a large platform, every possible feature, or a complete business model in the opening paragraph.
This also makes the idea easier to question constructively. Another person can ask whether that first outcome matters before discussing a much larger roadmap.
Separate evidence from assumptions
List what you have actually observed. Perhaps you have spoken with potential users, tried an existing workflow, built an early prototype, or collected examples of the problem.
Then identify what remains uncertain. If you have not spoken with users yet, say so. If a prototype demonstrates only one part of the idea, describe that boundary. Estimates should be labelled as estimates, and claims about demand should be connected to the evidence you have.
A short, honest account is more useful than impressive numbers that cannot be explained.
Explain what you can bring and what you need
Describe the work you have already done and the contribution you expect to make next. That might involve domain knowledge, design, development, access to a relevant community, or time to investigate the problem.
Then state your request. Are you looking for feedback on the problem, help narrowing the first version, or a discussion about building together? A specific request gives the reader a clearer way to assess the introduction.
If you have a demonstration or a relevant public page, include a focused link and explain what it shows. Begin with a summary that can be shared safely, and reserve sensitive material for an appropriate later discussion.
Use the project topic in Support
Before submitting, browse the Alileus projects. This helps you understand the studio's existing work and notice possible connections.
When you are ready, enter your account, then open Support with the project topic selected. Use a clear subject and organise the message into short sections. The project topic belongs in the same support flow as other account requests, so there is one place to start.
A compact outline is enough: intended user, problem, first useful outcome, evidence, current stage, your contribution, and the conversation you are asking for. Save the reference shown after submission.
Read the brief once more before sending. Can someone understand the idea without a meeting? Can they tell which statements are facts and which are still questions? If the answer is yes, you have prepared a useful introduction.
Explore the studio's projects, then start your project conversation.
Sources & further reading
The references used in this article.
Get studio updates
Get project updatesOur project updates, in your inbox.
Launches, updates, and articles from Alileus projects. Choose your language and unsubscribe whenever you like.