ps61PS-01: Safe Natural-Language Search for Commudle
PROBLEM
People think in sentences, not filters. Commudle users searching for "Android developers near me" or "speakers on Flutter who have spoken in Lucknow" have to translate that into filters and keywords themselves, across communities, events, speakers, hackathons, builds, labs and jobs.
CHALLENGE
Build a pluggable semantic search system that converts a natural-language request into the right query, executes it safely against the database, and returns ranked results. It must not leak private information, and must resist prompt injection from users and from content stored in the database itself.
Example: "find Android developers near me" → intent and filters extracted → validated query against public fields → permission-checked results → ranked profiles.
MVP / EXPECTED OUTCOME
- Search API taking a query plus requester context (logged out, member, organiser, city)
- Natural language to structured query: technology, location, dates, role, content type
- Permission-aware execution against a mock schema with synthetic data
- Injection and leakage defences enforced in code, not in the prompt
- Demo interface showing results and blocked attempts
- Test set: 20 normal queries with expected results, 15 adversarial queries blocked
BONUS
Hybrid search with embeddings plus structured filters, Hindi and Hinglish queries, clarifying questions for ambiguous requests, ranking by recent activity, logging of blocked attempts.
CONSTRAINT
No real personal data. Never expose emails, phone numbers, RSVPs, attendance, form responses, private channels, drafts or organiser-only analytics. The model must never have raw database access.
ps62PS-02: Merchant Growth AI (Paytm)
PROBLEM
Millions of small merchants run on Paytm without an analyst, a marketer or a finance team. The data to grow their business exists in their transactions, but the insight does not reach them in a form they can act on.
CHALLENGE
Build an AI business partner for a Paytm merchant: something that understands the merchant's transaction history and tells them what to do next, in language a shop owner actually uses.
MVP / EXPECTED OUTCOME
- Merchant-facing assistant working over synthetic transaction data
- Plain-language insights: sales patterns, slow periods, repeat customers, cash flow
- Specific recommended actions, not just charts
- Conversational interface a non-technical merchant can use
BONUS
Hindi and regional language support, voice-first interaction, WhatsApp delivery, proactive alerts, settlement and working-capital insights.
CONSTRAINT
No real merchant data. Must be usable by someone with no analytics background. Must not give regulated financial advice.
ps63PS-03: AI-Powered Financial Journeys (Paytm)
PROBLEM
Insurance, lending and fintech journeys are full of jargon, forms and drop-off points. Users abandon applications because they do not understand what is being asked or what they are agreeing to.
CHALLENGE
Make one financial journey simpler, faster and more human using AI. Pick a single flow, for example a loan application, an insurance claim, or policy comparison, and rebuild it end to end.
MVP / EXPECTED OUTCOME
- One complete journey working end to end on synthetic data
- Plain-language explanation of terms, eligibility and next steps
- Document understanding where the flow needs it
- Measurably fewer steps or less friction than the current experience
- Clear handling of the moments users usually drop off
BONUS
Indic languages, voice, accessibility for low-literacy users, explainability for automated decisions.
CONSTRAINT
No real financial or personal data. Must not make credit, underwriting or claim decisions autonomously, and must not give regulated financial advice.
ps64PS-04: Autonomous AI Teammates (Paytm)
PROBLEM
Most AI assistants respond. They do not finish the job. Real work needs something that plans, takes multiple steps, uses tools and closes the loop.
CHALLENGE
Build an AI teammate that completes a real workflow end to end, rather than answering questions about it. Pick one job a person does repeatedly and hand it over entirely.
MVP / EXPECTED OUTCOME
- Agent that plans and executes a multi-step task using tools or APIs
- Visible reasoning and progress, so a human can follow what it did
- Error handling and recovery when a step fails
- Human checkpoints before consequential actions
- A demo showing the task completed start to finish, not a scripted path
BONUS
Multi-agent coordination, memory across sessions, integration with real tools, cost and latency tracking, an evaluation harness for reliability.
CONSTRAINT
No autonomous actions with financial consequences without human approval. No real user data.
ps65PS-06: AI Signal Intelligence Challenge (MacroVision AI)
PROBLEM
Business and financial decision-makers work across fragmented sources: statements, transactions, invoices, operational records, customer activity, supplier information, reports and contracts. The important signals sit between these sources and only become visible when several pieces are read together, so a human analyst usually spots them late.
CHALLENGE
Build an AI/ML system that discovers meaningful signals, anomalies, trends, relationships and emerging risks or opportunities across heterogeneous business or financial data, and clearly explains the evidence behind each finding.
Example: revenue up 20%, receivables up 55%, DSO up materially, payment terms changed → SIGNAL: working-capital pressure may be increasing → investigate customer concentration, collections and recent credit-term changes.
MVP / EXPECTED OUTCOME
- Ingest at least one structured source (CSV, Excel, JSON, database export, API) and at least one unstructured source (PDF, report, business update)
- Detect anomalies, unusual changes, trends or notable events
- Correlate evidence across multiple records or sources, not a single observation
- Surface risks or opportunities worth human investigation
- Explain each signal with its supporting evidence
- Recommend what a decision-maker should investigate next
- One complete workflow: source data → detected signal → evidence → recommended next step
- Interface or dashboard with an evidence view, plus a technical note on data sources, architecture, methods and limitations
DATA
No dataset is provided. Sourcing it is part of the challenge. Use public or open datasets, public company filings and reports, free-tier APIs within their terms, or synthetic data you generate. Do not rely on confidential, proprietary, illegally obtained or paid restricted data.
BONUS
Choose your own scenario: financial, company, supply-chain, customer, due-diligence or operational intelligence. Techniques worth reaching for include LLM reasoning and extraction, embeddings, semantic search or RAG, anomaly detection, clustering, entity and relationship extraction, temporal reasoning, agentic tool use and predictive modelling.
CONSTRAINT
A dashboard or purely rule-based analytics application is not enough; there must be a meaningful AI/ML component. Do not build an autonomous investment, lending or financial decision engine. The system provides intelligence, evidence and investigation leads for a human, and does not replace human judgement. Software only, no hardware.