A few years into running Marpu Foundation, I started getting asked the same question by other NGO founders.
How do you actually write a CSR proposal that gets funded? Mine keeps getting ignored. I send it to twenty companies and hear back from none. What am I doing wrong?
For most of those founders, the proposal was not the problem. The problem was that the proposal had been written from the wrong perspective entirely. It read like a request, when it should have read like an answer. It listed what the NGO needed, when it should have shown what the company would get. It tried to inspire, when it should have tried to make the CSR head’s job easier.
This is the single biggest shift that separates proposals that get funded from proposals that get ignored. And once you make this shift, almost everything else becomes mechanical.
This article is the honest playbook for writing a CSR proposal that actually gets funded in India. The mindset most founders get wrong. The structure that works. The specific sections that decide whether a CSR head reads to the end. And the small differences that make the difference between a polite no and a yes.
The Mindset Shift That Changes Everything
Before any structure, you have to understand what a CSR proposal actually is.
It is not a funding request. It is a document that helps a CSR head defend a decision internally.
When you write a proposal and send it to a CSR team, that proposal does not just land with one person. It travels through their organisation. The CSR head reads it. Then they share parts of it with their finance team to confirm the spend is eligible. Then with their audit team to confirm the documentation will hold. Then with their sustainability team to confirm it feeds BRSR disclosure. Then with their leadership to confirm the impact narrative is strong. Then with their communications team to confirm the story can be shared externally.
At every step, your proposal is being read by someone different, with a different concern. If the proposal does not give each of those readers what they need, it gets stuck. Often, the CSR head who likes you personally cannot push the proposal through because their finance team flags the spend classification, or their audit team wants different documentation, or their sustainability team needs different metrics.
The proposal is not asking one person to say yes. It is helping six or seven people, in sequence, each have one fewer objection to saying yes.
Once you understand this, the structure of a strong proposal becomes obvious. It must answer every question that anyone in the corporate chain will ask. The sections, the data, the documentation, the language. All of it exists to make the CSR head’s internal defence of your proposal easier.
Research the Company Before You Write a Word
The proposals that get funded are usually visibly written for one specific company. The ones that get ignored could be sent to any company with the company name changed.
Before you write anything, spend time on the company.
Read their CSR policy if it is publicly available. Read their last annual CSR report. Look at the projects they funded in the last two years. Understand which Schedule VII categories they prioritise. Understand the geographies they operate in and the regions their CSR has reached. Look at their BRSR disclosure if they are a listed company. Read their leadership team’s public statements on social impact.
This research takes a few hours and gives you something most other proposals do not have. The ability to write a proposal that fits their priorities, not yours.
When the CSR head opens your proposal and sees that you understand what they fund, where they fund it, and why, you have already separated yourself from the dozens of generic proposals in their inbox. They will read the rest of your proposal differently because the first impression has earned attention.
The Structure That Works
After research, your proposal needs a clear structure. The structure below is what I have found works in practice, after seeing how proposals move through corporate review.
Section 1: Executive Summary
The first half page is the most important. Many CSR heads will read only this and then decide whether to invest the time in reading further.
The executive summary should answer five questions in plain language:
→ What is the proposed project?
→ Where will it run?
→ Who will it benefit?
→ What will it cost?
→ How does it align with the company’s CSR priorities?
Keep this section under 300 words. Every word should be specific. Names of places. Numbers of beneficiaries. Exact alignment with their Schedule VII activities. A CSR head reading this section should be able to imagine the project clearly within a minute.
Section 2: The Need You Are Addressing
This section explains why the project matters, using data and evidence, not emotion.
Many founders fill this section with emotional appeals. Children who deserve better. Communities that have suffered. Lives that need transformation. This language fails because it is generic and it triggers the corporate reader’s instinct that they are being manipulated.
Instead, use data. Government surveys, published research, district-level statistics, sector reports. Show the gap you are addressing with hard evidence. Cite your sources. A proposal that opens with a Niti Aayog statistic or a state government report data point earns more credibility than a paragraph of sentimental language.
Section 3: Your Proposed Solution
This section explains exactly what your project will do, in operational detail.
The structure that works:
→ Project name and category
→ Project description in plain language
→ Specific activities with timelines
→ Geographic scope and locations
→ Number of beneficiaries by category
→ Implementation methodology
→ Community engagement approach
→ Project duration
The more specific this section is, the stronger your proposal. Vague proposals about “transforming communities” lose. Specific proposals about “training 240 women across 8 villages in tailoring and digital skills over 9 months, with placement support, in partnership with the local industrial training institute” win. The corporate reader can picture what they are funding.
Section 4: Schedule VII Alignment and Compliance
This section makes the CSR head’s compliance defence easy. It is short, technical, and absolutely required.
State clearly which Schedule VII activity category your project falls under, with the exact wording from the Companies Act 2013. Confirm that you hold valid 12A and 80G certificates. Confirm Form CSR-1 filing. State your organisation’s registration type, registration number, and date.
This section reassures the CSR head’s finance and compliance teams immediately. Without it, the proposal gets stuck even if everything else is strong.
Section 5: Expected Impact and Outcomes
This is the section the company’s leadership and communications teams will care about.
Spell out the measurable outcomes your project will produce. Use clear, audit-friendly metrics:
→ Number of beneficiaries reached, broken down by category
→ Specific outputs (schools renovated, plantation count, women trained, health camps held)
→ Outcome indicators (attendance improved, income increased, survival rates, behaviour change)
→ Long-term impact statements with realistic time frames
Be careful not to over-promise. Corporate readers have seen proposals that claim impossible outcomes from small budgets. Realistic, well-defined impact statements earn more credibility than ambitious-sounding ones. The CSR head who funds you is taking responsibility for your delivery. They want to fund a project where the impact claims will hold up at audit.
Section 6: Documentation and Reporting
This section often makes the difference between proposals that get funded and proposals that get a polite no.
Spell out exactly how you will document and report on the project. The CSR head’s audit and BRSR teams will read this section carefully.
What you commit to deliver:
→ Utilisation certificates with itemised spend
→ Photo and video documentation with geo-tagging
→ Beneficiary records
→ Implementation reports at agreed intervals
→ Final impact report at project close
→ BRSR-aligned data for sustainability disclosure
→ Audit-ready financial documentation
This section signals operational seriousness. Many proposals are vague here, and they lose because the CSR head’s compliance team cannot defend the project on documentation grounds. Strong proposals are unusually specific about reporting and documentation. This earns trust before the project starts.
Section 7: Budget
The budget section needs to be itemised, defensible, and clear.
Break the budget into clear categories: programme costs, materials, beneficiary support, documentation, and partner organisation costs. Show what is covered by the company’s CSR contribution and what is covered by other sources.
Avoid round numbers that look invented. A budget that says Rs 5,00,000 for “implementation” looks weak. A budget that itemises Rs 4,82,500 across specific cost lines looks operational.
If your project costs span more than a single financial year, show how the spend phases across years. CSR heads need to plan their disclosure cycle, and clear phasing makes their planning easier.
Section 8: Why Us
This is the credibility section. Keep it short and specific.
What to include:
→ Organisation’s registration details and tenure
→ Geographic operational reach
→ Number of corporate partnerships completed
→ Multi-year delivery track record
→ Sample past projects in the same theme
→ Key team profiles
→ Awards, recognitions, or media coverage that support your credibility
Avoid generic language about being passionate or committed. Every NGO claims that. Instead, show specific operational facts that prove you can deliver.
Section 9: Community Engagement and Sustainability
This section often gets overlooked, and it matters more than founders realise.
Spell out how the project engages the community before, during, and after implementation. CSR heads increasingly distinguish between projects that arrive in a community and projects that work with a community. The difference shows up in long-term outcomes, in audit narrative, and in BRSR disclosure quality.
If your project has a sustainability plan beyond the funded period, name it. A school infrastructure project that includes teacher training has stronger long-term impact than one that only builds classrooms. A health camp that includes community health worker training compounds beyond the camp itself. CSR heads value this thinking.
Section 10: Annexures
Keep your annexures specific and useful. Common annexures that strengthen proposals:
→ Sample utilisation certificate format
→ Sample impact report format
→ Geo-tagged photographs from similar past projects
→ Letters of recommendation from past corporate partners
→ Project location maps
→ Detailed activity timeline
→ Risk and mitigation note
Language and Tone
Strong proposals are written in confident, operational, neutral language.
Avoid emotional manipulation. Beneficiaries deserve respect, not pity. Communities are partners, not subjects. Children are students, not victims. The tone should be one of an experienced organisation describing work it is fully capable of executing.
Avoid corporate cliches. Synergies, ecosystems, transformative change, holistic approach, leveraging strengths. CSR heads have read these phrases in every proposal. They lose credibility on contact.
Avoid promising what you cannot deliver. Overpromising in a proposal is one of the fastest ways to lose long-term relationships. The proposal that gets you funded once but creates trouble at audit hurts more than the proposal that did not get funded at all.
Use plain language. Specific nouns. Numbers. Names. The proposal should read like an operational plan, because that is what it is.
The Length of a Good Proposal
The right length depends on the budget and the company.
For most CSR proposals between Rs 5 lakh and Rs 25 lakh, a proposal of 8 to 12 pages plus annexures is usually right. Long enough to address every question, short enough to be read in one sitting.
For larger budgets above Rs 25 lakh, proposals can stretch to 15 to 20 pages, often with more annexures.
For smaller budgets below Rs 5 lakh, proposals can be tighter at 5 to 8 pages.
What matters more than length is density. Every section should carry weight. A 12-page proposal of dense, specific content beats a 30-page proposal padded with stock phrases every time.
Common Mistakes That Get Proposals Rejected
A few patterns appear consistently in proposals that fail.
Generic content that could be sent to any company. The CSR head sees instantly that this is a copy-paste proposal. Trust falls before they finish the first page.
Vague impact claims. “Transform lives” and “create change” mean nothing in audit terms. Specific outcomes do.
Missing compliance details. Proposals without Schedule VII alignment, registration details, and 12A and 80G information signal an organisation that is not ready for serious CSR partnership.
Weak budget breakdown. A budget without itemisation, with round numbers, or with unexplained categories cannot survive finance team review.
Over-promising. Impact claims that sound impossible for the budget proposed make the entire proposal look unreliable.
Photographs without context. Photo galleries of past work without dates, locations, or project context are window dressing. Photographs with full context build credibility.
Emotional manipulation. Proposals that try to guilt the company into funding usually fail. Corporate readers are trained to spot this and resist it.
Missing documentation samples. Proposals that do not show what reporting will look like leave the CSR head’s audit team uncomfortable.
What Happens After the Proposal Is Sent
Sending the proposal is not the end of the process. It is the start of a follow-up sequence.
A polite follow-up two weeks after sending is appropriate. Another follow-up two weeks after that, if the first goes unanswered. After that, persistence without becoming a nuisance.
If the CSR head has questions, respond fast and specifically. Slow or vague responses to clarifying questions kill more proposals than weak proposals. The CSR head is testing how you will behave once funded.
If the proposal is declined, ask for honest feedback. Many CSR heads will share what stopped the proposal, which gives you exactly what you need to improve the next version.
If the proposal is accepted, the relationship is now beginning. The first project is your audition for the longer arc. Overdeliver. Document everything. Build trust that earns the second project, then the third.
The Compounding Effect of One Good Proposal
The first successful proposal does more than fund one project. It builds the case study you need for the next ten proposals.
A funded project gives you a logo, a reference, an impact report, and a CSR head who can vouch for you. These four assets make every future proposal stronger. The company you are pitching next will take you more seriously because you have proof from a peer that you can deliver.
This is why the first proposal that gets funded matters so much, and why it is worth investing real time and care in writing it well. The compounding effect is enormous. Five funded projects in your first three years build the foundation for fifty projects in the years after.
The path is long but the structure is clear. Research the company. Write for the chain of internal readers. Be specific in every section. Use data instead of emotion. Be honest about what you can deliver. Spell out compliance and documentation. Make the CSR head’s internal defence easy.
Do this consistently and the funded proposals will come.
If you are an NGO founder working to land your first or your next CSR partnership, I am happy to share more from my experience. Write to me at raghu@marpu.org.
Kadiri Raghu Vamsi 
Leave a comment