LinkedIn thought leader ad examples

Why do folks with a technical background still outperform when using agents to build software? And how does this change as models improve? Engineers know when to pick option 3! Right now the best models seem to get things right 90% of the time - my rough guestimate. Perhaps 95% of the time in the good case. So if you hit 1 every time, you're letting error creep in every 10-20 executions. Sounds small, but it begins to accrete quickly. With our software factory at DevHawk, we see the difference among clients - and the most dangerous of all are the ones who think they are "developers" now. So they build complex features, merrily hitting 1 or just going full auto. The PR comes up for review. It's a bloodbath lol, maybe just a straight rejection. My take: over the coming year models will continue to improve, but they won't touch the magic line of perfection. And so having engineers around to help redirect them will be a good idea for some time to come!

I can’t believe I still need to say this in 2025… People who work in social shouldn’t be expected to wear every hat. Not everyone is a natural on camera. Not everyone is fluent in every editing platform. And not everyone can crank out content every single week. It’s exhausting and the more we hold social media managers to that standard, the less space we give them to grow in the areas they actually want to specialize in. Because let’s face it. You can’t become an expert in everything. No one can. Which is why when we find something that makes even one part of the job easier, we cling to it. And this is exactly how I felt when I tested out Descript, a video and audio editing platform with some insanely powerful AI features 🙂↕️ Studio-level sound without stepping foot in a studio (goodbye mini mic). Filler words removed in a single click. And the ability to move your script around like a Google Doc to shape the exact video you want. It’s perfect for your next talking head video. Give yourself your time back here: https://lnkd.in/gMcaNQ8Z #DescriptPartner

OCI Punch-out is voor veel B2B-bedrijven geen extra functionaliteit meer. Het is inmiddels een harde eis.🎯 Grote inkooporganisaties verwachten dat leveranciers direct kunnen koppelen met hun inkoopsysteem. Kun je dat niet? Dan lig je vaak al buiten de selectie voordat het gesprek begint. Toch zien veel bedrijven Punch-out nog steeds als een groot IT-traject. Dat hoeft niet. Met Conneqt realiseren we OCI Punch-out koppelingen in dagen in plaats van maanden. Juist omdat snelheid en onderhoudbaarheid steeds belangrijker worden in B2B e-commerce. Wil je weten hoe wij dit doen? Ga dan naar 👉 https://www.conneqt.io/

Veel bedrijven stellen integraties uit omdat eerdere koppelingstrajecten te duur, te langzaam of te kwetsbaar waren... Begrijpelijk ook! Vaak wordt alles volledig op maat gebouwd. En dan ontstaat bij iedere update opnieuw hetzelfde probleem. Wij van Conneqt geloven dat integreren slimmer moet kunnen. Met gestandaardiseerde connectors werk je sneller, blijven beheerkosten lager en voorkom je dat koppelingen vastlopen bij nieuwe versies van je systemen. Integreren hoeft geen langdurig traject meer te zijn. Wil je weten hoe wij dit doen? Ga dan naar 👉 https://www.conneqt.io/

⛵ BINGO ON A BOAT ⛵ Few people have ever been brave enough to try it! On Monday, a fearless cohort of Imperial alumni boarded the historic Golden Hinde to do exactly that. Founders, traders, scientists, doctors, operators, dealmakers and everything in between. The competition was fierce: Monday nights have never been done like this! Huge congratulations to the winners of the game Ovi Doke and to Julia Wiszniowska. 💰 And the winners of the best dressed award: Lantian Pinkney and Tom Bellingham. 👗 Link to all the pics are below.

🍹 You can now host events for your community on Clanmark. No painful sharing the link and adding email lists. Instant distribution and signups in your communiti(es). We released it last Friday, Wayne A. used it on Sunday and his event for Imperial alumni sold out in 48h! It is entirely free for now (except for the card processing fees).

