Solutions · Fintech
Crowdfunding platform: what to decide, build and test.
Planning one? Here's what to settle before you brief anyone, what goes in the first version, how the build runs week by week, how the beta is tested with real people, and the numbers that show it's working.
One cause or open to everyone? The choice behind every other choice
"Crowdfunding platform" covers a school alumni appeal and an open site where strangers raise money for surgery. They need different legal footing, different trust tools and a different budget. Decide which you are building.
- Your own organisation, or other people's campaigns. A single NGO collects into its own account and issues its own receipts. An open platform collects money on behalf of others, which brings payment-partner rules, verification and moderation. The first is simpler; the second is where the trust problem lives.
- Donation, reward or lending. Donation and reward models are what this page covers. Lending campaigns sit under RBI's rules for peer-to-peer platforms, which require registration as an NBFC with a net owned fund of at least ₹2 crore. Treat those as a different product.
- Pay the organiser, or pay the hospital or vendor. Direct payment to the treating hospital is easier to defend to donors but means a verified payee list and invoices. Paying the organiser is faster but needs withdrawal checks.
- How you earn. An optional tip, a fixed platform fee or a sponsor each change what donors see at checkout. Show whichever you choose before payment.
- Foreign donors or not. Foreign money is a separate legal track (below). Decide now whether you want it.
Brief checklist: who can start a campaign, who verifies, who can withdraw, where money sits, whether you hold an 80G registration, and whether foreign donors are in scope.
Version 1 of a giving platform: trust before reach
Our Pitchin concept builds its pages around two ideas: funds going to the treating hospital, and a ledger of how money was used. Version 1 should protect those and defer growth tools.
| Module | First version | Add later | Why |
|---|---|---|---|
| Donation page | Amount chips, UPI, a short story, progress | Cards, wallets, matching gifts | Two taps from a WhatsApp link is the whole point |
| Receipts | Acknowledgement by email or message; 80G certificate if you are registered | Donor account with all past receipts | Tax-time requests arrive in bulk each year |
| Campaign builder | Story, goal, documents, photos | Video, templates, translation help | Weak campaigns waste the verification team's time |
| Verification desk | Document checks, payee check, approve or reject with reasons | Hospital API checks, scoring | Nothing goes live without a human read first |
| Payout | Release in steps against bills | Automated schedules | Staged release is your best trust signal |
| Fund-use ledger | Entries with bills for each release | Public dashboards | Donors trust what they can inspect |
| Updates | Organiser posts and donor messages | Thank-you videos, milestones | Updates reduce complaints and repeat gifts |
| Moderation | Report button and a review queue | Automatic duplicate detection | Fraud arrives early; plan for it |
| Recurring giving | Skip unless a charity needs it | Monthly mandate | Mandates add partner steps and failure states |
A twelve-week plan, with the paperwork that cannot wait
| Weeks | What gets built | What you supply |
|---|---|---|
| 1–2 | Donor and organiser journeys; verification checklist drafted | Your registration papers, a policy on who may raise money and for what |
| 3–5 | Donation flow, receipts, campaign pages | Payment partner account and test credentials; sample campaigns and photos |
| 5–8 | Organiser tools, verification desk, ledger | Reviewers' names and rules, document list, payee details policy |
| 8–10 | Payout flow, moderation queue, language versions | Translations or approvals, terms and privacy text from your lawyer |
| 10–12 | Testing on budget phones, review of every money screen, launch | Sign-off from your CA on receipts; first real campaigns lined up |
How we work with you each week
The same rhythm runs from week 1 to launch, so you always know what's happening and what we need from you.
- Friday: a demo link and a 30-minute call. You open the latest build on your own phone and try it yourself, rather than watching our screen.
- Within 48 hours: your feedback, in writing. In one shared doc, next to the screen it's about. Written feedback is clear, dated and doesn't get lost between calls.
- Monday: triage. Every comment goes into fix now, next week or later. Anything that changes the agreed scope gets a written quote before we touch it.
- Each milestone: two revision rounds, then your sign-off. Sign-off is against the scope we agreed, so it's clear what done means.
- One decision-maker on your side. Most delays aren't build time. They're feedback waiting on several people who disagree.
The full version, including how the beta and user testing work across every kind of project, is on our process page.
What we test with real people, and the tasks we set
Donors test on the phone that received the link, organisers on the phone they will run the campaign from, reviewers at their own desks. Each gets a task in plain words and in their language, and we watch without stepping in. Roughly five sessions per role shows where trust breaks. We fix those points and test them again.
| Who | The task | What we watch for |
|---|---|---|
| Donor | "Open the campaign from this WhatsApp forward and give ₹501 by UPI." | Can they do it in two or three taps? Do they see any tip or fee in rupees before paying? Does the receipt arrive? |
| Donor claiming tax relief | "Give ₹5,000 to the NGO's appeal and get your 80G certificate." | Is PAN asked only here, and only once? Is the name on the certificate spelled the way they typed it? |
| Organiser | "Start a campaign for your father's knee surgery at a hospital in Pune and upload the cost estimate." | Do they know which documents to add? Do they understand that money goes to the hospital, not to them? |
| Organiser | "The first ₹40,000 bill has been paid. Post an update for your donors." | Do they find the update screen, and does the update reach donors without them asking? |
| Verification reviewer | "Check this campaign. The patient name on the estimate doesn't match the story." | Do they spot it? Can they reject or ask for documents with a reason the organiser will understand? |
| Finance staff | "Release ₹40,000 to the hospital against this invoice and record it in the ledger." | Does the second check happen? Is the ledger entry visible to donors with the bill attached? |
The numbers that say it's working
Pick two or three of these in week 1. If you raise money today through bank transfers or a donation form, we note what you can see from that as a baseline. We set up the tracking before the beta and report at launch and 30 days after. We don't promise where the numbers go; we make sure they're in front of you.
| Goal | What we measure | Where it comes from |
|---|---|---|
| Donors finish giving | Share of people who open a campaign link and complete a donation | Page analytics and payment partner records |
| Receipts are right | Receipts reissued because of a wrong name, PAN or amount | Receipt log and CA spot checks |
| Verification keeps up | Time from campaign submission to decision, and the reasons for rejection | Verification desk |
| Every rupee is traceable | Share of released money with a bill attached in the ledger | Fund-use ledger |
| Organisers keep donors informed | Days since each campaign's last update | Campaign data |
| Problems surface early | Reports per campaign and time until a reviewer looks at each | Moderation queue |
What a crowdfunding platform costs, and why
A single-organisation donation site is near our one-user-type tier, ₹3–10 lakh for a small studio. An open platform with donors, organisers and a verification and payout desk is two user types plus admin, ₹10–25 lakh. These are ballparks from our cost guide; we quote each project.
- Verification depth. A checklist with a reviewer queue is modest. Document scoring and outside data checks add integration work.
- Payout rules. Staged release against bills means more states and more screens than a single withdrawal.
- Receipts and reporting. Donor statements for tax filing need correct data from the first donation.
- Languages. Campaign pages and share cards in several Indian languages multiply content as well as screens.
Tax, foreign money and data: what to check with your lawyer
- 80G is for registered institutions. The deduction applies to donations to eligible institutions and funds, and donors are told to check the registration. An individual's medical fundraiser should not issue something that looks like an 80G receipt.
- Annual reporting. A registered trust or NGO files a statement of donations and issues donor certificates by 31 May after the financial year. The statement carries each donor's name, address and PAN or Aadhaar, so capture them correctly at donation. These forms were called 10BD and 10BE; under the Income-tax Act, 2025 they are Forms 113 and 114. Your CA confirms the current process.
- Foreign contributions. These need FCRA registration, normally after three years of work, or prior permission for one project, and must arrive in a designated account at SBI's New Delhi Main Branch. Do not accept them on a general checkout.
- Holding other people's money. Collecting for campaigns usually means a regulated payment partner and an escrow account, not your ordinary current account.
- Sensitive data. Medical papers and IDs are the most sensitive files you will hold. The DPDP Rules apply fully from 13 May 2027; plan consent, retention and deletion now. See our DPDP checklist.
- Payments. Our UPI guide covers collect requests and failure handling.
This is general information, not legal advice. Charity, tax-exemption, foreign-contribution and payment rules change; have a lawyer or CA confirm your registrations and flows. See the NGO playbook for set-up basics.
Seven ways giving platforms lose donor trust
- Going live before verification exists. One bad campaign costs more trust than a slow launch. Build the desk first.
- Hiding the fee. Show the tip or fee before payment, in rupees.
- Releasing all money at once. Release in steps against bills, and log each step.
- No update path. A campaign that goes silent looks like a scam. Prompt organisers for updates.
- Collecting PAN you cannot protect. Ask only when a receipt needs it and store it with care.
- Copying a receipt template. Check wording and registration numbers with your CA before launch.
- Skipping budget phones. Most donors arrive from a WhatsApp link on an entry-level Android phone. Test the donation page there.
Instead: pick one cause type, write the verification rules on one page, and release the first campaigns by hand. Then send a brief for a fixed quote.
Cost and timeline
8–12 weeks for a first version.
Fixed quote within 48 hours of your brief: scope, timeline and price in writing before we start. These are what move the number.
- Verification steps and who reviews them
- Payment partners, payouts and escrow-style releases
- Receipts and tax reporting
- Organiser tools and moderation
- Languages
Questions
About your crowdfunding platform.
What does a crowdfunding platform cost?
It depends on verification, payouts and reporting. Every project gets a fixed quote within 48 hours of your brief. Our guide to app development cost in India explains typical ranges. A single-organisation donation site costs much less than an open platform with organiser tools, verification queues and payouts.
Do you handle the regulatory side?
No. Collecting donations, foreign contributions, payouts and tax-exemption receipts are regulated, so they need your organisation's own registrations and a regulated payment partner. We design and build the platform around them, and your CA or lawyer confirms the rules for your setup.
Can donors get 80G receipts automatically?
Yes, if your organisation is registered for them. The platform collects the donor's PAN and details, issues the receipt with your registration number and keeps records for your annual filings. Donors can download past receipts from their account at tax time.
How do you make campaigns trustworthy?
By verifying documents before launch, paying hospitals or vendors directly where possible, and showing donors a ledger of how funds were used. Our concept build Pitchin puts that ledger on every campaign page. Donors trust what they can check for themselves, so updates and bills are visible to everyone who gave.
Who owns the code and donor data?
You do. Code, designs and donor records are handed over in full, with consent and data handling planned in. Donor trust depends on careful data handling, so you decide what is collected and how long it is kept. Nothing stays locked in our accounts.
Read next
- PaymentsAdding UPI payments to your app: a plain guide →How UPI works inside an app or website: intent, QR and collect flows, payment gateways, refunds, AutoPay mandates and reconciliation, explained for business owners.
- ComplianceThe DPDP Act for app owners: a practical checklist →What India's Digital Personal Data Protection Act means for your app or website: notice, consent, data rights, children's data, security and breaches, in plain words.
- MessagingWhatsApp and your app: order updates, OTPs and support →How Indian businesses use the WhatsApp Business Platform with their app: approved templates, opt-in, the 24-hour window, OTPs, team inboxes and costs.
Start a project
Tell us how your business runs. We'll build what it runs on.
Four taps, about a minute. Fixed quote within 48 hours.


