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

Decide what this launch is for, in one sentence, before you list a single task

Most launch plans start with tasks. Start with a purpose instead, because the purpose decides which tasks matter.

Write one sentence. Some honest purposes for a small launch:

• Sell the first batch of 120 jars to people who already know us
• Find out whether people will pay €9 for this, before making a bigger batch
• Get the product to ten regular customers and hear what they think
• Add a new product without disrupting the orders we already pack

Each purpose leads to a different launch.

If Orla's purpose is "find out whether people will pay €9", a giveaway muddies the answer, because free jars tell her nothing about price.

If her purpose is "sell 120 jars to people who already know us", a press email to a food writer is a good idea for later, not a launch task.

Pick one. Write it at the top of your plan. When you're unsure whether a task belongs, read the sentence again.

The cut test: would a buyer notice it was missing before they paid?

Now take every task on your list and ask one question about it: would a buyer notice this was missing before they paid?

If yes, it's a launch task. If no, it can wait.

For Orla's chilli oil, the yes pile looks like this:

• What it is, in plain words: chilli oil with crispy garlic and shallot
• How hot it is, described in a way a stranger can use
• The jar size: 180 ml
• Allergens, stated clearly: contains sesame
• How long it keeps, unopened and once opened
• How to store it
• The price
• Where she delivers, and how a glass jar is packed
• What happens if a jar arrives broken
• How to ask a question

And the no pile:

• The launch reel
• The giveaway
• The gift box
• The press email
• The discount code
• The countdown graphic

None of the no pile is a bad idea. A gift box might be lovely in December. A reel might help a second batch. They just don't decide whether a stranger can understand the product and order it with confidence.

Why the fun jobs survive and the essential ones get cut

It isn't laziness. The jobs in the no pile are visible and satisfying. You can show someone a finished reel.

The yes pile is quieter work: checking a label, measuring a jar, ringing the courier about glass. Nobody compliments you on a shelf-life line.

But a missing shelf-life line costs you the careful buyer, and careful buyers are often the ones who come back.

Write one fact card, because products keep changing in launch week

Small products change right up to the last minute. The jar supplier changes. The price moves once you've added up the labels. The dispatch day shifts because the courier only collects on certain days.

So keep every fact in one place: a fact card, dated at the top.

Orla's looks like this:

Notice the "not yet" row. That's honest. It's also a launch blocker, because shelf life is something a buyer of food needs before paying.

The card makes that gap impossible to forget, which is exactly what it's for.

The two facts that move most in the final fortnight

In almost every small launch, the price and the dispatch timing are the facts most likely to change late.

Price moves when the real costs land: labels, jars, packaging, payment fees. Dispatch moves when you discover how long packing actually takes.

Check those two on the card the day before you announce. If either changes after you've written your email, update the card first, and everything else follows from it.

Set an order limit from your real packing capacity

Here's a part of launch planning that rarely gets mentioned: deciding how many orders you can actually handle.

A big brand worries about selling enough. A small brand can be hurt by selling more than it can pack well.

Late parcels, rushed wrapping and broken jars do more damage to a new product than a quiet first week.

So work out your capacity before you announce:

• How many orders can you pack properly in one session? Be honest about glass, wrapping and labels.
• How many packing sessions do you have in launch week?
• When does the courier collect?

Orla times herself packing ten test parcels. With careful wrapping, it takes about an hour and a half. She has two packing evenings a week. That's roughly 30 orders a week she can send well.

Her batch is 120 jars. If the average order is two jars, that's about 60 orders, or two weeks of packing.

So she makes two decisions before launch:

• The shop shows exactly 120 jars of stock, so it can't oversell
• The page says orders are packed on Mondays and Thursdays, in the order they arrive, so a buyer on day one knows theirs might go out the following week

That's a far better launch than one that sells 60 orders in a day and then spends three weeks apologising.

Write the sold-out message now, while you're calm

Decide what the page will say when the batch runs out. It should say whether there will be another batch, roughly when, and whether people can leave their email to hear about it.

"This batch has sold out. The next one is planned for late November. Join the list below to hear first."

A sold-out page with a clear next step keeps the interest you worked hard to create.

