They Sold You a Builder, Not a Solution
The most common reason software fails in service businesses isn't the software. It's that the vendor handed over a toolkit and called it a solution. Three customers, same story.

Review notes: Problem-aware. Quotes name HubSpot and SleekFlow critically — needs a call on whether we name competitors or genericise before publishing. Evidence: school group, hospital group, independent travel agent.
This is the most repeated story in every sales call we've had this year, and almost nobody in our category writes about it.
A marketing lead at a five-campus international school group, explaining why they were looking to switch CRM:
"We didn't quite get the support that we wanted at the beginning, so we were left in the dark without any support."
Then she reached for an analogy that we've been unable to improve on:
"It's like an electrician job. You call an electrician, you would expect them to come with the tools and set it up for you or fix the problem. But it was different. When we explained that we have an issue, what they do is they just throw us tons of YouTube videos and PDF documents. Oh, this is how you can do it. Here you go, here's the resources. And you do it yourself, you fix it yourself."
And the conclusion:
"We're kind of fed up with that, because we pay a lot of money to them. And it's not that the tools aren't good — it's because we don't know how to use the tools that they have. We don't have the right guidance, we don't have the right support, and we had enough."
Read that middle sentence again. It's not that the tools aren't good. She is explicitly not blaming the product. She's blaming the handover.
Three companies, one story
A private hospital group, on a WhatsApp automation platform they'd tried before us: "The setup is quite challenging, because we have to set the workflow like — they ask this keyword, what might be our answer if they say that." We asked whether the vendor helped build it. "No, we need to set it ourselves."
An independent travel agent, thirty years in the trade, on a marketing tool someone sold him: "They will teach us how to do it and ask us to post on our own, which I do not know how to post, and that's a lot of restriction. That's why I just forget about it."
That's why I just forget about it. That is what churn sounds like from the inside. Not a cancellation email. A quiet decision to stop opening the tab.
Why this keeps happening
Software vendors are structurally incentivised to ship a builder rather than an outcome, because a builder scales and an outcome doesn't. A workflow builder serves ten thousand customers with one codebase. Actually configuring a five-campus school's admissions pipeline serves one.
So the industry solved its own problem and handed yours back to you: documentation, video libraries, certification courses, a community forum. All genuinely useful, all fundamentally a transfer of labour from the vendor to the buyer.
For a company with an operations team, that transfer is survivable. For an admissions office of four people, a hospital marketing team of three, or a one-man travel agency, it isn't. The school group above told us plainly: "We're talking about non-technical... being not technical necessarily in our team to be using this. So it will definitely take some time."
They were right. It took so much time they gave up and went shopping.
The tell, before you buy
Ask these during the sales process. The answers are diagnostic.
- "Who builds the first version — you or us?" If the answer involves the word "enablement," it's you.
- "What happens when it breaks in month four?" Not month one. Month one everyone is attentive. Month four is the real answer.
- "Can I speak to a human?" One head of edtech told us, mid-demo: "I was hoping that it's a real human, because everything is AI. We will get frustrated. Like, can I get to talk to a real human?" She was evaluating an AI product at the time. That's not a contradiction — it's a requirement.
- "What percentage of the features we're being shown will we actually use?" The same school group had already lived this: "One of the biggest issues we have is we're only using one third of the functions, and we're paying a lot of money for it."
The uncomfortable part
Every vendor reading this, including us, has to answer for it. So here is our honest position rather than a claim.
Setup work that a customer cannot do themselves has to be done by someone, and that someone costs money. Any vendor who says otherwise is either subsidising it temporarily, hiding it in the price, or about to hand you a video library. The question is not whether implementation labour exists. It's whether it's on your side of the line or ours, and whether anyone said so out loud before you signed.
Ask us the four questions above. Ask our competitors too. The answers will tell you more than any feature comparison.
LinkedIn native post (link in first comment)
"You call an electrician, you'd expect them to come with the tools and set it up for you."
That's a marketing lead at a five-campus international school, explaining why they're leaving their CRM.
"But what they do is they just throw us tons of YouTube videos and PDF documents. Oh, this is how you can do it. Here you go. And you do it yourself, you fix it yourself."
Then the line that matters: "It's not that the tools aren't good. It's that we don't know how to use them. We don't have the right guidance. And we had enough."
She isn't blaming the product. She's blaming the handover.
I've now heard the same story three times this year from completely unrelated businesses:
— A hospital group on a WhatsApp platform: "We have to set the workflow ourselves." Did the vendor help? "No, we need to set it ourselves."
— A travel agent, 30 years in the trade: "They teach us and ask us to post on our own, which I don't know how to do. That's why I just forget about it."
"That's why I just forget about it" is what churn actually sounds like. Not a cancellation email. Someone quietly stops opening the tab.
Four questions to ask any vendor before you sign 👇
LinkedIn article angle
Lean into the structural argument — why the SaaS business model produces builders instead of outcomes. More opinionated, better for authority. Title: Your Software Didn't Fail. The Handover Did.
CTA
The four vendor questions → website.
Yalla is the chat-native CRM where the AI does the work, not just the talking.
See how much of your business it can reach.
or book a free demo