Social mediaCAN I VIBECODE
Loomly?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Loomly is a social media management SaaS founded in 2015, headquartered in New York, with $7.2M funding. It provides per-brand content calendars, a Post Builder with channel-specific optimizations, automated publishing and near-native posting, custom approval workflows and roles, real-time collaboration/commenting, labels and templates for campaign organization, hashtag manager and post ideas (including X trends), RSS-triggered auto-posting, advanced analytics with PDF/CSV export, Loom.ly link shortener, and a unified inbox for comments/messages/DMs with assignment and saved replies. Integrations include Slack, Microsoft Teams, Google Drive, Unsplash, and Canva. Pricing plans scale by number of social accounts, users, and calendars (Starter to Enterprise, with AI Assistant on paid plans).
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a focused replacement for Loomly, the social media planning/collaboration platform. Do not copy Loomly's brand, logo, or visual UI. Core workflow: A brand team plans posts on a shared monthly calendar; a creator drafts posts with channel-specific preview/optimization tips; reviewers comment and approve; an admin schedules and auto-publishes via platform APIs; community managers handle incoming comments/DMs in a unified inbox; analysts view performance metrics and export reports. Requirements: user authentication with roles (admin, creator, reviewer, client); per-brand calendars; post editor with title, body, media, channel target, scheduled time, labels, hashtags; post lifecycle states (draft, in-review, changes-requested, approved, scheduled, published, failed); commenting per post; approval workflow configuration; unified inbox with conversation assignment/archiving; basic analytics dashboard (impressions, engagements, clicks) and CSV export; integrations with Slack/Microsoft Teams notifications and Google Drive/Unsplash/Canva media pickers; webhook receiver for platform publish confirmations. Implementation approaches: Next.js (App Router) frontend, Node/Express or NestJS API, PostgreSQL with Prisma, BullMQ/Redis for job queues, S3 for media storage, OAuth for social platform APIs, Tailwind CSS. Out of scope: native mobile apps, AI assistant, post-sponsoring/ads features, RSS auto-generation, multi-language i18n, SSO/enterprise SAML. Write a README explaining setup (env vars, database migrations, seed data), architecture overview, and important limitations (API rate limits, no production-safety guarantees, per-platform approval differences).