One product page that carries the whole offer

In a small launch, the product page does the work a bigger launch might spread across posts, emails, videos and an FAQ. It has to stand on its own.

Write the first three lines so a stranger could decide from them alone. Orla's:

"Slow Heat chilli oil, 180 ml jar. Medium heat that builds slowly, with crispy garlic and shallot. Contains sesame."

Then, beside the price and button:

• Stock: "First batch: 120 jars"
• Dispatch: "Packed Mondays and Thursdays"
• Delivery: "Ireland and Northern Ireland. Jars are wrapped in recycled paper and sent in a fitted box."

Lower down come the fuller details: ways to use it, storage, the shelf life once confirmed, what to do if a jar arrives broken, and then the story of how the recipe came about.

Rule-out facts belong beside the button, not in a footer

For food, cosmetics or anything a body touches, the facts that could make the product unsafe for someone are rule-out facts. They go where the buying decision happens.

A buyer with a sesame allergy shouldn't find out three scrolls down, or worse, from the jar itself. Put it in the first lines, in plain words.

If your product is food, labelling rules apply to the jar and often to what you say online too. Check current guidance from your national food safety authority before you publish, because those rules are specific and they matter.

Test the page on someone who isn't your usual customer

Your page has to make sense to people who don't already know you. So find someone outside your usual audience.

Orla shows the page to her neighbour, who rarely eats spicy food. She asks three questions and says nothing else:

• What is this?
• How hot do you think it is?
• What would you want to know before buying it?

The neighbour says, "Chilli oil, medium hot, I think. But how long does it last once it's open?"

That's the shelf-life gap again, arriving from a completely different direction.

One person's question isn't proof of anything. But when it lines up with the "not yet" row on your fact card, you know it matters.

Keep the details on the page and point everything else at it

A small launch has fewer places to go wrong, as long as you don't copy the details everywhere.

The page holds the facts: size, heat, allergens, storage, dispatch, delivery. The email and any post say what's new, who it suits and where to find it.

They don't repeat the dispatch days or the delivery areas.

Why? Because if the dispatch day changes on Wednesday, you update one page. If those details are copied into an email, three posts and a pinned comment, at least one of them will be wrong by Friday.

The only exception is a safety fact like an allergen, which is worth saying in the email as well, because someone might act on the email alone.

Test the order route from a device you never use for the shop

Your own laptop knows too much. It's logged into your shop, it remembers your address, and it may show you things customers can't see.

So test the route on a device you never use for the shop: a family member's laptop, a borrowed tablet, a library computer. Use your shop's test mode or test payment option if it has one. Don't place a real order you plan to refund.

Walk through it in order:

• Open the exact link you'll put in your announcement
• Check the page shows the right product, price and stock
• Add two jars to the basket and check the quantity and total
• Enter an address you deliver to and check the delivery charge and timing
• Try an address you don't deliver to and see what happens
• Read the confirmation email and check it says the same dispatch days as the page

For Orla, that last check catches something. Her shop's default confirmation says, "Your order will be dispatched within 24 hours." Her page says Mondays and Thursdays.

Someone who orders on a Friday would expect a parcel on Saturday and receive it the following Tuesday.

She changes the confirmation template to match the page. That one mismatch would have produced a week of polite "where's my order?" emails.

One announcement that answers three questions in its first lines

A small launch can be a single email. It should answer three questions before anything else:

• What is it?
• Who might want it?
• Where do I get it, and is there a limit?

Orla's announcement:

Subject: Slow Heat chilli oil is ready


Hi,


Our first chilli oil is ready: a 180 ml jar of medium-heat oil with crispy garlic and shallot. It's good spooned over eggs, noodles or roast potatoes. It contains sesame.


This first batch is 120 jars. When they're gone, the next batch is planned for late November.


[See Slow Heat chilli oil]


Orders are packed on Mondays and Thursdays. If you have a question before ordering, just reply.


Orla

The subject line names the product, so the right people open it and nobody feels tricked. The limit is real and explained. The allergen appears in the email as well as on the page.

Only call it limited when you can say why

"120 jars" is honest because it's one batch from one kitchen. It would stop being honest if Orla quietly topped up stock and kept saying "limited".

