═══ BATTLE CARD — ClickUp vs Asana (Project Management SaaS) ═══ SECTION 1 — COMPETITOR PROFILE: ASANA Official positioning: Asana positions itself as the work management platform for enterprise teams — structured, scalable, and built for cross-functional collaboration. Their marketing targets operations leaders and programme managers at companies with 50 to 500 employees. Competitive behaviour: In deals, Asana leans heavily on brand recognition and customer reference stories. Their sales team focuses on integration depth and timeline views. When challenged on price, they offer extended trials rather than discounts. They rarely compete on AI features, which is their current strategic gap. Pricing: Asana's Starter plan is $10.99 per user per month. Premium is $24.99. They are significantly more expensive per seat than ClickUp at equivalent feature sets. Procurement teams at companies over 100 users frequently flag this. Target customer: Mid-market companies with structured project management needs, particularly those already invested in Google Workspace or Salesforce integrations. Not strong for startups or companies that need heavy task-level customisation. Recent moves: Asana added AI features in late 2025 but buyer reviews consistently rate them as surface-level. Their mobile experience remains a known weak point. They announced a partnership expansion with Microsoft in Q1 2026. SECTION 2 — STRENGTH AND WEAKNESS MAP Strengths: 1. Brand recognition: Asana is often the default recommendation from consultants and integrators. Deciding factor in roughly 30% of mid-market deals where the buyer has been told "just use Asana." 2. Integration depth: 200+ native integrations, particularly strong with Salesforce, HubSpot, and Google Workspace. Deciding factor in deals where buyers have existing enterprise software stacks. 3. Customer success support: Asana provides dedicated CS reps for accounts over $10K ARR. Buyers value this when they have had bad implementation experiences with other tools. Weaknesses: 1. Price per seat — High severity: $24.99 per user per month at Premium vs ClickUp's comparable plan at $12. For a 50-person team that is $7,494 extra per year. Buyer language: "It's more than we expected for what it does." Counter: "Most teams that switch to ClickUp from Asana save $6,000 to $15,000 in year one while getting more features." 2. Customisation limits — High severity: Asana's task structure is relatively rigid. Custom fields have caps and workflow automations require Premium tier. Buyer language: "We couldn't make it work for our specific process." Counter: "ClickUp gives every team a completely custom workspace — no workarounds needed." 3. AI features — Medium severity: Asana's AI is marketing-heavy but functionality-light in 2026. Buyer language: "The AI features felt bolted on." Counter: "Our AI is built into the core workflow — it works where your team already works." 4. Mobile app — Medium severity: Asana's mobile is consistently rated 3.2 stars vs ClickUp's 4.4. Buyer language: "The mobile app is unusable." Counter: Ask: how much does your team work on mobile? Then show the ClickUp mobile experience. 5. Reporting and dashboards — Low severity: Asana's reporting is limited unless you pay for additional seats or use a BI integration. Buyer language: "We need better visibility without buying more tools." Counter: "ClickUp's dashboards give you cross-project visibility without a separate reporting tool." SECTION 3 — SALES BATTLE CARD When buyer says: "We've heard Asana is the industry standard." You say: "It's well known, which is exactly why so many teams have tried it and switched. What specifically are you hoping the standard approach delivers for your team?" When buyer says: "Asana integrates with everything we use." You say: "What integrations are non-negotiable? ClickUp has 1,000+ integrations — I'd rather show you the specific ones that matter for your stack than list all of them." When buyer says: "Asana looks cleaner and simpler." You say: "Simplicity matters. The teams who stay with ClickUp long-term usually say it felt like more at first, then realised the flexibility is why it works. What does your team's actual workflow look like?" When buyer says: "We already started an Asana trial." You say: "That's useful context. What have you found in the first week? I ask because most teams discover the gaps at week 3, not week 1 — that's when the customisation limits tend to appear." When buyer says: "Asana has better enterprise support." You say: "Enterprise support matters most when implementation goes wrong. Can I show you our onboarding data? 94% of teams are fully operational in under a week — which reduces how much support you'll actually need." When buyer says: "Our CEO used Asana at his last company." You say: "That's actually a common starting point for us. What was the use case at the previous company? The reason I ask is the requirements often look different at different stages of growth." When buyer says: "Asana's pricing seems more straightforward." You say: "It is simple — it's also $14 more per user per month than our comparable plan. For a 30-person team that's an extra $5,040 per year. Would it be useful to run the numbers side by side?" When buyer says: "We need something the whole company will actually use." You say: "Adoption is the real metric — tools only work if people use them. What's caused low adoption with tools in the past for your team? That usually tells us what to prioritise in the demo." SECTION 4 — DISCOVERY QUESTIONS Question 1: "How customised is your current workflow — do different teams work differently, or is there a standard process everyone follows?" Exposes: Asana's customisation limits. Positive answer: "Every team has its own process." Question 2: "When you imagine your perfect project management setup, what's the one thing your current tools don't do that you wish they did?" Exposes: Opens gap-finding without naming any tool. Positive answer: mentions anything Asana is weak at. Question 3: "How important is mobile access for your team — are people managing work from their phones regularly?" Exposes: Asana's weak mobile app. Positive answer: "Yes, our team is often out of office." Question 4: "What does your reporting process look like today — how do you get visibility into project status without having to chase people?" Exposes: Asana's reporting limitations. Positive answer: "It's manual and painful." Question 5: "If I asked your team members what frustrates them most about how work gets tracked today, what would they say?" Exposes: Real-world pain that Asana may be creating or that no tool has solved yet. Question 6: "How many different tools does your team currently use to manage work — and do they all talk to each other?" Exposes: Integration pain that a more consolidated platform like ClickUp solves. Question 7: "When a project runs over deadline, what does the communication process look like — how does the team know and who tells who?" Exposes: Visibility and automation gaps. Question 8: "Has your team tried a project management tool before that didn't stick? What caused the abandonment?" Exposes: Previous pain points that the competitor may have caused or failed to fix. Question 9: "As the company scales, how confident are you that your current approach to project management will still work at twice the team size?" Exposes: Scalability concerns with rigid tools. Question 10: "What does success look like at the end of the first 90 days with a new tool — how will you know it worked?" Exposes: Buyer's real criteria, and whether the competitor is likely to meet them. SECTION 5 — OBJECTION SCRIPTS Objection 1: "Asana is what our IT team approved." Script: "Understood — IT approval is important. What were their main requirements when they evaluated options? I ask because IT teams often approve the tool they know, not necessarily the one that fits the workflow best. If we can meet the same security and integration requirements, would you be open to a side-by-side look?" Objection 2: "We're already halfway through an Asana trial." Script: "That's actually useful — you've already done the hard work of getting the team to engage with a new tool. What's working so far? And what hasn't clicked yet? The reason I ask is most teams hit the real gaps in week 3. If there's anything on that list, I'd rather show you now than after you've committed." Objection 3: "Asana is cheaper for us because we have a discount." Script: "Good to know — discounts change the maths. Can I ask what plan you're on and the per-seat cost? I want to make sure we're comparing the same feature set, because the plans that look similar on price often have meaningful differences in what's included." Objection 4: "Our team already knows Asana." Script: "That familiarity has real value — change costs time. What I'd ask is whether the tool your team knows is the tool your team loves. If there's even moderate friction, the switching cost usually pays back within 60 days. Would a quick trial with your actual workflow help us answer that question?" Objection 5: "The CEO wants to go with Asana." Script: "CEO alignment matters — getting that wrong is painful. What's driving the preference? If it's based on a previous experience, it's worth understanding whether the use case was similar. I'm not asking you to override the decision — just to go into it with the right information. Could we set up a 20-minute call with the decision-makers before it's final?" SECTION 7 — DISPLACEMENT EMAIL SEQUENCE Email 1 — The Observation: Subject: Question about your project tracking "Hi [Name], I've been speaking with a few [industry] leaders lately about a consistent frustration — the gap between what a project management tool promises at demo and what it actually delivers for a team of [X] people. Curious whether that's something you've run into. Happy to share what I've seen working. [Your Name]" Email 2 — The Evidence Drop: Subject: What [similar company] found after 6 months "[Name], a [company type] we work with moved away from their previous PM tool after 8 months because the customisation limits were forcing their team into workarounds that added 3 hours per week per person. After switching, they recovered that time in 30 days. I have a one-page breakdown of what they changed if it's useful. [Your Name]" Email 3 — The Direct Comparison: Subject: 15 minutes to compare properly? "[Name], if you're evaluating project management options, I'd rather spend 15 minutes walking through a direct feature-for-feature comparison than have you discover the gaps after you've committed. No pitch — just a clear look at where tools differ for teams like yours. Tuesday or Wednesday this week work? [Your Name]" SECTION 9 — WIN STRATEGY SUMMARY The one thing to remember: Asana wins on brand comfort. You win on flexibility and value. Every conversation should move the buyer from "I've heard of Asana" to "I need to understand what I'm actually getting for that price." The one thing to never say: Never call Asana overpriced, outdated, or a bad tool. Buyers who chose Asana feel defensive when it's criticised. Redirect, never attack. The one question that changes deals: "What would your team do differently if the tool had no workflow limitations at all?" This question makes buyers articulate their real needs — which Asana often cannot meet. The one proof point that wins: A case study from a company of similar size that switched from Asana to ClickUp with a specific result — time saved, cost reduced, or adoption rate. Make it specific. "A 45-person SaaS company in Austin saved $8,400 per year and cut their weekly sync meetings from 5 to 2" beats any feature comparison.