A profile that turns a visit into a follow
From a recommended post people land on your profile and decide in seconds. A 150-character bio and a pinned post built for that decision.
Текст промта
Put together my Threads profile: bio and pinned post. What I do: {occupation} What I'll be writing about: {2–3 topics} Who for: {audience} How I differ from others in this niche: {experience, numbers, point of view} What someone gets by following: {specifically} People arrive at the profile from the recommendation feed and decide in a couple of seconds. The bio is 150 characters, and that is all you get. Give me: 1. Five bio options under 150 characters. Each must make clear what the profile is about and why you specifically. No "coffee and travel lover", no list of credentials. 2. For each option — who it suits and who it doesn't. 3. A pinned post under 500 characters: who you are, what will be here, and one example of your usefulness inside the text itself — not a promise, but something useful right away. 4. Three topics for the first posts that will make good on the bio's promise. If the bio promises breakdowns and the first posts are about breakfast, people unfollow. Separately, tell me if my answers don't show any difference from a hundred similar profiles — and what to put up front in that case.
У фігурних дужках — те, що треба замінити на своє.
Приклад результату
Bio (129 characters): "4 years selling on marketplaces, 6 stores now. I write about honest unit economics — including my own million-dollar mistakes." Who it suits: people already making sales. A beginner won't see themselves — for them, option 3 works better.
Схожі промти
The first line decides everything: on a phone only about 90 characters show before «more». Hooks are written to that limit.
Write 20 opening lines for Threads posts on the topic "{topic}". Audience: {who} My role: {who you are to them — practitioner, seller, observer} Hard limits: — No line longer than 90 characters. That is what shows in the feed before someone taps "more"; anything past it goes unread if the first part didn't land. — No "Did you know that", "Top 5 ways", "Here's a roundup" — these read as templates and get scrolled past. — No caps lock, no emoji chains. Give 4 groups of 5: 1. Personal experience with a specific number or timeframe. 2. Disagreement with received wisdom in the niche. 3. An observation the reader recognises in themselves. 4. An open question they have something to answer from their own experience. After each line, in brackets, say what reply it is built for. If the only possible reply is "agreed" — rewrite it: that hook collects likes, not conversation.
Показати приклад результатуСховати приклад
Personal experience: "Posted on Threads daily for six months. First four months: about 30 views each." (expecting: "so what changed in month five?") Disagreement: "Posting at the best time is advice that will do nothing for you. Here's why." (expecting: pushback from people who believe in timing)
Replies are the strongest signal in the recommendation feed. This post is assembled so people want to write, not silently like.
Write a Threads post on the topic "{topic}" designed to pull replies. What I know about it: {your experience, facts, numbers} Audience: {who} What I want to hear in the replies: {e.g. how other people solve this} Rules: — No longer than 500 characters, that is the platform limit. 300 is better. — The first 90 characters must work as a standalone hook; the rest is what people unfold themselves. — End on a question the reader already has an answer to from their own experience. Not "what do you think?" but something specific: their case, their number, their choice. — Leave a place in the text where the reader can disagree. A post everyone agrees with gives nobody anything to say. Don't do this: — "Tell me in the comments!" — a direct ask works worse than a question people simply have something to say to. — Don't invent provocation for the sake of an argument. A fight collects replies once, and then people unfollow. Give 3 versions of the post and, under each, what kind of reply it is most likely to collect.
Показати приклад результатуСховати приклад
Version 1 (298 characters): "I let go of the strongest person on the team. He was right more often than anyone — and that was the problem. He didn't argue, he explained. After a few of those explanations people stopped offering their own ideas — why bother if you'll turn out wrong anyway. One strong voice can quietly switch off everyone else. Has this happened to you, and how did you handle it?" Will collect: stories about people's own "too-right" colleagues, and an argument about whether letting them go was right.
The feed watches speed: 20 replies in half an hour push a post further than 50 over a day. A plan for that window.
Draw up a plan for the first 30 minutes after publishing a Threads post. Post text: {paste the post} Topic: {what it's about} Who I am in this niche: {role} Fo
Промт входить до PRO-добірки
Відкрити доступA link in the body sends people off-platform, and the feed accounts for that. The scheme: the post stands alone, the link comes as the first reply.
Split my link into a Threads post and a first reply. Where I'm sending people: {URL and what's there} Who needs it: {audience} What they get by clicking: {spec
Промт входить до PRO-добірки
Відкрити доступ