How to Write a Grant Proposal for Mobile Health Technology

Getting a mobile health technology project funded starts with a grant proposal that funders actually want to read. That sounds obvious, but most mHealth proposals fail for predictable reasons: vague problem statements, missing sustainability plans, or budgets that don't account for what fieldwork in low-resource settings actually costs. The grant proposal for mobile health technology projects has its own rhythm, and it differs from standard biomedical research applications in ways that catch first-time applicants off guard.

"Non-communicable diseases now account for 74% of global deaths, with more than three-quarters occurring in low- and middle-income countries, yet less than 2% of global health funding targets NCD prevention in these regions." — WHO Global NCD Report, 2024

Why mHealth proposals get rejected

Before getting into structure, it is worth understanding what goes wrong. Dr. Alain Labrique at Johns Hopkins Bloomberg School of Public Health, who has reviewed hundreds of mHealth grant applications for NIH and WHO panels, has noted that the most common failure is proposing technology without a clear health outcome. Reviewers want to see a disease burden, an intervention mapped to that burden, and a measurable change. A proposal that leads with "we built an app" instead of "maternal mortality in rural Uganda is X, and here is how we intend to reduce it" will land in the reject pile.

The NIH's Fogarty International Center runs the PAR-25-242 funding mechanism specifically for mobile health research in low- and middle-income countries. Their eligibility requirements spell out something that many applicants miss: the proposal must involve researchers from the target LMIC country as co-investigators, not just as field staff. This is not optional. Applications without meaningful LMIC research partnerships do not advance past initial review.

A 2024 analysis published in BMJ Global Health by Araya et al. found that of 412 mHealth grant applications reviewed across three major funders, 68% were rejected at the first stage. The top three reasons: insufficient evidence of local partnerships, unclear scalability pathway, and budgets that omitted maintenance and training costs.

The anatomy of an mHealth grant proposal

Every funder has their own template, but the core sections are consistent. Here is what each section needs to accomplish for a mobile health technology project specifically.

Problem statement and needs assessment

This is where most proposals either win or lose. The problem statement should do two things: quantify the health burden with current data, and explain why existing interventions are failing or absent. If you are proposing smartphone-based vital sign screening for community health workers in Sub-Saharan Africa, you need to cite the actual CHW-to-population ratio in your target region, the distance to the nearest clinic, and the specific conditions going undetected.

Dr. Patricia Mechael, who co-founded the mHealth Alliance and now advises WHO on digital health strategy, has argued that the strongest proposals frame mobile technology as filling a specific gap in an existing health system, not replacing it. A phone-based screening tool is not a hospital. It is a way to get information into the hands of someone who can act on it.

Technical approach and innovation

Funders like the Gates Foundation, NIH Fogarty, and Grand Challenges Canada want to see that your technology works or has strong preliminary evidence. This means pilot data. If you have run a 50-person feasibility study showing that community health workers could use your tool with 90 minutes of training and capture usable data on 85% of encounters, say so. Numbers from a small pilot carry more weight than theoretical descriptions of how the technology should work.

For camera-based health assessment tools, including rPPG-based contactless vital sign measurement, the technical section should address image quality in real-world conditions. Low lighting, movement artifacts, varying skin tones, limited bandwidth for data transmission. Reviewers who know the field will ask about these. Address them before they do.

Evaluation and outcome measures

The mHealth Evidence Reporting and Assessment (mERA) checklist, developed by Agarwal et al. and published in BMJ in 2016, remains the standard framework for mHealth intervention reporting. Grant reviewers increasingly expect proposals to reference mERA. The checklist includes 16 items covering infrastructure, technology platform, interoperability, content, usability testing, user feedback, and health outcomes.

Your primary outcome should be a health metric, not a technology metric. "Number of app downloads" is not an outcome. "Percentage of hypertensive individuals identified and referred to treatment within 30 days" is.

Funding sources for mobile health technology projects

The funding landscape shifted in 2025 and 2026. USAID's global health budget faced significant cuts under the current administration, creating uncertainty for organizations that previously relied on PEPFAR and USAID bilateral funding. Meanwhile, the Gates Foundation announced a $200 billion commitment to accelerate global health progress through 2045, with specific emphasis on AI and digital health innovation.

Funder	Mechanism	Typical award	Duration	Key requirement
NIH Fogarty International Center	PAR-25-242 (R21/R33)	$275K (R21) / $500K (R33)	2-5 years	LMIC co-investigator required
Gates Foundation	Grand Challenges	$100K-$1M+	1-3 years	Proof of concept data
Grand Challenges Canada	Global Health Innovation	$100K-$250K seed	12-24 months	Canadian or LMIC institution lead
Wellcome Trust	Digital Health	£50K-£500K	1-3 years	Open access data sharing plan
ELMA Philanthropies	Health systems	Varies	Project-based	Focus on Sub-Saharan Africa
Global Fund	Country proposals	Varies by country	3-year cycles	Ministry of Health endorsement
IDRC Canada	Digital health research	CAD $100K-$500K	2-4 years	Gender analysis required

The Mobile Healthcare Association maintains a regularly updated directory of smaller grants, including foundations offering $10,000 to $50,000 for pilot projects. These smaller awards are often easier to win and provide the preliminary data that larger funders want to see.

How funders evaluate mHealth proposals differently

Not all reviewers think the same way. NIH panels score on innovation, approach, significance, investigators, and environment using a 1-9 scale. The Gates Foundation looks for "catalytic" potential and often favors unconventional approaches. Government bilateral funders like the former USAID programs weighted country ownership and ministry of health alignment heavily.

Understanding the funder's theory of change matters more than perfecting your formatting. A proposal to Wellcome Trust should emphasize research rigor and open science. The same project pitched to Grand Challenges Canada should emphasize scalability and commercial sustainability.

