A rejected application is rarely a bad idea. It is almost always a poorly prepared file: a blurry problem, a team nobody understands, a market claimed but never checked. Knowing how to apply to an incubator in Morocco is therefore less about inspiration than about method. This guide walks through the five steps, in order, with what is actually expected of you at each one.
Step 1 — Assess your stage and choose the right program
This is the step almost everyone skips, and the one that costs the most. An incubator does not reject you because your project is too young: it rejects you because you applied to the wrong scheme for your stage.
Start by placing yourself honestly:
| Your stage | What you have | What you should look for |
|---|---|---|
| Idea | An intuition, an identified problem | An ideation program or a framing bootcamp |
| Prototype | A mockup, an MVP, first tests | A pre-incubation or incubation program |
| Traction | Users, sometimes revenue | An acceleration program, focused on market and funding |
Then cross that stage with the theme. The offer is segmented: some programs are generalist, others sector-specific — agriculture and environment, applied artificial intelligence, short hackathon formats. At the EIC, the range goes from ideation (startech) to sector tracks (agreentech, tech4farmers), through intensive formats (hackdays, ainnovathon, digi-hackathon) and ecosystem gatherings (demodays, kawaliss, medyouthlab).
If you are still hesitating, our comparison of EIC programs lays out the decision grid, and the programs page keeps the actual terms of each scheme up to date.
Simple rule: never apply to a program whose eligibility criteria you have not read in full. It is the cheapest filter to pass, and the most frequently ignored.
Step 2 — Build the application file
The application file is an exercise in clarity, not in length. A selection committee reads a lot of applications: yours has to be understandable in three minutes.
The blocks you will find almost every time:
- Identity — founder or team, contact details, home region, legal status if it exists.
- Problem — who suffers, from what, how often. One sentence, not a paragraph.
- Solution — what you concretely do, and how it differs from what exists.
- Stage — idea, mockup, tested prototype, first users. Be accurate: overstating your stage always backfires in the interview.
- Market — estimated size, priority segment, and above all what you checked yourself.
- Business model — who pays, how much, why.
- Team — who does what, and why these specific people are credible on this problem.
- Support needs — what you expect from the program. A precise answer beats "everything".
Submission terms, required documents and deadlines change from one program to another and from one edition to the next. Do not rely on a blog post for that, including this one: check the program page on /en/programs.
Step 3 — The deck and the pitch
The deck is not the application file turned into pictures. It is a standalone, short object that must stand up without you. Ten slides are enough: problem, solution, demo, market, competition, business model, traction, team, roadmap, ask.
Three principles that make the difference:
- One idea per slide. If the slide needs explaining, it has failed.
- Evidence, not adjectives. "Innovative" says nothing; "23 farmers interviewed, 18 face this problem every season" says everything.
- An explicit ask. What you want from the program, in one line.
Keep the deck to about ten slides and rehearse it out loud at least once. The format matters far less than your ability to defend every claim on it.
Step 4 — The jury interview
If your file passes, you present to a committee — often a mix of domain experts, ecosystem representatives and partners. The usual format: a short presentation, then questions. The questions are what decide.
Prepare for the ones that come up every time:
- Why this problem, and why you?
- What have you tested, and what did you learn that changed your mind?
- What does acquiring a customer cost, and how do you know?
- What kills you within 12 months?
- What happens if you are not selected?
Two reflexes in the room: answer the question that was asked (not the one you would have preferred), and say "I don't know, here is how I plan to find out" rather than improvising a number. Juries spot improvisation immediately, and it costs more than admitted ignorance.
Step 5 — After the answer
If you are selected: the real work starts. In the first week, set three measurable goals for the duration of the program, identify the two mentors you actually need, and block the time in your calendar. Support you merely endure produces nothing.
If you are rejected: ask for feedback, write down the objections, and fix the most recurring one before any new application. In most cases, what is missing is market evidence — not technology. Many selected projects got in on their second attempt, with the same idea and a different level of preparation.
The mistakes that get you rejected
- The problem told as a solution. "We are building an app" is not a problem.
- A market claimed, never verified. Quoting a global study does not replace ten conversations with Moroccan users.
- A team without roles. Three "versatile" cofounders make a jury nervous.
- The wrong program. Applying for incubation with an untested idea, or to a hackathon with an already profitable company.
- An incomplete or late file. An incomplete file is often set aside before it is even read in depth.
- Mishandled confidentiality. Flag what is confidential inside the file rather than hiding everything: an unreadable project cannot be evaluated.
Checklist before you submit
- My stage is identified and matches the program I am targeting.
- I have read the full eligibility criteria on the program page.
- My problem fits in one sentence a non-specialist can understand.
- I have at least one piece of field evidence (interviews, tests, pre-orders).
- My deck is 10 slides and reads without commentary.
- Team roles are explicit.
- My support request is specific.
- Every requested document is attached and legible.
Morocco's support landscape has grown denser: at the EIC alone, that means 175 projects supported and 46 startups created since 2019. In other words, the seats exist — they go to the prepared applications.
Next step: identify the program matching your stage on the programs page, then read the EIC incubator guide to understand how the support works.
