Source: The Artificial Intelligence Show (Marketing AI Institute / SmarterX), YouTube (yt-podcast), August–September 2026. The four case studies come from the “AI Transformations” series hosted by Mike Kaput and “presented by Google Cloud” (each episode carries a Gemini Enterprise ad read):
- Ep 234 HubSpot —
raw/Ep._234_-_How_HubSpot_Is_Reimagining_the_Entire_Customer_Journey_With_AI_Agents.md· https://www.youtube.com/watch?v=QCBKRp1jEMA - Ep 238 Peapack Private —
raw/Ep._238_-_How_a_700-Person_Bank_Is_Using_AI_to_Build_Apps_Agents_and_Digital_Employees.md· https://www.youtube.com/watch?v=IIHsCFPo2zY - Ep 240 David’s Bridal —
raw/Ep._240_-_How_David_s_Bridal_Is_Rebuilding_a_76-Year-Old_Business_Around_AI.md· https://www.youtube.com/watch?v=MFc9UP0XwUU - Ep 242 Baptist Health —
raw/Ep._242_-_How_Baptist_Health_s_Marketing_Team_Took_the_Lead_on_AI_Transformation.md· https://www.youtube.com/watch?v=hw2XbmWvqiA
2026-10-27 additions:
- Ep 244 Alibaba.com —
raw/Ep._244_-_How_Alibaba.com_Is_Building_the_Future_of_Agent-to-Agent_Commerce.md· https://www.youtube.com/watch?v=pTLdkUZVpEk. Same “AI Transformations” series, but this episode carries a MAICON ad read, not the Google Cloud one. - Ep 246 AI Answers, live from MAICON (2026-10-14) —
raw/Ep._246_-_AI_Answers_-_Live_from_MAICON_2026_-_AGI_AI_Costs_and_the_End_of_GPTs.md· https://www.youtube.com/watch?v=XH1u09pL0Hk - Ep 247 (Roetzer’s FAQ-page use case) —
raw/Ep._247_-_OpenAI_Safety_Concerns_Anthropic_s_AI_Expectations_Gap_MAICON_2026_Recap_Gemini_4_Argon.md· https://www.youtube.com/watch?v=nvyNQmOTKfY
2026-11-13 addition: Ep 251 AI Answers (Roetzer and McPhillips; questions left over from the November 11 Scaling AI and September 30 Intro to AI classes) — raw/Ep._251_-_Forward-Deployed_Engineers_Shadow_AI_Owner_Bottleneck_AI_on_Your_Resume_Token_Budgets.md · https://www.youtube.com/watch?v=jLrrWAAXE_Q. AI Academy promotion skipped.
The leader Q&A is from the “AI Answers” series: Ep 236, raw/Ep._236_-_AI_Answers_-_No_Time_for_AI_AI_Budgets_Vendor_Terms_Data_Risk_AI_Disclosure.md (Paul Roetzer and Cathy McPhillips) · https://www.youtube.com/watch?v=NLFQkHiaCiQ.
Five first-hand accounts of company-wide AI adoption (Alibaba.com added 2026-10-27), each told by the executive who ran it, plus a Q&A episode of leader tactics from the show’s hosts. Every number below is the guest’s own claim, unverified and delivered on a sponsored series. The value is in the operating mechanics, which are specific enough to copy: how each company found use cases, organised builders, measured results and handled governance.
Key Takeaways
-
Agents can run the business process, not just answer about it (Alibaba.com, 2026-10-27). Accio Work’s agents handle sourcing end to end for 10M+ small businesses. A week of supplier comparison becomes a day or less, and the agent ships a new version of itself daily.
-
Measure the business metric, not the bot.
- Peapack judged its “Penny” chatbot by the support team’s ticket volume (down 60%), not by questions answered.
- HubSpot reports save rates (+7 points), meetings booked (10,000 in a quarter) and AEO conversions (almost 2,000% growth).
-
Every company put coaches inside the business:
- HubSpot: open Slack sharing channels
- Peapack: 29 AI champions embedded in business lines
- David’s Bridal: the head of product “deployed” to each leader
- Baptist Health: AI Sherpas
In each case the coaches pull use cases out of the business rather than having IT push tools in.
-
Centrally built beats rep-built. HubSpot’s globally built agents, “tuned with the right context and the right evals”, outperform what individual reps build for themselves in Gems or Glean.
-
Governance speed is now the bottleneck for marketing teams in regulated firms. Baptist’s CMCO calls year two “quicksand” and wants “lanes that are appropriately slow and appropriately fast.” Roetzer’s fix is “horizontal approvals”: approve a connector once for everyone.
-
Prerequisites are sequential. Peapack’s CTO: the data warehouse (built about five years earlier), in-house developers, then agents — “these things all need to happen linearly.”
-
AI shifts build-vs-buy even for a 700-person firm. Peapack replaced a “$375,000 plus a year” vendor quote with a Codex-built internal tool. It was “the first year that the number of third party technologies our bank used actually decreased.”
HubSpot — Agents Across the Whole Customer Journey (Ep 234)
John Dick, Chief Customer Officer, leads HubSpot’s global sales and customer success. Vendor caveat: much of his stack is HubSpot’s own product.
-
The frame. Go-to-market problems haven’t changed (“how do I build demand? How do I win deals?… happy loyal customers”). AI is interesting because it breaks old constraints: the share of sales-rep time spent talking to customers “just never moves”, and one-to-one personalised customer-success emails were impossible at scale.
-
Fluency came first. It came from the top: the CEO shared a video of how she used AI in her own day. Staff got dedicated time and “a culture of… no fear sharing” through Slack channels for posting wins.
-
Order of deployment:
- support first (“the first place where generative AI had super clear product market fit”)
- then marketing content and engineering code
- then the full journey
The early lesson from support was to optimise for CSAT, not resolution rate: “if you build great CSAT your resolution also goes up.”
-
Agents and reported results:
- an AEO strategy plus an AEO agent: AEO conversions grew “almost 2,000%” over “the last couple months”
- a demand agent that sets fit criteria and finds companies with intent signals (the “best version of our understanding of our TAM”)
- an AI SDR sales bot handling “over 80%” of website chats
- a prospecting agent that “booked 10,000 meetings” last quarter
- Guided Success, a custom rep assistant built on HubSpot’s Breeze: “the win rate is up a bunch”
- a CS assistant that triggers agents: “a seven point increase in save rates”
-
Org design went through three phases:
- “Wild west” plus hackathons.
- About a year of cross-functional pods (subject-matter experts, engineers, data people) under one AI-focused marketing growth leader, Kieran Flanagan (captioned “Flanigan”). “We moved all the KPIs.”
- About three months before the interview, all go-to-market agentic engineers, systems, data and product people and SMEs were direct-lined to him, because pods still meant “competing priorities” and “coordination cost.”
The trade-off Dick accepts: global priorities win over local experiments.
-
The goal is “from individual productivity to institutional productivity”, meaning moving P&L lines, not saving individuals minutes.
-
Advice:
- “You are not behind.”
- Pick one real problem.
- Set a high quality bar: “I hate slop… human authenticity plus AI efficiency is like the secret sauce.”
Peapack Private Bank & Trust — Champions, Codex Builds and Digital Employees (Ep 238)
The CTO (first name John; surname garbled in captions as “Cowall”/“Coowalt”) speaks for a boutique private bank: about 700 employees, 13B.
- 2023 start. They began when Microsoft Copilot was still “Bing Chat for enterprise”. Policies and governance came first, then extensive training. By the end of 2023 every employee had AI chat and AI meeting summaries.
- 29 AI champions, the CEO’s idea, are embedded in business lines and moved AI “from being technology-driven to business-driven”:
- after one year: about 100 projects completed and a pipeline of 80+
- the champions meet monthly as a group and individually with the CTO
- they present wins at a quarterly internal webinar
- they hold a dotted-line report to the CTO
- the ask to them is “bring us the challenge”, not the answer
- The CEO asked the CTO to spend 70% of his time on AI. That triggered a reorganisation and a dedicated AI engineering team. Everyone in IT has a role; support teams also support the AI tools.
- The stack is standardised primarily on OpenAI: ChatGPT Enterprise for staff, Codex for developers, enterprise APIs for agents. Project Atlas layers AI over the data warehouse schema plus a knowledge base of how the bank operates, turning analysts’ questions into queries. It logged 2,000+ interactions in a month.
- Build instead of buy. A wealth-division account-review process lived in spreadsheets; a vendor wanted “$375,000 plus a year.” AI engineers built a Codex “mini platform” pulling from the warehouse, and each review takes 50% less time.
- Digital employees are named agents that sit on top of other agents, automations, data and classic tools. They reach staff through Teams (urgent) and Outlook (routine), you can reply to them, and each has its own Mac mini where it needs a computer. They call deterministic scripts where AI isn’t needed.
- Alex (IT) watches the ServiceNow queue: it suggests replies, routes tickets and monitors escalations. A few weeks after launch it was “closing roughly half the tickets of a full-time employee.” It is being given a skill to message staff on Teams when they near their compliance-training deadline.
- MIA (“marketing intelligence agent”) runs a weekly review of all the bank’s websites for dead links and outdated content, and makes AEO/SEO/GEO suggestions.
- Naming them as members of a department rather than after a task changes what people ask of them: “It’s not the IT support bot. It’s Alex.”
- Measured outcomes:
- Penny (financial-centre chatbot): support tickets down 60% in four months
- an iPad proforma app for bankers: 100 proformas in the first month, made in about half the manual time
- a redesign of the ~55-step loan-closing process with an outside AI partner (captioned “Verapath”)
- Lessons:
- “Start simple, learn, and the innovation will come.”
- Finding use cases isn’t the hard part; being ready to implement them is.
- When something fails, “try again in a few months.” Document Q&A failed in 2023 and is now core.
- The key guardrail: “AI cannot replace a control. It can supplement controls.” Keep a formal inventory of everywhere AI is used in a process.
David’s Bridal — Pearl Planner and an In-House Harness (Ep 240)
Alina Vilk (President and Chief Business Officer) and Mike Ball (Head of Product). The company was founded in 1950; Vilk claims “90% of all brides” pass through its ecosystem.
- The problem is stress. Typical wedding checklists have about 30 steps. The real job is hundreds of connected tasks (Kaput cites 300+); one checklist line, the engagement shoot, hides about 20 decisions.
- Pearl Planner turns date, style, budget and preferences into a guided plan. It shows only what matters now (“if you’re getting married in 18 months… you’re going to see only what you need to see right this moment”) and matches vendors at the right point in the sequence.
- The vision quiz uses expert knowledge as the eval rubric. Brides pick images instead of describing a style they can’t name. Ball sat with stylists and merchandisers (“why do we call it boho?”) across dresses, flowers and cakes, and uses that knowledge on the back end to judge what the AI infers from the images.
- Budget by priority, not dollars. Couples mark categories as splurge or save. When they later need money, the assistant suggests cuts only from low-priority categories, using memory that persists across the platform.
- The stack is their own orchestration harness: agent roles, permissions, triggers and guardrails, built in-house rather than using an out-of-the-box framework so it can be reused internally. They rotate models only after reviewing evals and logs, and let new releases “sit for a little bit” first. Several agents are in use, for example one that logs expenses from receipts, screenshots or emails.
- Pearl Connect is the vendor side, “entirely powered by Google Cloud” (the series sponsor). Vendors see a bride’s vision before replying, and incoming messages are triaged by intent and sentiment.
- Traction: “hundreds of thousands of users” before any marketing; free for couples.
- Internal adoption:
- no usage mandate; start from each team’s problem statement (merchandising and finance differ)
- Ball’s rule: “30 minutes of my time will save you 10 to 15 hours a month”
- a monthly survey where most staff self-report at least 20 extra hours of output a month
- a maturity-level framework before anyone goes “full speed with Fable”
- the PMO standardised Slack and Confluence structure, with org-level rules so agents know where each project’s information lives
Baptist Health South Florida — Marketing Leads the Enterprise (Ep 242)
The Chief Marketing and Communications Officer, Christine (surname garbled in captions), runs marcom at South Florida’s largest health system: 12 hospitals, 30,000+ employees, 4,500 physicians.
- The trigger was a late-2024 talk by Roetzer (the host’s own CEO) to a room of CMOs: her “holy bleep moment.”
- Year one: literacy with teeth.
- A year-long AI curriculum built like a college syllabus: external modules, IT and HR lunch-and-learns, keynote watch parties, and dedicated work time to practise.
- Progress was tied to performance conversations and evaluations: “This wasn’t optional.”
- Baseline surveys at the start, repeated quarterly.
- Supporting structure:
- a department AI council linked to the enterprise council
- marcom-specific usage guidelines
- learning labs^[ambiguous] (see Open Questions)
- office hours and a Slack channel
- a learning hub holding resources, the team’s own use cases, and its successes and failures with the reasons
- short pilots decide whether a tool is for everyone, a smaller group or no one (per Kaput’s intro)
- AI Sherpas coach; they don’t do the work. Early on they tested tools and tutored. Now a team brings a problem, the Sherpas advise, the team builds, and comes back for more help: “iterative and supportive rather than hey, go do this for me.”
- The standout Sherpa came from restaurant entrepreneurship, not tech. The traits that mattered were curiosity, resourcefulness and fearlessness.
- The Sherpa role has become a formal job: “marketing technology transformation and enablement.”
- Results:
- Online listings: a manual job that “once took somebody about 10 hours every week now takes about two minutes”, as an automated red/yellow/green dashboard built in a couple of weeks. It is now being rolled out to the other teams that manage listings.
- Creative self-service: designers built on-brand Adobe Express templates; account teams now produce routine jobs themselves, with a human approving at the end. That cut the creative backlog and reliance on external freelancers.
- People lessons:
- What looked like resistance was “pride of expertise”, which called for more empathy while keeping expectations firm.
- Other departments (strategy, finance, HR) now join marcom’s sessions.
- Year two is “quicksand”. Tools are built but integrations stall in security and governance review. Her case: split clinical work (slow lane) from corporate functions like marketing (fast lane), because “this talent won’t sit tight.”
- Year three is workflow redesign. “Because we’re starting with traditional structures, it is very hard to build an AI native… team.” Whiteboard by function, not by people’s names, then decide where a human is actually needed.
- Advice:
- “You got to go first.”
- Leaders “cannot outsource their own AI literacy.”
- Give people “real tools, real rules, time to learn, visible support.”
Alibaba.com — Accio and Agent-to-Agent B2B Commerce (Ep 244)
Guest: Kuo Zhang (captioned “Quo”; spelling normalised, unverified), president of Alibaba.com since 2017. As with the other cases, every figure is the guest’s or host’s own claim.
- Scale. In fiscal 2026, more than 47M buyers from over 190 countries used Alibaba.com, and it had more than 240,000 paying members. Accio (captioned “Axio”) launched in November 2024 as AI sourcing search. More than 10M small businesses now use Accio Work, which consumed 1 trillion tokens over a recent three-month period. Token use is up 6× in the four months since Accio Work launched in April.
- What the agents do. They break a business goal into tasks: market research, product sourcing, supplier negotiation, store operations, marketing, logistics and compliance. The agent can also write a product design pack for a buyer who doesn’t know how.
- Why B2B suits agents. The average order is about $3,000, so decisions are expensive. Comparing suppliers takes a table of at least 20 columns: price, MOQ, certificates, delivery time, payment terms, Incoterms. A typical procurement takes about 60 steps across time zones and languages. “For human beings we save time so that we can kill time. So agent is designed for save time part.” His conclusion: “B2B will go to A2A.”
- Sourcing, before and after. Before: email requirements to 20–100 suppliers, wait, and compare replies in Excel for about a week, then negotiate terms and samples, often taking weeks or months. After: the agent finds matching suppliers, runs the back-and-forth, and builds the comparison “within a day, if you’re lucky in hours”, then carries it through to contract and Trade Assurance payment.
- Org design: a startup inside the company. Accio runs as a startup team within Alibaba. The main site ships features weekly or monthly behind A/B tests, while Accio Work ships a new version every day, and much of that code the agent writes itself from execution logs. Alibaba.com was rebuilt as part of the agent’s harness so the agent can invoke its services. Accio is now merged back as “AI mode”, so the main site also updates daily.
- Commerce Agent Bench. Distilled from millions of real buyer–seller conversations, with 107 tasks now and an expected 300+ next year. It scores binary pass rate, time and steps, and price: “only the affordable AI is a useful AI for SMBs.” Frontier models, including Qwen, run inside Accio’s harness to route each task to the best-fit model.
- Vendor benchmark claim, treat with caution. On the same 107 tasks, Kuo says Accio “can have a higher pass rate with less than half of the price” than Codex and Claude Code. This is Alibaba’s own benchmark, run in its own harness, on tasks it defined. It is not a neutral comparison.
What to copy:
- Run a fast-shipping AI unit as a separate team with its own release cadence, then merge it back.
- Expose your own site or system to agents (CLI or API) as part of their harness.
- Score agents on pass rate, steps and cost together, not accuracy alone.
Leader Q&A — Tactics From the Hosts (Ep 236)
Paul Roetzer (CEO, SmarterX) answering audience questions, with Cathy McPhillips (CMO):
- For a time-starved team, run a forcing-function workshop. “We are all going to leave here in 90 minutes with one to two AI use cases… that’s going to save us at least three hours a week.”
- About 20 minutes setting the stage, 25–30 minutes listing tasks over 3 hours a week and prioritising, then 30 minutes building or sharing.
- Stretch it to two hours for a real build session, and repeat every other week or monthly.
- McPhillips adds “jam sessions” where someone screen-shares while doing the work.
- Use consultants as a short-term fix and build the skill in-house. SmarterX is creating an internal “Labs” unit that works like forward-deployed engineers. AI ops roles can come from technical marketers or project managers.
- Horizontal approvals. “If we want to connect HubSpot to ChatGPT, let’s approve it once.” Read-only, for many uses, so nobody re-requests the same connection.
- Human checkpoints in agents. Build approval gates or read-only access. Let only low-risk actions run unapproved (his example: a weekly marketing summary emailed internally).
- Vendor terms triage. Paste a tool’s terms of use into ChatGPT and ask how it handles your data, or compare the contract against your AI policy and ask what to flag for your attorneys. Legal still decides. Re-review when terms change (he cites the Fable 5 data-retention change).
- Budgeting AI.
- Priority order: people to decide, then platforms and token budgets, then infrastructure (Mac minis, GPUs), then possibly your own fine-tuned open-weight models.
- The only forecasting model he has seen is a monthly cap.
- Plan for “intelligence redundancy” rather than betting on a single provider.
- Disclosure default. “When authenticity matters you should be doing the work.” Otherwise disclose simply, e.g. “co-authored with Claude”, and always if an agent answers your email for you.
- Entry-level talent. Roetzer’s working theory is apprenticeships supported by AI-guided learning. He says nobody has solved where future managers come from.
More leader Q&A, live from MAICON (Ep 246, 2026-10-14)
- Connect the assistant to the CRM. Connecting Claude to SmarterX’s CRM “opened up thousands probably of use cases almost immediately for marketing, sales, customer success.” Unblocking it took a leader who could tell IT “we have to accept a little bit of risk”. In SmarterX’s case the COO then gave legal 48 hours to make it work.
- Build an “AGI horizons team”. A team whose job is to look 12–18 months ahead at model advances and map “the trickle down of what that means to our staffing, to our product, to the services we offer”. Then keep the organisation flexible enough to act on it.
- What AI-forward candidates should ask in interviews: Can you share your AI policy? Do you have responsible-AI principles, and how are they taught? What tools will I have, and are there limits? Is your AI connected to the CRM? Kaput adds that people using Claude on personal accounts at night will “jump ship” to employers that allow the tools.
- IP stays with the employer. “Nothing you create for a company do you own when you leave”, including agents and workflows. SmarterX addressed likeness and avatars in its contracts.
- Can vs should. An AI-written product FAQ is fine. Strategy documents you hand in must be ones you can defend. Roetzer’s anecdote: an employee could not give five bullet points from a 20-page document Claude had written.
A worked example: the 7-month Claude Project (Ep 247)
Roetzer had used the same Claude Project for seven months to build AI Score (assessments, prototypes). Before a launch he gave it the marketing page plus 80 questions from his team and asked for “a best-in-class SaaS product FAQ page”. He spent about 10 minutes editing the draft, asked for a Word doc and an HTML file, and the page was live about 30 minutes later. He estimates it saved 10 or more hours.
Agents, shadow AI and agency pricing (Ep 251, 2026-11-13)
Roetzer’s answers, opinion unless stated:
- Place each agent on an autonomy scale before governing it. Some steps are deterministic automation (rules you set, as in Zapier or Make); others let the model plan, write or segment on its own. Start low: his example is an analyst agent that reads yesterday’s marketing data each morning and reports internally, so a mistake reaches no one outside. Raise autonomy, data access and the power to act one step at a time.
- Stack low-risk use cases in regulated firms. For SOC 2 or HIPAA organisations, learn the compliance stakeholders’ limits, then work through marketing, sales, HR and finance tasks that never touch regulated data.
- Standardise for most staff, keep a lab on all platforms. At SmarterX everyone has Gemini, Claude and ChatGPT licences, about $60 per user per month for the three, but only centrally approved tools get CRM and finance data. For high-value work he builds the same prototype in all three and keeps the best; in larger companies he would give a lab or centre of excellence all three and put everyone else on one.
- Shadow AI is common (his observation, no data). He once saw the person who set a company’s AI guardrails using a personal account for work. If leaders understand the capabilities and still block them, his advice to employees is to look elsewhere; an interviewer who never asks about your AI skills is a sign the company is not doing much.
- Proactive agents are the next step (prediction: within about six months). Agents with CRM and finance access that watch the data and bring recommendations, for example spotting that a LinkedIn ad drove a jump in webinar sign-ups and drafting three alternate versions. He expects central AI teams to build these per role.
- Forward-deployed engineers are a stopgap. He doubts they will be as necessary a year or two from now; over about five years he expects companies to centralise strategic business people who can vibe-code and have them run workshops, boot camps and hackathons with each team.
- Use plain automation where it is enough. “We don’t need Astra 6 Pro… to like do something that’s literally just a if then statement.”
- For agencies and consultants selling AI-enabled content: check the client contract first (many enterprise contracts ban AI or require disclosure and approval, and copyright transfer must be clear). Expect clients to bring content in-house and to push on price once they know the work is mostly AI; he has been in rooms where marketing executives said they were dropping their agency portfolio. He cites HubSpot’s new Marketing Studio, an on-demand content creator, announced the day before recording (not checked). Training and workshops may be the steadier business.
- Personalised outreach can stay authentic. His fundraising example: an agent that each week gathers a donor’s public interviews and podcast mentions and drafts a personal note for the advancement officer to finish. The same pattern works for account-based sales.
- AI on a resume: bring a prototype or analysis built for the employer’s actual problems (for a public company, from its latest earnings call) instead of listing tools. Inside a company, make the same case with a short deck.
- Token stipends in job offers: an outlier outside AI research and software today, but SmarterX already gets ChatGPT credit requests every few days and hits HubSpot credit limits; he advises CFOs, CIOs and HR heads to set token budgets now.
- JobsGPT (SmarterX’s custom GPT for job-impact forecasting) moves to a plugin when OpenAI retires custom GPTs; see Custom GPTs Retire.
Try It
- Map your customer journey against AI (Dick’s prompt): “Here’s what my customer journey is. Help me map… AI solutions against each of those.” Pick the stage with the biggest constraint, not the easiest.
- Run Roetzer’s 90-minute session on that stage: everyone leaves with one or two use cases worth at least 3 hours a week, and at least one built before the session ends.
- Name a digital employee for marketing, Peapack-style. Start with a weekly site audit (dead links, stale content, AEO/SEO suggestions) that posts findings where the team already works.
- Measure the downstream metric. Track tickets, hours or conversions for the team affected, not usage of the tool.
- Ask IT for one horizontal approval, e.g. read-only CRM to your assistant, and a fast lane for low-risk marketing tools. Roetzer’s Ep 246 account is the case for doing this first.
- Keep one long-lived project per product. Do Roetzer’s FAQ move: point a Claude Project that already holds the product’s history at a new deliverable, add the team’s open questions, and edit the draft rather than writing from scratch.
- Rate each agent on autonomy before approving it (Ep 251): list its steps, mark which are fixed rules and which the model decides, and require a human check on any model-decided step that reaches a customer.
- Score agent vendors on cost per passed task. Copy the Commerce Agent Bench dimensions (pass/fail, steps, price) on 10–20 of your own tasks before you believe any vendor’s comparison, including Accio’s.
Open Questions
- Learning-lab cadence: Kaput’s intro to Ep 242 calls Baptist’s learning labs “weekly”; the guest says “bi-weekly AI learning labs.” The guest’s account is more likely correct.
- Garbled names. Captions mangle several: Peapack’s CTO (surname), Baptist’s CMCO (surname), HubSpot’s growth leader (“Flanigan”, most likely Kieran Flanagan) and Peapack’s AI partner (“Verapath”). Verify before quoting.
- HubSpot support metrics are unclear. The support-side statement (“industry standard resolution rates… 60% CSAT is high”) is garbled; no clean number was recorded.
- Sponsored, self-reported numbers. None of the figures are audited. The series is presented by Google Cloud, and HubSpot’s CCO is describing HubSpot’s own product.
- Accio’s benchmark is self-run. No independent replication of the Codex/Claude Code comparison, and the task set is not public.
- Guest name. “Quo” is normalised to Kuo Zhang from the caption, unverified.
- HubSpot Marketing Studio (Ep 251) is Roetzer’s description of a trailer video; features and pricing were not checked.
- Baseline for AEO growth. HubSpot’s “almost 2,000%” AEO conversion growth has no starting figure, so the absolute impact is unknown.
Related
- 2026 — How AI Is Restructuring Organizations — the cross-company synthesis these cases add to.
- Uber’s Agentic Pods — another embedded-builder pattern, comparable to HubSpot’s pods and Peapack’s champions.
- The Self-Driving Company (Replit) — org-wide agent adoption with measured results.
- How Anthropic’s Marketing Ops Team Uses Cowork — a marketing-team case from inside a lab.
- AI Marketing ROI Measurement Framework — how to measure the outcomes these guests report.
- Custom GPTs Retire — the same hosts on OpenAI retiring custom GPTs, and the “rented land” question from Ep 236.
- AI Podcasts — where the show’s feed is tracked.
- How Work Is Changing Inside Anthropic — the same hosts’ Ep 247 discussion of Anthropic’s employment report.