When an NGO asks several agencies for a website quotation and gets back three documents that cannot be compared, one for a small figure, one for a large figure and one that is a single line, the problem is almost never the agencies. It is the brief. A clear one-to-three page brief, sent to every vendor in the same form, produces quotations you can set side by side and lets you judge who understood your work. This guide, written for trustees, programme heads and communications officers planning NGO website development in India, explains what to put in a brief, how to compare quotations fairly, which questions separate experienced teams from inexperienced ones, and which clauses to look for in the agreement. It is practical rather than legal; for contracts, have your own adviser read the final document.
It does not give a price, because the honest price depends on the features you choose. For a feature-by-feature view of what drives cost, read our NGO website development cost breakdown. Here the aim is to help you ask for the right thing so that the figures you receive mean something.
Why a brief matters more for an NGO than for a business
A company can often buy a website by saying "we need a modern site". An NGO usually cannot, for four reasons.
You have several audiences. Donors, volunteers, beneficiaries, CSR partners, funders, government officials and journalists all visit, and they want different things. A vendor who has not been told which matters most will design for none.
Money and trust are on the line. A donation page that fails, or an annual report that is out of date, costs you supporters. Your site is part of how your organisation is judged.
Compliance matters. Registration and tax details, receipts, foreign-contribution rules where relevant, and data protection duties all affect what the site must show and do. A vendor cannot guess your position.
Staff turnover is real. A site that only the vendor understands becomes a liability the day your communications officer leaves. The brief should say who will maintain it.
A brief forces you to decide these things once, in writing, rather than discovering them mid-project when changes cost money.
Before you write: five decisions
Spend a meeting, not a month, on these.
- What is the website for, in one sentence? "To let supporters donate and see how funds are used" is a purpose. "To have a presence" is not.
- Who are the top three audiences, in order? Rank them. If donors come first, the donation journey leads the design; if CSR partners come first, credibility and reporting pages do.
- What action do you want from each audience? Donate, volunteer, enquire, download a report, share a story.
- Who will own and update it? Name the person or role. If no one, plan for a maintenance arrangement.
- What is the budget range and the date that matters? State a range or a ceiling honestly. Without one, vendors guess, and many price high to be safe. If a campaign or event drives the date, say so. Be realistic about what content you can supply; most delays come from content, not code, as we explain in why launches get delayed by content, copy and photos.
What to put in the brief
Aim for a document a busy trustee can read in ten minutes. Use these headings.
1. About the organisation
Two or three paragraphs: what you do, where, for whom, since when, and your registration status. Include your current website address if you have one. This tells a vendor your scale and tone, and lets them look at what exists.
2. Goals and audiences
Your one-sentence purpose, the ranked audiences, and the action wanted from each. This is the core of the brief.
3. Scope: pages and features
List what you need in plain words, and divide it into must have, should have and later. A typical NGO list might include:
- Home, About, Programmes, Impact or Annual Reports, Governance and policies, News, Contact
- Donation page with one-time and recurring options, and receipts
- Volunteer sign-up
- Event or campaign pages
- Story pages with consent for photographs of beneficiaries
- A donor or supporter area, if needed
- Multilingual content, for example English with Hindi or Marathi
- Newsletter sign-up
- Admin area for staff to edit pages without a developer
For each, a sentence on why you need it is enough. If you are unsure whether something is necessary, mark it "advise us". Our guide to NGO website navigation for donors, volunteers and CSR partners can help you shape the page list.
4. Donations and payments
Say what you need without naming a vendor's product unless you have one in mind: one-time and monthly giving, which receipt format your finance team needs, whether you collect donations from abroad, and whether donors need tax-benefit documents. Because donation rules (for example for foreign contributions, or the tax treatment of donations) depend on your registration, state your position and tell vendors your accountant or legal adviser will confirm the details. Do not ask a web agency to decide your compliance. A good vendor will ask the right questions and build the fields your finance team specifies. See our articles on recurring monthly giving and donation receipts and failed payment help for what the build involves.
5. Content
Who writes the text, who supplies photographs, and who approves? Are there existing documents, such as reports and audited accounts, to be published? Is anything to be translated? If you want the vendor to write copy, say so, because it is a separate and substantial piece of work.
6. Design and brand
Share your logo, colours and any style guide. Point to two or three websites you like, and two you dislike, with a sentence on why. Specify accessibility expectations: for example, that the site should meet WCAG 2.2 AA, and work on low-bandwidth mobile connections, which is how many of your supporters will see it. Our article on low-bandwidth mobile donors explains the reasoning.
7. Technical and hosting expectations
State preferences rather than technology brands: that you want to own the domain and hosting account, that staff must be able to edit content, that backups must exist, that the site must be secure, and that you need a handover at the end. Ask vendors to recommend a platform (a WordPress build, a custom build, or a platform product) and explain why. Our guide to donation site security and hosting lists what to expect.
8. Data protection
Tell vendors that the site will collect personal data from donors, volunteers and possibly beneficiaries, and that you expect them to follow India's data protection law and your own policies. Ask how they would handle consent, retention and access. Do not leave this to the end.
9. Integrations
List the tools the site must connect to: accounting software, a CRM or donor database, email newsletter tools, WhatsApp, analytics. If you do not use any yet, say so.
10. Timeline and process
Give your target launch date and any fixed dates. Ask vendors to propose a timeline with milestones. State who on your side will give approvals and how quickly.
11. Maintenance and support
State the support you expect after launch: how long for bug fixes, whether updates and backups are included, and what response times you expect.
12. What you want in the proposal
Ask each vendor to answer the same list, in this order:
- Their understanding of your goals in their own words
- Proposed approach and platform, with reasons
- Page list and features, mapped to your must/should/later list
- Deliverables and what is not included
- Timeline with milestones and what they need from you
- Fixed price or price range, with the breakdown
- What happens after launch, with support terms and cost
- Ownership of code, content, design files, domain and accounts
- Two or three relevant examples, with permission to contact the client
- Names of the people who will work on it
Making vendors answer a common list is what makes comparison possible.
How to run the process
- Shortlist three to five vendors. Ask peers in similar organisations, look at NGO websites you admire and check who built them, and review portfolios. Our guide to shortlist questions for a web development company can help.
- Send the same brief to all, on the same day, with the same deadline for questions and the same deadline for proposals.
- Offer a short call or form for questions, and share each question and answer with all vendors so no one has an advantage.
- Be honest about budget. Vendors who know the range propose within it, and you can compare approaches, not guesses.
- Do not ask for free design work. A speculative homepage mock-up from every bidder wastes effort, tends to reward flashy pictures over understanding, and is unfair to small teams. Ask for relevant samples and a conversation instead. If you want to see design thinking, pay a modest fee for a paid discovery or design sprint with your top one or two.
- Score with a simple grid. See below.
Comparing quotations fairly
Quotations rarely line up because each vendor includes different things. Build a comparison table with your must-have features as rows and vendors as columns. For each cell, record: included, included at extra cost, or not included. Then add rows for the hidden items that cause surprises:
| Item | Vendor A | Vendor B | Vendor C |
|---|---|---|---|
| Design revisions included (how many rounds) | |||
| Content entry and migration | |||
| Donation page with recurring giving | |||
| Receipts and finance reports | |||
| Accessibility testing | |||
| Staff training | |||
| Hosting, backup and security in year one | |||
| Renewal cost of hosting and domain after year one | |||
| Third-party licences (themes, plugins) and who pays renewals | |||
| Support after launch: duration and response | |||
| Ownership of code and content | |||
| Handover documentation | |||
| Payment terms and milestones |
Quotations that look cheap often exclude items from this list. Ask each vendor to confirm in writing what is not included.
Look for the questions they asked. A vendor who asked about your audiences, your finance team's needs and your content has understood the job. A vendor who sent a price and a template without a question may have priced a template.
Be wary of extremes. A figure far below the others usually means a narrower scope, a template with limited changes, or costs that will arrive later as extras. A figure far above may include features you do not need. Ask both to walk you through the difference.
Weigh people over portfolio. Ask who will actually do the work, and whether you can speak to a client with a similar project. Our article on questions to ask before hiring lists more.
Do not choose on price alone. The cheapest site that your staff cannot update, or that fails on donation day, is expensive. Equally, the highest price is no guarantee of quality.
Questions that reveal experience
Ask these on a call, and listen to how specific the answers are.
- "Which NGO donation sites have you built, and what went wrong on one of them and how did you fix it?" Experienced teams have a story; inexperienced ones do not.
- "How will you handle a spike in traffic during a campaign?" (See traffic spike readiness.)
- "How do donations reconcile with our accounts, and what happens when a payment fails or is disputed?"
- "What can our staff change without you, and what needs a developer?"
- "Who owns the domain, hosting, code and content, and how do we take the site elsewhere if we need to?"
- "How will you protect donor data, and what do you collect by default?"
- "How will you make the site accessible and fast on a basic phone?"
- "What do you need from us, and what delays have you seen on similar projects?"
The agreement: clauses worth checking
This is a checklist for a conversation with your own adviser, not legal advice.
- Scope and deliverables that match the proposal, with a change process and pricing for extras.
- Milestones and payments linked to delivery, not only to dates. Avoid paying everything up front.
- Ownership: your organisation should own the domain, the hosting account, the content and, normally, the design and the code written for you, subject to third-party licences. Clarify this in writing. See our guide to contract, ownership and warranty.
- Third-party licences and who pays and renews them.
- Warranty and bug-fix period after launch, and what it covers.
- Support and maintenance terms after that period, with prices.
- Confidentiality and data protection obligations.
- Handover: credentials, documentation, a staff walkthrough and a checklist; see the website handover and ownership checklist.
- Termination: what happens to the work and files if either side ends the project.
- Acceptance: how you will test and sign off.
If you have already built a donation site and are changing vendors, plan the move carefully: donation site migration explains the risks to recurring donors and receipts.
Own website or a platform?
Some NGOs ask whether they need a custom website at all, or whether a crowdfunding or donation platform suffices. The honest answer depends on your size and goals; both can coexist. Our article on your own website versus a crowdfunding platform sets out the trade-offs. State your thinking in the brief and ask vendors to comment.
A short brief template
Copy this outline and fill it in.
- Organisation: who we are, where we work, registration status (two paragraphs).
- Purpose of the website in one sentence.
- Audiences, ranked, with the action wanted from each.
- Must-have, should-have and later features.
- Donation needs: types, receipts, currencies, finance contact.
- Content: who writes, who photographs, languages, existing documents.
- Design: brand assets, examples liked and disliked, accessibility expectation.
- Technical: ownership, editing, backup, security, integrations.
- Data protection expectations.
- Timeline: target date and approver names.
- Support after launch.
- Budget range.
- What we need in your proposal (the list above).
- Dates: questions by, proposals by, decision by.
Illustrative scenario
Consider an education NGO in Pune that sends the same one-page brief to four vendors and receives four proposals. In the comparison grid it notices that one vendor's lower figure excludes receipts and training, another includes a bespoke donor area it never asked for, a third has not mentioned who owns the code, and the fourth has asked three sharp questions about how recurring donations will be reconciled. The NGO invites the fourth and the second for a paid half-day workshop, learns which one explains trade-offs more clearly, and signs with them on milestone payments. This is an invented example to show the process; it is not a description of a real client.
Work with the Govindani team
We build donation websites for non-profits in India, with receipts, recurring giving, volunteer sign-up and staff-editable admin, and our team has delivered over 500 NGO websites. If you would like a second pair of eyes on your brief or a proposal from us, see our NGO website page and website creation services, then contact us or call 092019 58274. We are happy to answer questions on a brief even if you choose another vendor.
Frequently asked questions
What should an NGO website brief include?
Your organisation's background, the website's purpose, ranked audiences and actions, must-have and later features, donation and receipt needs, content responsibilities, design and accessibility expectations, ownership and hosting preferences, data protection expectations, timeline, support needs and a budget range.
How many vendors should an NGO ask for quotations?
Three to five is usually enough. Send the same brief to all of them at the same time, share questions and answers with everyone, and ask each to answer a common list so you can compare like with like.
Should we ask agencies for a free design mock-up?
Generally not. Free speculative designs reward presentation over understanding and are unfair to small teams. Ask for relevant samples, references and a conversation, or pay a small fee for a design sprint with your final one or two.
Who should own the NGO's website?
Your organisation should own the domain, the hosting account and the content, and normally the design and code made for you, subject to third-party licences. Confirm this in the written agreement and take professional advice on the wording.
Why do website quotations differ so much?
Because vendors include different things. One may exclude content entry, receipts, accessibility testing, training or support. Compare quotations in a grid of features and hidden items, and ask each vendor to confirm in writing what is not included.
Sources:
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- MeitY: Digital Personal Data Protection Act, 2023
- Guidelines for Indian Government Websites (GIGW 3.0)
About the author: written by the Govindani Infotech NGO web development team in Pune.