Never charge hourly when starting out — clients will question why a bug took 3 hours to fix. Charge per project milestone: - Milestone 1: Wireframes & visual designs in Figma (30% upfront) - Milestone 2: Functional staging deployment (40%) - Milestone 3: Production domain launch & handover (30%). Never deploy to their live domain until the final payment is cleared in your account.

At the national hackathon hosted on our campus last month, the problem statement was vague and boring. While exploring the sponsor company's public API docs, we spotted an unauthenticated SSRF vulnerability in their webhook validation endpoint that exposed their staging AWS metadata. Instead of building another generic AI resume parser, we submitted a complete patch with automated penetration testing scripts and a secure proxy relay. The CTO who was judging choked on his coffee, called their DevOps team on speaker in the auditorium, and gave us the 1st prize on the spot.

During automated email testing in our Web Development lab, I put the department faculty mailing list into a cron job test script. Every Monday morning at 8 AM for three consecutive weeks, all 24 professors and the HOD received a high-resolution meme about recursion and off-by-one errors from 'bot@campusloop.internal'. The HOD printed out the meme, stuck it outside his office cabin, and wrote 'Very informative, improve formatting next time'.

We ran a campus ticket booking system for our college fest. Everything was fine in testing with 50 users. As soon as 2,000 students refreshed at 10 AM, the server froze. PostgreSQL was doing sequential table scans on `orders.user_id` for every check. One simple `CREATE INDEX` reduced query latency from 12,000ms to 4ms. Always index your foreign keys!

We built a simple WhatsApp bot that sends daily mess menus and laundry token alerts for our campus hostels. Distribution playbook: 1. Shared on unofficial batch WhatsApp groups during lunch time. 2. Put small stickers with a QR code near the water coolers on every hostel floor. 3. Word-of-mouth did the rest: 500 active users in 72 hours. Solve real localized inconvenience.

Judges don't care about your 1,500 lines of code; they care about 3 things: 1. The Problem Hook (first 30 seconds: relatable student or real-world pain point) 2. Live Working Demo (never use slide screenshots; show real clicks) 3. Business / Scalability model (how does this survive beyond Sunday morning?). Keep slides under 6 pages.