Tom Wentworth, CMO @ incident.io 🔥 --dangerously-skip-permissions

CMO @ incident.io 🔥 --dangerously-skip-permissions

  • incident.io
  • Computer Software
  • United States
Rank
#424of 18,993
  • 20.1K followers
  • 12 posts / 60d
  • 0.9% avg engagement
  • 475 follower growth / 30d

Tom Wentworth ranks #424 of 18,993 creators on the LinkedIn Ranking, working in Computer Software and based in United States. They have 20.1K followers and published 12 posts in the last 60 days at a 0.9% average engagement rate.

The roast

Tom Wentworth’s LinkedIn headline claims he is dangerously skipping permissions, which is the perfect way to describe a CMO who treats his engagement rate like a firewall he’s successfully blocked. He spent his career scaling up marketing just to land at a company called incident.io.

About Tom

High growth SaaS executive with expertise in both enterprise product-led and enterprise GTM models. I infrequently post advice on tech marketing at https://tomwentworth.com and used to host a podcast called Scaleup Marketing.

Highlights

  • Top 5% in Computer Software

    : Ranked #67 of 4742 creators

  • Top 5% in United States

    : Ranked #154 of 5851 creators

  • Top 10% Audience

    : 20,129 followers

  • Top 10% Impact

    : 178 avg engagements per post

Recent posts

  • Many hot takes in here also nice of me to get dressed up. At least my basement looks 🔥🔥

    62 reactions · 16 comments · 1 reposts

  • I’m pretty technical for a CMO and I’ve always wanted to be an engineer. I got close as a long time sales engineer, but no one wants me writing production code. If I were coming up in marketing now, I’d have gone through the GTM Engineer / Marketing Engineer path. I do a fair bit of that as a CMO today. It’s fun and I’m pretty good at it. But I also have a front row seat to watch real engineers like Tom A. Oni Bhaumick Zain Mobarik and James Kelly do GTM work and there’s levels to this shit. I’d be lucky to get a job on their team. There’s a big gap between Marketing Engineers and Engineer

    96 reactions · 22 comments · 1 reposts

  • Not sure why Atlassian would kill Opsgenie. But they did. And thousands of companies are not being forced to find an alternative. Today we're expanding our PagerDuty rescue program to also include Opsgenie. Simple migration. Contract buyout. Much better product. And real agentic SRE tooling. p.s. if any other competitors want to kill your products too, please do!

    40 reactions · 6 comments · 0 reposts

Last updated 2026-08-01