Connor McLeod

The hook 'You need customers before you need a platform' is a direct contradiction of what engineering teams and investors typically push for. It stops the scroll because it's immediately actionable and challenges the reader's current approach. The specificity (customers vs. platform, not just 'build lean') makes it memorable.

Opens with the contrarian claim, then acknowledges the counter-pressure (engineering team, investors, advisors), then pivots to pattern evidence ('Most startups die with perfectly architected products'), then provides concrete examples (Kubernetes clusters, 99.9% uptime), then reframes the solution (sell first, build second), and closes with a reframing of MVP as 'surgical focus' not 'cutting corners.'

• Acknowledge the objection first - 'I get it. Your engineering team wants to build it right from day one.' This disarms resistance.
• Use vivid failure imagery - 'Kubernetes clusters handling zero traffic' and '99.9% uptime for services no one used' make the problem tangible.
• Reframe the narrative - 'That's not reckless. That's risk mitigation.' Flips the moral judgment.
• Contrast the two paths - 'The companies that succeeded? They sold first, then scrambled to build.' Short, punchy, memorable.

Ends with 'I've seen and experienced in the 0-to-1 trenches with dozens of founders who bu...' (truncated). The CTA is implicit: apply this logic to your startup. The post drives comments because it challenges a deeply held belief and offers a counterintuitive path forward that readers want to debate or validate.

The hook 'Last week an incredible chapter of my life closed' is emotionally loaded and vague enough to create curiosity. It signals a major life event without revealing it, forcing readers to keep reading. The phrase 'incredible chapter' is positive, so readers expect a win or learning, not a failure.

Opens with the emotional hook, then reveals the transition (leaving Nerd/Perspect), then provides a detailed recap of accomplishments (scaling team 1 to 25, shipping blockchain loyalty platform, growing MRR from thousands to $100k+), then signals openness to new opportunities (advisory, coaching, startup groups), and closes with gratitude and a call to action for community.

• Quantify the wins - '1 to ~25,' 'few thousand dollars of MRR to more than $100k MRR,' '0 to a few hundred DAUs in a few months.' Numbers make the story credible.
• Praise the team - 'deeply motivated by our mission, highly skilled, focused on creating real value.' This positions Connor as a leader who recognizes talent, not just a solo achiever.
• Signal openness without desperation - 'I'm always open to discussing interesting opportunities, startups, advisory, and coaching!' Leaves the door open without begging.
• End with community - 'Let me know if you or anyone you know has a startup founder group I could join.' Invites readers to help, making them feel useful.

Closes with 'Here's to all the Nerds and all the awesome friends I had the chance to innovate with along the way.' This is a gratitude play that drives comments because readers want to either congratulate him, ask about the next move, or offer opportunities. The post is a soft landing announcement that builds goodwill.

The hook 'How many of your developers are playing League of Legends when they should be working? 🚨' is provocative and assumes a problem (low productivity). The emoji signals urgency and prevents the question from feeling accusatory. It's designed to make engineering leaders and managers feel seen and slightly defensive, which drives engagement.

Opens with the provocative question, then cites the source (Dimitar Bakardzhiev on Andrew Boyagi's thread), then presents two competing assumptions (business leaders think % of non-workers is high; engineers think it's low), then flips the equation (Netflix/productivity correlation is wrong; strategy/culture is the real driver), then provides a solution framework (outcome-driven companies, good strategy, clear timelines, visionary leaders).

• Use emojis as visual shorthand - '🙅‍♂️' for dismissal, '📈' and '📉' for correlation, '💩' for bad outcomes. This makes the post scannable and adds personality.
• Create a false equation, then flip it - 'Netflix watching->📈 = Productivity->📉' vs. 'Strategy/Culture->💩 = Outcomes of Eng Teams->💩.' This is a pattern interrupt that forces re-reading.
• Acknowledge the rabbit hole - 'maybe I'll post about this some other time... 🐇' This is self-aware and invites future engagement.
• Provide a solution framework - The bullet points at the end give readers actionable steps, which increases perceived value.

The post is truncated, but the structure suggests it ends with a framework for leaders to implement. The high comment count (32 out of 83 engagement) suggests readers are debating the premise, which means the hook successfully triggered disagreement and discussion.