Sometimes We Talk Clients Out of Spending the Money

Once, a client came to us with budget in hand for a self-hosted e-commerce build. Clear requirements, money ready — the kind of deal client-services teams dream about. We talked for two hours, and at the end we told him: "You shouldn't self-host right now. Go build your business on a storefront platform first." We let that deal go with our own hands.

Not out of nobility. It's because we run a brand e-commerce store ourselves and know the true cost of self-hosting all too well: not just the development fee, but the monthly operations afterward, the 3 a.m. payment-gateway incidents, the ongoing investment in updates. At his order volume and team size, that money would have bought a "great system he couldn't afford to keep." A platform's monthly fee is rent, yes — but an apartment you can afford beats a mansion with a mortgage you can't pay off.

The proposal clients want to hear is this industry's biggest trap

Client services has a structural temptation: whatever the client wants to do, you say yes. You get paid either way, and if it fails, that's the client's decision problem. Many proposals are, at their core, not "what you need" but "what you want to hear."

It got more obvious after the AI boom. Of the "help us adopt AI" requests we've received these past two years, a substantial share ended — after we mapped the workflow — with our conclusion: not yet. Some problems were solved by one automated report. Some processes had too little volume, with AI's build-and-maintain cost far exceeding the labor saved. We pay our own LLM bills and run a subscription AI product, so we can calculate which projects have negative ROI — and then we lay that calculation out in front of the client.

The agreeable proposal wins you this deal; the honest advice keeps you this person. We choose the latter, because we plan to be around a long time.

Talking clients out of it is actually a business strategy

Here's a counterintuitive observation: the clients we've talked out of projects come back at a higher rate than the ones who signed.

The reason isn't hard to see. When a vendor is willing to give up its own revenue for your benefit, you remember it. That client we sent off to a storefront platform? His business actually took off — repeat purchase rate and order value eventually grew enough to justify self-hosting. Who did he call first? The people who once told him not to spend the money. Because in the entire market, only one team had been proven to say things aligned with his interests.

And talking someone out of a project isn't rejection — it's offering a better path. We spell out: under what conditions you should come back to this, which numbers to watch for first, and what cheap preparation you can do in the meantime. That takes several times more effort than saying "sure, let's build it" — but that's what consulting is. Otherwise you're just a contractor.

To be blunt, we have selfish reasons too

There's a very practical reason for honest refusal: a bad-fit project is a loss for both sides. The client spends money without results and feels cheated; we build something doomed to fail, gain nothing for the portfolio, and pay for it in reputation. Earning one less deal in the short term removes a long-term landmine.

So if you come to talk to us about a project, expect one of two outcomes. Either we tell you how to build it, what it costs, and how long it takes — numbers we even publish on our website — or we tell you not to do it yet, and when to come back. We mean both answers equally. After all, in this industry, people who will tell you the truth may be rarer than people who can write code.