A Great Product, Dying of the Wrong Comparison
Every deal she loses, she loses to Asana. The product was never built to beat Asana. Find the fix before the board meeting.
You're advising Priya, founder of RouteIQ, a scheduling and dispatch tool built specifically for field-service companies — HVAC, plumbing, electrical crews juggling technicians, trucks, parts, and same-day emergency jobs. She built it after three years running ops at an HVAC company herself, and the product genuinely solves the hardest part of that job: reassigning a tech mid-route when a job runs long, without every other appointment that day sliding into chaos.
RouteIQ launched on its landing page and in every sales call as 'project management software for service teams.' The website hero says 'Organize your team's work in one place.' It worked, for a while — inbound was decent. But the sales team keeps reporting the same pattern, and Priya is starting to panic ahead of a board meeting where she needs to explain a soft quarter.
| Signal (last 2 quarters) | Detail |
|---|---|
| Deals where prospect explicitly compared to Asana/Monday.com | 68% of lost deals |
| Most common lost-deal reason (CRM notes) | "Doesn't have as many features as [Asana/Monday]" |
| Feature RouteIQ has that Asana/Monday don't | Live GPS re-routing when a job overruns — the #1 thing happy customers cite |
| Trial → paid conversion | 11% (category benchmark for niche vertical tools: ~25-30%) |
| Sales cycle | 54 days average — closer to horizontal PM-tool cycles than vertical tools |
| NPS among closed-won customers | 61 (very strong) |
| Common quote from happy customers | "I don't know how we dispatched before this." |
| Common quote from lost prospects | "It's basically Trello with a map, right? We already have Monday." |
Priya's instinct is to catch up on features — add more generic task boards, more integrations, more views — to compete head-on with Asana. "If they think we're missing stuff Asana has, we should just build that stuff," she says.
Data snapshot
Priya wants to build more generic project-management features to compete with Asana and Monday.com feature-for-feature. Tell her whether that's the right move. Diagnose what's actually broken using the numbers above, identify the competitive alternative RouteIQ should be positioned against instead, and write the repositioning move — the market category and the language — you'd have her test in the next sales calls, plus how you'd know within a quarter if it's working.
Rubric
- Rejects the feature-catch-up trap. Explicitly argues against building more generic PM features to match Asana, and explains why chasing feature parity in the wrong category is a losing game (Asana will always have more generic PM features).
- Diagnoses the real problem as positioning, not product. Uses the NPS-among-closed-won (61) versus the 11% trial-to-paid gap to show the product itself is strong — the losses happen before people experience it, because they're mentally filing it in the wrong category and judging it by the wrong yardstick.
- Names the competitive alternative correctly. Identifies that RouteIQ is being compared to horizontal project-management tools (Asana/Monday) when its real competitive alternative is manual dispatch/whiteboards/spreadsheets or dedicated field-service tools — and that its unique value (live re-routing) only matters against that alternative.
- Concrete repositioning move. Proposes a specific new category framing (e.g. 'dispatch software for field-service teams' / field service management) and rewrites the core language away from generic 'organize your team's work,' anchored on the re-routing capability and the ops-background story.
- Names a way to test it. Gives a concrete, time-boxed way to validate the repositioning (e.g. rerun a subset of sales calls or landing traffic with new category framing next quarter, track lost-deal reasons and trial-to-paid conversion as the signal) rather than asserting it will just work.