A commenter has Claude plan events minute by minute with menus, and act as a personal shopper comparing prices, return policies and shipping costs across sites.
A commenter has Claude plan events minute by minute with menus, and act as a personal shopper comparing prices, return policies and shipping costs across sites.
One commenter uses a Claude agent in two personal workflows. For parties, they give it a theme, go back and forth until they agree on ideas, and then it creates a Claude artifact with a countdown to the event plus minute-by-minute planning and menu management. For shopping, it searches product listings across websites, writes an MD file with links and prices, and recommends the best site using return policies, shipping costs, Wirecutter, and other sources.
They describe both setups as regular personal-life uses and say the shopper mainly helps with clothes and household items. The thread gives no hard results or savings figures, and they had not connected it to buying groceries for the party planner.
The main catch is that the process still starts with ideating together first; only after they agree on what they like does the party plan get turned into an artifact.
I'm hosting [type of event] for [number] guests on [date] with a budget of [amount]. Build a minute-by-minute schedule and a menu with a shopping list, including dietary needs: [restrictions]. Then compare prices, shipping costs, and return policies across [stores or sites] for the key items. Finish with one plan and one shopping table, and don't buy anything.
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.
Copilot and Claude review each PR for bugs, missing tests and risky changes before a human looks, so reviewers can focus on design.