Diogo Guerner's Linkedin Analytics

When an MVP is having technical issues, often people think the tech stack is the issue. We’ve seen it too many times. A founder shows us their app: something they’ve poured time, money, and energy into. At first glance, it seems like there's just some small bugs. But once we peek under the hood... - Disorganised database. - Unclear logic. - Redundant API calls. - Features stitched together like duct tape. - One fix breaks three other things. And here’s the truth: - We’ve seen this in Bubble. - In Xano. - In fully coded apps. The real problem? No foundational engineering principles. - No thought-out architecture. - No data model planning. - No separation of concerns. So… how do you avoid this? Ask questions like: - How do you plan your database structure? - What’s your process for avoiding fragile workflows? - How do you plan for change and growth? - What makes your builds scalable? If you're not technical enough, hire someone technical on a hourly basis to help you choose the right partner to work with. It's important to trust your idea to a team that will build it properly. The tool doesn’t build the product. The team does.

Is your SaaS product just sitting there with no customers? Don’t worry, we can fix that! Here’s a 6-step guide to get you back on track: 1️⃣ Really get to know your customers’ headaches. Your product is supposed to help, right? Forget about your cool features for a minute and try to see things from their perspective: - Ask them for feedback - Watch how they deal with everyday hassles - Really listen to what annoys them 2️⃣ Then, let’s keep it simple. If your message is too complicated, nobody’s going to stick around. Make sure people can understand what you do in 10 seconds. 3️⃣ Build some trust before you go in for the sale. Cold pitching is hard. Instead offer value upfront by sharing insights, giving away something helpful, and focusing on being helpful rather than salesy. 4️⃣ Check your messaging—is it actually clicking with your audience? If they’re not interested, your words might be way off. Speak their language, drop the fancy talk, and make it super clear why they need you right now. 5️⃣ Don’t spread yourself too thin. Find that one marketing channel that really works and focus on it. One great channel is way better than a handful of meh ones. 6️⃣ And don’t forget to follow up! Not everyone’s ready to buy the first time they hear about you. Keep in touch, offer value, and stay on their radar (without being annoying) The bottom line: If your SaaS isn’t getting traction, it’s not the end of the road. It’s just time to tweak your approach.

Think your business degree taught you everything? The truth is, you cannot learn entrepreneurship inside a classroom. You only learn it by doing it. How? Start a business. You'll learn more in 3 months, than in your entire business degree.

With every major innovation, there are two types of people: 1. “This will impact my job” → so they resist it. 2. “This will impact my job” → so they learn how to use it best. I think it's always better to be in the second group. If you don't adapt, you risk becoming obsolete.

Meet the engineer team behind Amazon Web Services (AWS)' AI no-code platform ⚡ We're super excited to welcome Igor Araújo for our first buildersklub meetup. He will share with us his experience building a no-code AI tool inside the world's largest cloud computing provider. In this fireside chat, Igor will share unique insights on: 👉 The current state of AI and why 2025 is a turning point (MCPs, APA, etc..) 👉 How PartyRock is transforming the way non-technical users build and use AI applications 👉 The challenges of building an AI product at the scale of AWS. This meetup is perfect for: • Business leaders looking to implement AI solutions • Product managers interested in AI capabilities • No-code enthusiasts wanting to explore AI • Anyone curious about the future of AI application development Here’s the details: 📅  Where: Circula's Office in Berlin Prenzlauer Berg 📌 When: Thursday, April 24th, 2025 - 18:30 🎟️ Tickets: Free Make sure to join us for an evening of practical insights, engaging discussions, and a glimpse into AI application development! Don't miss this opportunity to expand your toolkit and connect with fellow builders in Berlin. Grab your spot through the link in the comments below! PS: big thanks to the whole Circula team for hosting us.

Building a SaaS product without client input is like throwing darts in the dark. Most teams try to please too many stakeholders during development. - Clients - Stakeholders - Executives But let’s be real: you can’t build every feature. You should think instead: - Which features gets built first? - Which ones can be built later? - Which ones are not needed at all? That’s where feature prioritisation frameworks come in. They help you decide: - What users actually want - What aligns with business goals - What’s realistic to build now Let’s break down some of the most popular: 🔹 Scoring Table Model → Score based on cost, value, complexity 🔹 ICE Framework → Impact, Confidence, Ease 🔹 PRISM → Potential value, risk, and strategic alignment 🔹 RICE → Reach, Impact, Confidence, Effort 🔹 Story Mapping → Organize user journeys visually 🔹 Kano Model → Satisfiers vs. delighters vs. must-haves These frameworks allow your team to move faster, allocate resources smarter, and launch better. Prioritisation isn’t about doing more. It’s about doing what matters most 🚀

