Buffer

Hey ya'll! 👋🏽 What has helped you find your community on LinkedIn?

Not many people know, but I started my career working with nonprofits, including incredible organizations like Parkinson Canada, Canada Organic Trade Association, and a few others. That gave me firsthand how important the work these teams do is, but also how often it's done with limited time, budget, and headcount. That’s part of why I’m proud that at Buffer, we offer 50% off for qualifying nonprofits on every plan, for life (on top of our generous Free plan). Social media can be a powerful lever for nonprofit teams. It can raise awareness, mobilize supporters, and support fundraising. But often, the people managing it are also juggling a dozen other responsibilities. That’s why I love seeing nonprofit teams use Buffer. Thousands around the world already trust us to help them share their mission and show up consistently online with less effort. And as another values-led, small team trying to do good, while doing well, we are here to support small teams doing meaningful work however we can. If you’re part of a nonprofit team, you can learn more about the offer at buffer[dot]com/nonprofits (🔗 link in the comments)

One of the most common questions we hear is simple: “When should I post?” The honest answer has usually been: it depends. Check your analytics, test a few times, and keep iterating. 😅 That works, but it is also a lot to carry, especially when you are managing multiple channels or trying to stay consistent alongside everything else. 💙 In his latest post, Brandon Green, our Staff Product Manager, shares how we are starting to make social data feel more helpful inside Buffer! We are beginning with Smart Scheduling: recommended posting times based on platform patterns, with the option to customize anytime. 🥳 Would love to hear what kind of insights would make the biggest difference in your workflow! ⬇️ 💬 🔗 Full scoop: https://lnkd.in/eePBCaQY

Well, would you look at that... I reached a 20 week posting streak on Buffer! 🎉 😉 #consistency #executiveassistant #accountability

Buffer's API is now in Public Beta. That means Buffer can start to live inside the tools and workflows where writing and creating already happen. 👏 Right now, in beta, you can create and schedule posts, build automations, and connect through our MCP server with tools like Claude, Raycast, or Zapier. It's early, and we're building it alongside the people using it, eager for feedback before we launch more fully in April. If you've ever thought, "I wish Buffer could just connect to X," now's the time to find out if it can. ➡️Go to settings in Buffer, and you'll see the API tab. If you start building something, I'd love to hear what you're making.

"What do I even post about?!" If that question has been holding you back, this one's for you. 🥞 Kirsti Lang, one of our senior content creators, has a little hack that will help you solve that problem. It involves podcasts, pillars, and pancakes (bear with us here). Here's how to find your content pillars — the topics you can talk about with real authority, and how to connect them so your content feels cohesive and follow-worthy. What are your pillars? 👇 We'd love to know what niche/s you're building in! P.S. This clip is part of our bumper LinkedIn creator course on YouTube (if that sounds like it might be up your alley, hop over to the 🔗 down below.

The Buffer API and MCP that just entered beta have me really excited. It's still early, but it already feels like a game-changer for creating and scheduling content. Here's what's shifted for me: the creation process is no longer a separate activity. It's integrated directly into my daily work and the projects I'm tinkering with. I'm not context-switching between the web app, the mobile app, and whatever else I have open. Everything just flows. And this is just the beginning. I'm genuinely curious to see how others use and build on the Buffer API. The potential is huge, and we're only scratching the surface. Have you started to think about how you would go about including the creation process directly into your existing workflows?