Build a Launch Share Kit Your Supporters Will Use

Picture this. Launch morning arrives and your friends, customers and fellow builders all say the same thing: "Let me know when it's live and I'll share it!" Then it goes live, you message them, and... nothing much happens for hours. It is not that they do not care. Writing a post from scratch takes effort, and most people do not want to get it wrong in front of their own followers.

A share kit fixes that. It is a small bundle of ready-to-use material that makes helping you a thirty-second job. This guide shows what to put in one, how to keep it honest, and how to hand it out so people actually use it.

What a share kit is, in plain words

Think of it as a goody bag for supporters. It holds everything someone needs to tell their own audience about your launch without having to ask you a single follow-up question.

A good kit has five parts:

1. The link, short and tested.
2. A few sample posts, in different tones.
3. One or two images that look right when shared.
4. A plain one-line description of what the product does.
5. A kind, specific request.

That is it. No giant brand guidelines folder, no forty files. If it takes longer to read than the post it helps someone write, it is too big.

Part one: the link

Start with the link everyone will use, because a wrong link ruins everything else. Use the public page for your launch, not a login page or a draft preview. Open it on your phone, on mobile data, while logged out. If it loads for a stranger, it is ready.

Keep the address short and clean. If you add tracking tags so you can see where visits come from, test them too, and use one tag per channel so your numbers make sense later. Tell supporters to use the link exactly as given.

Part two: sample posts

This is the heart of the kit. Write three to five short posts and make each one sound different. People will not copy them word for word, but they will borrow a phrase, and the starting point removes the blank-page fear.

Give each sample a label so supporters can pick the style that fits them:

The friendly note. "A friend of mine just launched something for people who keep losing track of their invoices. Had a look and it is simple and clear. Worth a peek."

The one-fact post. "New this week: a tool that turns a messy spreadsheet into a tidy weekly report. Link below if you want to see it."

The personal story. "I have watched this get built over the last year, so seeing it live today feels great. Here is what it does and why I think it is useful."

The question. "How do you currently keep track of X? A new tool launched today that tries a different way. Curious what you think."

The short and sweet. "Launch day for something I use myself. Have a look."

Notice what these have in common. They are specific, short and written in a normal human voice. None of them shout. None of them claim the thing is the best, the first or the only. If a supporter posts one, it should still be true when a stranger reads it.

Keep every sample claim true

Only put claims in samples that you can back up. If a supporter repeats "used by thousands of teams" and you have forty customers, that line is now spread under their name. Stick to what the product does and how it feels to use. A supporter who is happy to say "I use it myself" is worth far more than a big number.

Part three: images that behave

When someone shares a link, most platforms build a preview card from the page. That preview is usually the first and sometimes the only thing people see. The Open Graph protocol is the common standard behind it: a few tags in the page header that name the title, description, image and address of what is being shared. Your launch page should carry them, and you can check how it looks by pasting the link into a private message to yourself.

Beyond the automatic preview, include one or two images people can attach directly:

• A square or near-square card with the product name, a simple screenshot and one short line.
• A wide image sized for preview cards, with the important part in the middle so it does not get cropped.

Describe each image in a sentence so supporters can paste it as alt text. Alt text helps people who use screen readers, and the Web Content Accessibility Guidelines treat text alternatives for images as a basic requirement. A supporter who reads "Screenshot of a weekly report with three coloured charts" is more likely to add it than one who has to invent it.

Part four: a one-line description

Supporters often get asked "what is it?" in the replies. Give them one calm sentence to paste. Write it the way you would explain the product to a friend who has never heard of your category: what it does, who it is for, and nothing else.

Test it by reading it aloud to someone outside your field. If they can repeat it back, it works.

Part five: the request

Here is where many kits go wrong. The request is not "please upvote". Votes on a launch page should come from people who have really looked at the product and liked it, and some communities treat organised vote requests as against the rules. Hacker News, for instance, says in its Show HN guidelines that you should not ask friends to upvote or comment. Other places have similar customs, so read the rules of anywhere you plan to share before you write your request.

A better request is simple and honest:

"If you have a minute, take a look and tell me what you think. If you like it, sharing it with one person who might find it useful would mean a lot."

Notice the shape. It asks for attention and an honest opinion first, and a share second. If someone wants to leave a vote or a comment after trying the product, that is theirs to decide.

This is also a matter of trust. A launch ranked by votes from people who never opened the product is a poor signal to everyone, including you. The best result is a smaller set of reactions from people who meant them.

Timing: two sends, not ten

Send the kit twice.

A few days before launch, give supporters a heads-up with the kit attached, so they can see what is coming and say yes or no. Include the date and the usual time window in their time zone if you know it. Ask for a quick reply so you know who is in.

On launch morning, send a short message with the live link and a reminder of the kit. Keep it to two lines.

After that, stop. A third nudge in the same day starts to feel like pressure, and people who wanted to help will have done it by now. If someone has not shared by the next day, let it go gracefully.

How to hand the kit out

Keep the kit in one place, like a simple page or a shared document anyone with the link can open. Send it to supporters directly: a message, an email or a chat group, whichever you normally use with them. Avoid posting the kit page publicly, as it is meant for your inner circle, and a public "please share this" page can look desperate.

Make it work on a phone. Most people will read your message on a phone and want to copy a sample from there. Short paragraphs, big tap targets and no downloads that need a laptop.

Make saying yes easy, and saying no fine

Not everyone will share, and that is normal. People have good reasons: they do not post publicly, the product is outside their audience, or it simply is not their thing. Say so in the message: "No pressure at all if this is not your thing." It keeps friendships easy and keeps the responses you do get genuine.

Also think about who is in your circle. A good share is relevant. A designer sharing a tool for accountants may confuse their followers. Ask each person whether the product fits their audience instead of blasting the same message to everyone.

Say thank you in public and in private

When someone shares, notice it. Reply to their post, add a heart, or send a short direct message. Public thanks has a knock-on effect: it shows others how supporters are treated, and it gives the post a second moment of attention.

Keep a note of who helped. Later, when it is their turn to launch something, you will know exactly who to return the favour to.

A small checklist

Before you send the kit, run through this list:

• The link loads for a logged-out stranger on a phone.
• Every sample post is true and sounds like a person.
• The preview card shows the right title, description and image.
• Images have short descriptions ready to paste.
• The one-line description makes sense to someone outside your field.
• The request asks for a look and an honest opinion, not a vote.
• You have read the rules of every place the kit might be used.
• You know when each send goes out.

Where this fits on the platform

If you are preparing your own launch, the submit page is where you set up the entry the link will point to, and the launches page shows how other entries look to a visitor, which is a good way to judge your own preview card. The pricing page explains what is free and what is optional, so you can tell supporters honestly how the launch is set up. If you want to know who is behind it all, the founders page tells that story.

The short version

A share kit is a kindness to the people who want to help you. Give them a working link, a few true sample posts in different voices, a clear image, a plain description and a gentle request that never asks for votes. Send it twice, thank everyone, and let the product speak for itself when people arrive.