What’s the best use case for AI in software development? Here’s my honest take after diving into tools like Cursory AI lately: It’s not massive, mature codebases. (It gets weird there… fast) - It’s greenfield. - It’s MVPs. - It’s building from scratch. That’s where AI shines the most. When you feed it good documentation, clear tech requirements, and guardrails, it can write large parts of an app. - Not perfectly. - Not completely. - But fast enough to give your team some momentum. Now… try throwing AI into a legacy codebase? - You’ll get hallucinations. - Conflicting styles. - And eight different buttons on the same screen because it forgets what it did five minutes ago. (It’s like working with a genius who has amnesia) Used right, it’s a force multiplier. My friend Victor Purolnik made a very cool video on this. Make sure to check it out in the comments.

Want to see AI & Automation builders in action, not just talk about it? Super happy to announce that tickets are now on sale for the buildersklub conference, happening on the 25th of June in Berlin.   This isn’t your typical conference.   ❌ No pitching ❌ No corporate jargon   Instead?   👉 Real builders sharing their automation & AI journey 👉 Live workshops where you build alongside experts 👉 Genuine connections with fellow entrepreneurs and operators   Whether you’re an automation enthusiast or a startup founder... this event is built for one thing: Helping you launch and scale companies faster!   👉 Come to Berlin. 👉 Learn with us. 👉 Build with us.   Link to early bird tickets in the comments 👇 Pierre-Yves Garcia, Deniz Can Sebik 🪩, Alexandre Kantjas, Justine Bigot de Préameneu, Jan Meinecke, Doris Di Domenico, Mario Liebrenz let's do this 🚀

Why external teams can be the secret weapon for internal innovation? (and how companies can finally build those “nice-to-have” ideas) Scale-ups often face this challenge: - The internal team is slammed. - The roadmap is full. - And the backlog? Overflowing with good ideas no one has time to build. It’s not because the ideas aren’t valuable. It’s because the internal team is rightly focused on the core product. (Mission-critical comes first. Always.) But here’s what we’ve seen work, again and again: - Bringing in an external team to own those sidelined ideas. - One that can build fast, stay aligned, and ship without draining internal resources. How does that look in practice? - We start with a deep product sync - We align on tech stack, roadmap, and use cases - Then we build, iterate, and launch. Independently Meanwhile, your core team? Still 100% focused on the mission-critical roadmap. The result? You get to explore new features, new experiences, even new revenue streams without burning out your internal team or derailing priorities. If your backlog is full of “someday” ideas... Maybe it’s time to give them a real shot.

Vibe coding is dead... No, it's not. It's just starting. (Yeah, yeah. Classic clickbait, I know 😂) It already does some very cool things. But of course, it's not perfect. Whenever a new technology emerges, you get two extremes: 1️⃣ The optimists – "This is revolutionary! It’s going to replace everything." 2️⃣ The skeptics – "This isn't as powerful as existing solutions. It will only create problems." As with most things in life, I believe the the real value is somewhere in the middle. The best results happen when you bring your own original ideas and use AI to accelerate the process, letting it take care of the heavy lifting. That’s exactly where we are with AI coding. Sure, some people will use it to build something fast and scrappy, full of bugs and inefficiencies. But those who truly understand good coding practices and engineering can really speed up their work and move super fast without sacrificing quality. I’ve seen this firsthand with our CTO, @miguelcoquet. He knows exactly when AI is helpful and where the dangers are. So he knows how to use it with the right caution. That’s the real conversation we should be having: not "AI will replace engineers" vs. "AI will never replace engineers." Instead, we should be asking: How do we use these tools properly? Because the truth is, it’s not about being perfect today. It’s about improving over time. And if we focus on how to use it well, the possibilities are huge. What do you think? How do you integrate AI into your workflow?

We know that automation is great to streamline digital workflows, but can it transform real-world operations? That's exactly what we explored yesterday! Yesterday marked the very first Munich edition of nocodeklub, hosted by our friends at Make. We had the pleasure of welcoming Maximilian Mayr, Head of Operations at Peter Park, who shared how they are using tool like Retool and Make to reshape the parking industry. Peter Park is transforming traditional parking lots into seamless, barrier-free experiences using license plate recognition technology. Operating in 250+ cities across Germany, Switzerland, Austria, and Italy, they manage over 50 million parking stays annually. Here are the main highlights from Max’s insights: 👉 Efficiency Boost: Peter Park doubled their installation capacity in just 12 months without expanding their project management team. By automating repetitive tasks like customer communication and logistics coordination, they significantly increased productivity. 👉 Physical Meets Digital: Automation isn’t limited to digital processes. Peter Park successfully streamlined physical operations – such as barrier removal, kiosk installations, and signage production – by integrating automation into their real-world workflows. 👉 Automation Culture: They’ve built a dedicated Business Automation team and fostered a vibrant company-wide culture of innovation. Employees across all departments actively contribute automation ideas through a dedicated Slack channel, celebrating each other’s creativity. 👉 Smart Prioritization: Peter Park uses clear metrics to prioritize automation projects, focusing on implementation effort, ongoing maintenance, and expected time savings. This ensures they consistently tackle high-impact initiatives first. 👉 Quality Assurance: To maintain high-quality customer interactions, automated communications are reviewed by project managers before sending. This human-in-the-loop approach balances efficiency with personalized customer care. Beyond the insights, the energy at the meetup was fantastic! It was inspiring to see such a diverse group of automation enthusiasts, professionals, and curious minds coming together, exchanging ideas, and sharing their passion for no-code and innovation. A huge thank you to Max for the inspiring insights, Make for hosting us, and everyone who joined us for this fantastic first Munich meetup! 🙌 We're announcing a bigger event soon, so stay tuned 👊

