The ArchDesign World has enough problems.
Build Tools that Make Their Work
Better — Faster — Easier
Nine real problems across architecture, design, construction and the software behind them. Pick one, question the existing way, prototype something better.
One project.
Dozens of people.
Hundreds of decisions.
Thousands of messages.
Architect
Coordinates design intent across clients, consultants, vendors and execution teams.
Who could your idea help?
Eight audiences, one shared project. Open a card to see the day, the friction and the opening.
Don’t build another todo app. Build something the industry actually needs.
Choose one problem statement. You do not need to solve the entire industry.
Find one painful part.
Understand it deeply.
Build one intelligent intervention.
The problem statements
Kill the coordination black hole nightmare
Too many people. Too many handoffs. Too little visibility.
Make project communication intelligent, not overwhelming
The problem is not a lack of communication. The problem is that important information is buried inside communication overload.
What if you could talk to your project?
Less clicking. More doing.
Reinvent the timesheet
Nobody wants to fill one. Every business needs the intelligence behind one.
Build the marketing machine
Give a 10-person studio the automation of a 100-person company.
Build a modular app ecosystem that works as one
Each app should stand alone. Together they should feel like one product.
Break the login — and everything it protects
Getting in is one boundary. What you can reach after is the harder one.
Make the design presentation an interactive experience
Go beyond drawings and ordinary 3D tours—let people explore, understand and decide in one connected experience.
Prove the platform cannot be broken into
One tenant's data, files and secrets must stay unreachable to everyone else.
60-minute open session
Bring anything: how to read a brief, what counts as scope, what to skip, how the demo round works. Drop in on Google Meet — no registration needed for the session.
This is a real project week. Somewhere in here is a decision.
Six channels. Six versions of the truth. Nobody is wrong, and nothing is resolved. Press the button and watch what software should have been doing all along.
You don’t need
to build the whole thing.
Build the part that makes us say: “that’s interesting.”
Six moves from confusion to conviction.
Understand
What is actually broken?
Question
Delve deep to find why the process works this way.
Imagine
Picture what today's technology makes possible.
Prototype
Make the idea tangible.
Demonstrate
Show us that it can work.
Explain
Tell us why you built it this way.
Yes.
Use AI.
CHATGPT · CLAUDE · CODEX · CURSOR · FIGMA · LOVABLE · WHATEVER HELPS YOU BUILD
We are not testing whether you can build without AI.
We are testing whether you can think with it.
Use AI aggressively. But understand what you submit. You should be able to explain:
- the problem
- your decisions
- your architecture
- your prototype
- what AI helped with
- what you would improve next
What we read instead of your CV.
- 9.1 CGPA, top 5% of batch
- “AutoCAD, Revit, MS Office”
- “Team player. Fast learner.”
- a prototype that actually runs
- a 3–5 minute video of it working
- what broke at 2 AM, and how you got out
That’s the portfolio we read.
Problem understanding
Did you identify the real friction, or the obvious solution?
User–product sense & communication
Explain clearly why somebody would actually use this, and how it will be advantageous.
Technical execution
Did you make the idea tangible?
The format
Register
Read the nine problem statements and submit your entry.
Until 12 September 2026 at 6:29 pm UTCSelect
Lock one problem statement. A change means a fresh registration, up to three.
Max 3 per applicantBuild
Prototype your intervention.
Your own scheduleSubmit
GitHub repo, documentation, video walkthrough — deployed URL preferred.
By 16 September 2026 at 6:29 pm UTCPresent
Remote, 30 minutes, presented by the applicant.
Shortlist within ~1 weekInternship
Remote internship consideration; offers generally 7–10 days after the final assessment.
Remote · 3–6 monthsEverything decided, in one place.
Dates, eligibility, deliverables, shortlisting and internship terms.
Registration closes 12 September 2026 at 6:29 pm UTC.
Closes 16 September 2026 at 6:29 pm UTC. Nothing is accepted after the cutoff.
Maximum three registrations. Changing your problem statement means a fresh registration, inside the same limit of three.
Individual, not team-based. Think, argue and build with peers or a team if you like — the internship belongs to the applicant who registered.
Not required at registration. Your prototype is the application.
Optional, and may be submitted with the project.
Mandatory with the project submission.
Mandatory. Explain the problem, your decisions, the architecture and what AI helped with.
Part of the submission package — 3 to 5 minutes of the prototype working.
Strongly preferred and weighted positively.
Thursday 10 September 2026, 8:00pm–9:00pm IST on Google Meet. Not recorded, so join live.
Approximately within one week after the submission cutoff.
Published on this website, and sent by email and WhatsApp.
Remote, 30 minutes, on a slot you book yourself.
The applicant only. Applicant details must match the person presenting.
Shortlisted for internship consideration — not declared winners.
Remote, 3–6 months of your choice, ₹9–12k monthly stipend plus defined incentives. Offers generally follow 7–10 days after the final assessment.
Four things. Nothing else.
The idea
What problem are you solving?
The prototype
GitHub repository — mandatory. Deployed URL strongly preferred.
The walkthrough
3–5 minute video of it working.
The documentation
Mandatory: the problem, your decisions, the architecture, what AI helped with, what you would build next. Portfolio optional.
What a strong build gets you.
Shortlisted builders go straight to a conversation with the team that will use what they built. No aptitude test. No group discussion.
Read the brief together, argue about it, build with a peer or a team if that helps. Registration is individual, and one person registers as the applicant.
Whoever applies is the person considered for the internship. The applicant details must match the person who claims the submission and presents the demo.
Build the app and its integrated features.
Deliver it and take away the cash prize.
* The cash prize depends on the size, technology, depth of integration and delivery. This can be considered in discussion.The industry will change.
The question is: who will build?
What comes Next - Now!
Choose one problem.
Build one idea.
Show us how you think.
Know your application status.
Check registration, submission, shortlisting and demo updates in one place.
Shortlisted participants will present on Monday, Tuesday and Wednesday. Timing slots to be sent later.
Pickable demo slots will be shared by direct message with shortlisted candidates only.