Growth doesn't create new problems in a franchise network. It exposes the ones you were already absorbing. Most franchisors I speak to describe the same stretch. Somewhere between 10 and 40 locations, the things that always worked quietly stop working: - the answers - the consistency - the support - the onboarding None of it broke. It just stopped scaling. In my experience the reason is that all four were being held by people, not by systems. A founder who knew every franchisee by name. An ops manager who had become, in effect, a human FAQ. A regional lead who could hold the whole picture in their head because there wasn't much picture to hold. It works remarkably well, right up until it doesn't. And when it goes, it doesn't go loudly. Nobody rings head office to say the network has drifted. What actually happens is: - the same question gets asked five times, and answered five slightly different ways - a new franchisee gets a worse onboarding than the last one, for no reason anyone can name - someone quietly works around a process because finding the right one takes too long The brands I have watched come through that stretch cleanly nearly all did one unglamorous thing early. They got the operating knowledge out of a few people's heads and into something the whole network could actually find, before they were forced to. Not a better manual. Something a franchisee can search at 9pm on a Saturday and get the same answer everyone else gets. It is a shift in mindset from: "Who knows the answer to this?" to: "Where does the answer live?" Most franchisors postpone it, because it feels like admin rather than growth. In my view it is the highest-leverage thing a network does before it scales, and the most often done too late. The manual defines standards. It doesn't ensure execution. Whether the answer can be found, by anyone, without asking, is what does. For context, I build franchise operations software, so this is how I naturally think about it. The findable layer is rarely one thing. Product detail sits in a knowledge base, the rules in policies people have to acknowledge, the processes in forms and support desks, onboarding in a project plan. What makes it work is that they all live in one hub, and one search runs across the whole of it. The franchisee never has to know which is which. They ask, and the answer comes back. It is almost never what a franchisor arrives asking for. It is usually what does the most work. There is a second reason it matters more now than five years ago. Every franchisor I speak to is thinking about what AI could do across their network. But AI cannot reason over what only lives in somebody's head, or over five systems that do not talk to each other. The search across the hub can only be an AI search because everything is in one place. The networks that did the unglamorous work early are the ones that will actually be able to use it. #FranchiseOperations #FranchiseManagement #MultiSite #Franchising

96% of patient insurance eligibility checks in US healthcare are electronic. And yet eligibility is still one of the biggest causes of claim denials. After running these checks in production every day, we learned why this gap exists: the electronic transaction is answering the wrong-sized question. It can usually tell you: “Is this coverage active?” But providers need to know: “Can we treat this patient, for this service, under this program, with this provider, and get paid?” The gap is why so much eligibility work still happens across payer portals, spreadsheets, browser tabs, phone calls, and internal know-how. We wrote about why more APIs, RPA, and offshore headcount have not really fixed this, and how Champ is fully closing the gap now for our customers. https://lnkd.in/g_wRNhE2

A browser automation is only as good as its thousandth run. Production portals change. Sessions expire. Pages load in strange orders. Edge cases arrive without warning. Champ handles that complexity behind the scenes. Every workflow begins with a deterministic path, repairs itself when the interface changes, and brings in AI when judgment is useful. We own the outcome so you don't have to spend time battling broken bots. We wrote about what it takes to run browser automation reliably in production. https://lnkd.in/gxefxQRV

I’ve sat through a lot of calls where someone explains a genuinely complicated process, everyone nods along, and then afterward you’re left trying to turn hours of conversation(s) into a diagram that actually makes sense. For the Solutions Engineers, FDEs, and consultants in the room, this likely sounds familiar. ~6 months ago, Sean Hardy built Splash to solve for this internally at ClickUp. You give it a call transcript or recording(s), and it turns that into a Mermaid process map you can bring into a ClickUp Whiteboard and keep editing with the customer. It's been super helpful for ⬇️ - FDEs who need to understand the real technical flow, dependencies, and automation opportunities quickly - Solution Engineers who want to make discovery more visual without spending half the day drawing boxes and arrows - Implementation Consultants who need a solid current-state map before designing what the future state should look like Over the last few weeks, I've leveraged OpenAI's Codex to refine it to have better diagram alignment, deeper context on the agents/challenges/integrations, and a few other UX improvements. It’s not really about having AI make a pretty diagram. The useful part is getting to something tangible faster, so the conversation can move from “Did we capture this correctly?” to “How should we improve it?” Less time cleaning up notes. More time actually solving the problem. #SolutionsEngineering #AI #ProcessMapping #ClickUp

