Launch Strategy

Enterprise Feature Launch GTM: SSO + Permissions

Segment your 45 Pro accounts before anything:

Outreach script for hot accounts:

"[Name], we're rolling out SSO (Okta, Azure AD, Google Workspace) and role-based permissions next week. I held a spot for you at the enterprise tier — given your team size, the per-seat math actually works out to less than what you're paying now. Can I show you a 15-minute setup walkthrough?"

Supporting assets to build (1 week):

• 1-pager: SSO + permissions feature brief (for IT/security buyers)
• Objection FAQ: "We already have LastPass" → "SSO isn't password management, it's centralized identity control"
• ROI calculator: time saved on user provisioning/deprovisioning

Launch email sequence (3 emails over 10 days):

1. Day 0: Feature announcement to all Pro accounts
2. Day 4: Case study email — how a similar company uses it
3. Day 10: Last chance — upgrade offer expires

Target: Convert 12 of 45 accounts = $6,000 incremental MRR

Launching head-to-head against Asana and Linear is a losing strategy. Your goal at launch isn't to win the market — it's to win a specific segment so decisively that you build a reference base that makes the broader market move.

The Wedge Strategy

Asana and Linear are built for everyone, which means they're optimized for no one in particular. Your wedge is identifying the segment where "optimized for no one" is most painful and where your mobile and AI advantages are most visible.

The wedge has to be narrow enough that you can dominate it in 90 days, and real enough that winning it produces paying customers and reference stories.

Wedge candidates to evaluate:

• Mobile-first teams: field teams, sales orgs, agencies, construction — people who live on their phones and find Asana's mobile app an afterthought
• Specific company sizes: 10–50 person teams that have outgrown Trello but find Asana over-engineered
• Specific industries: creative agencies, marketing teams, professional services — where AI task generation from briefs has immediate ROI

Score each candidate on: (a) how often they cite mobile UX as a pain point in G2/Reddit complaints about incumbents, and (b) whether a reference customer in this segment is accessible to you today.

Category Entry vs. Category Creation

You're not creating a new category. "AI-powered project management" is not a category — it's a feature. Trying to create a new category when two well-funded incumbents own the existing one will bleed your launch budget with no payoff.

Category entry means you compete in the existing category but win on a specific dimension. Your framing: "project management built for how teams actually work in 2025" — mobile-first, AI-assisted, without the desktop-era complexity.

The goal is to be the obvious choice for a specific buyer, not a credible alternative for all buyers.

Turning Their Strengths into Liabilities

Asana was built for desktop workflows in 2012. Linear was built for engineering teams. These are facts you can use.

Positioning frame: "Built when everyone worked at a desk" — position their desktop-first architecture as a legacy choice, not a strength. Their brand recognition comes from a time before mobile-first work was the default. Your advantage is that you're not carrying that architectural debt.

Specific proof points to develop:

• Side-by-side mobile experience comparison (video, not feature list)
• Time-to-complete common tasks on mobile vs. Asana (measurable, quotable)
• AI-specific use cases that Linear/Asana cannot replicate — auto-generated task breakdowns, smart deadline suggestions, natural language project updates

The goal is to make enterprise buyers think: "Asana is what we use, but it's what we've always used — not necessarily what we'd choose today."

Launch Channel Sequencing

Phase 1 — Community (weeks 1–3):

• Reddit: r/projectmanagement, r/agency, r/remotework — not product pitches, genuine participation in existing "what PM tool do you use" threads
• Product Hunt: coordinate for a Tuesday launch, build your upvote list before the day
• Slack communities: agency ops communities, startup Slack groups — offer a free migration service from Asana/Linear as a launch hook
• Hacker News: "Show HN" post, founder-voice, focus on the technical AI decisions you made

Phase 2 — Content (weeks 3–8):

• SEO content targeting "Asana alternatives" and "Linear alternatives" (high intent, direct comparison traffic)
• Case study of your first 5 paying customers — specific, named if possible, with before/after metrics

Phase 3 — Paid (weeks 8+): Don't start paid until you have 10 reference customers and a conversion rate you understand. Paid on a brand you haven't validated yet is expensive learning. Community gives you signal first.

Turning Early Adopters into the Switching Cost Antidote

Your biggest structural problem is switching costs — teams already in Asana have their data there. Your counter: make your early adopters the proof that switching is worth it.

The reference customer program:

• Identify your first 20 customers who came from Asana or Linear
• Ask them to participate in a structured case study: what did migration take? What was the payoff in 60 days?
• Use these stories in every late-stage deal where a prospect raises switching cost as an objection

A prospect who hears "I migrated a 30-person team from Asana in a weekend and our mobile task completion went up 40%" from a peer will discount the switching cost objection themselves. That's the story your sales motion needs. Build it from launch day.

The migration lever: Offer a white-glove migration service for the first 50 customers. It costs you time, but it removes the switching cost objection from 50 reference accounts and teaches you exactly where the migration friction lives — which you then productize.