Most enterprise launches treat the weeks after "go live" as one continuous campaign: the same enablement, the same proof points, the same amplification, released on a rolling basis until the market notices. That approach spends two different kinds of buyer readiness on one set of assets. Sales ends up under-armed at the moment buyers are most willing to engage, or the market gets asked to believe a proof point the company hasn't earned yet.
The Asana Service Management launch was built to avoid that problem. Early Access and General Availability weren't two checkpoints on the same campaign. They were two separate motions, sequenced against two distinct buyer states, with a different asset list built for each one.
Two Motions, Four Weeks Apart
Early Access went live August 18. General Availability followed September 16. Four weeks apart, and I built almost none of the same assets twice.
Early Access was a mini-marketing moment. The goal was proof. I put sales enablement first: a first call deck for incubation sellers, a use cases cheat sheet, and an Enablement 101 training covering personas, value props, and the competitive landscape. Reps needed to walk into a room and defend the product before I needed a room full of buyers to walk into. On the demand side, the launch blog carried the tagline and the four value props directly into market, the product page picked up case studies and ROI framing, and a sizzle video ran inside IPCs, social, and paid. Social presence from the ELT and Asana's own channels signaled the launch without overselling it. An Enterprise Service Buyers Guide gave prospective buyers a way to evaluate a category most of them hadn't looked at through an AI-native lens before.
General Availability was mega-marketing rolling thunder. The goal shifted from proof to scale, and the asset list widened to match. A press and media kit went to the right outlets, the pricing page went live, and a polished demo video replaced the sizzle cut on the website and in Consensus. Sales enablement went deeper: demo training, customer stories and case studies, a "get to know the IT buyer" asset. Analyst validation targeted "up and coming tools" coverage, something Early Access didn't have the proof points to earn yet. New use case pages went live, the IT Teams and Enterprise pages updated, and the WIS form CTA changed from "waitlist" to "contact sales," a small edit that marks a real shift from interest to pipeline. Customer validation came from a DPG customer, lifecycle emails and a "how to get started" video supported onboarding, and Gartner IT Symposium put the message in front of buyers already mid-evaluation. One campaign overlay ran across all of it: "Win every IT leader," alongside expansion revenue and net-new logo motions for AWM, StackAI, and Asana Service.
| Early Access | General Availability | |
|---|---|---|
| Goal | Proof | Scale |
| Sales Enablement | First call deck, use cases cheat sheet, Enablement 101 (personas, value props, competitive landscape), annual roadmap training | Demo training, customer stories and case studies, "get to know the IT buyer" asset |
| Website | Product page updated with case studies and ROI | Pricing page live, IT Teams and Enterprise pages updated, new use case pages |
| Video | Sizzle video in IPCs, social, and paid | Polished demo video on website and in Consensus |
| Amplification | Launch blog, ELT and Asana social channels | Press and media kit to targeted outlets |
| Validation | Enterprise Service Buyers Guide | Analyst validation ("up and coming tools"), DPG customer validation |
| CTA | Waitlist | "Contact sales" |
What Each Buyer Was Ready For
A four-week gap between Early Access and GA looks like the same launch stretched over two press releases. It isn't. Early Access buyers are willing to evaluate something unproven because they're already in the market, actively comparing ESM vendors, motivated enough to tolerate rough edges in exchange for early access to a differentiated product. GA buyers aren't. They want proof the product works before they'll spend evaluation time on it, which is why analyst validation and customer case studies show up at GA and nowhere in Early Access. Building the analyst and customer proof too early would have meant asking for validation before the product had customers to validate it. Building enablement too late would have meant sales fielding buyer questions with nothing to point to.
The sequence only works if each motion sources buyers it's actually built for. Early Access reaches sellers who already know how to sell the product and buyers already primed to evaluate it. GA reaches a wider net that needs the case studies and analyst validation to convert. Collapsing the two into one motion would have either burned the Early Access window on enablement that wasn't ready, or launched GA without the proof points that make it credible to a broader buyer.
The Framework, One Product Down
Motion-Market Fit isn't specific to this launch. I've used the same logic to run three GTM motions across three products under one function, and here it holds at the level of a single product's first sixty days. The rule doesn't change with scope: match the motion to where the buyer actually is at that moment. Early Access earns its buyers through access. GA earns its buyers through proof. Building both moments off the same asset list gets the calendar right and misses the buyer.