This week we built a full week of social posts for a client with one goal: get more comments. One idea was genuinely strong. Invite the architects in the audience to comment a single word, and in return we'd send them a real set of project drawings from a past job. It's the kind of hook that stops a scroll. It's also the kind of marketing promise you can't deliver until you check a few things — and that's exactly where we stopped, before it ever went out.
The hook that outran the asset
The offer worked on paper. Comment a keyword, get something valuable and specific back. That's a clean trade, and the right audience would take it.
Then we went to line up the actual thing we'd be sending. And the problems stacked up fast.
- Nearly every file was saved under a real customer's name — names, job numbers, sometimes an address, right in the filename.
- Some of the documents in those folders weren't even ours to give away. They were sent to us by other companies.
- There was no clean path from "someone comments" to "someone receives it." Every reply would be a person doing manual work.
So a great hook was suddenly attached to something we couldn't hand over safely. The idea was fine. The delivery was a trap.
What makes a marketing promise safe to make?
A public offer is a debt. The second someone takes you up on it, you owe them the thing — on time, and clean. If you can't pay that debt, the hook doesn't build trust. It burns it.
This is easy to miss when you're excited about an idea. The idea lives in your head, where everything is simple. The delivery lives in the real world, where files have owners, and a "yes" from a stranger becomes work you didn't plan for.
The lesson isn't "play it safe and offer nothing." It's the opposite. Make the bold offer — right after you've made sure you can keep it.
Three checks before any public promise goes out
Run these three questions before you post an offer, a giveaway, or a "comment for X" hook. If any answer is no, fix it first.
1. Do you actually have the thing?
Not "could I make it." Do you have it, finished, in hand, today? A promise built on something you still have to create is a deadline you gave a stranger.
2. Are you allowed to give it away?
Is it yours to share? Does it contain a customer's name, private data, or someone else's work? If a lawyer or a client would wince at it going out, it's not ready.
3. Can you deliver it when the replies come in?
Ten replies is a good day and a small headache. A hundred replies with no system is a promise you'll quietly break. Know how the "yes" turns into delivery before you ask for the "yes."
The fix wasn't to kill the idea
Here's the fix we put on the table. Instead of scrambling to scrub a real client's files, build one purpose-made version — a real detail from a real project, redrawn clean, with no customer name, no address, nothing private. A few hours of work, once.
That version is honest ("a real example from a project we built"), it's safe to send a thousand times, and it removes the risk permanently. Same bold hook. None of the exposure.
The offer that stops the scroll is only worth making if you can keep it — so build the thing you're promising before you promise it, not after the replies start coming in.