## Objection Map | # | Objection | Type | Inner thought (buyer's voice) | One-line counter | Strongest proof (+ why) | Placement | Score | |---|-----------|------|-------------------------------|------------------|--------------------------|-----------|-------| | 1 | We already run Asana/Monday — switching is a nightmare | Competition / switching cost | "I'd have to migrate every project, every task, and retrain 50 people. Not worth the upheaval." | Import your entire Asana or Monday workspace in one click — projects, tasks, and assignees move over in under an hour. | **Demo / migration walkthrough** — switching pain is visceral; showing a 1-hour import kills it faster than any claim. | Hero subhead + dedicated "Switching from X?" section | 10 | | 2 | My team won't adopt yet another tool | Risk (adoption) | "I'll roll this out, get blank stares, and spend two months nagging people to update tasks." | Task updates happen inside Slack and your code commits — your team adopts it without opening a new app. | **Case study with adoption %** — an ops manager seeing "92% weekly active in week one" trusts a peer's number over a promise. | Below hero + "How it works" section | 9 | | 3 | Annual billing locks me in before I know it works | Risk (lock-in) | "If this flops I've burned $30k and I'm the one who signed off. I can't un-ring that bell." | Full refund inside 60 days, no questions, no clawback — you prove it works before you're committed. | **Guarantee** — directly removes the downside that annual billing creates. | Pricing section + near primary CTA | 9 | | 4 | $49/user is steep — finance will push back | Price | "That's ~$30k/year for 50 seats. I'll have to defend this line item to my CFO." | Replaces the 6+ hours a week your team spends building status reports — that's the cost of one mid-level hire, recovered. | **ROI statistic / calculator** — reframes price as a labor-cost swap finance already understands. | Pricing section + ROI block above it | 8 | | 5 | "Automated reporting" is just a buzzword | Need / credibility | "Every tool says this. I'll still end up manually cleaning the dashboard before the Monday standup." | Reports build themselves from live task data and post to Slack automatically every Monday at 9am — you touch nothing. | **Live demo / interactive sandbox** — skeptics of "automation" need to watch it generate, not read that it does. | Features section ("See a real report") | 8 | | 6 | This looks like every other PM tool | Competition / differentiation | "What actually makes you different from ClickUp, Linear, or the ten others? I can't tell." | Built only for remote teams: async-first updates, timezone-aware standups, and zero-effort reporting — not a generic board with remote bolted on. | **Comparison table** — differentiation is best shown side-by-side, not asserted. | Mid-page comparison section | 7 | | 7 | Reports are only as good as the data my team enters | Risk (data integrity) | "If people don't update tasks, the dashboard lies — and now leadership trusts a wrong number with my name on it." | Auto-pulls status from GitHub, Slack, and calendars so reports stay accurate even when people forget to update. | **Demo of integrations populating data** — shows accuracy isn't dependent on human diligence. | "How it works" + integrations section | 7 | | 8 | I can't approve this spend alone | Authority | "Above $X I need VP or CFO sign-off, which means building a whole internal pitch." | Download a one-page ROI brief built for your CFO — the case is made for you. | **Downloadable business case / template** — arms the champion with the artifact they need internally. | Pricing section + FAQ | 6 | | 9 | It won't connect to our stack | Complexity / integration fit | "If it doesn't sync with Slack, GitHub, Jira, and our HRIS, it just creates another silo." | Native integrations with Slack, GitHub, Jira, Google Workspace, and 40+ tools — live in minutes. | **Integration logo wall + count** — instant visual reassurance of fit. | Below hero (logo bar) + integrations page | 6 | | 10 | Onboarding 50 remote people will eat weeks | Complexity / setup | "Coordinating setup across time zones with no in-person rollout is going to be brutal." | Self-serve onboarding plus a dedicated migration specialist gets your whole team live in under a week. | **Onboarding case study with timeline** — a concrete "live in 5 days" timeline beats vague ease claims. | "How it works" + FAQ | 5 | | 11 | The real price is higher than $49 | Price (hidden costs) | "There's always an integrations tier, a support upsell, an onboarding fee. What's the actual number?" | One price, every feature — integrations, reporting, and onboarding included, no add-on tiers. | **Transparent pricing breakdown** — naming "no add-ons" defuses the suspicion directly. | Pricing section | 5 | | 12 | Is our data secure? | Trust (security) | "We're a tech company. If this isn't SOC 2 and our roadmap data leaks, that's on me." | SOC 2 Type II certified, encrypted at rest and in transit, with full data residency control. | **Security badges + certification page** — compliance is a checkbox, satisfied by proof not prose. | Footer trust bar + dedicated security page | 4 | | 13 | I can't prove the ROI to my boss | Need / ROI proof | "How do I quantify 'better tracking'? My boss will ask for numbers I don't have." | A built-in time-savings dashboard shows exactly how many reporting hours you reclaimed each month. | **Screenshot of the ROI dashboard** — gives the buyer the measurement instrument up front. | ROI block + features | 4 | | 14 | Now is a bad time to change core tooling | Timing | "We're mid-quarter and scaling fast — touching the PM system now is too risky." | Run it alongside your current tool for 30 days — switch only when your team's already living in it. | **Risk-reversal / parallel-run offer** — removes the "change now" pressure entirely. | Near CTA + FAQ | 3 | | 15 | What if you get acquired or shut down? | Trust (vendor longevity) | "If you're gone in 18 months I'm migrating all over again. Why bet on a startup?" | Export everything to CSV or JSON anytime — your data is never locked in, whatever happens to us. | **Data-portability guarantee + funding/customer stats** — neutralizes lock-in fear with an exit ramp. | FAQ + footer | 3 | ## Ranked Priority (highest to lowest impact) 1. (10) We already run Asana/Monday — switching is a nightmare 2. (9) My team won't adopt yet another tool 3. (9) Annual billing locks me in before I know it works 4. (8) $49/user is steep — finance will push back 5. (8) "Automated reporting" is just a buzzword 6. (7) This looks like every other PM tool 7. (7) Reports are only as good as the data my team enters 8. (6) I can't approve this spend alone 9. (6) It won't connect to our stack 10. (5) Onboarding 50 remote people will eat weeks 11. (5) The real price is higher than $49 12. (4) Is our data secure? 13. (4) I can't prove the ROI to my boss 14. (3) Now is a bad time to change core tooling 15. (3) What if you get acquired or shut down? ## Top 5 Rewritten (publish-ready landing-page copy) **1. Switching from Asana or Monday** > **"We can't rip out Asana — migrating 50 people would take weeks."** > You won't lose a single project. Connect your Asana or Monday workspace and we import every project, task, comment, and assignee automatically — most teams are fully moved in under an hour, not weeks. Keep your old tool running in parallel until you're ready. Nothing breaks, nobody loses work, and you don't spend your weekend doing data entry. > *[Watch the 90-second migration →]* **2. Adoption without the nagging** > **Your team adopts it without learning a new tool.** > The reason last rollout stalled? You asked everyone to open one more app. Here, task updates happen where your team already works — a status change in Slack, a merged PR in GitHub, a moved ticket in Jira. It all flows in automatically. Teams hit 90%+ weekly active in their first week, because there's nothing new to remember. You stop being the person who chases people for updates. > *[See how Acme's 60-person team adopted it in 5 days →]* **3. The 60-day proof window** > **Annual billing, zero annual risk.** > We know signing for a year before you've seen results is the hard part — especially when it's your name on the PO. So you get 60 days to put it in front of your whole team. If it doesn't earn its place in your stack, email us and we refund every dollar. No clawback, no "retention call," no fine print. You commit only after you've already proven it works. > *[Start your 60-day proof →]* **4. Cheaper than the reporting it replaces** > **$49/user — and it pays for itself before the first quarterly review.** > Add up what status reporting actually costs you: managers stitching together updates, weekly standup prep, the Friday scramble to build leadership dashboards. For a 50-person team that's 6+ hours a week of skilled time — roughly the cost of a mid-level hire over a year. This automates all of it. Drop your team size into the calculator and see your number before you talk to finance — then hand them the one-page brief. > *[Calculate your savings →]* **5. Reporting that actually runs itself** > **Reports that build themselves — and post to Slack while you sleep.** > "Automated" usually means "you still clean it up Monday morning." Not here. Every Monday at 9am, a complete status report assembles itself from live task data and drops into your leadership channel — owners, blockers, progress, on-track flags, all current. You don't open a dashboard, you don't chase updates, you don't format a thing. Watch one generate in real time with sample data. > *[Generate a live report →]* ## Missing Trust Builders (prioritized, each with the action to close it) 1. **No incumbent-displacement proof.** The single biggest objection (switching) needs a named "Migrating from Asana/Monday/ClickUp" page with a timed migration video and a before/after from a real switcher. 2. **No quantified adoption evidence.** Publish a case study leading with a hard adoption stat (e.g. "92% weekly active in week one") from a 20–100 person remote company that mirrors the buyer. 3. **Weak risk reversal for annual billing.** Make the 60-day, no-clawback refund a visible badge at the pricing section and beside every CTA — not buried in the FAQ. 4. **No ROI calculator.** Build an interactive seats-and-hours calculator so the buyer self-generates the number they'll defend to finance. 5. **No CFO-ready business case.** Offer a downloadable one-page ROI brief so the ops manager can sell the spend upward without authoring it themselves. 6. **No side-by-side comparison.** Add a comparison table vs. the top 3 incumbents, emphasizing the remote-native and auto-reporting differentiators rather than feature parity. 7. **Data-accuracy story is implicit, not stated.** Add a "Reports stay accurate even when people forget to update" module showing integrations auto-populating status — this is the sophisticated, unspoken killer. 8. **Security proof not surfaced.** Place SOC 2 / encryption badges in the footer trust bar and link a dedicated security page; ops buyers scan for this before they commit. 9. **No parallel-run / "bad timing" answer.** Promote the run-alongside-your-current-tool option near the CTA to dissolve the "not now" stall. 10. **No data-portability guarantee.** State "export everything anytime, no lock-in" in the FAQ to neutralize the startup-longevity fear with an exit ramp. A note on what would sharpen this further: the analysis assumes a generic feature set (Slack/GitHub/Jira integrations, auto-reporting, refund policy). If any of those don't actually exist in the product, swap the corresponding proof for one you can stand behind — a fabricated guarantee or integration is the fastest way to convert an objection into a refund.