New father life means diapers. A lot of diapers. I order the same pack from FirstCry every few weeks, and the pricing on that site is chaotic. The same product swings from ~₹580 to over ₹1,000 depending on when you catch it. I usually wait for the ~₹600 range post-discounts, but between feeds and nap schedules, checking manually gets old fast.
Both Claude and Manus now have scheduled tasks and browser-use. I gave each a prompt: check this product’s price periodically, notify me on Slack if it drops below ₹650. Both set it up in one go. Test notification came through, done.
The average price hovers around ₹900. Getting it at ~₹580 with stacked discounts, repeatedly, without lifting a finger, adds up. I’m going to set this up for every product I reorder regularly.
The implementation difference between the two was the surprise. Claude did standard browser automation, navigated the site, read the page, compiled a report. Manus analyzed the network calls FirstCry was making, found the underlying coupon API that returns the best possible price after all discounts, and used that directly. No browser navigation needed. I wasn’t expecting that.
I took what Manus found and asked Claude to use the same API approach. Now the scheduled task hits the API directly, runs faster, and skips the flaky browser step entirely.
