A field guide to weasel words in software pitches

Software sales has a dialect. It sounds technical, it sounds confident, and a lot of it means nothing at all. The words are chosen to make you feel reassured without giving you anything you could later hold them to. That’s the trick: a promise you can’t measure isn’t a promise, it’s a mood.

You don’t need to learn to code to see through it. You need to know which words are load-bearing and which are decoration, and you need one good follow-up question for each. When a vendor uses a word from this list, don’t nod. Ask the question. Watch whether the fog turns into a fact or gets thicker.

“Enterprise-grade”

The most reassuring meaningless phrase in the business. It’s meant to summon images of banks and airlines running your software without a hiccup. It’s not a standard, a certification, or a measurement. Anyone can print it on a slide.

Sometimes it points at real things: independent security audits, uptime guarantees written into a contract, the ability to handle serious load. Usually it points at nothing, because if the real things existed, the vendor would name them instead of the vibe.

Ask: “Enterprise-grade how, specifically? Show me the uptime commitment in the contract, the security certification, and a customer your size running it.” Real answers are boring and concrete. Weasel answers circle back to the word.

“Scalable”

Every product is scalable until you scale it. The word implies your growth will be effortless, and it quietly transfers the risk of that promise onto you.

The question that matters isn’t whether it scales in theory. It’s what happens to the price and the performance when you actually grow. Plenty of “scalable” tools scale beautifully in capability and brutally in cost, so that succeeding with them becomes the thing you can’t afford. Others slow to a crawl once your data gets big, which the small, clean demo dataset was carefully chosen to hide.

Ask: “Show me this running with ten times the data and users I have now. What does the same screen look like, and what does the bill look like?”

“AI-powered”

The phrase of the moment, and increasingly the least informative. It’s been bolted onto everything, so on its own it tells you roughly as much as “electricity-powered.”

The useful questions sit underneath it. What does the AI actually do here, and what happens when it’s wrong? Where does your data go when the feature runs, and does it leave the country or train someone else’s model? Is the AI doing something you needed, or is it a feature bolted on so the pricing could go up and the press release could exist? A lot of “AI-powered” is a wrapper around a service the vendor is reselling, which is fine if they’re honest about it and a problem if they’re not.

Ask: “What exactly does the AI do, where does our data go when it runs, and what happens when it gets something wrong?” If the answer is hazy on the data question, treat it as a governance question, not a features one.

“Seamless integration”

There is no such thing, and the people who say it most tend to know it least. Integration between two systems is where the hardest, ugliest work in software lives, because it’s where one company’s assumptions meet another’s and neither warned the other.

“Seamless” is doing a lot of hiding. It’s hiding whether the integration is real or a one-way export you run by hand. It’s hiding what happens when a field doesn’t match, when a record exists in one system and not the other, when the connection drops mid-sync. Ask any team who’s connected two business systems and they’ll tell you the seams are the entire job. A vendor promising none is promising they’ve solved a problem they’ve probably just decided not to mention.

Ask: “Walk me through what happens when the two systems disagree about the same record. Who wins, and how do I find out it happened?”

“Best practice” and “industry standard”

These sound like there’s a rulebook somewhere that the vendor is dutifully following. Sometimes there is, and they can name it. Usually it’s a way of ending a conversation without answering the question, by implying that what they’ve chosen is simply what’s correct and there’s nothing further to discuss.

The tell is whether they can say which standard and why it applies to you. “It’s best practice” is an appeal to an authority that may not exist. A real answer sounds like “the standard for this is X, here’s what it requires, and here’s how we meet it.”

Ask: “Whose best practice, and where’s it written down? And is it best practice for a business like mine, or best practice for the vendor?”

“Fully customisable”

A promise that quietly becomes a bill. “Fully customisable” often means the base product doesn’t do what you need, and the customising is chargeable work you’ll be quoted for later, once you’ve already committed.

There’s a real spectrum hiding here. Some products let you configure them yourself, in the settings, for free. Others require the vendor’s team, at a day rate, for anything past the defaults. Those are wildly different deals wearing the same phrase. And “customisable” can also mean “we’ll build you something bespoke on top of our platform that only we can ever maintain,” which is a lock-in you should walk into with your eyes open, not one you back into.

Ask: “Which changes can I make myself in the settings, and which need your team at a cost? Give me the two lists.”

“Trusted by industry leaders”

A logo wall is not evidence. That a big company’s logo appears on a vendor’s site tells you the big company signed up at some point. It doesn’t tell you whether they still use it, whether they use the part you care about, whether they’d recommend it, or whether they got it for free in exchange for the logo.

The move isn’t to be impressed by the logos. It’s to ask to talk to one, ideally one your size rather than the flagship, and ideally with the awkward questions rather than the happy ones.

Ask: “Can I speak to a customer my size who’s been live for over a year? I’d like to ask them what broke.”

“Free” and “unlimited”

The two words most likely to have an asterisk you’ll meet later. “Free” usually means free until the useful bit, or free until you’ve moved your data in and switching out is the expensive part. “Unlimited” almost always has a fair-use policy, a soft cap, or a “we’ll be in touch if your usage is unusual” clause that surfaces the day you rely on it.

Neither word is a lie, exactly. They’re both bets that you won’t read the next paragraph. Read the next paragraph.

Ask: “Where’s the limit on the unlimited plan, and which features are behind the free wall? Point me at the fair-use terms.”

“We’ll sort that out in onboarding”

The phrase that pushes every hard question past the point of no return. Whenever a specific worry comes up in the sales conversation, and the answer is a warm “we’ll handle that during onboarding,” a small alarm should go off. Onboarding is after you’ve signed. It’s after the leverage has moved to their side of the table.

The things that get deferred to onboarding are, reliably, the things worth resolving before onboarding: the data migration, the tricky integration, the edge case that’s core to your business. If it can be sorted, it can be sorted into the contract now.

Ask: “Great, let’s sort it out now, in writing. What exactly happens with that during onboarding, and what if it can’t be done?”

The pattern under all of them

Every phrase here works the same way. It offers the feeling of a commitment while dodging the commitment itself. The defence is always the same too, and it’s not cynicism. It’s a single follow-up question that swaps the adjective for a number, a name, a document, or a demonstration.

A good vendor doesn’t mind this at all. They’ll happily trade “enterprise-grade” for the actual uptime figure, “scalable” for a live look at a big account, “seamless” for an honest walk through the failure cases. The ones who get cagey when you ask for specifics are telling you that specifics are exactly what they were avoiding.

You don’t have to be an engineer to buy software well. You have to notice when a word is doing the work a fact should be doing, and ask the question that makes it prove itself. If you’re weighing up a vendor and their pitch is starting to sound like this glossary, send us the proposal. We’ll help you turn the adjectives into questions, and read the answers with you.