Product Launch Plan for a Small Brand: Map Six Buyer Steps, From First Hearing to First Use, Before You Plan a Single Post

A post schedule counts messages; a launch plan maps decisions

A post schedule answers the question "how many things will we publish?"

A launch plan answers a different one: "what does a buyer need to know, at each moment, to go from never having heard of this to happily using it?"

The second question usually leads to fewer posts, each doing something specific.

Before writing any content, map the route. For most products it has five steps. For anything sold on pre-order, or made to order with a long wait, it has six:

• First hearing: someone learns the product exists
• Learning more: they work out what it is and whether it's for them
• Choosing: they pick an option or edition
• Ordering: they pay and give their details
• Waiting: the time between paying and receiving
• First use: they open it, use it and decide whether it was worth it

Each step has a different job, and a different place where the answer should live.

Write down the decision the buyer is making at each step

The easiest way to fill in the route is to write the decision a person is making at each step. The facts they need follow from the decision.

For Lantern Keepers:

Notice how specific the facts are. "Is it for me?" for a card game means play time and complexity. For a jacket it would mean fit and warmth. For a houseplant it would mean light and care.

Fill in the table for your own product before you write a single caption.

Walk the route on a wall with two colours of sticky notes

Here's a method that works better than a spreadsheet for a small team, because you can see the whole launch at once.

Write the six steps on sticky notes across a wall. Under each step, add notes in two colours:

• Yellow: facts or content that already exist and are correct
• Pink: gaps, things that don't exist yet or that you're not sure about

For Kestrel Table, the wall after twenty minutes looked like this:

• First hearing: yellow note for the announcement post. Fine.
• Learning more: yellow for "two players". Pink for "play time" (the page only said "quick"). Pink for "how a turn works".
• Choosing: pink for "what's in the deluxe tin", which existed only in a design file.
• Ordering: pink for "when are you charged?" and pink for "can I cancel a pre-order?"
• Waiting: entirely pink. Nothing planned.
• First use: yellow for the rulebook. Pink for "missing card replacement".

The pattern is common. The first step is covered several times over. The later steps are thin or empty.

The pink notes are your launch plan. Fill those before adding more yellow to step one.

Finish the product page before you send anyone to it

One rule saves most small launches from a disappointing first week: don't promote a page that isn't finished.

For Lantern Keepers, a finished page answers these near the top:

• What it is: "Lantern Keepers, a card game for two players"
• How long a game takes: "About 25 minutes"
• Who it suits: "Ages 10 and up. Easy to learn, with more strategy the more you play."
• The two editions and their prices, side by side
• The pre-order terms: when you're charged, when it ships, how to cancel

Lower down: a short clip of a turn, the full contents of each edition, and the story of how the game came about.

Then walk the order route in your shop's test mode. Check that the edition someone picks is the edition in the basket, that the pre-order terms appear before payment, and that the confirmation email repeats the expected ship date.

If your announcement post says "ships in March" and the page says "ships in spring", buyers will notice. Make the facts match before you publish anything that points at the page.

Make the options easy to compare, because choosing is where people stall

Two editions sounds simple. In practice, a buyer comparing them needs to know exactly what changes and what doesn't.

Kestrel Table's first draft simply said "Standard edition" and "Deluxe edition", with a photo of each. A buyer had to guess what "deluxe" meant.

The improved version:

The last row matters most. A buyer who just wants to play doesn't need the deluxe edition, and saying so honestly builds trust with both kinds of buyer.

It also means fewer messages asking "is the standard version missing something?"

Give each channel one job along the route

Once the route is mapped, divide the work. Each channel should do the job it's best suited to.

If every channel repeats "Lantern Keepers is here!", the buyer gets step one six times and steps three to six never. Different channels, different jobs.

Every post links to the place where its question is answered

The clip of a turn links to the product page, near the "how to play" section. A post about the deluxe tin links to the page with the comparison table in view.

Every link should land the reader where their next decision happens, not on a homepage where they have to start searching.

Write one description sentence that every channel repeats word for word

When six channels each describe the product in their own words, small differences creep in. The post says "a quick two-player game". The email says "a strategy game for two or more". The page says "for two players, about 25 minutes".

A buyer who sees all three starts to wonder which is true. Can three people play or not? Is it quick or is it strategic?

So before anything is published, Kestrel Table wrote one sentence that every channel uses exactly:

"Lantern Keepers is a card game for two players. A game takes about 25 minutes, and it's easy to learn."

The post opens with it. The email opens with it. The page opens with it. The clip's caption is it.

Each channel then adds its own job on top: the clip shows a turn, the email explains the pre-order dates, the page holds the edition comparison. But the description underneath never changes.

It also makes later corrections easy. If play testing shows a game really takes 35 minutes, there's one sentence to change, and a short list of places to change it.

Write your own sentence from the "learning more" row of your route table. Keep it to two sentences at most, and only include facts that won't move before launch.

Plan the waiting step, because pre-order buyers notice silence

The waiting step is the one most launch plans forget, and the one that most affects whether pre-order buyers would buy from you again.

Someone who pays in late autumn for a game that ships in March has months to wonder whether it's still happening.

Kestrel Table's plan for the wait:

• The confirmation email states the expected ship date and how to cancel
• One update email in January: printing progress, a photo of the proof cards, and whether the date still holds
• An email when it ships, with tracking

