| | Hello there. No new HubSpot release notes landed overnight, so today's issue leans on the people running the platform day to day. Wall Street is rethinking how fast AI pays off for HubSpot, admins want tighter guardrails on Breeze and shared views, and builders are sorting out the right credentials for Marketplace apps. In today’s newsletter, we’ll get into: - Barclays cut HubSpot to Equal Weight with a $240 target, saying AI-driven growth will take longer than it expected.
- An admin says users can lean on Breeze to get around record edit rules and wants bulk edit limits by permission set.
- Service keys are fine for your own account, but community experts say Marketplace apps should use OAuth instead.
| |
|
| | 🧮 A pricing calculator module for B2B websites built on HubSpot. A developer shared a B2B pricing calculator and quote module that lets visitors pick a plan, adjust seats, add extras and see an estimate instead of contacting sales first. Owners set pricing rules, billing options and styling in the editor, and the module can pass plan, seats and estimate into matching HubSpot form fields. Tiered or volume pricing support is still unconfirmed. 📰 Can a campaign track an external blog without importing it? A SaaS team launching through HubSpot hosts its landing page and blog on Vercel and wants to attach that content to a campaign without a full copy. Smart Sync imports the external blog, but it rebuilds every post in HubSpot's CMS with default formatting. Their question: can they simply link the outside pages into the campaign and still track social and email traffic? | |
|
| | 📉 Barclays downgrades HubSpot over slower AI payoff. Barclays moved HubSpot to Equal Weight from Overweight and kept its $240 price target. Its earlier call rested on AI usage speeding up growth; the firm still likes the long-term opportunity but now expects that to take longer. It notes HubSpot said at its analyst day that customers remain cautious about the AI transition. Worth knowing if you are planning renewals or partner bets. 🛡️ Admins say Breeze can sidestep record edit rules. An admin posted an idea asking HubSpot to limit bulk edits and creations by permission set, saying their users are using Breeze to get around the rules they set on record edits. If you rely on permissions to protect pipelines or key properties, check what your AI tools can change in bulk, and back the idea if it matches your setup. 🔒 A request to stop cloned views multiplying. Another idea asks for a permission to lock down views: either block users from cloning them, or keep clones private to their creator unless an admin or manager shares them. The poster says thousands of views with mixed permissions make consistency hard, and users open cases after working from cloned views they should not be using. 🔄 Let owner rotation include unavailable reps. A user wants the rotate record to owner action to include unavailable users. Today the rotation skips them, but the poster argues availability does not matter when the Prospecting Agent is doing the outreach, or when leads are being allocated for ABM work. If you route leads for account-based plays, this idea is worth a vote. | |
|
| | 🔑 Service keys are not for Marketplace apps. A builder asked whether a service key used as a bearer token could ship in a Marketplace app. The community answer was clear: service keys are a documented way to call your own account and fine for testing, but public apps should use OAuth. A HubSpot developer blog post on service keys says the same, so plan OAuth from day one if you intend to list. 🗺️ Mapping a SaaS database to contacts and companies. A B2B SaaS team stores users, emails and workspaces in MongoDB Atlas and is asking how to map that schema into HubSpot: users to contacts, orgs to companies, plus custom properties such as an Org ID or Account ID on the company object. They want best practices like those used by sync tools such as StackSync. Share your mapping if you have solved it. 🧷 Set default columns once for every help desk view. Service admins have to update help desk view columns one view at a time, and any user can change the columns for everyone. An idea asks for admin-level default columns for global help desk views, with the same control admins already have over ticket views in record tables. A small fix that would save a lot of clicks for support teams. ✂️ Trim internal notes from a reply before the customer sees it. A team that forwards customer emails internally for answers wants to edit or remove quoted incoming content before replying. Today the internal back-and-forth can travel back to the customer in the quoted thread. If your service or sales team works the same way, this idea is a quiet but real privacy and polish fix. | |
|
| | Three remote roles posted in the last two weeks, each linked to its own posting with the source named. Each posting is linked from the source named on its line, with the date it was posted. Check the details on the posting itself. | |
|
|
|
