Product Launch Marketing: A Practical 90-Day Plan

Product launch marketing is the work that decides whether a new product or service is noticed, or whether it is just an update on your own website that nobody outside the business ever hears about.

When a new thing is nearly ready, most owners do the same thing. They announce it, wait, and then wonder why the phone stayed quiet. I have watched that pattern for thirteen years, and it is almost never the product. It is that nobody outside the business ever worked out what problem the new thing solved, who it was for, or how to buy it, because the marketing got written in the last week instead of planned across the three months around the launch.

Launching something new is also less common than the noise suggests, which is worth knowing before you decide how loud you need to be. The Australian Bureau of Statistics reported that "In the two-year period ended 30 June 2023, under half of all businesses (46%) reported being innovation-active." It also found that "22% of businesses reported introducing a goods and/or services innovation which remained unchanged from the two years ended 30 June 2021." Those figures come from the ABS release dated 20 August 2024, describing the two years ended 30 June 2023, so read them as the position at that time. In plain terms, most businesses do not launch anything in a given two-year stretch, and the ones that do mostly repeat what they have already done. If your competitors are not launching anything, the marketing is the only thing that decides whether your launch gets noticed at all.

What Product Launch Marketing Actually Covers

The marketing around the thing, not the thing

This is the boundary that keeps the whole project sane. The product, the price, how it gets delivered and whether it works are decisions taken before any of this, and they are not what I am writing about. What sits in front of me is everything around the thing: how it gets described, who hears about it first, what they land on when they look, what proof they see, and what happens to the enquiries that arrive in the first fortnight. A launch with excellent marketing and a mediocre product will still disappoint. A launch with a good product and no marketing is a decision to keep it quiet, whether the owner meant that or not.

Why launch day is the middle, not the start

The date on the calendar is not the beginning of the work; it is the point where the work becomes visible. Everything that makes launch week effective has already happened by then: the page exists and can be found, the description of who this is for has been argued through and written down, and there is something to show a customer rather than a promise. The reason I plan the three months around the date rather than the week of the date is that launch week is a bad time to be making decisions. You will be answering questions, handling interest and fixing small things, and every decision that has not been made by then gets made badly or not at all.

What a launch has to achieve, in one sentence

One outcome, stated before anything else: the right people should understand what this is for and take one step towards buying it. That sentence is deliberately plain, because the failure I see most often is a launch trying to do four jobs at once, being a brand moment, a media event, a lead generation campaign and an awareness exercise, and landing none of them. Pick the one step you want a person to take. Book a call, request a sample, start a trial, ask a question. Everything in the plan either moves somebody towards that step or it comes out.

The One Decision That Shapes The Whole Plan

Who the new thing is for, and who it is not for

This is the decision that matters more than every other choice here put together, and it is the one owners find hardest, because narrowing the audience feels like turning customers away. It is not. A launch aimed at everybody produces copy that nobody recognises as being about them, and the second half of the decision does most of the work: who is this not for? I would rather write a sentence that excludes two groups of potential buyers than one that could describe anything sold by anyone in the industry. The exclusion is what makes the sentence specific enough to be useful.

The job it does, in the customer's words

Not the features, and not the way the team talks about it internally. The job it does for the person buying it, described the way that person would describe it to a colleague. This is usually a translation exercise, and it is the step where internal language gets left behind. A tool does not "provide an integrated workflow solution"; it stops somebody rebuilding the same spreadsheet every Monday morning. If you cannot say the job in the buyer's words, buy a coffee for three customers who have the problem the thing solves and write down the words they use. That conversation is worth more than any planning document.

Writing the sentence before you write anything else

Two lines, written down, before anything else is created. One sentence describing who the new thing is for and the job it does, and one date. That is the whole first step, and it is the step that decides whether the rest is marketing or noise. Everything downstream, the page, the announcement, the emails, the way enquiries get answered, is a variation on that sentence. If the sentence is vague, every piece of copy built on it will be vague in its own way, and no amount of work downstream will rescue it.

What Has To Be Ready Before Launch Day

The page people will actually land on

