Keynote is such a minor part of attending a 2 day conference that 10x is a conservative estimate.
Edit: And that's just "things learned" that doesn't even count the 20-30 conversations had that can spark collaborative efforts.
Keynote is minimal.
I don't think the OP was suggesting you hire the keynote speaker to come, deliver their keynote and leave. The point is that you could do a lot more than that.
Don't think of it as education. Think of it as spies debriefing the station crew at the embassy.
I'm not sure developers are naturally skilled at parsing presentations (done by other developers, who also often aren't fantastic presenters) into meaningful presentations to give back in the office. Not that conferences aren't worth it, I'm just not sure they're worth it for that.
Yes it could happen - but mostly it doesn't. Particularly if we're talking about engineers in tech.
Those employees are representing the company when they attend, network, and quite possibly sell the company's services or products to others that they meet.
If those employee have speaking spots (they're speaking at the conference), then the company has an even better chance at getting the company's name out there in front of a lot of people. In that case, the company can benefit even more when it comes to branding and other benefits that speakers give the company.
You also lose out on the (IMHO) most important and useful part of conferences: the hallway networking.