Sure, but if a client asks what you're doing, and you suspect they're not clueful about the work, you'd tailor your reply to as close to plain English as possible. But when you're talking to experts you correctly use jargon to rapidly communicate actual information.
There's a big difference between the example you gave and "executive" speak. About 80% of the uses I see of "leverage" / "leveraged" / "leverages" are bullshit. Not just 'could be replaced by use / used / uses' bullshit, but 'if replaced becomes meaningless' bullshit. It's not that people do not understand business talk, it's that much of it is vacuous nonsense that carries no information once you've decoded it.
The underground grammarian has some stuff about this (http://www.sourcetext.com/grammarian/) (although I can't remember where) when he gives an example of a legal definition for a door. It's a long, technical definition, and it's hard to understand. It's the kind of thing that people often make fun of. But he points out the context (maybe legislation about fire exits?) and says that being exact is important, and in that case it's good that there's no ambiguity.
I've totally heard people rattling off jargon where it didn't add anything. It didn't remove anything (save perhaps understanding by some within earshot), it's pointless complexity, and I'm a person who thinks pointless complexity should be eliminated.
If you didn't have intimate knowledge of modern web development, everything in that sentence could be a meaningless buzzword and you'd have no idea.
When I hear friends talk about a domain I have little experience in, I usually have little idea what they're saying.