PostsHQ is a distribution tool for teams. Scheduling, approvals, versioning, previews. Built for people who treat distribution as a system, not a habit.
I design and ship it in code. No Figma handoff. Staging link over prototype.
// Device switching — resume where you left off.## Problem
Teams don't want to "manage social media". They want distribution. Posting is the mechanism. Most tools optimize the mechanism and forget the outcome.
The crowded market is crowded for a reason. These tools make money. But the fundamentals break in predictable places — posts fail silently, media degrades, approvals scatter across tabs.
Reliability before intelligence. AI sits on top of a solid core, it can't replace one.
// Groups — organize accounts into logical workspaces.## Approach
→ Teams are the primary mental model. Solo users are welcome, not the target. → Platform depth over platform count. → Reliability before intelligence. → Design in code. Ship to staging. Watch real usage. → No feature because a competitor has it.
// Hook bank — never start from a blank page.## Previews earned trust
Users were scheduling posts correctly, then hesitating before publishing. On calls: they weren't sure how media would render across platforms.
The fix wasn't more AI. It was making media handling explicit and predictable. Usage improved because the product felt safer, not smarter.
// Preview — see it the way the audience will.Confidence beats cleverness.
## Versioning
Iterate without overwriting. Every version is cheap to create, cheap to switch between, cheap to abandon.
The model: a post is a thread of versions. Scheduling locks one. The rest stay around as drafts you can A/B in your head.
// Version creation — zero-friction branching. // Version switching — instant.## What's next
Conversations. DMs, comments, mentions, replies — one surface. Most tools treat each as a separate feature. A conversation is a conversation regardless of where it happens. Clarity first, intelligence later.