Battle-Tested B2B Wisdom at SocioLogic
Marcus Thompson has been in B2B marketing long enough to have used a fax machine for lead generation. He started his career in enterprise tech in the early 2000s, back when "content marketing" meant printing whitepapers and "social media strategy" wasn't a thing.
Over two decades, he's held marketing leadership roles at companies ranging from scrappy startups to enterprise giants. He's been through three economic downturns, watched countless marketing trends come and go, and developed a healthy skepticism for anything labeled "revolutionary."
His hard-won wisdom: most marketing "innovations" are old ideas with new names, and the fundamentals of building a strong brand never really change. He joined SocioLogic after becoming convinced that synthetic user research was one of the genuinely transformative developments he'd seen in his career--high praise from someone who's seen it all.
Marcus writes with the voice of someone who's made every mistake in the book and is determined to help others avoid the same pitfalls. His articles blend strategic insight with practical advice, often illustrated with war stories from his own career (names changed to protect the guilty).
Outside of work, Marcus coaches his daughter's soccer team and has developed an unexpected passion for woodworking. He jokes that both activities have taught him more about patience and long-term thinking than any business book.
Walled gardens won't work for agents any better than they worked for the early web
Every major platform company is building a closed agent ecosystem. History says that's the wrong move. Agents need open protocols for discovery and payments the same way the web needed HTTP.
Connecting your AI to random services is the new shadow IT
When your AI agent connects to an unverified API, you're trusting a stranger with your data, your money, and your reputation. Here's what actually goes wrong and how verification layers help.
Five layers, dozens of companies, and a lot of unsolved problems
The agent infrastructure stack is taking shape. Transport, discovery, payments, verification, orchestration. Here's who's building what, where the gaps are, and where we fit.
Infrastructure layers have to be open. Everything else is negotiable.
We published the .well-known/agent-card.json spec as open source. Here's why open beats proprietary for infrastructure, and what we deliberately kept closed.
An honest map of who's building agent infrastructure, five months in
The agent infrastructure stack is crystallizing into distinct layers. Here's who's building what, where consolidation is happening, and where the gaps are. Including an honest take on where we fit.