An exclusive, meticulously-curated circle for top-tier Product Management Leaders. Follow for insider insights and a glimpse into compelling leadership narrativ
London
Joined February 2010
- Tweets10.8K
- Following8.1K
- Followers11.9K
- Likes70.5K
Two questions for each supplier: what AI features are already in our plan but switched off? And what's shipping in the next 12 months?
You may already own the AI agent you're about to build.
Before you pay anyone to build one, spend an hour asking your current suppliers what's already there and switched off.
Last week a team wanted to automate a batch of routine emails. Sensible idea. Then we looked properly: a system they already use had the feature built in. Nothing to build.
Practice management, document, HR and ticketing tools are all adding AI, often faster than anyone inside the firm notices.
My rule: if an existing system does it, use it. If it's on the supplier's roadmap but a year away, build something small now and plan to switch it off later.
It keeps IT on side too.
You may already own the AI agent you're about to build.
Before you pay anyone to build one, spend an hour asking your current suppliers what's already there and switched off.
Last week a team wanted to automate a batch of routine emails. Sensible idea. Then we looked properly: a system they already use had the feature built in. Nothing to build.
Practice management, document, HR and ticketing tools are all adding AI, often faster than anyone inside the firm notices.
My rule: if an existing system does it, use it. If it's on the supplier's roadmap but a year away, build something small now and plan to switch it off later.
It keeps IT on side too.
Who looks after an AI tool once people depend on it?
Ask before anyone in your firm builds one.
The pattern I keep seeing: a senior expert spends weeks automating a painful bit of their job. It works brilliantly. They go back to the day job, it breaks, and nobody else knows how it works. Meanwhile two other people in the same building are building the same thing.
Building is the easy part now. Before a build starts, write down four things:
1. What it does
2. What done looks like
3. Who owns it after go-live
4. What happens if that person leaves
Then ask number 4 about every AI tool you already have.
The first AI agent I'd give anyone can't do anything.
Last week I helped someone build an inbox briefing agent. It reads every email, sorts each one into critical, important or for info, and sends one private summary each morning with a suggested next step.
It can't reply, delete, archive or forward. Every decision stays with the person.
The first run sorted 152 emails. When it gets one wrong, you tell it and it updates its own rules.
Read-only is why people actually use it. Nobody worries about an agent that can't break anything. Earn the trust first, then give it more.
Ross_72 retweeted
"This is a rule here in this country. You have to give me the tips."
UK Uber driver locks female passenger in her car, demands mandatory tip.
Women, be aware which car you’re getting into. Don’t enter cars from third-world country people.
The OpenClaw ecosystem is shipping fast, but B2B enterprises are terrified of rogue agents blowing budgets or violating compliance. Static registries don't solve behavioral supply-chain risks.
Today I’m open-sourcing ClawGovern — a zero-dependency policy engine that plugs directly into your CI/CD pipeline.
Define your AI rules (budget caps, approved models, mandatory human-in-the-loop triggers). ClawGovern audits your AGENTS.md, hard-blocks non-compliant PRs, and generates stakeholder HTML reports.
🔗 github.com/rossjwebb/clawgov…
Cc: @swyx @mattshumer_ @hwchase17 @steipete @iwebst @promptfoo @OpenAI
Ross_72 retweeted
I summarized Naval's most impactful lessons on wealth, life, and happiness from a 3+ hour podcast
Nano Banana Pro is wild...
The future of working with AI isn't prompting and going back and forth in a chat window to get a feature spec or roadmap.
The future is fully autonomous systems.
The way to prepare is to understand workflow orchestration, data, and agents.
Don’t be seen as the vendor . Go beyond this if you’re in b2b. B2c has cracked this nut - you can too
Problem is people see your b2b software as you’re the vendor. They want to hear from other people too
People talk about b2b growth like it’s one monolithic space.
Selling 100k per annum and 5k software requires a totally different approach
Ross_72 retweeted
All CRMs suck.
They turn you into a data entry slave.
+ Leave a meeting: enter data.
+ Get an email: enter data.
+ Text on Slack: enter data.
My friend is building an AI-based CRM that does it for you.
RT & comment “AI” and I’ll DM you early access.
can say this with confidence:
Building teams is hard, but building teams without the right system and support behind you is infinitely harder.
🧵✨ THREAD: Product Management Success Unveiled 🧠💼
Ready for insights from a chat between myself and John Kennedy (@johndkennedy)? 🗣️🎙️
🔁🔍 Sneak Peek:
Connect with myself and John on LinkedIn for a deep dive. 🌐🔗 #ProductLeadership
Wrapped up! 🎁 Engage, share thoughts & let’s unlock more product wisdom together. 🚀🌠 #FeedbackIsKey