Oscar Bennett's profile on Product Hunt

About

The Data Centre vendor market is growing fast, but commercial hiring hasn’t kept pace. Most recruiters either don’t understand the sector or rely on the same visible talent pool everyone else is fishing in. I built teambuild’s data centre specialism specifically to fix that: Placing Sales Director, VP Sales, CCO, and Commercial Director-level leaders across the vendor supply chain; liquid cooling, power infrastructure, electrical components, and beyond — across the UK and EMEA. My background is in construction supply chain recruitment, which turns out to be unusually good preparation. Long sales cycles, complex B2B procurement, technical buyers, relationship-led deal-making — the commercial DNA is near-identical.

Badges

Tastemaker

Gone streaking

Forums

p/murror

•

5d ago

What did AI make too easy for you, and what do you wish you'd kept doing by hand?

Every shortcut removes a bit of friction, and some of that friction was doing a job. I'd like to hear which parts of your workflow you handed over and which you took back.

When a tool makes something easy, you rarely notice what the difficulty used to give you. Writing a first draft by hand forced me to decide what I actually thought. Reading user feedback line by line made me notice phrasing that a summary flattens. Writing a spec from scratch was slow, and the slowness was where I found the holes.

•

12d ago

Why do users ask for features they end up never using?

Our most requested feature from feedback forms took us three weeks to build and ship. We launched it with an announcement email and in app banner but less than 5% of active users have touched it since.

It was a good reminder that what users say they want in a survey often differs from what actually fits into their daily habits.

How do you validate feature requests before committing engineering time to build them?

•

13d ago

From vanity signups to real retention: What changes when money enters the chat?

Focusing on signup momentum feels amazing early on, but cancellations hit differently once revenue is involved.

We used to celebrate new user milestones. Then the paid tier launched and churn taught us a lesson: people don't leave because of missing features. They leave because our product didn't fit into their daily workday routine.

Fixing actual workflow friction is the real bottleneck.

Do experienced founders get used to churn, or do you just build faster ways to analyze cancellation reasons?