ClickUp's Solutions Engineering team is rapidly adopting an AI-native operating model. I asked Brain² to create an Artifact for me that shows how our SE team actually runs inside ClickUp (shared in the comments)! What came back was a scrollable walkthrough of the whole motion, from intake to technical win, with the deal record, the agent layer, and the operating system around it all in one place. Artifacts today can generate landing pages, slide decks, reports, interactive dashboards, and more. What gets me truly excited is where this is heading in the near future: 🔜 Versioned containers with git-like history, so every iteration is tracked and you can roll back to any prior version. 🔜 Live Artifacts that read real-time workspace data and stay current without anyone lifting a finger. 🔜 App Artifacts with full read/write access, meaning buttons, forms, and actions that mutate your actual workspace. Not a prototype, but a live application built from your work. 🔜 A browsable Artifacts Hub so every output your team or agents create is discoverable in one gallery, not buried in a chat thread. This is an early look at the Artifacts experience we've been building at ClickUp. #clickup #solutionsengineering #presales #artifacts

Everyone is talking about software factories these days. Inner loop vs. outer loop Model provider harness vs. third party harness Prompt caching strategy All important topics. Yet what holds large complex enterprises back is that writing code was always just the first step. Getting it all the way into product quickly, safely and securely is the real bottleneck. To truly accelerate software development in the enterprise, we need to remove not just the first bottleneck, but the second, third and fourth. Testing, releasing, validating.

Flaky tests were always an annoying problem. With agentic coding, it's 100x worse. You run many more builds and tests passing are the feedback loop your agent needs. With CloudBees Smart Tests, we can identify your flaky tests and allow you to quarantine them so they stop breaking your builds. Once you isolated them, you can focus on fixing those tests and if we observe that they stopped being flaky, we will automatically include them in your builds again. Read Jake's blog post to learn more. Fantastic new feature Naoto Samyak Yoshiori 👏 https://lnkd.in/gzhdAyhQ

I’ve had the chance to collaborate with Karthik Balakrishnan and hear him lead panels. Always a goldmine of first-hand insight on succeeding in the AWS Marketplace. In his current role, Karthik has been driving innovations that directly shape how cloud sales scale…from localized buying experiences and global expansion to co-sell motions, Buy with AWS, and now the frontier of AI-driven selling. That’s why I’m so excited he’s joining our panel on scaling marketplace revenue with co-sell, automation, and Agentic AI. Few people have a closer pulse on how AWS is changing the game and what ISVs can do to capture the opportunity. Here’s the link to register - https://lnkd.in/d-cZjYwz #CloudSales #CoSell #Automation #AgenticAI #SaaS #PartnerEcosystem

Wiz’s Amazon Web Services (AWS) Marketplace adoption and trajectory is the stuff of legend. AWS Marketplace Partner of the Year three years running, and now 100% channel-driven. Nadav Tzuker has always been one of Clazar’s go-to for marketplace expertise and sharp insights. Recently, I also bumped into Steve Vaughan, Wiz’s AWS Alliance Leader, and we got talking. I knew I had to pull him into the fold, and he’s agreed to join our panel for Growing Revenue Faster with Co-Sell, Automation, and Agentic AI. Who better to talk about something that’s on everyone’s mind right now, especially with the launch of AWS Marketplace’s hottest new category: AI Agents & Tools? This category represents a massive opportunity for sellers: ▶️It’s where cutting-edge AI meets proven marketplace procurement channels. ▶️It’s greenfield enough for new entrants to carve out serious share but already attracting big-name innovators. ▶️It’s perfect for buyers looking to deploy AI solutions faster using committed cloud spend. Steve, along with other incredible panelists, will share how to position, co-sell, and scale in this new frontier. 📅 Don’t miss this one. 🔗https://hubs.ly/Q03CwDwH0

