Skip to content
    A well-travelled suitcase covered in luggage tags stands on a teal background beside a bold headline.
    Grants & Development Finance

    How to vet grant applicants for execution ability, not just impact metrics.

    Robert OdhiamboFounder, FundverseNovember 5, 20268 min read
    Share:

    A polished impact model tells you what a grantee hopes to achieve, not whether they can deliver it. Here is how to test execution ability before capital leaves your account and release funds against proof.

    Most grant failures do not announce themselves at the application stage. The theory of change is coherent, the impact projections are tidy, the pitch is rehearsed. Twelve months later the money is spent, the pilot is half built and the founder is writing a new proposal to a different funder.
    The uncomfortable point is that impact metrics describe an intention. They say nothing about whether the people behind them can run an organisation under pressure. For anyone deploying non-dilutive capital, where there is no equity upside to soften a bad call, that gap is the real exposure. What follows is a sequence you can apply to each applicant, starting with the question of why they are applying at all.

    Screen for the grant tourist

    A grant tourist is a founder whose organisation exists mainly to win grants. The language shifts with each funder's priorities, the programme is always about to scale, and the proposal calendar looks more like the real business than the operations do. They are not always dishonest. Often they are responding sensibly to a system that rewards good applications.
    The distinguishing evidence sits in the revenue and funding history. Ask what share of the last two years of income came from customers, beneficiaries who paid something, or government contracts, and what share came from grants. Ask what happened to the last grant: what was promised, what was built, and what was quietly dropped. A sustainable operator can tell you that story plainly, including the parts that went wrong.
    Warning signs worth recording are consistent enough to list.
    • Several concurrent grants funding the same activity under different names
    • No plan for the organisation's second year after the grant ends
    • Staff costs that rise whenever a grant lands and fall when it ends
    • Reluctance to share management accounts, only project budgets
    • A pipeline made up entirely of other funders
    None of these disqualifies an applicant alone. Together they describe founder risk that no impact figure will offset. Once you have a view on motive, the next question is how carefully they spend.

    Test capital efficiency, not vision

    Vision is cheap to articulate and expensive to fund. Burn rate discipline is harder to fake, which is why it belongs at the centre of grant evaluation. Ask for monthly actuals for the past year, not the forward budget, and read them as a story. Did costs track revenue or milestones? Were there months where spending jumped with no visible output?
    Then look for resourcefulness. Strong operators have usually done something with very little: borrowed space, negotiated deferred payments, built a first version with volunteers, or run a pilot at a fraction of the quoted cost. Ask directly what they did the last time money ran short. The answer reveals more than any cost-per-beneficiary figure, which is easy to engineer through selective counting.
    A useful discipline is to ask the applicant to rebuild their budget at 60 per cent of the requested amount and say what they would cut and what they would protect. Those who can do it quickly understand their cost structure. Those who cannot are telling you they have not tested it. Either way, you now know what to ask in the next step, which is how to structure the money itself.

    Tie each tranche to proof

    A single upfront disbursement turns your due diligence into a one-time bet. Tranching converts it into a series of small decisions, each informed by what the grantee has actually done. This is the most effective control available in capital deployment, and it costs the applicant nothing if they are as capable as they say.
    The craft is in choosing triggers. Avoid milestones that can be met by activity alone, such as hiring a coordinator or holding a launch event. Prefer operational evidence that a third party could check: a signed contract, a bank statement showing receipts, a site in service, a number of paying users with retention beyond a first month. Where impact is the trigger, define the measurement method in the agreement, not afterwards.
    Keep the first tranche small enough to be survivable and large enough to be meaningful, often enough to reach the first verifiable milestone and not much further. Build in the right to pause or reduce a later tranche if reporting is late or the budget drifts. Funders moving towards structures like these will find the reasoning in our piece on the shift from traditional grants to blended finance and revenue-based grants.
    If you source and monitor grantees, Fundverse for investors gives you one place to review applicants and track your portfolio against the milestones you set.
    A tranche schedule is only as good as the people expected to meet it, and those people will face conditions the proposal never anticipated.

    Judge the team under stress

    Technology and model are the most visible parts of an application and the least predictive. In development settings, currency moves, regulators change their minds, a key partner withdraws and a supplier fails. What separates grantees who deliver from those who stall is how the team behaves when the plan breaks. This is founder due diligence at its most useful, and our note on founder types that should give an investor pause covers related patterns.
    Ask for specific episodes. When did the original plan fail, what did you change, and who made the decision? Listen for ownership, speed and a willingness to abandon sunk work. Be wary of founders who attribute every setback to external factors, and of those who cannot name a single pivot. Speak to former colleagues, partners and previous funders, not only the references supplied. Check also whether the team has depth: if one person holds every relationship and every signature, a single illness or dispute can end the programme.
    Finally, rehearse a crisis in the room. Describe a realistic shock, such as a three-month delay in a government approval, and ask what they would do in the first week. You are not looking for a perfect answer. You are looking for a team that reasons from cash, commitments and beneficiaries, and that tells you early when it needs to renegotiate. Write that expectation into the grant agreement as a duty to report problems promptly, and pay particular attention to how the first bad news arrives, because a grantee who raises it early is showing you the habit that protects your capital.

    Frequently asked questions

    Share:

    Topics

    grant vetting
    development finance
    impact investing
    founder due diligence
    capital deployment
    grant evaluation
    non-dilutive capital
    founder risk

    Raising or investing?

    Find the right people on the other side of the table, and run the round in one place.