Buffer

I just hit 52 straight weeks of posting through Buffer. A full year of showing up. And the biggest thing I learned wasn’t how to write better hooks, chase trends, or outsmart the algorithm. It was this: Consistency is rarely a motivation problem. It’s usually a systems problem. I didn’t suddenly become more disciplined. I built a process that made posting easier: • Capture ideas before they disappear • Draft when the energy is there • Schedule before the week gets chaotic • Study what connects without letting one bad post ruin the plan Some posts took off. Plenty didn’t. But publishing every week gave me something more valuable than a few viral moments: enough evidence to understand my own voice, my audience, and the ideas I actually want to be known for. I’m still experimenting. Still adjusting. Still curious about why one idea travels while another barely leaves the driveway. But after 52 weeks, I’m convinced the creators who last aren’t necessarily the most inspired. They’re the ones who build a system that keeps working when inspiration clocks out. Here’s to week 53.

We've shipped a LOT at Buffer over the last few months: The public API, CLI and MCP integrations The new home screen Insights Support for more channels in Community Custom templates Custom saved views Alt text generation Lots of little refinements My question to the crowd: How is it all feeling? What do you love? What could we have made a bit better? What still feels missing to you? I'd love to hear it all

We're hiring a Senior Infrastructure Engineer at Buffer! 🎉 We're on a mission to help the next 200,000 creators and small teams build their brands. This role is foundational to making that happen. You'll join our small infrastructure team to own the systems every Buffer engineer ships on: production reliability, fast and safe deploys, and the internal developer tools that make building at Buffer a joy. Every feature we ship moves through infrastructure you'll run. This is a hands-on role where you'll: - Own the reliability of our production platform, end to end - Build deploy pipelines the rest of engineering trusts, with rollbacks measured in minutes - Evolve our internal developer tools so shipping stays fast for humans and AI agents alike If you treat infrastructure as a product with users, and you've felt the difference between code that ships and code that gets used, we'd love to hear from you. 🌍 Fully remote 📅 4-day work week 💙 Values-led, transparency-first culture 💰 $164,595 – $212,744 USD + equity 🔗 Apply: https://lnkd.in/dSDdKH5v PS: Know someone who'd be perfect? Please tag them in the comments!

Interviews ask candidates to show up with thoughtful questions about a company they've mostly seen from the outside. We started sending the answers first! When we invite someone to a first interview at Buffer, they get a role-specific Q&A doc along with the invitation: - who they'd report to, - what the team is working on, - how the 4-day workweek plays out day to day, - compensation, benefits. The questions people usually save for round three, answered before round one. We started this in engineering, and the candidate feedback was warm enough that it's now part of most of our open roles. It takes some upfront work (and a willingness to admit the doc is never quite finished), but the conversations that follow go deeper. Candidates ask about specific projects and what's hard for the team right now, and we get a truer read on each other. 💙 Kateryna Porshnieva, our Director of Product Engineering, recently shared how she puts these docs together on the Buffer blog, including a free Notion template you can copy for your own team! 🔗 https://lnkd.in/dYp2FRKQ

I had a chance to chat with Emily Kramer from MKT1 recently about how marketing teams can build with AI together instead of in silos. The teams moving fastest are the ones that get past single-player AI workflows and into multiplayer mode. And what makes that work is shared context. Our AI marketing system at Buffer comes down to two core layers: - Capabilities are what the system does. Skills, workflows, reusable prompts, reference files. The things that actually produce the work. - Context is what the system knows. Strategy, positioning, ICPs, funnel definitions, voice. The knowledge base a session starts from, so it isn't working from zero. Most teams jump straight to capabilities. The instinct is "how do I build a workflow that replaces what I'm doing today?" and they skip the contextual layer entirely. The problem is a workflow without context is running at maybe 60% of its potential. Your business context is what makes the output relevant and genuinely useful. So how do you build shared context and distribute it through an AI-pilled org? Emily, and others, are going deeper on just that in a new MKT1 series. I left the link to part 1 in the comments 👇️ ~Sent with Buffer~

Ever wanted to see your content calendar on an actual *calendar*? Ever wanted to integrate your social posts into your website or newsletter? Well, I built another thing for that! It's called Social Sindy. The easiest way to turn your social content schedule into an RSS feed or calendar integration 🗓️ 📡 All powered by the Buffer API 💁♂️ Just sign in with your Buffer account, create a feed of either type, choose which social channels and types of posts you want in the feed, and plug in the resulting feed wherever you want to use it. I was inspired by my recent explorations into RSS and other open formats. I have already found it useful to quickly spot-check on my calendar what posts I have scheduled for the upcoming week, and I even set up my RSS news reader with a feed so I can casually scroll through posts I've made in a nice, minimal reading interface. Try it out (link in comments) and let me know if you have any feedback!

