13 Years at Salesforce, Now Running a 3-Person Marketing Team: What Lauren Esposito Found in the Gap

Lauren Esposito spent 13 years at Salesforce leading some of the company's most complex brand integration work -- helping more than 20 acquired companies come into the Salesforce ecosystem, building the first global brand marketing organization, and working on the launch of Agentforce. When she joined Asymbl as CMO, she walked into a different kind of challenge: a full repositioning of a Salesforce partner into an AI workforce orchestration company, with a team of three and four months to get it done.The answer was the company's own philosophy. Asymbl does not deploy AI as a set of tools. It hires AI as a workforce - with names, job descriptions, KPIs, and a human manager responsible for coaching each digital worker week over week. The rebrand was built by running that philosophy on the rebrand itself.In this episode, Lauren breaks down how the work got done, what the AI org chart at Asymbl actually looks like, what she is looking for in AI-fluent hires, and why she believes the biggest rebrand mistakes come from projecting too far ahead rather than staying grounded in what is true right now.Key topics covered:Why Asymbl repositioned from a tools-focused AI narrative to treating AI as digital workers with human managersHow Lauren executed a four-month rebrand with a team of three and a 60-day budget, using AI to cover the execution gapThe internal AI org chart: Casey (digital content guardian), Sim (mascot turned generative asset), the inbound prospecting worker, service workers tracking project risks, and a Slack-based digital worker made up of 50 agentsAI fluency in hiring: the new role type Asymbl is building - people who coach and manage AI rather than just use itThe governance reality: skills that get built and then locked down, integrations that go offline, and why mitigation planning is not optionalBuild vs. buy vs. borrow: why the question is not just "can we build this?" but "should we?"Community sharing -- an internal Slack channel where employees share what they have built -- as the fastest driver of adoptionRebrand advice: authenticity over tactics, and staying grounded in what is factually true rather than chasing trendsGTM Takeaways:Repositioning requires a "why" before a look. Lauren's first step was not naming a design agency. It was answering why the rebrand was necessary. The answer - Asymbl had developed a genuinely distinct philosophy around AI as a workforce - became the foundation for every brand decision that followed.Apply your own product to your own work. The only way a team of three could execute a four-month rebrand was to use the same AI workforce approach Asymbl sells to clients. Name your digital workers. Asymbl gives every AI worker a name and a place on the org chart. Lauren found that naming accelerates adoption: "when you kind of name these digital workers, it's the same thing as naming your mascot. All of a sudden you can assign it a role, a mental model in your head how to work with it, how to collaborate with it. And that adoption, right, just kind of sinks in almost naturally."Every AI worker needs a human manager. At Asymbl, every digital worker has a human manager responsible for coaching them week over week. This is not cosmetic structure - it is the accountability mechanism that keeps AI outputs aligned with business needs.Start with what you dread. The most practical advice Lauren offered for AI adoption: find the task that costs you the most energy and figure out how to offload parts of it first. Community beats mandates. An internal Slack channel where employees post what they have built drove more AI adoption at Asymbl than any structured program. Governance is a present problem, not a future one. Skills Lauren built got locked down. Her Claude-Slack integration went offline. She learned directly that over-reliance on AI systems carries real operational risk and that mitigation strategies need to exist before something breaks - because it will.