Imagine paying for a CRM.
Then paying again to connect it to your favorite AI tool.
Yeah, we don't love that math either.
At HubSpot, everyday AI access is included. Bring your own agents. Use your existing APIs. And you’ll be able to scale with credits when you need more.
Learn more at https://t.co/E1R9QNKCpK
All roads might lead to paid ads.
But the best B2B SaaS CMOs know a few shortcuts 👇
1. Make founders the media
2. Crack AI search visibility
3. Own niche ICP newsletters
4. Publish pricing teardowns
5. Own the comparison keywords
6. Hijack industry conversations
7. Build organic distribution loops
8. Steal competitor search traffic
9. Turn free tools into lead magnets
10. Answer Reddit's buying questions
11. Turn customer ROI into case studies
12. Publish proprietary benchmark reports
13. Get into third-party software roundups
Build these roads first.
Then use paid ads to accelerate what's already working.
Lots of brands think content is the answer. But if your content isn’t worth sharing, it’s just an ad.
Great content is the Michelin guide. Bad content is just talking about your product.
Unless you can create great content, it’s probably not worth investing in.
i don't have any thoughts on the new models released by OpenAI other than I will be using Opus 5.5 for about 85% of things and Fable for 15% of things until someone else catches up.
@clairevo I call those "slop packets" and they are an indispensable tool in the toolbelt!
In the appropriate circumstance you absolutely should be sending slop packets rather than hand crafting
Had one engineering leader send a document generated by AI to another engineering leader. I reviewed it. It made perfect sense and made it clear how their approach to classifying events would work. They had a meeting about it to walk through it to make sure they were aligned.
Later, the other engineering leader tore into him because it was generated by AI, despite the fact the document communicated what it needed to.
I’m anti-useless documents. But it’s silly to get upset that something is AI generated if the person generating it can explain it and document does what it’s supposed to do.
.@Tobi’s emphatic case for reinstating Jensen at Nvidia:
“There is no replacing a founder like Jensen. There never has been, and there can never be, a true succession for a founder like him. Nvidia ends today, and is replaced with a thing cosplaying Nvidia. It will be run by custodians trying and failing to preserve the flame he ignited.”
A new faux pas I’m seeing: dismissing a teammate’s well-structured, probably decent agentic output as “AI slop” because you don’t want to read it.
If a teammate (or agent) has skillfully prompted and carefully edited something to solve a problem or communicate with the business, it isn’t automatic slop just because AI generated it. There’s often good stuff in there... if it’s long or you're multi-tasking, feed it to your agent.
Don’t overuse the term "AI slop" for any AI output. Save it for the actual sloppity slop, ya know?
Yes I'm having this a lot - just tell me what you don't like about it and I'll fix the prompt. We're not going back to a world where I'm writing everything by hand.
the best marketing teams have one person leading content and one leading growth
content figures out what people actually want to watch
growth figures out how to get it in front of more of them
there's too much work for one person to do both well, you need a clear owner
nuance I am describing are scenarios where the author HAS done the editing for brevity/conciseness but the reader is irrationally anti AI output "because it's AI"
@thedatadavis nuance I am describing are scenarios where the author HAS done the editing but the reader is irrationally anti AI output "because it's AI"
@nicknow 100% - no argument from me on the no.
nuance I am describing are scenarios where the author HAS done the work but the reader is irrationally anti AI output