Someone is going to read about this and want to know more, and the page they land on is the whole of your sales effort at that moment. It needs the plain description of who it is for, what it does and what happens next. It needs the limitations stated, because a buyer who discovers a limitation after enquiring has been misled, and a buyer who reads it beforehand has been qualified. It needs one obvious next step rather than four competing ones. And it needs to answer the first three questions a buyer asks, which are usually what it replaces, what it costs to run once it is in place, and who should not buy it.

Proof you can publish on day one

Whatever you have, gathered and checked before the announcement rather than after it. Early customer comments, screenshots of the thing working, a short comparison against the way people solve the problem today, numbers from your own trials, or the first few case notes if the product has been in front of real users. A claim with something behind it survives the first difficult question; a claim with nothing behind it does not, and the person asking that question is the one who was going to buy. If the proof is thin, say so in the copy before somebody finds out for themselves.

The groundwork that has to happen early

The work that cannot be done in the week itself, which is mostly the work that involves other people's time. Existing customers who will try it and comment. A supplier or partner who needs to know before their own customers hear about it. Whoever answers the phone knowing what the thing is and what it does not do yet. And the internal argument about the sentence, held early, in a room, so that the answer is consistent wherever the question is asked.

Getting The New Page Found In Time

Why the page has to exist before launch day

Because search engines have to find a page before anything can happen with it, and the documented timing is not instant. Google's own guidance on asking for a page to be recrawled says that "Crawling can take anywhere from a few days to a few weeks." It adds that "Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all." Put those two sentences next to a launch calendar and the conclusion is unavoidable: if your announcement goes out on Tuesday and the page was published on Monday, then for a period measured in days at best, and weeks at worst, you are sending interested people somewhere that search has not read. The page is not the announcement. The page has to be ready and live first, so that the announcement points at something that already exists.

Timing, indexing and internal links

Keep this part as simple as the timing question it actually is. Publish the page early, describe it plainly, and link to it from the handful of pages you already have where a reader might sensibly want it, which for most businesses means the most relevant service page and the page people actually visit. That is the whole lever you control, and it is a real one, because the links on your own site are the fastest way to get a new page seen by both people and search systems. A page that exists for two or three weeks before launch week begins gives you the most valuable thing available, which is a page that search has already found by the time anyone goes looking for it.

What I tell clients about ranking timelines

Do not plan a launch around a ranking, because the timeline is longer than a launch, and the research is unusually clear about it. A study by Ahrefs of how long it takes pages to rank found that "Only 1.74% of newly published pages rank in the top 10 within a year (down from 5.7% in 2017)." The same study put the useful number right beside it, and this is the one that matters for a launch: "40.82% of pages that ranked in the top 10 did so within 1 month." It also found that the top of the results is generally old, reporting that "72.9% of pages in Google's top 10 are more than 3 years old (up from 59% in 2017)." The study was published on 15 May 2025, and its own description of its method is worth quoting so you can weigh it yourself: "We took 1M random URLs seen by our crawler in September 2023 and looked if any of them made it to the top 10 within a year." The reading I give an owner is calm and unsentimental. A new page can absolutely rank quickly, many do, but most pages are not in the top ten inside a year, and the pages already there are older than your product. Search is one way a launch gets found. It is rarely the way a launch succeeds, so the announcement, the existing customers and the direct conversations have to do work as well.

Launch Week: What To Run And What To Hold

The channels I would turn on first

Start with the people who already know you, because they cost nothing and they are the fastest honest signal you will get. One email to your existing customers, written by a person, saying what the new thing is and who it is for. A post or two on the accounts where you already have an audience rather than the ones you wish you had. Direct conversations with the twenty or thirty people most likely to need it. And the page itself, live and linked, so there is somewhere for all of it to point.

What to deliberately leave until later

Paid advertising on day one, for most first launches, and anything that depends on a message you have not tested yet. The reason is arithmetic rather than caution. If you buy traffic to a page whose description is not landing yet, you have paid to learn something you could have learned for free from the first thirty people who looked. Leave the budget until you have watched real buyers read the offer and seen what they ask about, then spend behind the version that already has evidence behind it. I would also hold anything elaborate: the launch video, the countdown, the event, none of which matter if the description of who it is for is wrong.

Handling the enquiries that arrive

The enquiries are the launch. Everything else is preparation for them. Whoever answers should know the sentence, be able to say what the new thing is not, and know what the next step is. Write down every question that arrives during the first fortnight, word for word if you can, because that list is the most valuable document the launch produces. It tells you what the page failed to explain, what the announcement confused, and what the next version of the copy should say.

