We Just Launched the Pradeepta Basati Welfare Foundation Platform — 10,000 Users, Day One

Most software launches are quiet. A staging link becomes a production URL, a few dozen users trickle in, and you spend the first week watching error logs. The Pradeepta Basati Welfare Foundation platform was not that kind of launch. On the day it went live, over 10,000 people were waiting for it — and every one of them needed it to work.

This is the story of what we built, the decisions that made the difference, and why this project sits differently from a typical web build.

What is Pradeepta Basati Welfare Foundation?

Pradeepta Basati Welfare Foundation is a welfare organisation operating across multiple districts in India. Its work spans beneficiary support, fund management, community welfare programs, and field operations coordinated across three administrative tiers — Village Collectors, District Collectors, and State Collectors. Before this platform, all of that coordination happened through spreadsheets, phone calls, and physical paperwork. The inefficiency was measurable and the errors were costly.

What we built

The platform is a multi-tier governance dashboard with role-based access control at its core. Each tier of the organisation sees a different interface and holds different permissions — Village Collectors manage ground-level beneficiary records and local fund disbursements, District Collectors have oversight of all villages under their jurisdiction and approval authority for escalated requests, and State Collectors see the entire organisation with cross-district analytics, financial summaries, and compliance dashboards.

• Role-based access: Village Collector, District Collector, State Collector — each with scoped data views and action permissions
• Beneficiary management: registration, status tracking, document uploads, and verification workflows
• Fund disbursement records: end-to-end money trails from state allocation down to village-level distribution
• Real-time dashboards: live operational metrics, pending approvals, and flagged anomalies for each tier
• Compliance and reporting: automated report generation for audits, government submissions, and internal reviews
• Mobile-responsive: field collectors access it on phones, not desktops — the entire UI adapts

The technical decisions that made day one possible

Launching to 10,000 simultaneous users without preparation is a recipe for a very public failure. We spent a significant portion of the build thinking about the first hour of production, not just the last hour of development.

Server-side rendering for the dashboard meant the initial page load was fast even on slow mobile connections — a non-negotiable for field workers in areas with poor connectivity. Database queries were scoped per role at the API layer, not the frontend, so no collector could accidentally receive data above their clearance level. The backend was built to handle concurrent writes — multiple collectors submitting records simultaneously — without race conditions on shared financial records.

The measure of a governance platform is not what it does when everything works. It is what it does when 10,000 people press submit at the same time.

Day one: 10,000 users, zero incidents

The platform launched to the full user base on day one. All three tiers came online simultaneously — Village Collectors logging field data, District Collectors reviewing and approving, State Collectors monitoring the aggregate. For the first six hours we watched the dashboards, the error rates, the response times, and the database query performance. Everything held.

No 500 errors. No data inconsistencies. No permission leaks between roles. The load balanced cleanly. The real-time dashboards updated without lag. By end of day one the platform had processed thousands of records and the operations team reported that work which previously took days of back-and-forth was completing in minutes.

What this project means to us

We have built fintech dashboards, e-commerce platforms, SaaS products, and healthcare portals. This one is different. When the platform works, welfare reaches people faster. When it does not, the consequences are real. That weight made every architectural decision feel more important, every edge case feel worth finding, and every test pass feel more satisfying.

It is also the clearest demonstration we have of what it means to build at scale and have it just work. Not "work for the first 100 users and then degrade" — work for the first 10,000 users on the first day.

If you are building something similar

Government-adjacent and welfare platforms have specific requirements that generic SaaS templates do not handle well — multi-tier access control, audit trails, offline resilience for field workers, and report formats that comply with government submission standards. If you are building something in this space and want a team that has shipped it before, we are open to talking.