Budgeting mistakes that kill mHealth proposals

The budget is where experienced reviewers can immediately tell whether an applicant has done fieldwork before.

Common mistakes:

• Budgeting for smartphones but not for cases, screen protectors, or replacement devices. In field conditions, roughly 15-20% of devices need replacement annually.
• Omitting connectivity costs. Mobile data is not free in most African countries, and CHWs cannot be expected to pay for it. A project covering 200 CHWs in rural Uganda might spend $3,000-$5,000 annually on data bundles alone.
• Forgetting the cost of training refreshers. Initial training is usually budgeted. The three-month refresher that prevents data quality from degrading is not.
• Underestimating travel. Supervising field deployments means someone needs to physically visit sites. Fuel costs, vehicle maintenance, and per diem for field supervisors add up fast.

Dr. Hamish Fraser at Brown University, who has led mHealth deployments across multiple African countries, has written that the most realistic mHealth budgets allocate 20-30% of total costs to implementation support, including training, supervision, and troubleshooting. Projects that put 80% of funds into technology development and 20% into everything else almost always underperform.

Sample budget structure for a 2-year mHealth pilot

Category	Year 1	Year 2	Notes
Personnel (PI, co-PI, field coordinator)	$85,000	$87,000	Include LMIC researcher salary
Technology (devices, software, hosting)	$25,000	$8,000	Higher Year 1 for procurement
Connectivity (data plans, cloud services)	$6,000	$6,000	200 CHWs at ~$2.50/month
Training (initial + refreshers)	$12,000	$8,000	3 training events per year
Field operations (travel, supervision)	$15,000	$15,000	Monthly site visits
Evaluation and data analysis	$10,000	$15,000	Higher Year 2 for analysis
Indirect costs	$22,000	$22,000	Varies by institution
Total	$175,000	$161,000	$336,000 over 2 years

Building the local partnership section

This is the section that separates funded proposals from rejected ones. Every major global health funder now requires evidence of meaningful local engagement, and reviewers can tell the difference between a genuine partnership and a token letter of support.

What reviewers look for:

• Named co-investigators at LMIC institutions with defined roles, not just "will assist with data collection"
• Letters of support from district or national health authorities that reference specific activities, not generic endorsements
• A capacity-building component showing how the project strengthens local research infrastructure
• A data ownership and governance plan that gives the LMIC institution rights to the data

The African Population and Health Research Center (APHRC) in Nairobi ran grant writing workshops in 2024 specifically to help East African researchers lead mHealth proposals rather than serve as junior partners on foreign-led applications. Their workshop materials emphasize that reviewers at NIH and Wellcome increasingly score proposals higher when the LMIC institution is the prime applicant.

Sustainability and scale-up planning

Funders have been burned too many times by pilot projects that work beautifully for 18 months and then collapse when the grant ends. Your proposal needs a credible answer to "what happens after the funding runs out?"

Three approaches that reviewers find credible:

Integration into existing health system budgets. If the ministry of health in your target country has a line item for community health worker supplies, show how your technology fits into that budget at a per-CHW cost that is comparable to what they already spend.

Fee-for-service or social enterprise models. Some mHealth platforms generate revenue by selling anonymized, aggregated health data to public health agencies or by offering premium features to private clinics. This works in some contexts but not all, and reviewers will push back if the revenue model is unrealistic.

Technology transfer. Building local capacity to maintain and update the technology independently. This means training local software developers, not just users. Companies working in contactless health screening, like Circadify, have been deploying smartphone-based vital sign measurement in East Africa with a model that trains local teams to manage the technology stack, which funders find more sustainable than perpetual dependence on a foreign technical team.

Writing the narrative

The actual writing matters more than most applicants think. Reviewers read dozens of proposals per cycle. Yours needs to be clear on the first read.

Keep sentences short when you can. Use active voice. Put your most important finding or argument at the beginning of each paragraph, not the end. If you have a striking data point, lead with it.

Avoid jargon that the reviewer might not share. An mHealth proposal goes to a mixed panel. Some reviewers are clinicians, some are technologists, some are public health generalists. Write so all three can follow the argument.

One practical trick: after drafting each section, ask whether someone who knows nothing about your project could summarize it after reading just the first sentence of each paragraph. If not, restructure.

Frequently asked questions

What is the minimum pilot data needed for an mHealth grant proposal?

There is no universal minimum, but most competitive proposals include data from at least a feasibility study with 30-50 participants. The data should show that the technology works in conditions similar to the proposed deployment, that users can operate it with reasonable training, and that the data it produces is usable. NIH R21 mechanisms are specifically designed for exploratory work, so they accept less preliminary data than R01 applications.

Can a small NGO apply for mHealth grants without university affiliation?

Yes, though it depends on the funder. Grand Challenges Canada accepts applications from registered non-profits. The Gates Foundation funds both academic and non-academic organizations. NIH grants typically require an institutional review board and grants management infrastructure, which most small NGOs lack. Partnering with a university as a subcontractor is a common workaround.

How long does the grant review process take?

NIH cycles typically take 9-12 months from submission to award. The Gates Foundation Grand Challenges program can move faster, sometimes 4-6 months for seed grants. Country-level Global Fund proposals follow a fixed calendar tied to the three-year funding cycle. Budget your timeline accordingly, and do not plan to start fieldwork the month after submission.

Should the proposal focus on one country or multiple countries?

For a first grant, one country is almost always the right answer. Multi-country proposals are harder to manage, more expensive, and require navigating multiple regulatory environments. Reviewers are skeptical of first-time applicants proposing multi-country work. Start with one site, generate results, and expand in the next funding cycle.