Build What Moves India: OpenAI Hackathon to Reimagine Public Service Websites

Entrepreneur and creator Varun Mayya announced Build What Moves India — a hackathon in collaboration with OpenAI to rethink India's public service websites. Teased in early August 2026 and covered by Storyboard18 and TechGig, the initiative invites India's developer, designer, and product-building community to improve the digital platforms citizens rely on daily — with submissions due August 27, 2026.

This is not OpenAI launching a India-specific ChatGPT feature called "Reimagine Websites." It's a civic UX hackathon where OpenAI is the infrastructure partner (credits, tooling access, credibility with panels). If you're a builder in India wondering whether to participate — or a team elsewhere watching how OpenAI engages regional builder communities — here's the grounded read.

TL;DR

Why this exists: friction on India's most important websites

Mayya's framing in the launch teaser is blunt: some of India's most important websites are also the most frequently used, yet navigating them has become "a shared part of the Indian internet experience" marked by friction — slow flows, confusing forms, outdated IA, mobile-unfriendly layouts, and multi-step authentication pain.

That's a UX problem, not a model problem. India has invested heavily in digital public infrastructure — identity, payments, data rails — while citizen-facing portal UX often lags. The hackathon targets the layer users actually touch: the website where you file taxes, apply for a license, check a scheme, or download a certificate.

Mayya also named a structural issue for Indian builders: access. Strong engineers have ideas but lack a credible platform to show work that government decision-makers might take seriously. Build What Moves India is an attempt to create that channel — hackathon submissions, panel review, and (aspirationally) evaluator attention from public-service stakeholders.

What OpenAI contributes

OpenAI's role, per Mayya's public posts:

• Listed collaborator on promotional materials (Storyboard18, TechGig, Instagram announcement)
• AI credits for participants — Mayya said he spoke to OpenAI contacts to secure this
• Tooling ecosystem builders already use — ChatGPT, Codex, and ChatGPT Sites for rapid web prototyping

OpenAI is not announcing a sovereign India model or a government contract in this initiative. Compare to France's Mistral-first cyber-testing mandate or BharatGen's sovereign model stack — those are infrastructure/policy plays. Build What Moves India is builder community + UX outcomes.

ChatGPT Sites: the practical prototyping path

Many entrants will prototype with ChatGPT Sites — OpenAI's public-beta feature (Plus, Pro, Business, Enterprise, Edu) that turns a prompt into a hosted website or lightweight app from the ChatGPT desktop app, without a separate deployment pipeline.

What Sites is good for in this hackathon:

Sites workflow basics:

1. Open Sites in the ChatGPT desktop app (Plugins → Sites, or left nav)
2. Prompt with the word "website" or mention @Sites
3. Review the hosted preview; request one UI change at a time
4. Set visibility to public when ready to share the demo link

Limitations to plan around: Sites does not connect to live government APIs today; updates to dynamic data require manual refresh through Codex. For hackathon submissions, that's often fine — judges evaluate UX and flow design, not production integration on day one.

For teams that need exportable production code, OpenAI's docs point to Codex for independent hosting — the same split SME website guides describe: Sites for preview, Codex for deployable artifacts.

What people are asking

Is this only for Indian citizens?

The announcement targets India's builder community and public-service UX. Check buildwhatmovesindia.com for official eligibility rules — Mayya's teaser emphasized local expertise and citizen-facing problems, but full T&C weren't public at initial announcement.

How is this different from IndiaAI Mission / BharatGen?

See explainx.ai's BharatGen coverage and Sarvam Epoch announcements for the model-layer context.

Does OpenAI have other India builder programs?

OpenAI's DevDay Exchange 2026 global tour includes Bengaluru (October 16, 2026) — a separate developer conference track from this hackathon, but part of the same "deepen builder relationships outside the US" pattern. See explainx.ai's full DevDay Exchange city-by-city guide for all eight cities, the application deadline, and how to apply.

Can I use open-weight models instead of OpenAI?

The hackathon doesn't require OpenAI models exclusively in public materials — but OpenAI credits and Sites access are the stated perks. Teams building on Qwen3.8 locally or Kimi K3 should confirm submission guidelines on the official site.

What a strong submission probably looks like

Mayya hasn't published full rubrics yet, but civic UX hackathons usually reward:

