Real Agent Cases

Find smarter buying patterns in office supply order history with Claude Code

Posted
by Alex Hillman (@alexhillman)
Last checked
Method:
How we verify

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Outcome

Alex Hillman had Claude Code go through Indy Hall's paper products order history to suggest buying patterns that avoid costly last-minute orders.

Agent

Claude Code

Prompt Recreated prompt

The source didn't share its exact prompt, so we wrote this from what it describes.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Look at our supply order history and suggest a buying pattern that saves time and avoids last-minute orders.

Check with me first: Which items run out most often?

What I'll give you:
- My order history (export or receipts)

Rules:
- Find how often each item is ordered and when we end up rushing.
- Suggest order quantities and timing.
- If something is missing or unclear, ask me instead of guessing.
- Only suggest. Don't place orders.

Output: A short summary of patterns and a suggested ordering schedule.

You'll know it worked when: I have a simple plan that stops the rush orders.

Try this in:

ChatGPT Gemini Grok

Sends the Recreated prompt shown above. ChatGPT and Grok open with it filled in, and ChatGPT may send it straight away. Gemini opens empty, so we copy the prompt for you to paste. Every button also copies it.

The source used Claude Code, which can take actions on your computer or in a browser. These are general chat tools, so results may differ, and a normal chat may only give you a plan.

Opens in a new tab. We don't see what you send.

These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.

Optional stronger version

Our rewrite with extra checks. The poster didn't test it.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Analyze our supply order history and suggest a buying pattern that avoids rush orders.

Quick check first: tell me if anything below is missing or unclear.

Inputs (fill in or confirm):
- Order history
- Items that run out
- Lead times
- Storage space limits and budget per order

Rules:
- Compute order frequency and quantities per item.
- Identify rush orders.
- Suggest reorder points and quantities.
- Estimate savings.
- Group items by supplier so orders can be combined.
- Show for each item: average weekly use, lead time, safety stock and reorder point.
- Flag items with irregular use that need manual review.
- Suggest a regular order day.
- Show unit price trends.
- Note which items are seasonal.
- Flag items bought from several suppliers at different prices.

If you get stuck: If data is sparse, say so. If a login, CAPTCHA or two-step code appears, stop and ask me to handle it; never guess or store passwords.

Verify before you finish: Back-test the plan on past data.

Output: Report and reorder table.

Done when: the plan would have prevented past rush orders.

Source

https://x.com/alexhillman/status/2020352927848923387

Related cases