Ben Campbell isn’t a software engineer by trade—he’s a marketer. But over the past few years, he’s done something most marketers only dream of: he built not one, but two fully functional apps that integrate with Buffer, a leading social media management platform. And he did it without writing every line of code himself.
His journey is a modern blueprint for how non-developers can leverage APIs, AI tools, and deep domain expertise to create real software products that solve actual workflow problems. The result? PostIQ and Receipts—two companion apps designed to streamline social media content creation and approval processes, both powered by Buffer’s public API.
From Marketer to “Vibe Coder”: How Ben Learned to Build Apps
Ben describes himself as an “advanced vibe-coder”—a self-taught technologist who understands enough about development to architect tools without being a full-stack engineer. His technical foundation began during two years working at a coding bootcamp, where he absorbed key concepts like file structures, API integrations, and authentication protocols like OAuth.
While he didn’t become a professional developer, he gained enough knowledge to collaborate with AI tools like GitHub Copilot and ChatGPT to accelerate development. Instead of writing every function from scratch, Ben focused on strategy, user experience, workflow design, and product vision—while using AI to generate boilerplate code and debug issues.
This hybrid approach allowed him to stay in his zone of genius as a marketer while still bringing technical products to life. His deep familiarity with social media workflows—honed over eight years of using Buffer for personal branding and client work—became the foundation for his first app: PostIQ.
PostIQ: Solving the Pre-Publish Chaos
Long before it was a public tool, PostIQ started as Ben’s personal productivity system. Like many content creators, he found that the work before posting—drafting captions, splitting long-form ideas into platform-specific threads, saving reusable hooks and CTAs—was scattered across notes, spreadsheets, and documents.
He wanted a single place to organize all of this pre-publish work. So he built one.
PostIQ evolved into a suite of tools focused on the creative phase of social media: ideation, drafting, structuring multi-post threads, and storing high-performing content elements. It’s designed for creators and teams who want to move faster from idea to publish-ready content.
Initially, PostIQ existed in isolation. Users had to manually copy drafts into Buffer. But everything changed when Buffer launched its public API.
With access to Buffer’s API, Ben could finally connect PostIQ directly to Buffer accounts. Now, users can:
- Draft posts in PostIQ
- Split long-form content into platform-optimized threads
- Schedule posts directly to Buffer
- Sync drafts and scheduling data in real time
- Eliminate copy-paste errors and redundant steps
Buffer remains the publishing engine, but PostIQ handles the messy, creative front-end work—giving users a seamless bridge from idea to scheduled post.
“The API changed what PostIQ could be,” Ben says. “It went from being a personal toolkit to a real product people could use in their daily workflow.”
Receipts: Streamlining Social Media Approvals
After launching PostIQ, Ben noticed another pain point: getting approvals. Whether working with clients, managers, or compliance teams, getting sign-off on social posts often meant messy email threads, Slack messages, or shared documents with unclear status.
So he built Receipts—a lightweight approval tool that integrates with Buffer to let users send posts for review with a single click. When a draft is ready, the creator sends it via Receipts, which generates a clean, branded review page with a timestamp and approval button.
Stakeholders don’t need to log in or learn new software. They simply click a link, view the post (with preview images and platform formatting), and approve or request changes. Once approved, the post syncs directly to Buffer for scheduling.
Receipts eliminates back-and-forth and creates a clear audit trail—critical for agencies, enterprise teams, and regulated industries. And because it’s built on Buffer’s API, it maintains a smooth workflow without disrupting existing publishing habits.
“I didn’t want to rebuild Buffer,” Ben explains. “I wanted to make Buffer better for specific use cases. These apps fill gaps in the workflow that Buffer doesn’t need to solve itself—but that real users face every day.”
Why Buffer’s API Was a Game Changer
Buffer’s decision to open its API wasn’t just a technical move—it was a strategic invitation to builders like Ben. By allowing third-party developers to create “powered by Buffer” apps, the company empowered a new ecosystem of tools that extend its functionality without bloating its core product.
For Ben, the API provided the critical missing piece: secure, reliable access to Buffer’s scheduling and posting functions. Using OAuth, PostIQ and Receipts
InfluencerBlogger
