Chris Tveter

In the Claude sales plugin post, they note that Claude shows the proposed change before writing to the account.

• In the Deal Progression post, reps review and approve suggested CRM updates, next actions, and follow-ups from a single card.
• The aim is to reduce clicks and tab-switching without giving AI unchecked control over customer records.

Tveter writes that Claude shows the proposed change and asks the user to confirm before writing anything to a HubSpot account, calling that “the right default for putting AI in front of a CRM.” Deal Progression reads call, email, or meeting transcripts and suggests updates, which reps approve from one card.

Read original · Original 2

Teams may turn it on, skip configuration, and conclude it is half-built. The posts name the specific settings and communication tasks that determine whether adoption works.

In the Deal Progression post, Tveter notes that every deal record gets a new Catch-Up tab and the default Overview tab is renamed About.

• Conversation recording must be on, admins choose which deal properties can be updated, and sales methodology (MEDDIC, BANT, or SPICED) and Deal Plans each need separate admin activation.
• They say most teams will skip that step and assume the feature is half-built.
• The Claude plugin post also notes that the tool is free but requires a HubSpot portal, and that users should check Import Contacts before confirming matches.

Read original · Original 2

When automated flows create loops or prevent customers from reaching a person, they frustrate customers and lose sales. Their test for any company rolling out AI agents, bots, or automated customer-experience flows: can a customer still talk to a human when the system fails?

Tveter describes trying to move renters insurance to a new address, buy a new policy, and turn off auto-renew on an old one with Liberty Mutual.

• The app sent them to a generic quote page, which sent them back to the app, where they could not create a new policy.
• A call did not connect them to a sales rep.
• They call it a simple request from a loyal customer and tie the failure to lost revenue and a poor customer experience.

Tveter’s caution sits alongside their enthusiasm for AI sales tools. The message is not “avoid AI,” but keep human approval and access where the customer or the record is at stake.

Read original

The post shows a priority on the HubSpot ecosystem and on people navigating career changes, treating community support as an active professional responsibility.

Tveter writes that nearly 660 HubSpot people received the layoff email and offers three concrete forms of help: warm introductions to HubSpot customers and partners who are hiring, a thirty-minute conversation with no agenda, and an honest read on going independent.

Read original

Newcomers should start here: it turns a vague AI-in-CRM claim into eight named skills and a clear starting point.

Chris Tveter describes HubSpot's free Sales Plugin for Claude and eight pre-built skills that work with a company's own HubSpot portal.

• They explain Call Prep as a ten-minute meeting brief; Daily Brief as a prioritized morning list; Log Call as plain-language call capture that advances deal stages and creates follow-up tasks; Follow Up as a recap email drafted from deal context and call history; Pipeline Pulse as a pre-review scan for stalled deals; Contact Lookup as a full record view in chat; Import Contacts as CSV/list/email-thread mapping with deduplication; and HubSpot as a catch-all.
• They note that Claude shows proposed changes for confirmation before writing to the account, and recommend that reps start with Log Call and Follow Up.

For brands planning a campaign

For a HubSpot partner or RevOps consultancy, this is a ready-made pilot angle: practical AI-assisted CRM admin that reps will use. A content pilot could show the slash commands, approval step, and difference between logging calls after the fact and capturing them in the moment.

Start here for the operational checklist, not just the feature announcement.

Chris Tveter covers HubSpot Deal Progression entering public beta.

• The feature reads call, email, or meeting transcripts and deal context, then suggests CRM updates, surfaces a next best action, and drafts a follow-up; reps approve everything from one card.
• They flag that every deal record gets a Catch-Up tab and the default Overview tab is renamed About.
• Recording must be on, and admins choose which deal properties can be updated.
• They explain that sales methodology configuration for MEDDIC, BANT, or SPICED shows which criteria are met or missing and updates mapped properties.
• Deal Plans generate a branded buyer portal from the deal record without requiring buyer login.
• A deal with 14 or more days of silence gets a re-engage prompt.
• Methodology and Deal Plans each need separate admin activation, which they say most teams will skip and then assume the feature is half-built.

For brands planning a campaign

A partner can use this as change-management content: what to tell reps, which admin settings to turn on, and how to configure a sales methodology so the feature works. Pilot topics could include CRM rollout, adoption friction, and the difference between a demo and a configured deal process.

Start here for the argument about AI, automation, and escape hatches behind the tactical posts.

Chris Tveter describes a personal insurance task: moving renters insurance to a new address, buying a new policy, and turning off auto-renew on the old one.

