You’ve found a project that fits your skills, and you’re ready to apply. What you write in your application can make the difference between landing an interview or getting passed over.
Here's how to make your application stand out on Leafr.
Tip 1: Focus on clarity and relevance to the brief
One of the most common mistakes consultants make is copying content from their Leafr profile. But here's the thing: clients can already see your full profile.
What they want to know in your application is why you are right for this specific project.
Start by reading the project brief carefully. Pay close attention to the client’s goals, deliverables, and any specific pain points they mention. Then write a short, focused application that:
Shows you understand the brief and what the client is trying to achieve
Highlights relevant experience that directly connects to the project
Offers one or two examples of similar work you’ve done
Builds confidence that you can deliver value quickly and effectively
Do not repeat your full background. Instead, focus on what makes you uniquely relevant to this brief and this client.
Tip 2: Write like a person, not an AI
Clients want to work with someone they can not only trust, but can understand easily. Avoid buzzwords, stiff language, or over-polished phrases. Try to write how you talk (while keeping it professional). Clarity and confidence matter more than clever or academic phrasing.
And most importantly: while you can use AI to help you structure, or give feedback on your application, don't use AI to write the whole thing.
Trust us, people can immediately tell, and it doesn't give the impression you've put a lot of thought into the application. Use AI as a coach or mentor, not as a script-writer.
Tip 3: Apply quickly
Consultants who apply within 24 hours of a project going live are three times more likely to get an interview. Clients often start reviewing applications as they come in, and early submissions consistently perform better.
This is because there are less competitors with you at this point, so it's easier to stand out.
Check the platform or our project emails regularly, and aim to apply the same day or day after when you see a project you’re interested in.
Tip 3: Show how you would deliver the work
Strong applications don’t just say you’ve done similar things before. They also explain how you’d approach the project in front of you.
This doesn’t mean you need to outline a full plan, but giving a high-level sense of how you’d start or what tools you’d use. This is helpful because it makes the application more specific, and gives confidence in your ability to solve their problem.
For example:
“I’d begin by reviewing any existing data you’ve gathered, then map out a light reporting framework before building the dashboard.”
“My recommendation would be to use ACME Tool for this out of all the tool options you've listed, as it allows your internal team to manage updates over time.”
“I’d structure the work in two phases: discovery and delivery, with regular check-ins throughout.”
Tip 4: Stick to the scope
This one is a tricky one. It might feel tempting to offer “more” in your application: extra deliverables, broader strategy advice, or long-term ideas for the company. But in our experience, this usually does not help your chances.
Clients post projects with a clear scope in mind, and they’re often looking for someone who can deliver exactly what’s been outlined.
A note: very occasionally a client might ask for a blue-sky project, and be open to ideas, but they will state this within the project description. If they don't it's best to play it safe.
Offering additional services too early can make your application feel off-track or create the impression that you haven’t fully read the brief.
Focus your message on how you will deliver what the client asked for. Once you’ve built trust and started working, there may be space to explore more, but the application isn’t the place to do that.
Finally, here's 2 examples that illustrate our points.
Application examples
A good application
Hi, I've done a lot of extremely similar smart metering work to this project - both at large energy companies and for smaller players in the region you're operating in.
This project closely aligns with work I led at XYC Networks, where we built live data dashboards based on energy meter survey insights across the UK.
As Head of Customer and Market Research, I oversaw data collection and visualisation, focusing on metrics like fuel stacking and pricing trends. I developed Excel dashboards that updated live with ongoing survey data - similar to what you're aiming to build.
I also bring product and analytics experience. At 123 Energy Access, I used SQL and Tableau to visualise real-time data on customer usage and repayment. As a consultant, I led large-scale survey analysis projects for energy clients.
I can support delivery via Tableau, VBA-based reports, or a web-based dashboard. Based on your brief, I’d lean toward Tableau for flexibility and stakeholder access, but I’m happy to discuss the best format for your needs.
Why it’s good:
It directly matches the project brief, sticks to the scope, gives specific and relevant examples, shows measurable expertise, and offers a clear, confident solution tailored to the client’s needs.
It's clear the Consultant is directly responding to the project, and giving a richer picture of why they are a fit.
A bad application
I’ve worked in sustainability for 10 plus years.
Extensive experience producing reports - both corporate sustainability & regulatory.
Experienced in: GRI, CDP, SASB, SBTI, S&P CSA, EDCI, PMDR, EcoVadis, CSRD, CSDDD, TCFD, TNFD, NFRD, EU Taxonomy, SFDR, US SEC Climate Rules, ISSB, SEBI, BRSR, IFRS"
Why it’s bad:
It is short, vague, generic, and could be copied into any project. It just lists qualifications, and does not show any understanding of the brief or what makes the consultant a good fit.
Why aren’t I getting accepted to projects?
It can be frustrating to apply and keep getting rejected. But don't be disheartened! Most people on Leafr make 5-10 applications before they get accepted to one - bear that in mind.
Here are some common reasons consultants aren’t selected for projects:
Generic applications: If your message isn’t clearly tailored to the project brief, clients are less likely to engage.
Missing or unclear experience: If your application doesn’t clearly show the project experience or tools mentioned in the brief, clients may move on.
Weak profile: A profile that lacks detail, has formatting issues, or doesn’t match your application can raise red flags.
Irrelevant applications: Applications that are vague, or not perfectly suited to the project are unlikely to get accepted. Leafr is a high-quality, selective network, so competition (while lower than on platforms like LinkedIn) is still very high.
If you’re not sure why you weren’t selected, feel free to ask us for feedback at [email protected]. We’re happy to help you strengthen future applications.
Final tips
Read your application out loud before submitting. Keep it typo-free and natural.
Use simple, clear language. Avoid jargon unless the brief specifically uses certain certifications.
Always tailor your application. If it sounds like something you could send to any project, revise it.
Short, specific, and relevant wins every time. That is what clients are looking for, and what gets results on Leafr.