Have anyone experienced with the new Windows Desktop App for Linkedin? Is there any new features that is worth using?

I'm sure most of you have read the news about Builder.ai (https://www.business-standard.com/companies/news/builderai-faked-ai-700-indian-engineers-files-bankruptcy-microsoft-125060401006_1.html) A company claiming to have an AI that could code, in reality, had 700 Indians in the background. It is flagged as a scandal in the media and on social networks. However, following the Lean startup approach and everything we discuss here (which makes sense!) 1. You don't start by building, you start by validating 2. You sell before you build 3. You manually deliver, even if you lose money, to find the best delivery concepts 4. Then, when you know what you really need, then you start automating and investing in building solutions 5. And then you optimize for profit and have a running business Perhaps Builder.ai only got to step 3/4. They did everything right, by first validating if there is a market and need, delivering "manually" while validating, then trying to rapidly build an AI. Or?

I have one concern with collection of data for problem validation; how to avoid that the data is biased? For example, the people who agree to talk with you is likely those that have a problem. So if you talked with 5 people and they all say they have a problem, you might still risk that the 95 people that said no to a conversation do not have a problem. Can you still conclude there is a problem? Or when I walk at a conference about security, where people will be who are aware of security and concerned about it, can I then really conclude that there is a problem? I need an initial representative set. Normally you would choose 1000+ by random. Selected without bias. Then interview as many as possible, assuming the ones that won't talk have no problem. Or maybe I'm over analysing here?

Hey friends! This Tuesday's community call is exclusively for our pro-members and could save you months of wasted effort and thousands of dollars. We're diving deep into validation - the single biggest factor that determines if your product will be a hit or a total flop. The quality of validation you bring to your product journey literally makes all the difference. And I'm not talking about the warm fuzzy feedback you get when someone says "neat idea" - I'm talking about methodical, reality-based validation that ensures you're building something people will actually pay for. Join our live community call this Tuesday to see this framework in action with a real product example. Here's my battle-tested validation framework that's saved teams I've worked with from wasting months building things nobody wants: 1. Problem Validation: Don't Skip This Step! Before you even think about solutions, make absolutely sure you're solving a problem people would throw money at to fix. This is THE most critical step. A beautiful product solving a mild inconvenience? That's what I call a "zombie product" - looks alive but basically dead on arrival. 2. Solution Validation: Build What They Actually Need Once you've confirmed the problem is severe enough, people will actively want to help you improve your solution. But asking the right questions is crucial - I'll share my list of "forbidden questions" that lead to misleading feedback, and show you what to ask instead. 3. Pricing Validation: Timing Is Everything Here's where so many get it wrong. Only validate pricing after your solution has gotten enthusiastic "10 out of 10" responses. Trying to price-test a solution people merely "kind of like" is setting yourself up for failure (or very low prices). 4. GTM/Channel Validation: Finding Your People These validation questions help you discover the most efficient ways to reach more customers like your early adopters. Not absolutely critical, but incredibly valuable for scaling.

Hey everyone, I’m Marcus, excited to be the newest member of the community! I don’t come from a fancy software background, but I’ve been diving into AI automation and have picked up some skills along the way. I’ve built a few automations focused on content creation, and now I’m eager to learn how to package them into a sellable offer. Thinking to go with some low ticket offers first. Really looking forward to learning, connecting, and growing with all of you!