“Just following up on this…” ⬇️ If that phrase lives rent-free in your Slack drafts, you’re not alone. As a Chief of Staff, your job is to keep things moving, WITHOUT becoming the nag, the bottleneck, or the person manually tracking 2️⃣ 6️⃣ one-off tasks across 5️⃣ different tools. 𝐁𝐮𝐭 𝐡𝐞𝐫𝐞’𝐬 𝐭𝐡𝐞 𝐭𝐡𝐢𝐧𝐠: 🧩 Most project management tools weren’t built for fast-moving exec teams. 🧵 Or for Slack-first companies. 🧠 And definitely not for Chiefs of Staff. That’s why I was excited to test out Chaser. ✅ Turns Slack messages into trackable tasks ✅ Auto-follows up (so you don’t have to) ✅ Works inside Slack—no new tabs or tools required After trialing it with my EA, I was able to spin up tasks, assign them, and keep things moving without needing a new tool, process, or training session. ✨ 𝐀𝐧𝐝 𝐭𝐡𝐞 𝐛𝐞𝐬𝐭 𝐩𝐚𝐫𝐭❓ The team didn’t even need to know we were using it. (Which, let’s be real, is the dream.) 🪢 Whether you’re managing cross-functional initiatives, wrangling exec follow-ups, or just trying to close the loop, Chaser helps you do the invisible work that actually moves the business forward. 📍Check it out: www.trychaser.com 💡 Mention "Clara" or "Ask a Chief of Staff" to upgrade to a 3️⃣ 0️⃣ day free trial (instead of the usual 1️⃣ 4️⃣) Let me know if you try it—I’m curious how other Chiefs of Staff are using it too!

🚨 DADO FRESCO SAINDO DO FORNO. Desde o ano passado aqui na Cloud Humans, rodamos um diagnóstico com 180+ empresas avaliando o potencial de redução da carga de suporte com IA. A análise é feita em cima dos últimos 30 dias de atendimentos da operação de atendimento. E o resultado é um raio-x de quanto a IA pode, de fato, resolver SOZINHA. O que encontramos de média nos principais setores analisados: 💻 SaaS → 59% dos tickets são totalmente automatizáveis 💰 Fintechs → 61% dos tickets são totalmente automatizáveis 🛒 E-commerces → 67% dos tickets são totalmente automatizáveis Ou seja: Em média, mais da metade do volume total de suporte nessas empresas poderia ser 100% atendido diretamente por um agente de IA. Sem passar por um humano. E não estamos falando de bot genérico, FAQ em árvore ou assistente que só responde “Oi, tudo bem?”. Estamos falando de uma agente que de fato EMULA UM SER HUMANO: - Treinada com seus tickets; - Integrada aos seus sistemas fazendo consultas e ações; - Respondendo como alguém do seu time; - E sabendo passar a bola quando precisa. Se você quiser saber HOJE qual o percentual da sua carga de suporte que poderia ser reduzido com IA, marque a pessoa do seu time responsável pelo acesso aqui nos comentários! *Condições para ser elegível: - Empresas que oferecem suporte via WhatsApp, chat, formulário ou email. - Ter pelo menos 1.000 atendimentos de suporte reativos mensais Para saber mais sobre a nossa IA para atendimento: https://lnkd.in/eVm4iy7S

🔎Você sabia que o CSAT médio de IAs nas empresas é de cerca de 60%? Aqui na Boca Rosa Company, nossa IA está superando essa média com resultados impressionantes. A Rosa, nossa IA desenvolvida pela Cloud Humans, é a primeira linha de atendimento. Ela responde dúvidas, fornece assistência imediata e garante que nossos clientes tenham a melhor experiência possível logo no primeiro contato. 🌟 E como medir a eficácia dessa tecnologia? A resposta está no CSAT, uma das métricas mais importantes para avaliar a satisfação do cliente com o atendimento. Os números falam por si: em janeiro, atingimos 82,90% de CSAT e, agora, em fevereiro, estamos com 80%. Esses resultados refletem o trabalho contínuo e o aprimoramento da nossa IA. Mas, o que está por trás desses números? Como conseguimos superar as expectativas dos nossos clientes? Aqui estão os pilares que sustentam esse sucesso: ▪️ Auditorias Diárias: Acompanhamos de perto cada interação para identificar pontos de melhoria e tornar a Rosa cada vez mais humanizada e alinhada às necessidades dos nossos clientes. ▪️Aprimoramento Contínuo: Com base nos feedbacks, ajustamos conteúdos, fluxos e processos, tornando cada interação mais fluida e precisa. ▪️Tom de Voz Consistente: A Rosa se comunica de forma autêntica e alinhada à nossa marca. Temos também uma parceria de sucesso com a Cloud Humans | Bruno Cecatto | Ian Kraskoff, que aprimoram constantemente a ferramenta e suas funcionalidades, garantindo que entreguemos o melhor aos nossos clientes. Alcançar um CSAT de 82,90% não é algo comum, mas sabemos que sempre há espaço para evoluir. Isso nos motiva a seguir aprimorando todos os dias. Estamos só começando, e os próximos resultados prometem ainda mais! 🚀 #AtendimentoAoCliente #IA #CSAT #Inovação #BocaRosa #CloudHumans #InteligênciaArtificial #TransformaçãoDigital