Bye bye nocodeklub. Say hello to buildersklub! When we launched nocodeklub, we were passionate advocates for the democratization of software development no-code tools brought. We believed that powerful tools shouldn't require programming knowledge, and we built a community around that vision. The nocodeklub showcased no-code success stories, hosted workshops, and connected makers who were building impressive products without writing a single line of code. But since our first event, things have changed. The term "no-code" served us well during this journey, but it began feeling too restrictive for what we've become. Our community isn't just about no-code tools. It's about building smarter, faster, and better using whatever combination of technologies gets the job done. buildersklub reflects this evolved mindset. Whether you're: - Leveraging AI to supercharge your workflow - Creating with no-code platforms - Writing custom code when needed - Practicing "vibe coding" to find your flow If you're building innovative solutions, you're one of us. This rebrand embraces the full spectrum of modern creation methods because great builders don't limit themselves to a single approach. They adapt, combine, and innovate with whatever tools best solve the problem. Excited to embark on this next chapter together. Same supportive community, broader horizons! Let's build together. #jointheklub

Recently, in a call with a prospect, I said that we're a digital product studio and not a software agency. He then asked, "What is the difference?" In my view, a software agency tries to bring the client's vision to life through technical execution, while we position ourselves more as product experts. Our approach involves working alongside our clients to create solutions that not only meet their needs but also add significant value to their business. This involves questioning and challenging initial ideas, suggesting new paths, and actively participating in the creation of truly impactful products. I was super happy when he replied: “That's exactly what we need.” 👌

Is AI coding here to replace developers? I don't think so... I believe the future will be the blending of layers of abstraction. Let’s break it down. 🔧 Code is where it all began. You write logic, structure apps, use frameworks like React or Django. You have full control and flexibility. It’s powerful and scalable. But it takes time. You trade speed for precision. 🧱 Low-code / No-code came in to speed things up. It’s a layer on top of code, with visual editors and pre-built blocks. Great for fast iterations. But there’s often vendor lock-in. You can hit walls. And most of the time, you can’t see or touch the code underneath. ⚡️ AI coding (aka vibe coding) is the newest layer. You describe what you want in plain language, and the AI writes the code for you. It’s fast and creative, but sometimes messy. Prompts can be misunderstood. Bugs can appear. The magic? You can access the code, adjust it, and keep building from there. Some platforms are starting to combine all three layers like Lovable They’re not picking a single abstraction. They’re stacking them together: 🧠 Prompt it → 🎨 Tweak it visually → 💻 Fine-tune it in code It’s one fluid workflow. You can build an app just by describing it, visually edit components as needed, and still dive into the actual code if you want full control. It's not perfect yet but I think that’s a glimpse of the future. We won’t have to choose between code, low-code or AI. We’ll use all of them depending on what the task requires

There’s a quiet shift happening in software engineering. It used to be all about writing code. - Big teams. - Slow releases. - Lots of manual typing. But with AI tools getting better: coding is becoming much faster and cheaper too. What used to take 10 engineers? Now gets done with 2 and an LLM. So the question is: What happens to the role of the engineer? The answer: It’s less about how you code, and more about what you build... and why. We’re moving into an era where small teams can ship big products. But that only works if engineers start thinking like product people. - Understand the user. - Know the business. - Focus on impact. Of course, code is still important. But I think product thinking is the new superpower.

We’ve been testing Lovable extensively to create applications, and the speed is incredible. But when thinking about the real impact, I couldn’t help but go back to my time studying cinema. I see some interesting similarities. Today, most of us carry a powerful video camera in our pockets. In theory, we could all use it to make amazing films. But here’s the catch: You still need a great script. You need to understand lighting, cinematography, directing actors. Basically, you need to know the craft behind it. Yes, the technology is accessible, but most people don’t know how to tell stories. Instead, they use it for quicker, easier content: like a picture of their cat or a weird TikTok dance. I believe we’ll see the same in software. Smaller applications will become incredibly fast to create. But if you want to build something truly great and scalable, you’ll still need the people who know the craft. And in product, that craft means understanding Product Strategy, UX/UI Design, and Engineering. Of course, this might be true only until Skynet takes over and the machines do everything for us. Until then, there’s still a lot of work to be done.