Wrapped up a newsletter automation that researches a topic, creates supporting infographics, formats everything into an email ready newsletter, and delivers it straight to my Gmail inbox. Every project teaches me something new. Looking forward to seeing how these builds compound over the next few weeks.

#Onam, the official harvest festival of #Kerala, India, also marks the Malayali New Year. As an expat, organizing a celebration for over 100 people, while the feast and logistics are manageable, tracking expenses can quickly become chaotic. Receipts start pouring in from various people, shops, and categories. Questions arise immediately: "Who paid for the hall?" "How much have we spent on food?" "Can you send me that invoice?" To streamline this process, I developed a simple system where team members can upload receipts, add their names and categories in just 30 seconds. Once uploaded, the receipt is stored, AI reads and extracts line items, and everything is recorded in a database. A live dashboard updates automatically, showing spend by category, budget status, and direct links to the original invoices. This system provides clean data without the need for chasing updates or confusion over which version of the sheet is the latest. #TheBiggerPicture The underlying pattern is intriguing. This is not merely an event expense tracker; it’s a receipt-to-database pipeline with a live reporting layer. The Onam event serves as the context, but this architecture is applicable to any business with distributed spending-whether it’s field teams logging site expenses, franchise operators tracking outlet-level costs, or logistics companies capturing vendor invoices on the go. When it’s time to enhance the system-adding authentication, role-based access, approval workflows, reimbursement tracking, and multi-project support-the foundation is already established, allowing for extensions rather than a complete rebuild. This system was built over a weekend using #Nextjs, n8n, Supabase, #Codex, #GoogleDrive, and #Vercel

I created an email automation that runs every morning at 7 am on the cloud. This automation sends me daily sales advice from the original sales gurus straight to my inbox without any manual intervention. I initially developed the automation locally and then deployed it in Trigger.dev. I also connected it to GitHub for future iterations.

Built Landing Page using Claude Code Before Claude Code, my only real option for building a site was piecing something together manually slow, and never quite matching what I had in mind. This time was different. Built a full landing page, deployed it live: glowing-torte-6a6849.netlify.app Took a fair bit of back-and-forth to get the design and copy right, but nowhere close to the time a manual build would've taken. Quick tip if you're building one yourself: get the fundamentals right before you call it done — performance, mobile responsiveness, and basic SEO make a bigger difference than people expect. Day 6 next.

#AISChallenge Hello everyone. I actually finished building this newsletter out on June 6th, but only recently started doing the 7-day AIS challenge. What really clicked with me when doing this project is the incredible ability of the WAT framework to self-heal during the building phase. Additionally, I created the skill to be able to follow this same framework each time I want a newsletter for any sort of topic. The WAT Framework's ability to make a non-deterministic system as deterministic as possible is truly incredible. One thing I would improve for next time is not just using Tavily for research but potentially Firecrawl and/or Perplexity. If you all have any suggestions, I would love any feedback. I really appreciate the community we have here!