The First 90 Days After Launch

What to measure and what to ignore

Measure enquiries and what those enquiries turn into, questions asked by people who were interested, and which explanation of the offer produced a reply. Ignore impressions and likes as anything other than context, and be careful with one number in particular. Ahrefs' study of search traffic found that "96.55% of all pages in our index get zero traffic from Google, and 1.94% get between one and ten monthly visits", and that study was published on 1 December 2023. A launch page that nobody links to and nobody promotes is competing in that 96.55%, and the honest conclusion is not that search does not work; it is that publishing a page is not the same as launching something. If you cannot yet say which part of the launch produced your enquiries, that is a measurement question before it is a marketing one, and it is worth fixing before the next launch.

When to change the message

Change it when the evidence says the people who did engage understood something different from what you meant. That is a specific and observable failure: they ask questions that the page already answers, they describe the thing using the wrong words, or they are surprised by a limitation. Change the message then, on the page first, because the page is read by everybody and edited by you. What I would not do is change it because the first week was quiet, since quiet in week one usually means reach rather than message, and rewriting good copy to fix a distribution problem wastes the one asset that was working.

When to stop and go back to the core business

When the evidence has settled and it says the market does not want this, or the business cannot serve it profitably at the volume it produces. That is a legitimate outcome and a cheap one if it arrives in ninety days. The expensive version is a launch that keeps consuming attention for a year because nobody wants to write down that it did not work. Decide in advance what would count as enough, look at it at day 30 and day 90, and then respect the answer rather than extending the deadline.

What To Do When Nobody Notices

The three usual explanations

There are only three, and they have different fixes. Nobody saw it, which is a reach problem. People saw it and did not understand what it was for, which is a message problem. Or people understood it and did not need it, which is a product problem, and no amount of marketing work will fix that one. Naming which of the three you are facing is the whole job, and it is much cheaper than choosing a remedy and hoping.

Telling a message problem from a reach problem

Ask the people who did engage, directly, what they thought the new thing was for. That costs nothing and it takes a handful of conversations. If they describe it differently from how you meant it, the message is the problem. If the ones who engaged got it immediately and the only issue was how few of them there were, then the message is fine and you have a reach problem, which is a much easier fix: the same words, in front of more people. The one thing that never tells you which of the two you have is your own opinion of the copy.

What not to do when it is quiet

Increase the budget on the same message. That buys more of an answer you already have. The other reflex worth resisting is rewriting everything at once, because if the reach and the message and the offer all change together, the next result tells you nothing. Change one thing, look, then decide. And write down what you changed and when, because a launch that ran quietly is still the cheapest market research you will ever do, as long as the evidence survives the disappointment.

Running It Yourself Or Bringing In Help

The parts an owner should always own

The sentence, and the decision about who the new thing is not for. Those cannot be outsourced, because they are judgements about the business rather than tasks, and they are the input everything else depends on. The conversations with the first customers also stay with you, partly because you will hear things a consultant will not, and partly because a buyer wants to hear the owner talk about something new. And the answer to the question "what happens if I have a problem with it" should come from somebody who can actually decide.

The parts that are worth paying for

Writing, design, the page build, the mechanics of getting the announcement out, and the measurement afterwards. These are the pieces where a specialist does in a day what takes an owner a fortnight, and where the work has a defined finish line. The test I would apply is whether the task can be judged quickly when it comes back: a page, an email, a report and a piece of copy can be read and approved in minutes, whereas a strategy cannot. Pay for finished work with an obvious edge, not for activity.

Where a launch plan usually needs outside help

Two places. The first is the page and the content around it, because that is where most launches are thin: the offer is explained badly, the proof is missing, and the buyer has nothing to read that answers their real question. That is the content work a launch needs, from the page itself to the proof around it and it is the part I would fix first. The second is the measurement, because most businesses can tell you they had enquiries and cannot tell you which part of the launch produced them. It is also worth seeing what planned campaigns have produced for businesses in a few different industries before deciding how much of the plan to build yourself. And if the launch has to sit inside the rest of the year rather than stand alone, that is where one launch sits inside the wider plan for the year, which is a different exercise from this one.

Your Launch Marketing Checklist