I still don’t know how my marketing team talked me into this. But here we are, every Clientell 𝗔𝗜 paid plan is $𝟬 till December 4th. 𝗬𝗲𝘀... 𝗲𝘃𝗲𝗻 𝘁𝗵𝗲 $𝟭𝟬𝟬𝟬 𝗼𝗻𝗲 😭 Just head to app.clientell.ai -> hit upgrade, and go absolutely wild. If this offer gets exploited, someone’s getting fired :) #Salesforce #AI #BlackFriday #ClientellAI #BlackFridaySale

We've been working hard on adding more analytics/insights for chats on Chatbase! We now have charts that show the topics and sentiment of all chats. So you can see what topics people are asking your chatbot about and how that changes over time. It works by running a cron job that analyzes all chats on your chatbots and determines the topics and sentiment of each one. Powered by GPT 4o-mini and JSON mode

Introducing our new integration with Stripe’s customer portal. Your customers can now manage their billing and plans, all within chat.

Thank you Forbes and Dara-Abasi Ita for the feature. The biggest barrier to AI adoption for most businesses isn't the technology itself. It's complexity. Most small and mid-market companies don't have the time, budget, or expertise to implement enterprise-grade AI systems. The winners won't just build the smartest AI. They'll build AI that businesses can actually adopt. Appreciate the opportunity to share our perspective. Link to the article is in the first comment.

Booking the first meeting has never been harder. Buyers are overwhelmed. Everyone has outbound. Everyone has AI. Everyone wants 30 minutes. So instead of trying to optimize outbound, we started optimizing the first impression. Rather than asking prospects to book a demo before they've experienced anything, we now generate a fully personalized AI experience from their company URL. It includes tailored messaging, industry-specific use cases, live voice and chat agents, and workflows built around their business, automatically and at scale. The goal isn't personalization for the sake of personalization, but to give our prospects the ability to see what it would look like for their company. The early results have been incredible. It's no longer just an SDR tool. We've rolled it out now across AEs, pre-sales, Customer Success, and upsell motions throughout the company. Curious what one would look like for your company? Comment your brand below, and I'll generate one for you.

I feared Shadow-IT as CIO - there were literal business processes running on employees’ PCs under their desk. But with what I learned at Calibo, I would now advise IT-Leaders to embrace it. The problem with shadow-IT: IT gets a conflicting mandate: be secure, compliant, cost-efficient, and innovative. Add the layers of technology and process complexity to that, and business units end up feeling IT is too slow. They start hiring their own talent to build their own solutions - often outside IT’s environments and guardrails. In most organizations, this leads to several problems: → IT leaders feel undermined and lose visibility into critical systems. → Business units create security vulnerabilities and unsupported solutions. → The organization ends up with duplicated efforts, compliance gaps, and innovation happening in silos instead of at scale. This frustrated me as CIO, thinking, “Why is the business wanting to do things that should be within the technology organization?” But my perspective on shadow-IT shifted when I started working at Calibo. I saw companies utilizing a self-service ecosystem that’s monitored, governed, and secure. Giving business units access to data and tools with proper guardrails - without them having to wait weeks for infrastructure tickets. Shadow IT is now becoming a competitive advantage: business can test proof of concepts with 10 users quickly within a certified environment. When solutions prove to work and need to scale to 5,000 people, IT steps in. Last year, I even gave a talk titled “Enabling business (shadow) IT: Why fight it? Embrace it!” at the Gartner IT Symposium. (See Photo) Because the question isn't whether shadow IT will happen, it's whether you'll enable it safely. Would love to get your perspectives on this!!