When a customer has the problem, but still won’t switch
Something we’ve been learning in B2B:
Having a painful problem doesn’t automatically mean someone is ready to buy a solution.
A team might complain about spreadsheets, manual attendance, messy reporting, or repetitive admin work and still keep doing it the same way.
Why?
Because the current process is familiar.
That has changed the questions we ask during customer conversations.
Instead of only asking:
“What problems are you facing?”
We’re paying more attention to:
“What changed recently that made this worth fixing now?”
That second question seems to reveal much more about urgency, timing, and whether someone is actually ready to change their workflow.
For other B2B builders:
What signals tell you a prospect is ready to switch, rather than simply interested in a better solution?
That maps well to what we see. The trigger usually is not the pain itself, it is the moment the old way starts costing money or visibility, like a payroll error or a missed handoff someone finally owns. For us the buyers who can name that event are the ones who actually switch. With Trackly sitting on top of the tools teams already run, does the urgency signal show up in the data early enough to act on it, or only once the cost has already landed?
Having the problem is only one side of the sale. The replacement has to overcome migration risk, learning cost, internal approval, and the fear of breaking an existing workflow. Mapping those switching costs explicitly often reveals a smaller first wedge than a full replacement.
for early-stage founders struggling to find users, it's a huge difference between someone knowing they need users and someone genuinely ready to change their approach to get them. Many keep trying the same generic tactics across too many channels because it feels like 'doing something,' even when it's clearly not working. The readiness often appears when they hit that peak frustration, realizing the current, familiar process is actively hindering growth and there's no clear next step. That's when they're truly open to a structured, focused path rather than just another tip.
Exactly. We’re seeing the same with Trackly. Teams often tolerate messy attendance or reporting workflows until the friction starts affecting payroll, visibility, or day-to-day operations. That’s usually when the conversation shifts from “interesting” to “how do we actually switch?”
Seems like the trick is less about building a perfect solution and more about precisely pinpointing that breaking point for your ideal user, then making sure your message hits that exact spot. It's tough when you're just starting and still figuring out who those users even are, let alone their deepest frustrations.
The "what changed recently" question is the one that separates lookers from buyers for us. A prospect who can name the event that made the old way painful, like a new hire, a failed audit, or a missed deadline, is ready to move. A prospect who can only describe the pain in general terms is still comparing. We also look for a second signal: whether the person we are talking to has authority to change the workflow or has to sell it internally. Do you find the trigger event is usually external, like compliance pressure, or internal, like headcount changes?
Mostly internal for us. With Trackly, headcount growth, remote/field expansion, or payroll and attendance issues tend to create the strongest urgency. External pressure can help, but internal operational pain usually drives the actual switch.