Inside Our Lunch and Learn with ProcurePro: Closing the Gap Between Individual AI Wins and Team-Wide Adoption

<p>The pattern shows up across nearly every team we work with. One person figures out what their AI tools - Claude, ChatGPT, Copilot, whichever the team has rolled out - can really do. They build something useful for themselves: a prompt they reuse, a workflow they’ve tuned, an internal tool that compresses an hour into ten minutes. And there it sits. The build doesn’t travel. The rest of the function never sees it, never adopts it, never compounds on it. The function leader - head of CS, GTM, finance, ops, people - can see the early wins but doesn’t have a clear way to turn them into a team capability.</p><p>That’s the gap a Solaris lunch and learn is built to close.</p><h2>Why ProcurePro brought us in</h2><p>ProcurePro is a construction procurement platform used by some of the largest builders and developers in Australia and globally. The session was run virtually across the company - from Customer Success, Sales, Operations, HR, and Engineering, spanning individual contributors to executives.</p><p>ProcurePro wasn’t a team starting from zero. Claude was already the centre of gravity, leadership was actively encouraging adoption, and members of the team had been building useful things for themselves. What hadn’t yet happened was the next move - turning individual capability into team capability, taking what one person had built and getting it in front of the rest of the function. That’s exactly the kind of question a Solaris session is built to answer.</p><h2>What was different about this session</h2><p>The room arrived with working knowledge of AI tools and a real installed base of personal use. With Customer Success and Sales heavily represented, the foundational walkthrough wasn’t where the value sat. We swapped in case studies built around GTM teams running AI in production - companies operating customer success and sales motions on AI at meaningful scale, not as pilots - and reframed the product walkthrough around where each part of the Claude product surface earns its place in a stack the team was already operating.</p><p>The build portion was shaped around what the room kept pulling toward in live Q&amp;A: pre-call prep, post-call follow-up, and meeting transcript handling. Those were the workflows the team wanted to scope and build, so that’s what we built and scoped.</p><h2>What your team walks out with</h2><p>By the end of the session, your team will have:</p><ul><li><p><strong>A clear map of the full Claude product surface - or whichever AI platform your team is using</strong> - what each tool does, when to use it, and where each one fits into their existing workflow.</p></li><li><p><strong>Three live case studies in their function</strong> - concrete, current examples of how teams like theirs are using Claude in production right now.</p></li><li><p><strong>A working skill, built end-to-end</strong> - either by them or watched built, so they walk out understanding skills as the primitive that turns Claude from a chat tool into a system they can compound on.</p></li></ul><p><em>Workshop sneak peek — State of AI section</em></p><div class="captioned-image-container"><figure><img height="716" width="1456" src="https://substackcdn.com/image/fetch/$s_!3Ex6!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff46e9786-b567-4f51-9b3a-5f4915e43059_1980x974.png"></figure></div><p>The Lunch and Learn is the entry point. Behind it sits the full Solaris programme - AI capability assessment to baseline where the team actually is, targeted upskilling, and ROI measurement to capture what’s changing month over month. The session is the door; the programme is what’s behind it.</p><h2>When one build made the next one obvious</h2><p>The most useful moment of the session came from outside the function the workshop was tailored for. The room was Customer Success and Sales-heavy. The first concrete build came from an engineer, sitting in on a session aimed at his GTM colleagues, who had quietly built something while the conversation was happening. He’d taken a pre-call preparation workflow - pull the full account history from their CRM, structure the line of questioning around their sales methodology, cross-reference to actual prior conversations on file - and shipped it inside the build portion of the session.</p><p>The shift wasn’t “look what an engineer built for sales.” It was that the build made the unbuilt versions visible to the rest of the room. Within minutes, a member of the sales team had scoped the next workflow on top of it - pull the transcript from a customer call, run it against the same sales methodology, draft the follow-up email in his tone, leave a reviewable draft ready in his inbox. The pieces were already in the stack. What was missing was the picture of how they fit together.</p><p>The shift in the room wasn’t about what an engineer had built. It was that watching one workflow ship made the unbuilt ones legible. The team had been sitting on the same raw material - connectors, transcripts, a tone of voice, a sales methodology - without yet seeing them as components in a single picture. One build made the picture visible, and the next workflow scoped itself.</p><h2>What they took away</h2><p>The part the team named most valuable was hands-on build time with facilitator support - the working portion of the session where individual workflows got scoped and prototyped in real time, with the skills deep dive close behind. The pattern across responses was consistent: members of the team wanted more of the building, and wanted to take what they’d seen built back to their own functions.</p><h2>Book a session for your team</h2><p>We’ve run six sessions like this in the last month with teams across enterprise software - from GTM and customer success through to finance, ops, and people. We run them across Claude, ChatGPT, and Copilot, whichever stack your team is on. Each one is shaped around where the team actually is and what their function actually does.</p><p>Tell us where your team is. <strong>We’ll come back with a session designed around it - and a 30-minute call to scope it.</strong></p><p><strong><a href="https://solaris-signup.buildclub.ai/">Book a 30-minute scoping call</a></strong></p>