The HubSpot Help Line - Feb 25, 2026

[00:00] **Introduction** Chris Carolan: Big finish and jazz hands on this Wednesday morning. Welcome to the HubSpot helpline. George, that was for you. Thought I was going to trip in my chair over uh a piece of electrical tape, but I made it here. So uh, I'm joined by the extraordinary panel of experts. Calling them a panel feels wrong. So I apologize for that. We have Kyle Jepson. Uh, we have George B. Thomas. Don't ask him what the B stands for. You probably can't handle it. We have Chris Carolan. Uh, I'm going to just skip the joke I usually make because it's not fair anymore. And Casey Greyhound of the Helpline Hawkins. How are we today, ladies and gentlemen? [01:03] Casey Hawkins: Um, we're doing well. this you calling me Greyhound of the Helpline just reminded me that a client this week saw Frank, one of my Greyhounds walking in the back of my video and said, what is that? Is that a llama? [01:31] Chris Carolan: Oh, wow. [01:35] Casey Hawkins: And to which I had to say, no, that's my dog. [01:41] Chris Carolan: Don't Greyhounds have really, really short hair? Llamas are long and woolly. [01:46] George B. Thomas: Right, right. [01:48] Kyle Jepson: Yeah. I have a lot of questions and this is hard to transition from, so I'm going to try to do it. Speaking of a lot of questions, I'm sure you all have some. They're in the audience. Thank you for tuning in. We uh normally do an inbound 26 update, some other news and uh of course everyone's favorite Casey's couple of segments to include feature of the week. But uh Chris, as the producer, do we want to launch into the voicemail that we have since it is top of mind? [02:34] Chris Carolan: Yes, we do. Uh. [02:36] Kyle Jepson: Excellent. That is the purpose of the show. So thank you very much to uh whoever called in and left one. It is a doozy though. I can we heard it backstage. George has been pacing. He's been prompting Claude and GPT and Jimin and all of the things. He's been doing some research. I think I saw an encyclopedia opened at one point, but I think we're ready to tackle the voicemail from uh one of our listeners. [03:17] Chris Carolan: Let's do it. Uh, it'll be a two parter. So we'll we'll pause after the first part and uh see what we can do to help out. [03:31] **Problem Voicemail from Adam** Speaker: Hello, my name is Adam. I'm a HubSpot admin for Ragaku and I've got a couple different problems uh that I'm looking for help with. Uh the first one is um I've got the Salesforce integration running. Um, and I've got most of the uh record types to sync. Um, and objects to sync. Uh, however, I'm having problems with my uh deal records and syncing them across. Um, the error I get is an other error of an unknown type. Um, so error type is unknown and it's other. Uh and the description is cannot identify the Salesforce record type with ID uh blah, blah, blah. I've talked to my Salesforce admin, um, we've identified what that record ID is and identified that I have access to it, uh as the helpline integration user. Um, but we can't figure out why I can't get these 2,000 or so deals to sync over. [05:10] **Google Search Fix** Max Cohen: Yeah, so um, I'll just kind of lead the way. this this is not the only human has who has dealt with this because with a quick uh search of the Googles, which by the way, one of the things that I always like to say is you don't need to know everything, you just need to know how to find everything when you need it. Um, a quick search of the Googles, the actual AI overview on this one is really pretty useful. Sometimes I don't really dig what Google gives us for an AI overview, but it does match up to also, I'll put a maybe a link in uh the show after we're done. Um or you can search for this knowledge article. But anyway, what it says is a record ID error when syncing deals from Salesforce to HubSpot typically indicates an issue with the data integrity or association where the HubSpot integration cannot find a matching accessible or properly formatted record ID in Salesforce. So they give you some troubleshooting steps of like check sync errors in HubSpot, which you kind of talked about in the message where it's navigate to settings, integrations, connected apps in your HubSpot account, click Salesforce then go to the sync health tab, view the specific error details, which he talked about. Um but then verify record ID correctness. The error might mean the record ID in HubSpot or the value HubSpot is trying to push to a Salesforce uh reference field is invalid or formatted incorrectly. Uh it talks about you can export existing records from Salesforce to get the correct record IDs and update the corresponding HubSpot records properly or property value if necessary. There's also a thing of making sure that permissions are adequate. So he kind of leaned into that, but didn't really lean into that. So the Salesforce integration user must have the correct read and edit permissions on the deals object, uh opportunities in Salesforce and all related objects like accounts and users in Salesforce. So make sure that user permissions across the board is what you need. And then it goes into resolve association issues. There's more address data discrepancies, things like that. But those are a couple little places that you could start with. Uh and then there is a community um HubSpot community thing on this sync error missing Salesforce ID. So if it's actually missing versus like not formatted properly, you can head over there and there's a remotish agency has a post in here about contacts not getting pushed to over to HubSpot from Salesforce and they go into some detail about it being uh this issue occurred because someone mapped the and they're talking about content or content, contact ID in this case, but think about that for your record IDs. Somebody had mapped the ID to a Salesforce property. Uh the integration allows you to make this mapping, but anything mapped to the main ID will cause the integration error. So just know uh to maybe look at that level or this um this post. Um and again, I'll you can Google it, HubSpot Community sync error missed Salesforce ID or I'll try to put it also in the LinkedIn uh post once the show's over. So hopefully that's helpful. Uh Casey, any other additional thoughts past that potentially? [10:02] **Opportunity Object Tips** Casey Hawkins: Chris, can you put my screen up, please? Thank you. Um, so with the deal/opportunity objects specifically, um, when we look at record type, um that maps in HubSpot to the pipeline dropdown. Um, so worth going into your integration settings here, going over to deals and um, one, checking this mapping itself, making sure it's okay, checking the rules itself. Um, also if it's like a do not sync or something like that, that might cause a red flag. Um, and then also checking the pipelines themselves to see if you see that pipeline active in HubSpot. Um, if it's if you're not seeing it is a pipeline listed in HubSpot, you might want to make sure that on the Salesforce side that just, you know, these are those like restart kind of like restart your device kind of checks, but um making sure that the record type is active in Salesforce. I know that's something I run into a lot in Salesforce is I can oftentimes things you can see in Salesforce but they're not active. Um, so making sure like all of those boxes are checked. Um and it will also need a sales process assigned to it and um opportunity stages. Um, so those are just some things to check um while you're reviewing the um the record type as those can kind of cause the sync um to fail. [12:26] Chris Carolan: Very well done. [12:28] Kyle Jepson: You guys are so tired. [12:31] **Context is Important** Kyle Jepson: You you can listen. Casey, you had mentioned uh that you didn't interpret that well from audio audio being the uh mechanism of input that didn't work very well. So I was going to recommend either putting that in the comments, Chris or maybe George had the like the community blog or the link to where that was addressed. But I had a question and a bit of context. As uh as somebody that is back now, shout out to Sarah Madillo for saying uh welcome back. Yes, I was at an offsite. I got to participate in my first hackathon. Uh spoiler, I am not a developer. But one of the cool things that happened and something that I think we run into with questions and and stuff like this voicemail are that context is important. And one of the things that during me showing something I was experiencing as a negative was like this kind of insight from the dev team that sometimes recreating the problem is like half or more of the problem. Like I was not able to show them exactly what the problem was I was experiencing. So being enabled to unable to recreate the problem in and of itself was a problem. Is that something that is pretty common especially with the different routes you can take to address problems in HubSpot? [13:57] Casey Hawkins: How many times can you say problem? [13:59] Kyle Jepson: Problem. [14:01] Kyle Jepson: Problem problem problem. Yeah, a lot. [14:02] Casey Hawkins: Yeah, um that definitely is. I mean, so I had to bring up a real portal that I work in for that specific one because I don't have a demo portal with a demo Salesforce. Um, and even there, I'm like mine is syncing. So like it's a it can be hard to like it could be a bunch of things and without seeing the problem the problem problem that you're experiencing then we're just kind of backtracking into possibility land. [14:47] Kyle Jepson: Right, which is not somewhere we want to be unless we're accompanied by George B. Thomas, who is well known uh and useful in possibility land. Who's also muted. So there's a possibility that you may not even hear what he has to say if you're in possibility land. [15:07] George B. Thomas: Wow, thanks for calling me out. But I did say, wow, maybe. I don't know. Like I like possibilities. [15:16] Kyle Jepson: Sorry, off topic. Hi Max. [15:18] Kyle Jepson: I was going to say hi Max. [15:19] Max Cohen: The man, the myth, the legend. [15:25] Kyle Jepson: Yeah, Max, I'm back from the uh from the offsite now, so we can play Arc Raiders at some point. Anyway, moving on to uh what everybody's favorite part of the show is, which is Casey's uh segment. Although hold hold on. This isn't. I'm actually getting some breaking news and it's about an HubSpot has acquired Starter Story. Apparently this seems to be some breaking news, so I don't know if congratulations are in order. George just did the clap with the oos and ahs. But Chris, can we pull this up? I know that transitioning to kind of video and uh the, I think X funnel may have been the last company they acquired for AEO, but this seems to be pressing news considering this is HubSpot helpline. What do we think of this acquisition? Were we aware? And Casey, we promise we'll get back to you right after this. [16:24] **HubSpot Acquires Starter Story** Casey Hawkins: Um, how many acquisitions are we from when Chris said that? [16:29] Chris Carolan: The official number is a lot. That's the official number. Chris is like, I think this is the last one. Yeah, I think this is the last one. I got no, bro. [16:39] Kyle Jepson: So hold hold on. I I I can weigh in on this a little bit. So I I I did not know about this before I joined the the call this morning. Rob is the one who was watching the news reels and and saw this come in. Uh but it's important to note that this this acquisition is HubSpot Media. Uh which I don't, I don't mean to be pedantic and split but split hairs. What is this saying? Anyway. [17:07] George B. Thomas: Yeah, split hairs. Yeah. [17:09] Kyle Jepson: Yeah. So uh HubSpot has like if you want to talk about product acquisitions, I feel like we are kind of slower and choosier there though we have been much more active in acquiring product companies in the last five years than we were in the five years before that. But our media team, like we acquired the Hustle. Uh we now apparently have acquired Starter Story. HubSpot media brand is acquiring a lot of really kind of heavy hitters in the entrepreneurial, business, cool trendy uh content uh machine area. Um, and so this is this is another one to add to our bouquet, I guess. Uh which is really interesting. [17:57] George B. Thomas: Yeah, you know how hard it is for me to not watch the video on this page right now. Like I just want Anyway, we we don't have time for that. I'll do it after the show. [18:06] Kyle Jepson: Yeah, I'm got it's it's not splitting straws or hairs, Kyle. I think it's the differentiation is important. Words are important. So that has been. I I did a video maybe a year or two ago that compared the number of acquisitions like M&A activity over Salesforce's you know, whatever you want to call that span of them being in existence to HubSpot's. And I think the number at that time was 63 to 11. And I I mean I appreciate you pointing out the fact that this is more HubSpot media centric than it is like product. Like, you know, combining, you know, you you HubSpot whether it was them or other people in the community, you know, the the cobbled versus crafted. I know Yamini said that in Frankenstein. I think that is important to note. So, um, you don't have to go panicking yet about adding in another thing to like the product side. Um, but this this is just from the name Starter Story and kind of HubSpot's traditional focus on SMB and like telling the story. This is another idea that someone stole from Rob. Um, my my seven-year-old at one point coined the term Hopespot, which was more of like telling the stories behind people that had been successful using this product. So shout out to these guys who stole that. Maybe they saw my TikTok video and ran with it. Um, yeah, I think this is important for people to be aware of. [19:29] George B. Thomas: Yeah, this is pretty cool. I want to I want to dig into this. By the way, I would be remiss since we've talked about splitting straws and splitting hairs. Could it be splitting wood? That's another thing that you could split maybe. I don't know. Uh. [19:47] Chris Carolan: Y'all are making my job I mean I I think I have probably the easiest job and then the whole my Greyhound was a llama comment and then splitting wood versus split like what are we doing? Is this pick on Rob day now? [20:03] Kyle Jepson: Welcome back. [20:05] All: Welcome back. [20:07] Max Cohen: Are we robbing you? [20:11] Chris Carolan: Wow. Let's just wrap. Let's just wrap right there. Clock out for the day. Wow. [20:19] Chris Carolan: Casey, I just want to personally apologize to you. We will never again announce uh HubSpot news. We won't split straws, llamas, Greyhounds, hairs or wood. We I won't divert from the script ever again. So can we just please kick it over to you for your whatever the heck you want to talk about. [20:40] Casey Hawkins: Almost, almost. I do want to like [20:43] Kyle Jepson: Part two. [20:44] Casey Hawkins: Like uh I made a post yesterday about like LinkedIn suggested uh a HubSpot position to me um that was actually called Senior Product Marketer value storytelling. [21:07] Kyle Jepson: Oh. [21:08] Casey Hawkins: And this it makes sense and I these acquisitions if we could just get other businesses like this takes me back to 2020 when I actually was working with Ragaku where where Adam was calling from. And you can get leaders on board with this concept of needing to do video, needing to tell the story differently, but it's things that the organization has never ever done before. So at which point does an acquisition like that of just going to buy a company that the all right now you have this media operations that could be, you know, a part of the business versus like, you know, team member by team member and like when does that start to be a part of that conversation uh alongside like acquisitions for the product or like that add customers with the acquisi all the usual reasons you make acquisitions, right? And it's an interesting dynamic to see um, you know, a lot of companies could do things like this, but it's it's hard to like put the pieces together. Um, but very cool to see this as an example of what, you know, a lot of companies could be could be doing. [22:54] George B. Thomas: Yeah, very cool. So someday what I hear you saying Chris is there'll be a article that we're looking at on the show and it'll be like HubSpot acquires George B. Thomas. Is that what you're saying? [23:05] Kyle Jepson: Oh, no, no. Okay. [23:07] George B. Thomas: Actually. Not actually George B. Thomas. Maybe something George B. Thomas has done. [23:11] Kyle Jepson: Maybe. Yeah. [23:14] Kyle Jepson: In in my head and I I don't live anywhere near the rest of your head spaces which is fair, but it's more like the uh the commercial um when the kids are going across the stage for their graduation and one of the kids is announced as Kowalski Autobody LLC and the parents are like, what was that? It's like I sold the rights to my children's names. Um, so maybe George B. Thomas becomes George B. HubSpot media Thomas maybe something that happens. [23:42] George B. Thomas: Wow. Wow. Dang. [23:45] Kyle Jepson: Um, anyway, we have we have prevented the inevitable value add for far too long at this point. I am with no further ado, I'm going to kick it over to my trusted uh incredibly smart colleague Casey Hawkins for her segment. [24:03] Casey Hawkins: Um, all right. So starting off with the update of the week. Um, Chris, don't add my screen yet. Um, so this over the last seven days we covered 35 updates. We had five shows, which after Chris moved is actually a good thing because we got a little a little topsy turvy for a little while. Um, and as always, this is my opinion, my opinion alone and I come from marketing and ops background. So my picks tend to lean that way. But this week some things that stood out. First portal hygiene. HubSpot's making it easier to keep your portal clean without you having to carve out time for it. We got cleanup automation for unused reports and 90-day auto disable for unused URL redirects. These tend not to be headline makers, but they save you from portal bloat over time. Also forms and spam prevention, recapture V3 hit private beta for forms, which is the invisible version. No checkbox fruit is for your visitors. Plus daily spam submission digest gives you a heads up when spam's coming through instead of finding out three weeks later. Email and marketing, throttling marketing emails is now in beta. You can control how fast your emails go out instead of blasting everything at once. I know George is really excited about that one. Um, this is big for deliverability and big for teams that need staff ready to handle responses as they come in. Um, theme number four is the CRM quality of life, which has been an ongoing theme lately. Inline association tables, we talked about just this morning, as well as customizable Gmail sales toolbox last week and revert to prior revisions on workflows. Paired with our the workflow data restore from the week prior, HubSpot is building real safety nets for ops teams. But the number one update of the week, Chris, you can go ahead and add it. [26:31] Kyle Jepson: I'm super curious. [26:33] Casey Hawkins: Permission sets and seats are now decoupled. So up until now, permission sets were tied to paid seats. Um, if you wanted to give someone specific permissions, that cost you a seat. So admins had been making tradeoffs. Burn a seat for the right access or uh shoehorn users into permission sets that don't quite fit. This update separates the two. You can build permission structures your org actually needs. Um, George said on the Wednesday show that this deserved a major tag and I agree. Um, it tends not to be one of the flashiest updates, but it is fund foundational and affects every portal with more than a handful of users. It's in private beta, but um right now not re accepting new beta. So keep an eye on it. [27:51] George B. Thomas: Nice. [27:53] Kyle Jepson: How, I'll I'll be the How does this affect pricing? [27:57] George B. Thomas: Mm. [27:59] Casey Hawkins: No. [28:00] Kyle Jepson: And that is when I trip. [28:03] George B. Thomas: Wrong, wrong question. Uh, it it doesn't really affect pricing per se, Rob, but what it does is it allows the HubSpot admin who have been racking their brain on getting the humans in their organization what they need with the seat that they're in and it was near to almost impossible. [28:25] Kyle Jepson: Now that's not true. Not that not that I think it should. Just to clarify. I don't want to be I don't want to get direct all hate mail or complaints to Chris at you know all of that but actual. [28:39] George B. Thomas: Actually Rob, once you once you enable the beta HubSpot's free for life. Um so now I'm just kidding. I'm just kidding. That is not true. That is not true. [28:49] Chris Carolan: Well, apparently it's it's flashy enough uh to have a very special guest to join us so he can talk to us about permission sets and seats. Uh so. [29:06] Max Cohen: I hope I know who this is. [29:08] George B. Thomas: I thought he was coming to talk about Arc Raiders. [29:11] Chris Carolan: Let's go. Max, what do you think about this uh update of the week here? Permissions and seats. [29:18] Max Cohen: Decoupled. One word. It's cool. I don't even know what it is. What are we talking about? I. [29:28] George B. Thomas: Max, you look so cozy. [29:30] Max Cohen: Yeah. I looked so cozy. It wasn't so cozy the other day when I lost power for the entire day during the Monday morning briefing. That was tight. [29:37] Casey Hawkins: Oopsie. Um, Max, were you already wearing orange? Well, I I was, but I figured I needed for me to come up and just hang out. We would have a bunch of boring stuff right now and uh I'm gonna take my empty iced coffee fill it with a Diet Pepsi and just, you know, continue the day with some friends. [30:02] George B. Thomas: There you go. Love it. [30:04] Max Cohen: I don't want to derail anything. No. [30:05] George B. Thomas: I do want to decouple seats from. [30:08] Kyle Jepson: Yeah. [30:09] Casey Hawkins: Nailed it. [30:11] Max Cohen: Wait, so what does this actually mean? I missed that part because I was finding a Diet Pepsi. [30:14] George B. Thomas: Yeah. Well, the only thing I said, go ahead, Casey. Never mind. You can. I was just going to read the update as I do. Uh previously permission sets and seats were tightly linked. This often less led to errors when assigning users to permission sets, users being blocked or removed unexpectedly after seat changes and confusing situations where users in the same permission set had different access with no clear explanation. This update removes those pain points by giving admins more flexibility to grant access per their business needs, preventing the disruptive removals of users from permission sets and making it clear why a user does or does not have certain permissions. The result in is fewer surprises, less cleanup work and more predictable permission experience. [31:15] Max Cohen: So, how were these tied together before? Because admittedly, I haven't done a whole bunch of like actual admining and permissioning because I've never had to have that be my main job. What like how were they coupled together? Because I guess I didn't even realize that they were unless I'm just forgetting something. [31:34] Casey Hawkins: Um, correct me, George, if I get this wrong. But like I think that the way it did work was or if you're not in this beta, it still works, I guess. Um, is if you have like a sales seat that unlocks certain permissions, but if you get your sales seat removed, you might not even realize that like some of those permissions are not even necessarily like required for sales hub, but suddenly like [32:11] Max Cohen: Yeah. [32:12] Casey Hawkins: That makes sense. [32:12] George B. Thomas: Yep, yep. [32:13] Max Cohen: That's cool. That's cool. It sounds like they are trying to make up for some stuff that they thought was kind of clever back when they did it originally and then realized it very much wasn't. [32:26] George B. Thomas: It it very much felt like an oopsie moment without a doubt. [32:33] Kyle Jepson: Yeah, from LinkedIn user. Thank you LinkedIn user. Someone needed a seat they couldn't have the same permission as someone who didn't need a seat, so you had to make two different permission sets. My question, which got me almost booed out and you just replacing me as host was, does this affect pricing? George, quickly recommended. [32:52] George B. Thomas: I didn't boo. I didn't boo, no. I just said wrong. [32:56] Max Cohen: I I mean seats still cost the same amount. I'm looking at the product update now and it says uh HubSpot automatically grants the maximum access allowed based on a user's permission set and their seat. So to the point of like you have to have a seat to be able to enroll. You have to have a sales seat to enroll a contact in a sequence, for example. If a permission set grants sequence access and you give it to someone who doesn't have a sales seat, HubSpot is now smart enough to figure that out and uh work it out. [33:40] Kyle Jepson: Yeah, it sounds um maybe it's the inverse is true, but it sounds more like the ability to include the ability to include whatever permission sets is kind of the default and then you're able to then throttle or assign rather than having to play like pin the tail on the on the donkey with different sets at different times. Because I know a big problem was um like temporal like permissions or revoking of them based on some activity or some something that you needed to do for like a shorter amount of time, which was very difficult to keep up with both for the admin and the person who was granted the permission in the first place. [34:23] Max Cohen: Well and I think, I mean I'd love to hear other people's thoughts on this, but I think a good way to think about permissions is what you're not granting people, right? So like you there might be a lot of things you don't want to grant to most of your users, right? Uh maybe maybe turning on workflows, maybe like changing other users permissions. Whatever those things are. And so if the very restricted number of things you want to give people access to includes, you know, seated sales hub features and seated service hub features, you can now just use that restricted permission set for all your sales and service reps. Uh but then based on their seat they'll have access to sales tools, they'll have access to service tools and that'll you can have just one one permission set for like customer facing employees uh that then based on their seats is dynamic. [35:16] Kyle Jepson: I'm glad you piggy backed on that and and kind of halfway agreed with me. To me it would make more sense because George and Chris both say words are important, which I agree with. It sounds more like a clearance. Like you you would be given a certain level of clearance to be able to do things and then as you as more permissions are unlocked, you have a higher quote unquote clearance level um not to make that analogy too directly but that's what it sounds like more just the word permissions in this context. Your thoughts, Mr. Cohen. [35:53] Max Cohen: Yes. [35:54] Kyle Jepson: Great. I agree. [35:58] Chris Carolan: I work here is done. [36:00] Kyle Jepson: Um, Chris, over to you. [36:02] Chris Carolan: I did recently talk to that team, but I'm also in the situation like Max where I haven't spent a lot of time with lots of teams and lots of people to have to wade through all this. But it's been clear for a while that and I think this is where AI helps the most in the background. like the complexity required to be able to see all these things and then try to guess or advise or even require certain access in certain places is now here so they can start to um allow for users to get very complex with their permissioning without making us go through every single like, you know, granular spec of permissions. And previously we just or what I um, and the reason I think like at some point you just go to super admin because you're tired of trying to figure it out, right? A lot of assumptions were made where like, okay, you're going to click the sales rep button. That means you as a sales rep in this random organization must need access to sequences and this stuff and this stuff. And you definitely won't need access to any of the marketing tools or any of the service to which just a lot of that is not true in a lot of organizations wearing multiple hats and multiple places. So uh the team is working very hard on trying to create this a manageable experience while also serving like the complexity of all the humans involved. So. [38:23] Kyle Jepson: Yeah, um I we just got a comment Chris, if you want to put this up there uh speaking of context being important. Um not that one. Seats and permission sets got a little messed up. Thank you also Ben Francis, but seats and permission sets got a little messed up when HubSpot changed to the new pricing model with core and view only. So remembering that as context of like, why would this make sense now? What happened what existed before? I think this is important thing. Shout out to Robin Noll for calling that out as [38:56] Chris Carolan: But this and this is also like a perfect example, right? Like we just like the update of quotes being able to be associated with custom objects, right? And tickets specifically, right? Like that is something that that team has never had to have access to and now all of a sudden that capability requires like you to open up the teams and hopefully, I don't know Kyle, maybe you could speak to this like this like can we avoid the world where we don't need like one person doesn't need all of the different seat labels and there's some kind of like seat structure where it's not like, okay, you have to have a commerce hub seat and a sales hub seat and a service hub seat and this kind of seat. Like sometimes you just need to do all the all the things, right? [39:56] Max Cohen: Yeah. So there's a there's a lot of friction right now with the seats model and especially like uh commerce hub coming out with seats this last inbound has caused a lot of consternation, let's say. [40:15] George B. Thomas: Ooh, good scrabble word. [40:17] Max Cohen: Yeah. Um I HubSpot is very much aware of this and there's some like big open field thinking about like what what would actually make sense for a HubSpot pricing model. Uh I'm curious, let me let me just push it back to you all. If anyone wants to take take the bait on this, uh if you rebuilt HubSpot's pricing from scratch, you were not beholden to anything we had done previously, what would it look like? [40:51] Chris Carolan: Usage. [40:52] Max Cohen: I I think there's wide agreement on the problems. There is very little agreement on the solutions. [40:57] George B. Thomas: Hang on, we need we See Rob, this is why we need a uh we need like uh graphics and stuff because we need to activate feedback dialogue. [41:06] Kyle Jepson: I I literally just wrote that down. So Yeah. This is a great I can't think of a better segue into uh everyone's second favorite segment. Actually Max is here and I've seen the amount of all caps he uses whenever Kyle makes posts about product feedback. [41:24] George B. Thomas: What. [41:24] Kyle Jepson: It's that time again for Kyle Jepson's taking all product feedback back back. We need an echo effect on that one. We do, we do. So the prompt today Kyle. [41:40] Chris Carolan: Oh, we got a second soundboard now. [41:42] Casey Hawkins: Yeah, this is going to be a second fight. Yeah. Yeah. [41:50] Max Cohen: Max comes prepared. The the rest of all my all my buttons are broken. I'm like I somehow got my Go XLR profile like nuked itself yesterday and all my sound effects are gone except for. [42:03] Speaker: This one. [42:05] All right, I'll go first. Usage based everything. Make it figure out how to make it profitable for you HubSpot. But the way that AI is coming into play and the credits is like a step towards that. Uh, I don't know how we don't end up there, but it's also counter to the way like most SAS business models. So uh good luck. [42:29] Max Cohen: So it'd be like 100% credits. A no like monthly subscription. It would just be like you use it, you pay for it. hubs disappear. and just like you use that this thing cost that much and this thing. Interesting. [42:51] Kyle Jep