Case studies
What a real run looks like
Each story follows one job from the first ask to the last decision: what was typed, what Zaver returned, what the assistant did with it, and what the person decided. Every story is reconstructed from the customer's actual working session with the brand, creator identities, contacts and commercial numbers removed.
Customer story · Luxury fashion · travel creators
A luxury handbag launch roadshow: from a one-line brief to a priced creator proposal, without opening a platform
Influencer marketing agency, UK · Claude (desktop app) · Zaver Radar over MCP · Gmail connector
An agency had a week to staff a luxury handbag brand's launch roadshow for a new travel handbag, in Manchester and Birmingham and then London, with travel creators. The whole job ran inside Claude with Zaver connected over MCP and Gmail connected for sending and reading mail. Day one: 77 travel creators found and checked, 62 emailed with personalised rate requests.
Read the case study →Customer story · Hospitality · local
An Airbnb host's art café in Lisbon: a creator plan a two-person team can run without hiring an agency
Guesthouse with an art café, Lisbon, two people · Claude or ChatGPT · Zaver Radar over MCP · Gmail connector
A couple run a four-room guesthouse in Lisbon with an art café on the ground floor. Weekends are full; weekdays are empty, and the room bookings that come through the café are the best-margin bookings they get. They cannot afford an agency retainer and do not have time to learn a platform.
Read the case study →Customer story · Agency operations
An agency's creator roster that updates itself every morning in Google Sheets
Boutique influencer agency, four account managers · Google Sheets · Zaver Radar: Profile metrics → Google Sheet, scheduled · Claude or ChatGPT with the Sheets connector
A four-person agency keeps a roster of about 400 creators in a Google Sheet: beauty, fitness and food, mostly US. It used to go stale within weeks, so every pitch started with someone re-checking handles by hand, and client decks carried follower counts from last quarter. Now the roster sheet is connected to Zaver once, a Profile metrics run is scheduled every morning at six, and formulas flag drops, private or renamed accounts and engagement below the floor.
Read the case study →How the stories are built
From the session
Each story is reconstructed from the customer's working session, step by step, with permission. Scene images are renderings of the redacted messages, never screenshots of the original thread.
What is redacted
No creator names, handles, emails or quotes. No brand names, client budgets or markups. Numbers that stay are the ones the session itself shows.
What you can copy
Every ask on a page is the one that was typed. Copy it and run it with Zaver connected at /mcp, or follow the linked playbook.