What happens after you hit submit: how a Moonlabs application actually gets read

Applying to most things is a black box. You pour effort into an application, hit submit, and it vanishes into a void that answers, if it answers at all, weeks later with a templated line that tells you nothing. I have always found that disrespectful to the person on the other end, who spent time and some courage to apply. So this is the opposite of that: a straight account of exactly what happens to a Moonlabs Incubator application after you hit submit, from the moment it lands to the moment you hear back, including the parts most places would rather keep vague.

First, a human reads it. Specifically, one of us

There is no applicant tracking system scoring you on keywords. There is no junior screener filtering the pile before it reaches anyone who matters. James and I read the applications ourselves, every one, because the decision of who we spend twelve weeks building alongside is the most important one we make, and it is not a decision you can delegate to a filter.

That has a practical consequence worth knowing. We are reading as operators, not as recruiters. We are not scanning for the right credentials or the right phrases. We are looking for a spike, a single thing that is unusually real: evidence you have already built and shipped something, a customer you can name, a problem you clearly cannot stop thinking about. A competent, well-rounded application with no spike does less well with us than a rougher one with a single sharp point, because the sharp point is the thing that predicts you will actually build.

The first pass is quick, and I want to be honest about that rather than pretend every application gets a twenty-minute meditation. On a first read we are looking for a reason to lean in. Most of what makes us lean in is not polish. It is specificity, and something that reads like it came from a person who has done the thing rather than described the thing.

The ones that earn a second, slower read

An application that shows a spike gets the read it deserves, which is slow and careful and involves both of us. This is where we go looking for the substance behind the signal. If you claim you shipped something, we go and look at it. If you name a customer, we think about whether that customer is real and whether the problem is one someone pays to solve. If the idea is big, we try to find the wedge inside it, the small sharp first version, and we form a view on whether you can see that wedge too.

We are also, at this stage, reading for how you think rather than what you have concluded. A founder who has clearly wrestled with the hard parts of their own idea, who names the risks instead of hiding them, reads completely differently from one who has only written the optimistic version. Honesty about what is hard is one of the strongest positive signals in the whole process, because it is what working with you for twelve weeks will actually be like.

The conversation, which is not an interview

If the application clears the read, we talk. I call it a conversation rather than an interview on purpose, because we are not running you through a list of questions to be scored. We are doing the thing we would do in week one anyway: taking your idea seriously enough to push on it, hard, and watching what happens.

What we are actually testing in that call is not whether you have the right answers. It is how you respond when someone who has built companies pushes back on yours. Do you defend the idea reflexively, or do you take the pressure, turn it over, and come back a moment later having used it. The founders we say yes to tend to visibly improve their own idea during the conversation. That is the single most useful thing a call tells us, and you cannot really prepare for it, because it is a test of temperament rather than preparation.

You will also learn a lot about us in that call, and you are meant to. Twelve weeks alongside two people is a mutual decision, and a founder who comes out of the conversation deciding we are not right for them is a good outcome, not a failure. We would rather find that out over a coffee than in week three.

The small piece of real work

For the applications still standing after the conversation, we usually want to see a little real work, because behaviour tells us things claims cannot. This is not an unpaid project or a test designed to extract free labour. It is small and it is specific to your own idea: go and do the next thing your project needs, and show us what happened.

What this is testing is simple and hard to fake. Did you actually go and do it. How fast did you move. What did you produce when the person watching stepped back. A founder who, between two conversations, went and shipped the next small piece of their own product has told us more than any answer in an application form could. We are looking for the person who was already going to do the work whether or not we were watching, because that is exactly who they will be for twelve weeks and long after.

The decision, and the no

The decision is made by both of us, together, and it is made on fit and evidence, not on who can pay. We have said elsewhere that fee funds the programme and fit fills it, and this is where that actually bites: we turn down people who could write the cheque and we take people who cannot, on the strength of everything above.

We try hard to be fast, because a slow no is the cruelest thing an application process does. Leaving someone hanging for weeks while they reorganise their life around a maybe is not something I am willing to do to people who took us seriously enough to apply. When the answer is no, we try to give a reason that is true and specific rather than a template, because a real reason is something you can use and a template is something you delete. We do not always get this perfectly right when the volume is high, and when we fall short of it that is on us, but the intent is constant: treat the no with the same respect as the yes.

A no from us is also not a verdict on you. Often it is about timing, or fit with what the cohort needs, or a wedge that is not ready yet rather than a founder who is not good enough. Several people we said no to once came back later, sharper, and got a yes. The door is a good deal less closed than most rejection makes it feel.

Why we run it this way

All of this is more work than the filtered, automated, weeks-of-silence process that most applications go through, and we do it deliberately, for the same reason we do most of what we do. The application is the first interaction someone has with Moonlabs, and how you treat people when they have everything to gain and you have all the leverage says more about you than any values page. Reading every application ourselves, moving fast, and saying no like human beings is not a favour we do applicants. It is who we are trying to be as a company, tested at the exact moment it is easiest to cut the corner.

So if you are about to apply, know that it is not going into a void. Two people who have built companies are going to read what you wrote, look for the sharp thing in it, and if it is there, take you seriously. That is the whole promise of the process, and it is one we would rather over-deliver on than dress up.

Louis O'Connell-Bristow is a co-founder of Moonlabs, the operator-led AI incubator and academy, and previously built the home.co.uk, Homemove and homedata.co.uk stack. The Incubator reads every application personally and selects on fit and evidence, not fee. Site: moonlab.ventures.