• The app sent them to a generic quote page; the quote page sent them back to the app; the app would not let them create a new policy.
• They then tried to call and could not get connected to a sales rep.
• They argue that automation and AI should accelerate the path to purchase, not trap customers in loops, and that teams rolling out AI agents, bots, or automated CX flows should ask whether a customer can still talk to a human when the system fails.

For brands planning a campaign

This gives a campaign a concrete customer-experience hook: AI guardrails, human escape hatches, and revenue leakage from broken automation. For a campaign aimed at RevOps or CX audiences, a pilot could pair a practical HubSpot workflow with a discussion of where automation should stop and a human should take over.

Start here to understand the community and alumni relationship that runs through their work.

Chris Tveter writes that nearly 660 HubSpot people received the email nobody wants to get.

• They say that over the past six years they have gotten close with people at HubSpot and have never met a person there they did not get along with.
• They offer three forms of help: warm introductions to HubSpot customers and partners who are hiring, a thirty-minute conversation with no agenda, and an honest read on going independent.
• They ask people to send a message.

For brands planning a campaign

For a HubSpot partner or consultancy, this is evidence of community trust and an alumni network.

• It could support employer-brand or community-support content.
• This is a personal offer of help, not a paid partnership.

The post covers call prep, daily briefs, call logging, follow-up emails, pipeline review, contact lookup, contact imports, and general CRM questions. They highlight the confirmation step before Claude writes to HubSpot and recommend that sales reps start with Log Call and Follow Up.

A numbered list of each skill, with a plain-language use case and a specific recommendation for reps.

Tveter notes that the import skill needs careful checking before confirming matches and that the plugin is free but requires a HubSpot portal.

For brands planning a campaign

A HubSpot partner or RevOps consultancy can use this as a template for AI enablement content: concrete tool walkthroughs showing time savings for reps and the guardrails that matter. A pilot could ask for a similar breakdown of one AI sales tool, with a short demo or annotated sequence.

Examples: Source 1

The post describes how HubSpot reads call, email, and meeting transcripts to suggest CRM updates, next actions, and follow-up drafts for rep approval.

• They flag setup details: a new Catch-Up tab, the Overview tab rename, the need for conversation recording, and admin activation for methodology and Deal Plans.
• They also note a re-engage prompt after 14+ days of silence.

Frames the feature around what a team must configure, then adds a personal take on the gap between conversations.

Tveter warns that most teams will skip the separate activation steps and assume the feature is half-built—a practical adoption risk.

For brands planning a campaign

For a RevOps audience, this is a model for product-update content that pairs feature explanations with change management. A campaign could sponsor a “what breaks when you turn this on” post or a short checklist for admins enabling AI deal tools.

Examples: Source 1

The post describes a loop between an app and a quote page, an unsuccessful attempt to reach a sales rep, and a simple test for any company rolling out AI agents: can a customer still talk to a human when the system fails? They tie the failure to lost revenue and customer experience.

A personal narrative names a specific company, then uses a direct question to turn the story into a checklist item for readers.

The post is a single customer experience, not a systematic study of automation failures.

For brands planning a campaign

A brand in insurance, CX, or revenue operations can evaluate Chris Tveter for content that turns a frustrating customer journey into a practical lesson. A pilot could ask for a short post or video script walking through one broken automation and the fix, aimed at teams deploying AI agents.

Examples: Source 1

The post speaks positively about people who come out of HubSpot and their product and customer knowledge.

A direct, personal offer of specific help instead of general commentary.

For brands planning a campaign

For employer-brand, community, or talent-focused campaigns, this shows Chris Tveter can speak credibly to the HubSpot ecosystem and people navigating career changes. A campaign could offer a practical resource for HubSpot alumni or a community Q&A rather than a product pitch.

Examples: Source 1

They walk through new releases—the Claude sales plugin and Deal Progression in public beta—explain how each feature fits into a rep's day, and say they use the Claude plugin daily.

• In a post about HubSpot layoffs, they say they have gotten close with people at HubSpot over six years and offer warm introductions to HubSpot customers and partners who are hiring.
• The posts show deep product familiarity and personal ties.

View example

They single out the confirm-before-write behavior as the right default for AI in front of a CRM and say they use the plugin daily.

View example

They are a Liberty Mutual customer.

Original disclosure

I've had my renters, homeowners, life, and three auto policies with them for years.

View example

The posts say nothing about what connects Tveter to the company, and a hashtag on its own does not establish a partnership or payment.

View example

The focus is practical HubSpot and RevOps implementation, not abstract AI commentary.

Orlando G. tends to build and explain repeatable sales or support processes inside HubSpot, while Chris Tveter more often reviews new HubSpot AI features and the setup, admin activation, and change-management steps that determine whether teams adopt them.

