Bihar's future will not be built from a distance. It will be built by people who know a specific piece of its soil well enough to plant something there.
Learn More ↓Most enterprise challenges ask you to think big. We ask you to think specific. A well-understood local problem — one you've walked to, spoken to people about, and traced to its actual root — is worth more than a novel idea borrowed from a case study.
Bihar does not lack ideas. It lacks people who know Saharsa's fish markets, Sheohar's agricultural calendar, or Araria's migration patterns well enough to build something durable there. That knowledge is what this track is designed to build.
A deep, lived understanding of a local problem will always supersede a "unique" idea that lacks context. If you cannot explain why this problem exists in this specific place, your solution is speculation.
Your enterprise must be designed for the district you've chosen — its infrastructure, culture, economic patterns, and constraints. An idea that works in Bengaluru but ignores Buxar is not a Bihar enterprise.
A team proposes an app-based micro-loan platform for vegetable vendors in a Samastipur block market. The idea is clean. The need for credit is real. But field visits reveal that most vendors here don't own smartphones, operate entirely on daily cash cycles, and already have informal credit lines from the same supplier they buy stock from — lines that also come with loyalty, trust, and first access to produce. The vendor's actual problem isn't access to capital. It's supplier lock-in. That insight — the one that changes everything — only comes from standing in the market. The app, without it, solves nothing.
The journey has four phases. Each builds on the previous. You are being evaluated not just at the final presentation — your engagement through the entire process is part of your score.
Two sessions are open to all registered participants. The remaining five are exclusive to shortlisted teams. Each session contributes Session Grade Points (SGP) to your final score — so the work happens here, not just at the presentation.
| Session | Focus | Access |
|---|---|---|
| Decoding the Challenge May 16 |
What "district-rooted enterprise" means. How to choose a district and identify a problem worth working on. What the jury actually evaluates. | All Registered |
| How to Build a Concept Note June 06 |
Structure, language, and logic of a concept note. Live walkthrough of strong and weak examples. Common mistakes and how to avoid them. | All Registered |
| District Intelligence Shortlist Phase |
Field inquiry techniques. How to gather meaningful local data, conduct community interviews, and document what you find. Moving from observation to insight. | Shortlisted Teams |
| AI for Architects Shortlist Phase |
Using AI tools to stress-test your idea, identify blind spots in your problem analysis, and strengthen your concept note and presentation deck. | Shortlisted Teams |
| The Revenue Logic Shortlist Phase |
How to move from a "good cause" to a "viable business" in the Bihar context. Revenue models that work at district scale. Thinking about customers, not just beneficiaries. | Shortlisted Teams |
| Prototyping & Pilots Shortlist Phase |
How to design a Minimum Viable Product using local resources. What a "pilot" looks like at your stage. How to show early evidence of viability without a working product. | Shortlisted Teams |
| The Mauryan Pitch Shortlist Phase |
Narrative structure for the final jury presentation. How to anchor a pitch in your district research. Clarity over sophistication. Presenting conviction, not performance. | Shortlisted Teams |
Session engagement counts for 25% of your final score. The teams that build the most are the ones who show up consistently and synthesise what they learn. The SGP system rewards exactly that.
Each session carries a score. What your team earns depends on how many members attend.
A minimum of 2 members must attend for your team to receive 100% of that session's score. Fewer than 2 = partial credit only.
A minimum of 3 members must attend for your team to receive 100% of that session's score. Fewer than 3 = partial credit only.
After any session, write your team's actual takeaways and how they apply to your district work. Post it on LinkedIn. Tag #PatliputraSamvad and your district (e.g. #SamastipurInnovation). Earn a 20% bonus on that session's score. The bonus rewards thinking, not just attendance.
Problem understanding is the highest-weighted category at 35%. Not passion. Not a good slide. The jury looks for four specific things — each pointing to whether you actually spent time with the problem or constructed it from a distance.
Have you identified the specific individuals or groups most affected? Can you describe their current workaround — the imperfect, expensive, or exhausting thing they do today because the right solution doesn't exist?
Not "rural Bihar" or "small towns." Which block, which market, which stretch of highway, which type of farm? What does the physical and economic landscape look like? What infrastructure exists — and what doesn't?
Why does this problem persist? What is missing from the system — a market link, a behaviour, an infrastructure piece, a policy, a trust relationship? Surface causes are easy. The jury is looking for the layer underneath.
What solutions — formal or informal — already exist? Who else has tried to address this and what happened? What local knowledge, networks, or resources are already present that your enterprise can work with, not around?
The score reflects the full journey — from the quality of your field research to the rigour of your final pitch. Each category rewards something specific. None of them reward ideas alone.
WHO/WHERE/WHY/WHAT EXISTS. Depth of field research. Specificity of district knowledge. Evidence that you engaged with real people, not just secondary sources.
Session Grade Points accumulated across the workshop series. Consistent presence and active synthesis through the journey — not just showing up for the final.
Clarity of explaining the problem, the insight, and the solution. How well the jury can follow your reasoning — not how polished the slides are.
Is the proposed enterprise viable at district scale? Does the revenue model account for local realities — purchasing power, distribution constraints, existing market structures?
The jury evaluates your understanding — not your English. Present in Hindi, English, Hinglish, or your local dialect. What matters is that your reasoning is clear and the jury can follow it. A team from Darbhanga that explains their insight in Maithili-inflected Hindi with complete clarity will score higher than a team that recites polished English sentences without depth behind them.
Individual registration takes ten seconds — just your name, phone, email, and college. Your team and district can follow before May 31.
Secure your spot in under a minute. Form your team and choose your district before May 31.
Team is assembled. Register as a unit with your chosen district and problem focus.