If something is genuinely limited, give the reason: a batch, a season, a supply of an ingredient. If it's simply new, "new" is enough.

Buyers forgive "sold out". They don't forget a "last chance" that wasn't.

Send it to people who asked, in an order that's fair to them

Send the announcement only to people who agreed to hear from you. A new product doesn't make an unexpected email welcome, and consent rules vary by country, so check current guidance if you're unsure.

If you have a waiting list, there's a small, fair step worth considering: send to them a day before you post publicly. They raised their hand first. With a limited batch, a 24-hour head start is a genuine thank-you.

Only do this if your signup form said people would hear first. If it didn't, send to everyone at the same time.

If you post on social media, one clear post linking straight to the product page is a complete social launch. You can add a second post later if a real question comes up that's worth answering in public.

Prepare five answers before the questions arrive

Launch week brings questions, and they arrive at the same time as the orders. Write the answers in advance, from your fact card.

Orla expects these five:

• How hot is it, really? "Medium. Warm at first, then it builds. If you enjoy a mild salsa, you'll probably be fine. If black pepper is too much for you, this may be too."
• Is it gluten-free? Only answer yes if the recipe and every ingredient are confirmed. Otherwise: "We haven't confirmed that yet, so please don't rely on it."
• How long does it keep? The confirmed answer from the label check.
• Do you send to my country? "Not yet. Ireland and Northern Ireland only for this batch."
• What if a jar arrives broken? "Reply to your order email with a photo and we'll send a replacement."

Save them as ready replies. Choose one inbox for questions, and say on the page roughly how quickly you reply. A small launch isn't small to the person who has just paid.

The parked list: everything you postponed, with a date to look again

Everything from the no pile goes on a parked list, with a review date beside it.

For Orla: the reel, the gift box, the press email, the giveaway and the discount code. Review date: two weeks after launch.

When the date comes, she asks of each item: would this help the next batch, now that I know what people asked?

Maybe the questions show people want a recipe card more than a reel. Maybe the gift box is worth doing for December.

The parked list stops "later" from meaning "never". It also stops good ideas crowding out essential ones in launch week.

Stop rules: when a small launch should wait

A small launch still needs a line it won't cross. Decide in advance that you won't announce if:

• You can't say plainly what the product is and what arrives
• A rule-out fact is missing, like an allergen, a fit or a compatibility
• A safety or labelling question is unresolved
• The price or stock is uncertain
• The checkout or confirmation email contradicts the page
• You can't pack the orders you're inviting in the time you promise

For Orla, the shelf-life row means waiting five days for the label check. It's frustrating.

It's also far cheaper than taking back a promise she'd already made to 60 customers.

What to record in the first week, so the next batch is easier

Keep one page of notes during launch week:

• The date and time the announcement went out
• The page as it looked, saved as a screenshot
• The questions people asked, in their own words
• Any order problems: wrong items, delivery confusion, breakages
• Anything you changed, and when

Keep conclusions small. "Four people asked how hot it is" is a fact. "Customers want a milder version" is a guess until you've asked more people.

Then make one change for the next batch. Orla adds a short heat scale comparing her oil to everyday foods, because the heat question came up more than any other.

Why a small launch teaches you more than a big one

It's easy to see a small launch as a compromise. It isn't.

With one page, one email and one inbox, you can see exactly what happened. Every question came from someone who read the same words. Every order came through the same route. If something confused people, you know where.

A big launch spreads attention across many channels, which makes it hard to tell what worked. A small one gives you a clear first picture of how people understand your product. That's exactly what you need before you make more of it.

Your next step this week

Write your one-sentence purpose for the launch.

Run the cut test on your to-do list: would a buyer notice this was missing before they paid? Move everything that fails onto a parked list with a review date.

Work out how many orders you can pack well in launch week, and set your stock to match.

Then open your product page on a device you never use for the shop and read the first three lines. If a stranger couldn't decide from them alone, that's the first thing to fix.

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

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

A schedule of launch posts counts messages. A launch plan maps decisions. Lay out the six steps a buyer walks through, write what they need at each one, and give every page, email and post its own job along that route, including the wait between paying and receiving.