Everyone knows "comment the code word" grows your Instagram, most people setting it up skip the one step that actually does that
Hi Indie Hackers, small story from the last few months of talking to clients.
Everyone already knows the trick, you've seen the reel a hundred times. "Comment KEYWORD and I'll send you the guide." Not new, not a secret, it's one of the most reliable ways to grow on Instagram right now, and honestly that's exactly why it's everywhere.
What caught me off guard was watching people set this exact thing up on Mavibot. I kept expecting them to configure it the way it's supposed to work, comment gets a check, check confirms you're following, then you get the file. Instead most of them just wire the comment straight to the file. No check, no gate, nothing. Anyone types the word, they get the guide, follow or not.
Which means they've rebuilt the famous "comment for a gift" thing and quietly removed the one part that makes it a growth tactic instead of just customer service with extra steps.
I asked a couple of them about it directly. Nobody did it on purpose. They'd seen the tactic work for someone else, copied the visible part (post a reel, ask for a comment, send a file), and never noticed the invisible part doing the actual work underneath. It's a little like watching someone copy a recipe and skip the yeast, then wonder why the bread's flat, the trick still looks right from the outside.
The ones who do wire up the check see the follower jump everyone talks about. The ones who skip it get comments, sometimes a lot of them, and a follower count that just sits there.
If you're curious what the setup looks like, it's here:
Still not sure if this is a docs thing on our end or just people trusting a format enough to skip understanding it. Anyone else run into users nailing the surface of a tactic and missing the mechanic holding it up?
—Gadaev Sam
You found that people consistently reproduced the visible workflow while missing the mechanism that actually creates the growth outcome.
What would convince you that this is primarily a product design problem rather than a documentation or education problem?
Thanks for the comment, and yeah, we already landed on this being a design problem, not an education one. We built the mechanic assuming people would use it for this exact case, that was our mistake, not theirs. Docs had a gap too, we never really pushed this specific mechanic front and center, fixed that since. Hoping it sticks with new users going forward, we'll see.