Aurora is a SaaS vehicle quoting assessor using Gemini 2.h Flash to assess damages on a vehicle, searches google in real time for relative data such as part prices and, current market value of that particular vehicle so that once the quote is complete if can declare if the vehicle is viable for repair or not and if viable what the repair cost might be.
GCP | Firebase | Cloudflare | Gemini
🚀 I Build Real-World Apps That Work — Even Offline.
I turn business ideas into practical, reliable, and user-friendly applications designed to solve real-world problems — with or without an internet connection.
💰 Meet MoneyLens — my personal finance application for Android and web. It features multilingual voice-based expense entry in English, Hindi, and Marathi, along with on-device data encryption to keep financial information secure. It demonstrates my ability to build privacy-focused, multilingual applications with a seamless user experience.
💻 What I Build: Custom web applications, Android and mobile apps, business automation platforms, and scalable digital products.
🛠️ My Tech Stack: React Native, Next.js, React, Java, TypeScript, Python, and Firebase.
From understanding your requirements to designing, developing, and launching your product, I focus on clean code, practical solutions, and reliable delivery.
📩 Have a business idea? Let's discuss it. I'll help you find the simplest, smartest way to bring it to life.
A sophisticated website concept for a premium dining experience.
Designed with an elegant dark aesthetic, refined typography, and immersive food photography, this concept brings the restaurant's identity to life through a visually engaging digital experience.
Key design elements:
Premium restaurant website design
Elegant menu presentation
High-quality food imagery
Minimalist navigation
Modern, responsive layout
User-focused browsing experience
Focus: Combining visual storytelling, brand identity, and intuitive user experience to create a memorable digital presence.
Open to website design and development collaborations.
Your Logistics Team Shouldn't Have to Chase Every Shipment Manually. 🚢
A shipment is delayed. Your customer wants an update. Your operations team is checking carrier portals, copying tracking numbers into spreadsheets, and sending the same status emails repeatedly.
By the time everyone has the right information, the next shipment needs attention.
The problem isn't a lack of effort. It's disconnected logistics operations.
Common challenges:
Shipment updates scattered across multiple carrier systems.
Delayed shipments discovered too late.
Manual customer status emails.
Tracking spreadsheets that quickly become outdated.
Repetitive follow-ups between operations and customer service.
Limited visibility into shipment exceptions.
The solution: An automated logistics operations workflow built with n8n.
I can design an automation that connects carrier tracking APIs, your shipment database, and customer communication channels.
Instead of manually checking every shipment, your team receives structured updates when something actually needs attention.
What the automation handles:
📦 Shipment Tracking — Retrieve updates from supported carrier APIs.
📊 Operations Visibility — Maintain synchronized shipment records and exception histories.
🔁 Escalation Management — Notify the responsible team when an exception requires action.
The goal: Less repetitive tracking work, faster exception awareness, and more consistent customer communication.
Two ways we can work together:
Option 1: Already have carrier APIs, a TMS, or a defined tracking workflow? Share your requirements, and I'll help design the integration.
Option 2: Not sure which logistics tasks should be automated? We can map your shipment lifecycle and identify the highest-value starting point.
Make your logistics operations easier to manage as shipment volume grows.
Workflow architecture
Scheduled Trigger → Carrier API Request → Normalize Tracking Events → Match Shipment Records → Detect Status Changes → Route Exceptions → AI Summary → Customer Email / Operations Alert → Database Update
Implementation: Authenticate carrier integrations, normalize differing event codes, compare timestamps and event IDs, prevent duplicate alerts, route exceptions by severity, and log delivery failures for retry.
Benefits: Reduced manual tracking, clearer exception ownership, more timely customer updates, and an auditable shipment history.
Result: A centralized shipment monitoring workflow that allows operations teams to focus on resolving exceptions instead of repeatedly checking tracking portals.
The customs-hold exception is the one I'd find hardest to route, since it needs a different owner than a plain delay. Do you map each exception type to its own team in the escalation step, or is it one shared alert queue?