Festival content cadence, daily slip verification, slow-mover detection across stores.
Hub composition: All three agent types across /marketing, /finance, /ops.
What the team was already living with.
A jewellery retailer running a multi-store operation in western India. Marketing was a one-person team running festival creatives across nine-day cycles. Finance closed late and slip mismatches surfaced days after the entry. Inventory drift on bridal SKUs was visible only at quarter-end.
Leadership wanted a single operating view across stores without a heavy ERP refit and without central staff growing.
The agents that shipped.
- 01
/marketing Q&A on Telegram. Holds the festival calendar, the brand kit, and historic engagement signals. Answers what to post and why now.
- 02
/marketing Tools in Claude Code. Generates festival reels and posts from the brand kit, sized for Instagram, WhatsApp Status, and print.
- 03
/finance Tools that closes daily and weekly cycles, generating GST workings and an MIS draft.
- 04
/ops Slip-Verify. Operators drop a slip into a Telegram folder; the agent verifies against the ledger and posts confirmation back to the inventory group.
- 05
/ops Stock-Watch. Background agent that flags slow-movers before festivals.
Real questions. Real answers.
What changed, concretely.
- Outcome 01
Slip-mismatch resolution
From a multi-day lag to morning-of confirmation in the inventory group. [TBD: typical slips/week.]
- Outcome 02
Festival creative cadence
Daily posts produced from the brand kit during nine-day festival cycles, where previously the cadence broke after day three.
- Outcome 03
Slow-mover surfacing
Bridal SKUs flagged before festivals rather than at quarter-end. [TBD: window of clearance opened earlier.]
- Outcome 04
Cycle-close drafting
Daily and weekly close cycles are drafted by /finance and reviewed by the controller, rather than authored from scratch.
The hub is in retainer phase. Next quarter: extend /finance to a multi-entity consolidation across the group's holdings.