How to Engineer Virality on X

Your launch gets "congrats" from friends, a few likes from other founders, and then the conversation stops.

What exactly is someone supposed to add when they quote it? Open the quotes on a post that has taken over your timeline. Someone is explaining what it changes. Someone disagrees. Someone tried it and brought screenshots.

Each has found something worth adding. Their followers now have a reason to join a conversation they might otherwise have missed.

I've spent years helping tech startups get attention. When planning distribution, I want to know who would share the post and what they'd have to say.

1 - Give People a Reason to Quote Your Post

Think about the last thing you quoted. Maybe it backed up something you'd been saying for months. Maybe you knew a detail the author missed. You had a reason to put it in front of your followers.

Your own post needs to give someone that opportunity. Imagine you're launching a tool that turns spreadsheets into internal apps. "Excited to announce our new platform" leaves people with very little to discuss.

Show a messy inventory spreadsheet becoming a working app. Include what you started with, what the tool produced, and what you had to fix yourself.

• Now an operator can recognize their own problem.

• A developer can examine the result.

• Someone else can try it with a different spreadsheet.

Before publishing, ask yourself what a person who doesn't know you could add. If you're struggling to answer, include something more specific.

2 - Give the Same Post Different Angles

A quote needs its own reason to be read. "Insane launch" tells people you're impressed. It doesn't tell them what they should notice.

The same post can support several types of quotes:

• The founder's story. Explain what led someone to build the product. A problem they experienced personally or an unusual path to solving it can interest people who would scroll past a feature announcement.

• The product's implications. Go deeper into what it lets people do. Explain which part of their work could change, who benefits, or why a particular feature matters more than it first appears.

• A video reaction. Walk through the demo or try the product on camera. Pause at the interesting parts, explain what surprised you, and show where you're skeptical. Your reaction gives people another way to understand what they're watching.

• A controversial take. Pick a specific implication you're willing to defend. Explain why you think it matters and give people enough evidence to challenge you. A strong opinion gives the conversation somewhere to go.

• Competing interests. The same product can save one person money while threatening another person's business. It can give a founder more independence while raising concerns for the team responsible for maintaining the result. Explore that tension honestly. People on both sides have a reason to respond, and their discussion can introduce the product to new audiences.

On a recent launch, I chose the founder's motivation as my angle. Other people covering the same product could focus on its workflow or challenge its promise. That was the part I wanted my audience to notice.

Disagreement can bring attention, but think about what that attention will leave people believing about the product. You want a conversation your team can answer with evidence.

3 - Find the Right People for Each Angle

Once you have a few angles, look for people who can develop them from experience. Someone who deals with the problem every day will notice things a general tech account might miss. A specialist can explain what the product changes for their field. A customer can show their results.

Read their posts and replies before reaching out. Who pays attention to them? What questions come up? Would those people have a reason to try your product? A large following can help, but you should be able to explain why that particular audience would care.

Give creators enough access and context to form an opinion. A useful brief can be simple:

• Here's what the product does.

• Here's what you can test yourself.

• This is the part I think your audience would care about.

• Here's the evidence behind the claim.

• What's your take after trying it?

Get on a call if they need help understanding the product. Make paid partnerships clear, and let them develop the angle in their own words.

Their experience may lead them to something you hadn't considered. Leave room for that. If everyone ends up posting the same paragraph, you've lost much of the benefit of involving different people.

4 - Work Through the Response as a Team

Once the posts go live, divide the conversations across your team. Include your own replies, quote posts, and the comments under creators' posts. Agree on who handles product questions and who follows up on business opportunities.

1. Answer questions and notice who's interested. A potential customer might ask about integrations under a creator's post. Someone from a fund might ask about the market. An established founder might share a use case you hadn't considered. Answer where they commented. If there's a clear reason to continue privately, reach out with something relevant to what they said. Check their profile and understand the context first. A like alone doesn't tell you what someone wants.

2. Collect what you can use later. Keep a shared document with recurring questions, objections, product issues, and unexpected use cases. Include links to the conversations and the answers your team gave. Repeated questions can become your FAQ. A confusing feature may need a walkthrough. Product feedback should reach someone who can act on it. When you fix an issue or ship a requested improvement, return to the conversation and tell the person who raised it.

3. Share the strongest contributions. Look for people testing the product, posting results, or explaining it from an angle you missed. Ask permission to feature their work and credit them. A customer demo can become your next post. A thoughtful objection might deserve a video response. These give people a reason to revisit the product after they've already seen the announcement.

5 - Plan the Next Wave From What You Learn

After the initial activity, review which posts and angles brought the people you wanted to reach.

Look beyond views. Which conversations led to product trials, relevant DMs, or sales calls? Ask prospects where they found you when the source isn't clear. Keep track of what you can verify.

If a creator brought useful conversations, consider booking a follow-up over the next week or two. Give them something new to explore, such as a deeper walkthrough, a customer use case, or an update that answers questions from their first post.

Use the same feedback to refine your own content. If one use case keeps coming up in buyer conversations, give it more space in your next demo and on your landing page.

Before your next launch, make sure you have:

• A clear claim and evidence behind it.

• Different angles suited to the people sharing them.

• Creators who understand the product and its audience.

• A team ready to answer questions and follow up.

• An easy way for interested people to try the product or contact you.

Launching in the next 30 days? DM me "LAUNCH" with your product and target audience. I'll suggest a few angles we could build your launch around.