Library of what already ran
Every hook, body, headline and CTA as a Lego, with spend, CPA and ROAS across every ad it appeared in.
Creative library + editor desk
See which second of the ad made the money.
heybar is where finished cuts, reusable hooks, and live Meta numbers sit on one desk. Review what the editor sent. Keep what earned. Kill what did not.
Invite-only. Email one-time code — no password to remember.
277creatives on file
226copy blocks as Legos
5-ptretention, not a guess
In use on Doctor Trigger and Exquisite Song
— the same numbers the buyer and the editors already work from.
One desk for the people who make the ads, and the people who pay for them.
Spreadsheets remember spend. heybar remembers the hook, the cut, and whether it paid.
Review that lands in Linear
Watch the 9:16. Stamp a note at the second. Approve or send back. The editor is notified where they already work.
Performance without a second tool
Hook rate, hold rate, and Meta’s five-point drop-off — on the ad and on the part. Bonuses on performance, not speed.
From brief to live ad, in the order it actually happens.
This is a sequence, so it is numbered. Skip a step and the next person is guessing.
01
Ask for a brief
The generator reads live winners, what you have already tried, and any note you leave. A Linear issue lands on the editor.
02
Editor delivers in Linear
Full, hook, body, CTA as separate files. heybar picks them up. No Frame.io tab. No “which Drive folder.”
03
You review on the desk
Play the cut, timestamp the note, reuse a winning hook instead of a re-export. Approve moves it to Ready to Launch.
04
It runs. The library learns.
Meta numbers flow back onto the ad and onto each Lego. Next brief starts from what actually earned — not from memory.
Why buy five tabs when one desk does it.
The usual stack is a spreadsheet, Ads Manager, a review link, Linear, and Slack for “wait which version.”
| The usual stack | heybar | |
|---|---|---|
| Where is the hook that worked? | Buried in a sheet, if someone logged it | Searchable Lego with its ROAS |
| Editor feedback | A Slack thread and a timestamp in your head | On the frame, posted to Linear |
| Did this part beat the account? | Export, eyeball, argue | Hook rate vs account, on the part |
| Who can see it | Anyone with the link | Email OTP. If you are not on the list, you are out |
“Speed is visible. Bonuses are not paid on it. If a cut earned, it stays in the library. If it did not, we do not run it again and pretend it is new.”
How the desk is run — performance is the scoreboard, not delivery timeQuestions people actually ask before they sign in.
If your email is not on the allow-list, Sign in will not help. That is the point.
Who is this for?
Operators who pay editors on performance, and the editors themselves. It started as the desk for Exquisite Song, with Doctor Trigger’s history as the reference library.
Does this replace the ad buyer?
No. The Doctor Trigger autopilot keeps reading its spreadsheet. heybar is a one-way mirror of that history plus a native desk for new work. We do not move the buyer.
How do I get in?
An admin adds your email on the People tab. You sign in with a one-time code to that inbox. Shared links are useless to anyone not on the list.
Where do editors upload?
Into the Linear issue. heybar watches the team, mirrors the files, and puts them on the review desk. Editors never need a heybar account to deliver.
Can I trust the retention chart?
Meta only reports five checkpoints (25 / 50 / 75 / 95 / 100), never per-second. We draw those points and say so on the number. A smooth curve would be a lie.
What if I am not invited yet?
Ask the person who runs your product’s People tab. There is no self-serve signup on purpose — this desk holds live spend and unreleased cuts.
The next cut is already waiting.
If you have access, sign in. If you do not, this page is the whole tour — the desk itself stays closed.