Ian Maxwell

What if the real shift isn't "who works for whom," but that work itself becomes a shared loop where neither side is fully in control?

The hybrid approach seems safest. Build quietly, then share once there is something real to react to.

The incentive designs are strong, but what happens when every features starts getting "extra points"?

It's interesting how public launches test not just the product, but the team's ability to listen under pressure. What feedback was hardest to hear?

Curious whether people respond better to a transparent founder post like this than to a more polished promo style.

Curious whether remote roles still dominate these threads, or of more teams are learning back into location based hiring now.

The part about showing upon special Product Hunt leaderboards is smart. Funding gets attention, but visibility is what can really create momentum.

Would honestly love to see this split by workflow, because one "best model" overall feels too broad to be useful.

If anything this sounds less like "worst launch in PH history" and more like "strong product signal with terrible timing and logistics"

I can see why this connects, it's one of those habits people already have, so the barrier to caring about it feels low.

I think that you're thinking about long term impact before rushing it, because free plans can help a lot or quietly create support chaos. What's your biggest concern with launching it?

What stands out to me is how fast "being recorded" is becoming the default expectations in work calls. Do you think most people have actually agreed to that, or just stop questioning it?

Your pilot sounds more interesting than the idea itself tbh. Real user reaction will say a lot. What kind of response are you expecting from the subreddit?