You don't need 11 analytics tools. You just need one you'll actually open. Buffer just rounded up the best social media analytics tools of 2026, and here's the part worth remembering: the built-in insights on each platform have real gaps. (I'll link their findings below!) Instagram tells you one story, Facebook another, LinkedIn a third, and none of them talk to each other. So you hop between apps, screenshot numbers, and still can't answer the only question that matters: is this working? For most small businesses, one tool that pulls everything into a single view beats a fancy stack you never check. But here's my rule before you buy anything: a tool shows you numbers. It can't tell you what they mean for YOUR business. Decide what you're measuring for first. Then pick the tool.

This LinkedIn post is very different from the one I started out with. I was writing about how I wished I'd created a changelog when I built my LinkedIn Content Library app. A changelog would document how I work, how I iterated on the app, and show the app's growth. It would also let me reflect on the decisions I made, what was important to me at different times, and how much time and effort I spent on it in a given month. It's a story, and the storyteller in me can't resist one 😊 I wrote the whole post. It even said: "I've built it in Lovable, so it would have been easy enough to do — anytime I make any major edits, just ask Lovable to add it to the changelog." And I had a lightbulb moment. Lovable already has the app history. Could it create a changelog for the entire app from v1 to now? So I asked, and it did 🥳 I started out wishing I had a changelog. That's exactly what I ended up with. If you'd like to see how the app has evolved, here's my changelog from where it started to where it is now: https://buff.ly/b034yqJ And if you'd like to read more about the app, I wrote about it for Buffer: https://buff.ly/O0aKyQt

Three years ago, I wrote an article for Buffer about what I learned in my first year of taking my side hustle full-time. I reread it recently, and I thought it would be interesting to revisit the same points here with the context of three more years in business. Here's what I thought back in year one vs. what I think now! 1) On working vacations What I thought then: “work from anywhere” sounded better in theory than it felt in practice, and working vacations mostly meant combining the less fun parts of work with the less fun parts of vacation. What I think now: I still partly agree, but I’ve softened a little. Sometimes a working vacation is better than no vacation, and I do get more time doing fun things if I let some of them spill over this way. I still make sure I have some true vacations where I’m actually offline, but I don’t mind working from other places as much anymore as long as I know it’s going to feel a little different. 2) On non-linear growth What I thought then: once the early wins wear off, growth gets bumpier, and looking at the business month to month makes normal fluctuations feel much scarier than they are. What I think now: I still track growth quarterly instead of monthly and try not to put too much emotional weight on any one month. Seasonality is obviously real, and AI has made those fluctuations feel even more dramatic at times, but I’m still tracking up overall, which is what I care about most. 3) On wellbeing as a business asset What I thought then: rest wasn’t something to tack on later once I’d earned it. If I wanted the business to be sustainable, it had to be built in from the start. What I think now: I still completely believe that. I also think this is probably the one I’ve had the hardest time fully putting into practice. I’ve gotten sick a lot this year, and it’s been a reminder that believing something and building your life around it consistently aren’t always the same thing. This is still an area where I know I have work to do! 4) On ditching the 9-5 What I thought then: trying to force myself into a traditional workday just because it looked more legitimate was making me less productive. I worked better once I stopped treating 9-5 as the default I had to replicate. What I think now: I’ve mostly just doubled down on this. Thankfully, I work with a team that’s pretty flexible, so most days I work from around 7 to 3, take a nap almost every afternoon (!!!), and then do another chunk in the evening. It works so much better for me than the "typical" structure. All in all, it was nice to reread something older and realize I still agree with the version of me who wrote it. I don’t think I’d write the original article the exact same way now, but I do think I’d land in pretty much the same place. I'm curious what other people have found here, too - what still feels true a few years in, and what feels more nuanced now?

For months now, we've been building our AI fluency as a support team. Now we are also focusing on a different question: how do we become better writers? The other week, my colleague Dave Chapman and I got into a discussion about our writing skills. Since I joined Buffer, writing has been central to how we do support, but now with so much AI-generated content, it feels even more crucial to flex our writing muscles. Here's why both are so important going forward. 👇️ AI helps us with everything behind a customer support reply. The troubleshooting, digging into code, and pulling the context that enables us to reply faster and more personally. It gives us a stronger foundation to stand on when a customer wants to speak to a human. And when they do, we want it to be clear they're chatting with a real person. The support experience should feel like our customers are sitting across from us at a desk. Our words are an extension of us, and it's how we can ensure our customers feel looked after. There's something really nice about returning to the fundamentals of customer support. Paying attention to the actual words we use, one message at a time. We are even nudging the team to explore writing courses with their growth stipend 📖 I'd love to hear if others are exploring the same!