RebrandOS
Connect your owned accounts, prepare posts once, and watch each one move from scheduled to published.
About RebrandOS
- Role: Founder, product designer and builder — research, UX, UI, frontend, backend and hosting.
- What it is: A web platform for publishing to the channels you own. Connect your accounts, prepare a post once, and RebrandOS carries it out — moving each piece through clear delivery states so you always know what is scheduled, going out, live, or waiting on review.
- Who it is for: Brands keeping every channel on-message, agencies running many clients from one desk, and creators who want to ship once and appear everywhere. The workspace lives at ops.rebrandos.com.
Publishing operations
A warm command room for posts moving across every owned channel.
The design centers on delivery state instead of vanity analytics. Operators can read what is scheduled, publishing, published, or waiting for review without opening a dozen tabs.
- Workflow
- Prepare once
- Visibility
- Four delivery states
- Workspace
- ops.rebrandos.com
The problem
Publishing across channels is death by a thousand tabs. Teams copy the same content between platforms, lose track of what actually went out, and discover failures only when a client asks why a post is missing. The work is not the writing — it is the coordination: preparing once, delivering reliably, and being able to see the state of everything without chasing screenshots.
What I designed and built
- Connect once: Users link the owned accounts they are allowed to post to, so preparation and delivery happen from a single place instead of platform-by-platform.
- Prepare once: A post is composed a single time and targeted at the connected channels, removing the copy-paste tax and keeping a brand consistent across surfaces.
- Visible delivery states: Every post moves through legible states — scheduled, publishing, published, and needs review — so a team can read the status of a whole queue at a glance rather than opening each network.
- Review the results: Once delivery completes, users can review what went out and where, closing the loop between “we planned this” and “this actually happened.”
Design decisions
- State you can trust: The core promise is honesty about delivery. Rather than a fire-and-forget button, RebrandOS makes each step observable, so failures surface early and nothing is assumed.
- Warm, operational, calm: A warm cream-and-orange system that feels like a workspace, not a dashboard toy — dense enough for operators, friendly enough for a small team.
- Built around ownership: The platform is scoped to accounts a team actually owns and is permitted to publish to, keeping the model clear and accountable.
Outcome
RebrandOS is live and browsable, with an operational workspace at ops.rebrandos.com. It collapses multi-channel publishing into one prepare-once flow with delivery states you can actually trust — designed, built and hosted end-to-end.
