All case studies
Enterprise SaaS · Discovery
How a 1,000-person SaaS company figured out if switching to Claude was worth it
A 60-person partnerships team was paying for a Gemini contract that wasn't working. We ran a discovery session and scoped a workshop to show them exactly what Claude could do for their real workflows.
The problem
The MD of Global Solutions at a 1,000-plus employee SaaS company ran a 60-person team across partnerships, technical sales, and enablement. The company moved from Microsoft to Google and landed on Gemini. It was not working. Slides generation broke constantly. Document reasoning was weak. Engineering was already on Claude for code. IT and security would make the final call. The question was whether a switch was worth it and how to actually get it approved.
What we built
- The team knows exactly where Gemini is failing them. We mapped every gap between the current Gemini setup and Claude for Work. Slides generation broken, weak document reasoning. Concrete findings, not vague impressions.
- The partnerships team can see Claude working on their actual tasks. We scoped a live workshop with demos on partnership-deck generation, deal-room synthesis, and partner-call prep. Real workflows, not a generic tech pitch.
- AI stops being a chat window people forget to open. We designed a Lindy layer on top of Claude for Work. Claude handles the thinking. Lindy triggers on emails, calendar events, and Slack messages automatically.
- IT and security have a clear path to say yes. We mapped the approvals needed: data residency, SSO, audit logging. The rollout sequence. The political considerations. Enterprise migrations fail on this step. We did the map.