1. Specific portal, specific user — "Tax filer on mobile in Tier-2 city" beats "fix all gov websites"
2. Before/after flow — screen recording of current pain vs. proposed 3-step flow
3. Accessibility — Hindi/regional language toggle, low-literacy-friendly copy, WCAG contrast
4. Offline/low-bandwidth — progressive enhancement matters on Indian mobile networks
5. Hosted demo link — Sites public URL or deployed static preview; judges won't clone repos

Avoid: generic "AI chatbot on every page" without solving a concrete task completion problem. The friction Mayya describes is navigation and form design, not lack of LLM wrappers.

Sample prompt: ChatGPT Sites prototype for a public portal

If you're entering with ChatGPT Sites, start from a single task on a single portal. Example prompt structure (adapt the portal name):

Build a mobile-first website for completing a single government service online.

Service: renewing a driving license (learner's permit holder, first renewal).
User: 22-year-old in Pune, Android phone, Hindi/English toggle.

Pages:
1. Landing — what you need (documents checklist, 3 min read time)
2. Form — photo upload, address confirmation, fee summary
3. Confirmation — reference number, expected processing time, support link

Design: high contrast, large tap targets, progress bar, no jargon.
Language: English default with Hindi toggle on every screen.
Do not add a chatbot — fix the form flow only.

Iterate one change at a time: "Move document upload before payment" beats "make it better." Record a 60-second screen capture of the current official flow (public pages only) alongside your Sites demo — judges respond to side-by-side friction counts (taps, scrolls, fields).

For teams using Codex instead of Sites, export static HTML/CSS or a Next.js scaffold and host on any Indian provider; the hackathon cares about demonstrable UX, not which OpenAI surface you used.

Timeline and context (August 2026)

The hackathon sits in a busy month for OpenAI product and policy news; participation is about civic UX, not model releases. Indian builders already tracking Razorpay's Vulcan payments model or local inference costs may still enter — the submission is a website experience, not an infra benchmark.

After the hackathon: what "success" looks like

Mayya's stated goal isn't a single deployed portal — it's proof that better UX is buildable and attention from people who control procurement. Realistic outcomes:

• Short term: Portfolio pieces, panel feedback, OpenAI credit usage, social proof for civic-tech startups
• Medium term: Ministries pilot static redesigns on non-critical flows (informational pages, status trackers)
• Long term: RFP language that scores mobile UX and accessibility — only if evaluators actually attend

Builders should document metrics: time-on-task, error rate on form fields, number of screens to completion. Government IT evaluators speak procurement; "feels modern" loses to "40% fewer abandoned sessions in user test."

If your demo includes AI at all, keep it assistive (plain-language field help, document checklist) rather than open-ended chat — aligned with how ChatGPT for Teens restricts open-ended harm categories rather than adding unconstrained conversation everywhere.

Honest limitations

• One hackathon ≠ policy change. Mayya acknowledged a single sprint won't fix systemic procurement, legacy CMS contracts, or inter-ministry data silos.
• Evaluator access is aspirational. Getting decision-makers to review submissions is the hard part; the hackathon creates a venue, not a guarantee.
• Sites beta caps. Plan-specific usage limits apply; high-traffic public demos may hit storage or visibility ceilings during beta.
• Production gov deployment requires security audits, accessibility certification, and data residency compliance — none of which a weekend prototype satisfies alone.

Summary

Build What Moves India (deadline August 27, 2026) is Varun Mayya and OpenAI's bid to mobilize India's builder community around public service website UX — the citizen-facing layer of digital government that daily use exposes as broken. OpenAI brings credits, tooling, and brand; ChatGPT Sites is the fastest path to a shareable hosted demo; Codex remains the route to exportable production code. It's complementary to India's sovereign AI model efforts, not a replacement for them. Apply at buildwhatmovesindia.com if you have a concrete portal redesign worth showing.

Related on explainx.ai

• OpenAI DevDay Exchange 2026: eight cities, how to apply
• BharatGen: India's sovereign AI for 22 scheduled languages
• Sarvam Epoch 2026 announcements from Bengaluru
• ChatGPT for Teens — OpenAI's August 2026 safety launch
• France sovereign AI: Mistral over OpenAI for gov cyber testing
• Headless SaaS for agents — charge per interaction
• Can governments ban AI models? Regulation guide
• Qwen3.8-27B open weights — local frontier option

Sources: Storyboard18 — Varun Mayya + OpenAI hackathon · TechGig — Build What Moves India · OpenAI ChatGPT Sites docs · buildwhatmovesindia.com

Details reflect public announcements as of August 19, 2026. Judging criteria, prizes, and eligibility may update on the official site — verify before submitting.