Inside Our Lunch and Learn with Veridooh: When an Already-Advanced Team Discovers Skills

<p>The hardest teams to move forward aren’t the ones starting from zero - they’re the ones already using AI but not compounding on it. Everyone has access. Half the team uses it daily. But the work stays transactional: write this email, summarise this doc, draft this response. No one’s built anything that persists beyond the chat window. The tools are there - Claude, ChatGPT, Copilot, whichever the team has rolled out - but the infrastructure to make that work reusable isn’t. And the function leader - head of CS, GTM, finance, ops, people - can see the activity but not the leverage.</p><p>That’s the gap a Solaris lunch and learn is built to close.</p><div class="captioned-image-container"><figure><img height="970" width="1456" src="https://substackcdn.com/image/fetch/$s_!yRHc!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F24a779eb-6364-4b42-ae29-ddbf43e4cbd7_2048x1365.jpeg"></figure></div><h2>Why Veridooh brought us in</h2><p>Veridooh is the award-winning global leader in independent out-of-home (OOH) verification. With its proprietary SmartCreative™ technology, Veridooh independently tracks, measures and verifies the performance of OOH advertising campaigns. Headquartered in Sydney, with offices in London and New York, Veridooh’s clients include global brands such as Google, Amazon, Mercedes, Pepsi, Unilever, Sony and McDonald’s. The session brought together people from across the company: engineers, account managers, product leads, operations, finance, and design.</p><p>Veridooh wasn’t starting from zero. Members of the team were already using Claude daily - far ahead of the 20–30% baseline we typically see pre-session. The question wasn’t “what is AI” but “what can we do with this that we’re not doing yet.” 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 split naturally along technical and non-technical lines - engineers, sales, and product spread across both. We framed the session for non-technical teams (Cowork setup, hands-on builds), but the engineers stayed anyway. What started as a split agenda became a shared discovery: Cowork wasn’t just for non-technical teams. The engineers found it immediately relevant for their own workflows, and the cross-functional energy shifted the room from “learning a tool” to “what can we automate together.”</p><p>The other distinctive frame was the focus on what AI handles well versus where it breaks. For a team working across three time zones with high-volume, cross-functional work - structured synthesis, document processing, workflow automation versus judgment calls under ambiguity - that calibration mattered more than feature walkthroughs.</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="678" width="1456" src="https://substackcdn.com/image/fetch/$s_!J4BG!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc720c912-20c0-44a7-a538-6fe853c4cfa3_2040x950.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>The skills realisation</h2><p>The most engaging moment in the session was when the team discovered they could package repeated workflows under skills. For a group already using Claude daily, the shift wasn’t about learning a new tool - it was about understanding that the work they were already doing could become reusable infrastructure. Chat conversations could be saved, refined, and deployed as persistent tools rather than one-off outputs.</p><p>That realisation changed the frame. The shift wasn’t “now I know what Claude is.” It was “now I see how this compounds.”</p><div class="captioned-image-container"><figure><img height="970" width="1456" src="https://substackcdn.com/image/fetch/$s_!6FYH!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8599251d-f97c-4a83-aa6f-25a7f90cbe3f_2048x1365.jpeg"></figure></div><h2>What they built</h2><p>Five builds stood out during the session.</p><p>A finance team member built an overdue-email-reply skill. Any email sitting unanswered for 48 hours gets flagged, and Claude drafts a response. Simple threshold, immediate utility.</p><p>Someone built an email and Slack mentions checker - a single view of every place they’ve been tagged or cc’ed across both platforms, with an assessment of what actually needs action versus what’s informational. Context-switching between channels was eating hours per week.</p><p>A product team member prototyped an end-to-end workflow for capturing product feedback and insights - pulling signal from scattered sources and synthesising it into a structured format the team can actually use.</p><p>Another product lead built a skill that reads a Google Drive folder of product ideas, identifies the top 3–4 based on stated criteria, and drafts a pre-PRD document. What used to be an afternoon of manual triage became a 10-minute review task.</p><h2>What they took away</h2><p>The part the team named most valuable was understanding the Claude ecosystem end-to-end - products, features, and how they fit together. One Veridooh attendee wrote:</p><blockquote><p><em>“I’ve used Claude Code for skills and agents before - it was refreshing to see how to leverage Cowork for the same use cases.”</em></p></blockquote><p>Another said the biggest surprise was <em>“the fact that chats can be saved as skills.”</em> Members of the team estimated their new workflows would save them between 1 and 5 hours per week once deployed - not transformation claims, just compression of high-volume, low-judgment work that was bleeding time.</p><h2>Book a session for your team</h2><p>We’ve run eight 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/?utm_source=solarispage&utm_campaign=main_cta">Book a 30-minute scoping call</a></strong></p>