## Objection Map | # | Objection | Type | Customer's exact thought | One-line counterargument | Recommended proof | Funnel stage | |---|-----------|------|--------------------------|--------------------------|-------------------|--------------| | 1 | Status quo works | need | "Look, the spreadsheets and Slack aren't pretty, but the work gets out the door. Why blow up a system that's fine?" | "Fine" hides the unbilled hours and blown budgets you only notice at month-end, which is exactly what one dashboard surfaces in real time. | data point | landing/product page | | 2 | Team won't adopt it | complexity | "My designers already resent 'process.' I'll pay for this and they'll go right back to Slack in two weeks." | Task, time, and budget live in one screen instead of three, so there's less to log, not more, which is where adoption usually dies. | demonstration | landing/product page | | 3 | Cost vs. free tools | price | "Twenty-nine a head? For ten people that's three grand a year for stuff we basically do for free right now." | If the app helps each person recover even one billable hour a month, the seat pays for itself several times over. | data point | landing/product page | | 4 | Just another PM tool | competition | "I've tried Asana, Monday, ClickUp. They all promise the world and I churned off every one. What makes this different?" | Those tools track tasks; the difference here is client budgets tied to logged time in the same view, so profit isn't a separate spreadsheet. | comparison | comparison | | 5 | Migration pain | complexity | "Moving every active project out of spreadsheets is going to eat a week I don't have. Not worth the disruption." | You can import existing project sheets and start with live work only, rather than rebuilding history before you get value. | demonstration | decision/CTA | | 6 | Per-seat scaling | price | "Per-user pricing punishes me for hiring. Every new person makes my 'productivity tool' more expensive." | The recovered billable time scales with each seat too, so a bigger team means the tool defends more revenue, not just costs more. | comparison | comparison | | 7 | Unknown vendor | trust | "Never heard of you. What happens to all my client data if you fold in eight months?" | Ask for the data-export policy and uptime record up front; a tool worth trusting lets you leave with everything you put in. | guarantee | decision/CTA | | 8 | Data security | trust | "Client budgets and rates are the most sensitive numbers I own. Where does that live and who can see it?" | Confirm encryption, access controls, and where data is hosted before entering a cent of financial data. | data point | checkout | | 9 | Bad timing | timing | "We're mid-launch for three clients. I can't switch tools in the middle of this chaos." | Run it alongside your current setup on one new project first, so nothing in-flight gets touched. | demonstration | decision/CTA | | 10 | Paying for idle seats | price | "Half my team logs in twice a week. I'll be paying full price for people who barely touch it." | Even occasional users still log time and hit deadlines in it, which is the data the budget view depends on. | case study | comparison | | 11 | Redundant with Harvest/Toggl | competition | "I already pay for a time tracker that works. Why rip it out for this?" | Standalone time tracking still leaves you exporting hours into a budget spreadsheet by hand, which this removes. | comparison | comparison | | 12 | Setup burden on the owner | complexity | "This is going to land on me to configure, and I'm already the bottleneck for everything." | A pre-built agency template means projects, roles, and budgets are structured out of the box, not built from a blank slate. | demonstration | landing/product page | | 13 | Overkill / feature bloat | need | "All-in-one usually means a hundred features I'll never use and can't turn off. I want simple." | The three things it combines are the three you already track daily; there's no fourth workflow to learn. | testimonial | landing/product page | | 14 | Wrong moment to spend | timing | "Cash is tight this quarter. A new recurring bill is the last thing I want to sign up for." | A monthly plan means you can validate the savings on one billing cycle before committing to anything longer. | guarantee | decision/CTA | | 15 | Wasted spend if it flops | risk | "If we commit and it doesn't stick, that's money gone and my data trapped in yet another dead tool." | A trial plus a clean export path means the downside is capped at one cycle, not a year of lock-in. | guarantee | checkout | ## Impact Ranking 1. **[TOP 5]** Status quo works (#1) — the default is doing nothing; every buyer feels this and it silently kills the sale. 2. **[TOP 5]** Team won't adopt it (#2) — most owners have been burned before and treat adoption failure as the likeliest outcome. 3. **[TOP 5]** Just another PM tool (#4) — prior churn off Asana/Monday makes differentiation the make-or-break question. 4. **[TOP 5]** Cost vs. free tools (#3) — the price is weighed against $0 they're paying now, not against competitors. 5. **[TOP 5]** Migration pain (#5) — perceived switching effort blocks even buyers who already believe in the value. 6. Unknown vendor (#7) 7. Per-seat scaling (#6) 8. Redundant with Harvest/Toggl (#11) 9. Wasted spend if it flops (#15) 10. Data security (#8) 11. Overkill / feature bloat (#13) 12. Setup burden on the owner (#12) 13. Bad timing (#9) 14. Paying for idle seats (#10) 15. Wrong moment to spend (#14) ## Top 5 Sales Copy **1. Status quo works** Your spreadsheet-and-Slack setup works right up until the end of the month, when you find out a project ran over budget three weeks ago and nobody flagged it. The cost of the status quo isn't the tools you're paying for — it's the margin that quietly leaks while you're heads-down on the work. One dashboard shows tasks, hours, and budget burn against each client in real time, so you catch the overrun on day three, not on the invoice. **2. Team won't adopt it** You've watched a "productivity tool" get abandoned before, usually because it asked your team to log the same thing in three places. This puts tasks, time, and budget on one screen, so there's less to enter, not more — the reason most tools get quietly dropped. Try it on a single project and see whether your team is still using it in two weeks before you roll it out. **3. Cost vs. free tools** At $29 per seat, the honest question is whether the tool recovers more than it costs — and for most agencies, one billable hour clawed back per person each month already covers it. Your spreadsheets feel free because the price shows up somewhere else: unbilled time and budget overruns you can't see until it's too late. Put the numbers side by side for your own team and decide from there. **4. Just another PM tool** If you churned off Asana, Monday, or ClickUp, it's probably because they tracked tasks brilliantly and told you nothing about whether the project was actually profitable. That's the gap this fills: logged time flows straight into each client's budget, so profitability lives in the same view as the work instead of a separate spreadsheet you update on Fridays. Compare it feature-for-feature against whatever you last tried and look specifically at the budget view. **5. Migration pain** You don't have a free week to rebuild every project from scratch, and you shouldn't have to. Import your existing project spreadsheets and start with live work only, leaving finished jobs in the archive where they belong. You get a working dashboard the same afternoon, not after a migration marathon. ## Trust Gap Analysis **No stated guarantee or trial** — The offer names a price but no risk-reversal. Add a free trial or a first-cycle money-back guarantee so buyers can validate savings before committing; this directly disarms objections #14 and #15. **No data-export / no lock-in commitment** — Owners fear trapped client data (#7, #15). Publish a plain one-click export policy so leaving is visibly easy, which paradoxically makes people more willing to start. **No security signals** — Client budgets and rates are the most sensitive data these buyers hold (#8). State encryption, access controls, hosting location, and any compliance certifications on the pricing and checkout pages. **No agency-specific social proof** — There are no testimonials or case studies from comparable 5–20 person creative shops. Gather 3–5 short outcome stories (hours recovered, overruns caught, adoption rate) from real agency users and place them beside the differentiation and adoption copy. **No quantified value claim you can stand behind** — Several counterarguments lean on "recovers billable time" and "catches overruns." Measure this with real users and turn it into a defensible number (e.g., average hours recovered per seat) rather than a promise. **No onboarding / migration support offer** — Migration fear (#5) and setup burden (#12) go unanswered. Offer a pre-built agency template plus guided import or a setup call, and say so explicitly on the product page. **No pricing transparency on commitment terms** — It's unclear whether $29 is monthly or annual, and whether seats can flex down. Clarify month-to-month availability and how seat count adjusts when the team shrinks, to defuse #6, #10, and #14.