That's three emails across several months. Not a newsletter, just enough to keep the promise visible.

They also decided in advance what they'd do if printing was delayed: email every pre-order buyer as soon as they knew, give the new date and remind them of the cancel option. Writing that email before it's needed means a delay becomes an honest update, not a scramble.

If your product isn't sold on pre-order, the waiting step might only last a few days. It still benefits from a confirmation that says when the order will be sent.

Choose a real reason for the launch date, and never fake scarcity

A launch needs a true reason to happen when it does.

For Lantern Keepers, it's the print order. The studio needs to confirm a print run by a certain date, so pre-orders close then. That's a genuine deadline, and they say so: "Pre-orders close on 30 November so we can confirm the print run."

What they avoid is fake scarcity. "Only 300 copies!" would only be honest if they genuinely never planned to reprint. If a reprint is likely, "first print run of 300" is accurate. "Only 300 ever" isn't.

If your release depends on something real, like a batch, a print run, a harvest or a supplier date, say what it is. Buyers respond better to a real reason than to a countdown timer, and they remember which one they were given.

Test the route with three people from your waiting list

If you have a waiting list, ask two or three people from it to look at the product page before launch. Pick people you've already spoken to, and ask politely.

Ask them three things:

• In your own words, what is this game and who is it for?
• Which edition would you choose, and why?
• What would you want to know before paying for a pre-order?

All three of Kestrel Table's testers asked the same thing: "Is my card charged now, or when it ships?" That was a pink note on the wall. Three people asking it confirmed the answer needed to sit beside the button, not in an FAQ.

Treat the answers as a clarity check, not a survey. Keep their comments private unless they say you can share them.

New buyers and returning buyers walk different routes

Not everyone on the route starts at step one.

Someone who played Kestrel Table's earlier print-and-play game already knows the studio and trusts it. Their route is short: they want the editions, the price and the ship date, then the button.

A newcomer who found the game through a board game forum needs the whole route: what it is, how long it takes, whether it's for them.

Write the page for the newcomer, because you never know who a post will reach. Then make it quick for returning buyers, with the editions and the button near the top and the details below for anyone who wants them.

In the waiting list email, you can be shorter, because those readers asked to be told.

Decide who does what on launch day, and what would make you pause

In a two-person studio, launch day roles are simple, but they're still worth writing down:

• One person publishes the page and sends the waiting list email
• One person watches incoming orders and checks the first few look right in the shop's order list
• Both answer messages, from one shared inbox
• An hour in, one person walks the order route again from the start

Also decide what would make you pause: a wrong price, an edition adding the wrong item to the basket, a checkout error, or a confirmation email with the wrong ship date. If one appears, stop promoting, fix it, then carry on.

Deciding this calmly beforehand stops you panicking over small things or shrugging off big ones.

Plan the first-use step, because that's where your next launch starts

Most launch plans end at the order. The route doesn't.

For a card game, first use is a game night. The buyer opens the box, reads the rules and teaches a friend. If that goes badly, the game sits on a shelf. If it goes well, they tell people.

Kestrel Table planned for it:

• A three-minute rules video, linked from a card in the box and from the shipping email
• A simple form for missing or damaged cards, with replacements posted free
• A quick-start sheet so two people can play their first round within ten minutes of opening the box

Word of mouth mostly comes from the first-use step. A buyer who received exactly what the page described, and could start using it easily, is far more likely to recommend it.

What's the first-use moment for your product? It might be a first wear, a first wash, a first planting or a first recipe. Plan one small thing that makes it go well.

Review what the launch taught you, within a week

A week after launch, gather your notes and look at the wall again. Ask:

• Which pink notes caused the most questions?
• Which posts or emails seemed to lead to orders?
• Was anything about the editions confusing?
• What did people ask that nothing on the route answered?

Keep conclusions modest. "Several people asked whether the deluxe cards work with the standard game" is a fact. "Most buyers want expansions" is a guess.

Turn each finding into one change. For Kestrel Table, it was one new line in the comparison table: "The deluxe character cards will also be sold separately, to add to the standard game later."

If your launch also needs to be smaller, with fewer channels or a limit on orders, that's a separate decision. This plan maps the route. Deciding how much of it to do comes next.

Your next step this week

Write six sticky notes: first hearing, learning more, choosing, ordering, waiting, first use. Put them on a wall.

Under each, add yellow notes for what already exists and pink notes for the gaps.

Then count. If step one has five yellow notes and steps four to six are mostly pink, you know where your product launch plan needs to go next.

Fill the first pink note this week. That's your launch, planned from the buyer's side.

Keep going

Marketing Campaigns / Practical guide

Test Your Checkout Before Launch: Follow the Exact Link Your Customers Will Click, All the Way to the Order You'll Make From

Checking each piece of a launch on its own proves very little, because customers don't meet pieces. They meet one journey, and the bugs live in the handoffs between steps. Walk that journey from the real shared link to the confirmation email and the order record you'll actually work from.

Marketing Campaigns / Practical guide

Small Product Launch Plan: Launch One Product Properly With One Page, One Email and an Order Limit You Can Actually Pack

A small launch should shrink the number of places you show up and the number of orders you take, not the facts a buyer needs before paying. Here's a plan built on one purpose, one fact card, one page, one tested route, one announcement and a packing limit you set before anyone clicks.