Read original · Original 2

They argue that forecast calls and coaching conversations often run separately, even though a deal risk and a rep's skill gap are frequently the same underlying fact. The posts stay close to how sales managers work and to the systems and products that could connect those views.

Vandan Jain's angle is sales-manager decision-making across forecasting and coaching, while Chris Tveter's posts center on HubSpot AI sales tools, CRM change management, and customer-facing automation risk.

Read original · Original 2

The content is concrete, tool-aware, and aimed at revenue teams looking to make AI useful inside existing CRM and sales processes.

Omprakash Karuppanan focuses on account-based marketing execution and diagnosing stalled enterprise deals, while Chris Tveter focuses on HubSpot AI feature adoption, sales productivity workflows, and keeping a human escape hatch in automated customer experiences.

Read original · Original 2

In one post, they use HubSpot Breeze to draft a discovery-call playbook framework, choose among the generated options, fix the one setting HubSpot gets wrong — the answer type — and attach the playbook to the contact record so every question and answer lands on the timeline for whoever works the deal next.

• In a second post, they route a shared support inbox into a HubSpot ticket queue, let AI handle the first pass from the knowledge base, hand off to a human with an assigned owner, and require the rep to read the chat log before replying.
• For a partner whose client needs a working configuration, that is closer to the deliverable than a feature explainer.

The range is narrower than the campaign's needs imply.

• Both pieces walk through HubSpot mechanics — playbook setup and inbox triage — demonstrating how to configure a system, not how to drive adoption, brief an admin team, or take a position on where automation should stop.
• A partner seeking an argument-led piece or a market point of view gets less from this work.
• The written text recaps setups presented in video, rather than offering full tutorials.
• Ask for rates, sponsor terms, and audience composition before booking.

Examples: Source 1 · Source 2

One post separates the two recurring meetings most sales managers run: the weekly forecast call, which lives in the CRM and a deal-intelligence dashboard, and the coaching conversation, which lives in the manager's memory and maybe a call scorecard.

• Jain argues they should be one view, bringing together a forecast risk and the coaching action it implies.
• The other post uses Salesforce's State of Sales 2026 report, which says 51% of AI-using sales leaders say disconnected systems hold AI back, then walks through a single deal: the buyer questioned price, the rep tends to defend price before asking why, a customer example already proves the value, and that knowledge is split across the call recorder, the shared drive, and the manager.
• The proposal is one memory that feeds the pre-call brief plus a six-minute practice drill on handling price.
• A partner selling mid-funnel diagnosis to sales leaders can use that framing directly.

Both posts promote PitchSense AI and close with a DM invitation, offering a problem diagnosis and product direction more than tested steps.

• The posts provide no independent evidence that the product does what they describe, or configuration details a client team could run itself.
• They include fewer named HubSpot features and admin caveats than the other alternatives, so a partner who needs a rep-ready checklist gets less from this option.
• Ask for evidence of the product's capabilities and a runnable configuration before using the material with clients.

Examples: Source 1 · Source 2

One post lists five of ten Claude skills built for ABM: deal reporting that pulls account intelligence, meeting transcripts, website engagement, and closed-lost and closed-won CRM data; audience targeting that ties ad spend to CRM data so accounts outside the ideal customer profile can be suppressed; account research that combines the closed-lost list and the ICP list against external signals; field marketing attribution that credits pipeline at the account level, gives opportunity creation 90 days, puts sales time in the cost column, and picks 25 people from an attendee list for pre-booked meetings; and stall diagnosis that ranks open deals by single-threaded, champion lost, no compelling event, buying-stage mismatch, and sequence fatigue.

• The second post argues that top-of-funnel outbound got worse because everyone bought the same tool, that the edge lies where deals quietly stall, and that enterprise buying committees of six to ten stakeholders often include half who never speak to a rep.
• It illustrates the point with an audit of 31 stalled accounts, 17 of which had a trigger event in the last 60 days but no one acted on it.
• That is detailed mid-funnel method a partner could package for enterprise clients.

The method targets ABM programmes running on HubSpot or Salesforce, not HubSpot feature rollouts, admin activation steps, or enablement for generalist sales teams.

• A partner whose client is switching on a new CRM feature gets less from it.
• Both posts end with a direct service pitch; one names the creator's own ABM execution programmes and asks readers to message.
• A partner seeking a neutral educator is buying a commercial angle.
• The AI examples are described rather than shown, and the referenced podcast episode is not included in the posts.
• Ask for rates and terms, and for a demonstration of the AI examples and the referenced episode before booking.

Examples: Source 1 · Source 2