All case studies

Food distribution · United States

Menu in, supplier proposal out

A per-prospect deliverable that took hours of manual work now runs from a menu upload.

Stack

  • Claude Skills
  • PDF generation
  • Structured product catalogue
Menu in, supplier proposal outMenu in, supplier proposal out — Trigger → Rules engine → System of record → Delivery. Write-back: number · status · balance01Trigger02Rules engine03System of record04DeliveryWrite-back: number · status · balance

The problem

A food distributor pitching restaurants needed a tailored supplier proposal for each prospect.

Each one meant reading the prospect’s menu, deciding which products fit that venue’s identity and audience, and formatting a presentable document.

Hours of skilled judgment, repeated per prospect, with inconsistent output depending on who built it.

The approach

I packaged the entire deliverable as a Claude Skill.

The prospect’s menu goes in. The skill analyses it against the wholesale catalogue, selects the products that fit that venue’s positioning and audience, and generates a send-ready document.

The commercial rules are encoded in the skill — which products to lead with, what to disclose at proposal stage, what to hold back for the conversation — so the judgment is applied the same way every time, not reconstructed per prospect.

The result

A deliverable that previously took hours of manual work now runs from a menu upload, ready to send over messaging or email.

The transferable piece

Any firm whose proposal quality depends on who happened to build it can have that judgment encoded once.

Next caseAn editorial system with enforced brand voice

Let's talk

Send me the process that costs you the most time.

I will tell you whether it is worth automating before you spend anything. Thirty minutes, no commitment, no pitch deck.