Jisr

I'm personally mentoring a couple of Senior IC PMMs who have been doing some great work and are actively looking out for their next role. The first person is amazing at systems thinking. In less than 2 months, they've set up an AI-first, scalable PMM infrastructure in their role. They've singlehandedly built and scaled GTM enablement, messaging infra across Sales, Demand Gen and more. They'd be perfect for a GTM team who are in a high-growth phase and looking to leverage AI in PMM. The second person is a business-first PMM who can co-own P&L with their product counterparts. They have a proven track record of taking multiple products from 0-1 and scaling 1-10 as a solo PMM. They'd be a good fit for any company who is pre-PMF and looking for their first PMM hire or close to PMF and are looking to scale fast. I'd love to make connections! Please DM 🙂

Yesterday was a genuinely great day. I had the pleasure of being invited to visit Sanabil Studio , representing Career 180 and what an experience it was. Got to dive deep into what they're building, meet incredible founders and ecosystem builders, and have real conversations with people who are clearly cooking something special. A special shoutout to: Ali Al Qudah, Co-founder of Raff, a standout startup making waves in the Retail sector. One to watch. Aseem K Thakur from Sanabil Venture Team, great energy and even greater vision. Thank you both, and the entire Sanabil Hub team, for the warm welcome and for opening the doors. #SanabilHub #VentureCapital #StartupEcosystem

We've all been obsessed with our homepages. It's the poster-child of great positioning. If a buyer lands on it and instantly gets what you do, why it matters, how you do it and understand you're built for them, you've nailed it. But in an AI-first world where buyers aren't even getting to your homepage till they are close to buying, is this the right litmus test for great positioning? No, I'm not saying homepages aren't important. I'm just saying the obsession needs to trickle down to how AI is describing you in conversations where you aren't present. It's the bane of my existence today that no matter how great our positioning, it's only helping someone convert once they land on our website and not helping anyone who's still in the problem-aware or solution-aware phase. Why? Because our on-point positioning is not updated in every single place (yet) and of course, all the AI tools pick the worst possible source (Seriously one of the sources is a random case study with AWS!) So, yes, obsess over your home pages but *also*, obsess over what these bots are saying about ya because your best positioning is only as strong as the worst source an AI will quote about you. Okay, rant over.

I Implemented CRMs to 7 clients and audited 14 active accounts. I always believe most revenue problems are not performance problems. They are infrastructure problems. Performance is the output don’t blame your employees. Infrastructure is the cause. Fix the system, simplify your process. Revenue follows. #Revenue #churn #GTM #Hubspot #salesforce

Crazy Pairing 😍

🚀 55k GitHub stars. One file. Zero overhead. While frameworks like Superpowers and Spec Kit build out massive methodologies, multi-step workflows, and rigid TDD enforcement gates... andrej-karpathy-skills takes the path of "Surgical Minimalism." 🔪 Instead of adding more tools, it adds more discipline. It’s a single CLAUDE.md file that forces a Senior Engineer mindset onto the agent. 🧠 The "Karpathy Stack" in 4 lines: 1️⃣ Think First: Stop the agent from "vibe-coding." Force it to surface assumptions and ask questions before writing a single line. ❓ 2️⃣ Simplify: No abstractions. No speculative code. No bloat. Keep the logic flat and readable. 📉 3️⃣ Surgical: Touch only what’s needed. No more annoying "drive-by" refactors or accidental style changes. 🎯 4️⃣ Goal-Loop: Define success early and work until the specific criteria is met. 🔄 Frameworks are great for teams that need rigid rails. 🛤️ But if you want "senior-level" output without the heavy configuration tax? This is the ultimate shortcut. ⚡ Repo: https://lnkd.in/d_tMhV6D #AI #SoftwareEngineering #ClaudeCode #Programming #Minimalism #CleanCode

One year ago I said yes to Jisr | جسر I could write about the scale-up life, about working on critical systems (and how much I enjoy it), about how things move so fast here I need a calendar blocker just to eat lunch, about some of the amazing people I work with. But that will be for another day... Today I want to talk about working full remote. Since most companies are still cutting on work from home policies, it still feels worth talking about it... I was actually one of those people who doubted it, remote work. I genuinely enjoyed the office (just not the traffic). But remote work changed my life. I wake up super early, watch sunrise at the gym or get a head start on the day (if you know me, you know I'm a morning person). I work next to Teca and Pinha, take them for a walk at lunch, have coffee in the sun in my garden. I finish early because I start early, and it's 2 minutes to pick up my son from school at a decent hour. Sometimes we go straight to the beach (FINALLY enjoying all the perks of living by the beach). Sometimes swimming classes. Sometimes grandparents' house. Sometimes just home to play with the dogs. I'm just so much happier at work, and that is because of how balanced my personal life is. Where I want to get at is: this is not a remote work manifesto, I just want to share that this one small big change, made everything different for me for the better... I'm not worrying if I'll be in time for school pick-up, or if the dogs are walked, or feeling bad about not getting exercise. Not everyone has the same 24h, and the proof is that I got some of mine back.

Lately, I've fallen in love with Product Marketing all over again. Big thanks to Lovable and Claude. I love the strategic side of PMM but man, it hurt when my best ideas died on the execution hill: Engineering bandwidth, RevOps priorities or a budget fight over weeks for a semi-decent tool. And if I was lucky enough to get the help, I'd have to compromise on quality. Well, not anymore. Now we think it, we do it. - We've killed pricing and discounting misalignment with clean pricing calculators on Lovable - Knowledge bots for every product/segment on ChatGPT - No more fighting with Gsheets/Excels, interactive ROI calculators are now on Lovable with the narrative baked in - After jumping on the Gamma bandwagon and struggling, we're now moving all our Sales collaterals on Lovable (Still under testing but it's coming out great!) - Building a Skill on Claude so it can give us the best guidance to create product videos with Arcade - And a monster project we're fleshing out is how do we make internal knowledge so easy to use that it'd be crime to miss them My dream list is endless! Just a word of caution: Recently, we've gotten so carried away and while it's fun, the best option sometimes is still to find an existing tool that will do the work for you and make sure it connects to Claude/Lovable. (I've not given up on SaaS just yet) We have a long list of problems/opportunities that just keeps getting longer. Would love to hear what problems other PMMs are solving with our fav AI buddies :)

This resonates deeply. I've been on the hiring side for product designers and conducted 150+ interviews in less than a year, the pattern he is describing is real and consistent. What I've noticed is that the gap isn't just about skills. It's structural. Many designers spent years in environments where they were handed solutions to "make pretty", never given the space or the expectation to question the problem itself. They never truly collaborated with product and engineering as equals. Teresa Torres talks about the product trio for a reason: when designers sit outside that loop, they lose touch with business context and engineering reality alike. They end up optimizing pixels in isolation. So when you ask them to zoom out and think about flows, trade-offs, or system-level impact, it's not that they can't. They were never put in a position where they had to. That said, I'd push back slightly on the framing of "junior vs. senior." The issue isn't seniority, it's environment. A senior designer who spent 5 years shipping features without ownership will look weaker than a junior who spent 1 year thinking end-to-end alongside PM and engineering. The real question for companies isn't "should we hire junior?", it's "are we building an environment where designers are expected to think like product people from day one?" Because if the environment doesn't change, even those talented juniors will plateau the same way.