Go-to-Market

For a long time, launching meant a deploy date. Engineering finished, the servers took the new build on a Tuesday night, a one-line note went out, and that was the whole event. Underneath sat an assumption: a good feature will get used on its own.

That assumption broke at Pagedeck with the permissions feature built for company accounts. Three months of work, shipped on the day it was scheduled, and two weeks later exactly four teams had turned it on. In the same stretch, Sofia in sales was asked by a customer whether permissions could be split by department and said she would check. The feature was already live. When Grace, the CEO, asked in a meeting why the person selling the product didn't know, what surfaced was that telling her had never been anyone's job.

The cause was that engineering had a schedule and selling had none. What would be built by when was written down. Who would buy this, why they should buy it now, and who would say so where appeared in no document at all.

It wasn't that the decisions were missing. They were scattered. Price was set by the CEO ahead of an investor meeting, the kind of company to chase was judged by sales from whatever inquiries came in, and the words on the page were written separately by marketing. None of the three knew about the others, so they didn't line up. Sales was meeting fifty-person companies while the price sheet was denominated in five-person teams and the landing copy spoke to someone working alone. No single one of those was wrong. They just couldn't be shown to one customer at the same time.

A go-to-market plan — shortened to GTM in most conversations — gathers those decisions into one document and puts it in front of the launch date. It normally starts when the build is about half done. Starting after the build is finished is usually too late, because how money gets charged decides what the payment screen has to do, and who it's sold to decides what the defaults should be. When the plan arrives late, closing those gaps turns into post-launch work.

On the product map this term sits in the launch branch. A release, in the same branch, is the act of putting the built thing in front of users. Go-to-market is the set of decisions wrapped around that act — one is something that happens on a date, the other is weeks of preparation aimed at that date.

One branch sits under this term. It is called components, and it holds the three pieces of machinery that make the plan actually run. The three make more sense after the questions the plan has to answer, of which there are five.

The first is who it's sold to. The written-down conditions describing the customer that fits best and stays longest are the ideal customer profile (ICP): industry, size, tools already in use, the job title of whoever decides. When that description isn't narrow, the answers to the other four questions all blur.

The second is what it promises. Choosing the place a product will occupy in a customer's head among competing options is positioning, and turning that place into actual sentences is messaging. The same feature set reaches different buyers depending on whether it's placed as a fast way to write documents or as a document archive that survives an audit.

The third is which path it reaches them through. Three are common: a salesperson meeting the buyer directly, the product letting people use it free until they pay on their own, and selling through another company. When one customer pays a small amount, a path with a person on it doesn't add up. Three visits against a contract worth a few hundred dollars a year costs more to win than it brings in.

The fourth is what it costs. Setting the number and the unit it's charged in is pricing, and the unit chosen here has to agree with the three answers above. Charging per person only works if the product spreads across a team, and that requires invitations to be part of the plan rather than an afterthought.

The fifth is when and how it's announced. That question is where the three terms below do their work.

1. Launch tier — the grade that says how large this particular launch will be treated. Three levels is typical. The top level carries a press release, a webinar, and a page of its own; the bottom level carries one line in the release notes. The grade comes first because not every launch can be treated as large. A team shipping two hundred times a year that writes two hundred press releases trains everyone to ignore them, and the signal is buried on the day something genuinely big goes out.
2. Launch checklist — the list of items that have to be finished before the launch. Whether the help article is published, whether the price sheet changed, who picks up the customer questions, how to undo it if undoing becomes necessary. The tier decides the length of this list. Requiring twenty items for every minor launch teaches people to skip the list entirely.
3. Internal enablement — getting sales and support able to explain the thing before it ships. What changed, which customers it's worth raising with, how to answer the questions that will come up, all handed over in advance. This is exactly the item that was missing in the permissions story above. A feature that ships while the people selling it don't know is, from outside, a feature that didn't ship.

The outer half of the plan lives on the marketing map. Writing out by date which posts, pages, and emails go out around the launch is the launch plan, and producing the deck, the pricing explanation, and the competitor answers that sales will use is sales enablement. Go-to-market settles what is sold, to whom, and why; those two turn the settlement into dates and materials.

The order among the three is usually fixed. Set the tier, pull a checklist sized to that tier, and run internal enablement as one item inside it. Reversed — starting from the checklist — every launch gets handled at the same weight, and within six months the list is a formality nobody reads. Pagedeck began with no tiers and a single list. A launch that changed one line of copy still demanded a help article update, an internal announcement, and a support answer sheet, so within two months people opened the list, ticked everything, and moved on. Only after the grades were split into three did the items on the top grade start getting filled in for real. The list got shorter for most launches and longer for the few that mattered, which is the trade the tier exists to make.

"We can't just ship this one without a GTM. The pricing unit changes, so sales has to know first."

A brake applied because this launch changes how the product is sold rather than only what it does. GTM here is the everyday short form of go-to-market, and it's what actually gets said out loud.

"Let's call this tier 3. Release notes only, no separate page."

A decision to treat this launch at the lightest grade. Not a decision to skip promotion, but a cap set in advance on how many people-hours the preparation gets.

"Customers will ask about this next week. Is Sofia in a position to answer?"

A question about whether internal enablement is done. When it comes up in a launch meeting, the answer is usually no.

At Pagedeck the plan gets used in a meeting four weeks before launch. Mia, the product manager, brings a single page with two sentences at the top — who this is sold to and why now — and tier, price, and owners underneath. The part that takes longest is always those first two sentences. Aim at company accounts and Sofia has to build a list of who to contact; aim at the free teams already using the product and Ravi has to prepare an in-product announcement. The two differ in lead time and in cost.

Once the two sentences are settled the rest moves quickly. The tier gets picked, Mia pulls up the checklist and fills owner names against the items, and two weeks out Sofia and the support lead sit through a thirty-minute internal walkthrough. What Grace watches in this meeting isn't whether every box is filled. It's whether those two sentences point at the same place the company said it was going last quarter.

The most common mistake is reading go-to-market as another name for a marketing campaign. The posts and ads that go out around a launch are the most visible output, so the reading is natural. But the campaign is part of the fifth question only. Who it's sold to, what it promises, which path it travels, and what it costs sit ahead of it, and marketing cannot settle those four alone. Launch with only the campaign ready and traffic rises while those people stop at the price sheet. Pagedeck did exactly this once. A post aimed at company buyers tripled inquiries, the companies that arrived wanted annual contracts and proper invoices, and the payment screen at the time accepted a credit card and nothing else. Most of the extra inquiries stopped right there.

The other common belief is that this plan is only for launching a new product. The name points at going to market, so it attaches easily to founding a company or shipping something brand new. But the moments when the way a product is sold changes keep arriving afterward. Selling an existing product to a new kind of customer, restructuring the price, moving something that was free behind payment — all of them qualify. Treat a change like that as an ordinary feature launch and, from outside, something people used yesterday is simply blocked today, with an unprepared support team absorbing the complaints. Demanding all five answers again for every small feature is a problem of the same size, which is why the grading machinery sits in front. The test is the size of the change a customer experiences, not the size of the build. Doubling a processing speed behind the screen may have taken three months and needs no explanation to anyone; renaming one button may have taken a day and has to be announced to everyone who uses it. The build calendar and the selling calendar measure different things, and the plan is what keeps them from being confused.