Two weeks out

The sentence is written and agreed: who it is for, what job it does, and who it is not for. The date is fixed and written down. The page is live and linked from the relevant places on your site. The proof is gathered and checked. Whoever answers enquiries has read the page and knows the limitations. The first email is written, and the list of people to talk to directly is made, by name rather than by category.

Launch week

The announcement goes out to the people who know you first, then to the wider audience, and each time it points at the same page and the same single next step. Every enquiry gets a reply from a person, and every question gets written down. Nothing new is invented mid-week; if a decision has not been made, it either gets made quickly or it waits until the fortnight is over. And somebody checks, every day, that the page loads and the enquiry route works.

Day 30 and day 90

At day 30, read the question list and change the page where it is clear that people are not understanding something. At day 90, look at what the launch produced against what you said you wanted at the start, and decide whether to keep going, change the offer, or stop. Whatever you decide, keep the list of questions, because it is the input for the next one. The content work that turns the launch into something that keeps producing enquiries is worth thinking about once the first ninety days are behind you, rather than in the week itself.

Frequently asked questions

What is product launch marketing, in one sentence?

It is the marketing you plan around a new product or service, from the weeks before it goes live to the months after it does. The distinction that matters is in the ABS numbers. In Australia, only a minority of businesses take this on at all: the ABS reports that "In the two-year period ended 30 June 2023, under half of all businesses (46%) reported being innovation-active", and that "22% of businesses reported introducing a goods and/or services innovation which remained unchanged from the two years ended 30 June 2021." When most of your competitors are not launching anything, the marketing is what decides whether the launch is noticed or whether it is just an update on your own website.

How far ahead should I start?

Far enough that the page exists before you tell anyone. That is the practical answer, and it comes from Google's own documentation rather than from opinion: "Crawling can take anywhere from a few days to a few weeks", and "Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all." If your announcement goes out on Tuesday and the page was published on Monday, then for a period measured in days at best, and weeks at worst, you are sending people somewhere search has not read. The rest of the timing is calm: research says only "1.74% of newly published pages rank in the top 10 within a year", which is why a launch plan should count the launch as the start of the work rather than the finish.

Should I build a new page for it, or just add a section to an existing one?

A new page, usually, and that is a decision about intent rather than about search. A new product or service that a stranger might search for needs a page that can rank for its own name and its own problem, and an extra section halfway down an existing service page cannot do that. If the thing is genuinely an option on an existing service, meaning it is the same buyer, the same problem and the same buying decision, then put it on the existing page and do not create a thin page nobody asked for. The test I use with clients is one sentence: if you had to describe it to a stranger in a sentence, and that sentence is not the same as the page it would sit on, it needs its own page.

Should I put money into ads on launch day?

Only if you already know what an enquiry costs you, and for most first launches you do not. The honest sequence is to launch quietly to the people who already know you, look at what they respond to, fix the page copy while the traffic is cheap, and then put paid budget behind the version that has already been tested. That is also why the first 90 days matter more than launch week. The figure worth keeping in mind is the blunt one from Ahrefs: "96.55% of all pages in our index get zero traffic from Google, and 1.94% get between one and ten monthly visits." A launch page that nobody links to and nobody promotes is competing in that 96.55%, and paying for traffic to fix a page that does not convert is the most expensive way to learn that.

Is it fair to count a blog post as launch marketing?

Only if it answers a real question the buyer has. A post published to have something to announce is not launch marketing, it is a diary entry, and I have seen hundreds of them. A post that answers the question your new product creates, meaning what it replaces, what it costs to run, who should not buy it, what the alternatives are, is the thing that gets found, shared and cited months later when the announcement is long forgotten. That is content marketing work, and it is genuinely part of a launch, but it is one part, and it does not substitute for a page the buyer can act on.

Our last launch was quiet. What now?

Diagnose before you spend again. There are only three usual explanations and they have different fixes: nobody saw it, which is a reach problem; people saw it and did not understand what it was for, which is a message problem; or people understood it and did not need it, which is a product problem and marketing cannot fix it. The way to tell them apart is to ask the people who did engage, directly, what they thought it was for. That costs nothing and it usually takes about five conversations. What I would not do when it is quiet is increase the budget on the same message, because that just buys you more of an answer you already have.