Employee Advocacy

Alan Shimel's argument that Google's AI Overviews are engineered to make the click unnecessary — his "Google Zero" — lands as hard on technology vendors as on publishers, because organic search was always rented distribution that merely felt owned. The largest untapped alternative is already on staff: a few hundred customer-facing employees, each publishing a weekly newsletter carrying the company's news section, is hundreds of trusted channels reaching the market with no algorithm in between. It succeeds where employee advocacy usually fails because the employee owns the asset, and the resulting traffic is attributable and rewardable per person.

Top sellers are the hardest people in the company to reward — cash is already maxed, the incentive trip ends, and promotion into management is often unwanted — while the independent streak that makes them outperform is exactly what makes corporate advocacy mandates slide off them. Sponsoring a personal newsletter inverts the offer: the firm pays, the rep owns it outright and marketing doesn't edit it, and the only ask is that the company news section rides along at the same usefulness bar. Kept scarce it becomes visible status rather than a program, and it buys marketing leadership a standing relationship with the best sellers in the building — plus weekly reach into the highest-trust networks the company has.

Sellers at large firms routinely stall on a personal newsletter because they haven't been approved to run one — and Scott McNealy's Sun-era mantra explains why asking is the wrong move: the person receiving an unprecedented request has no upside for yes and all the downside, so the safe answer is defer or decline, and a "no" on the record is far harder to reverse than a question nobody formally raised. The article draws a hard line between *prohibited* and *unprecedented* — follow any written policy, publish nothing confidential, never speak for the company — and notes that what remains is publicly available industry news posted on your own profile. The asymmetry is the sharp edge: Oracle and its peers cut tens of thousands of roles without asking anyone's permission, so waiting for that same party's blessing before building your own name misreads the relationship. A personal newsletter is guerrilla marketing — outsized exposure with no budget line, no creative review and no approval gate — and LinkedIn's five-newsletter allowance, each launch notifying your entire follower base, is five platform-delivered invitations: start vendor-neutral, make the second one match your role (a covered vendor, or *News From Our Partners* for solution providers), and change what you publish when the role changes, because you're the publisher.

Many reps abandon the idea of an industry newsletter once they picture the week their biggest competitor announces something great — publish it and you've advertised a rival to your whole prospect list; omit it and you're the biased vendor mouthpiece you were trying not to be. Filtering by hand fails under volume and produces a feed that reads as a brochure. The fix is taxonomy rather than vigilance: because vendor news is filed under vendor names, category sections are neutral by construction, while your own company's section is held to the same usefulness standard as everything else.