100 people from my LinkedIn network. For each one, an original idea for a conversation, collaboration, product, or partnership.
1. AI & Startup Founders
1. Ido Shamun — Co-Founder & CTO, daily.dev
daily.dev is a developer news aggregator with millions of users. Idea: Propose a "French Tech Deep Dives" content series on daily.dev. You've written 85+ analyses — repurpose them as daily.dev posts and get distribution to their massive developer audience. Alternatively: ask how they handle content curation at scale, and whether there's a gap for AI-powered analysis (your specialty).
2. Harsha Srijay — Co-Founder, Linc AI (YC S23)
YC S23 company. Idea: Ask about the YC experience candidly — what they'd do differently, how the batch network works post-demo-day, and whether the YC label actually helps with European enterprise sales. Use insights to decide if YC is worth applying to, or if the French ecosystem (Station F, Hexa) is better for your profile.
3. Andreas Lundmark — CEO & Co-founder, Berget AI
European sovereign AI infrastructure. Idea: Propose building an open-source "AI workstation on VPS" tool (you mentioned this in your journal) and deploying it on Berget's European infrastructure. Pitch: "sovereign AI dev environments" — EU companies get AI workstations without sending data to US clouds. You build, they host, revenue share.
4. Samy Lahbabi — Co-founder & CEO, Stellia.ai
Idea: Ask what vertical AI application he's building and whether he needs developer tooling around it. Offer to be a design partner — you use their AI tool, they use your event tracking / monitoring in exchange. Zero-cost mutual beta testing.
5. Saba Hesaraki — Founder & CTO, MedoraAI
Medical AI. Idea: Medical AI needs audit trails and event logging for compliance. Pitch a lightweight "clinical event tracker" — every AI inference logged with timestamp, model version, confidence score. Simpler than Datadog, designed for health-tech compliance (HIPAA/MDR). You already know how to build event trackers.
6. Thomas Sabatier — CEO & Founder, tolk.ai
Conversational AI. Idea: Interview him for a blog post on "how French AI companies compete with OpenAI on specific verticals." Cross-post on your site and his — mutual SEO benefit. Opens the door to discussing what tooling conversational AI companies actually need.
7. Alexis Gendronneau — Data & AI Director, NumSpot
NumSpot is the French sovereign cloud initiative. Idea: NumSpot will need developer tools built specifically for the French/EU market. Offer to consult on developer experience for their platform — you've studied every dev tool in the market (Supabase, Vercel, Railway, etc.). Position yourself as "the person who knows what good DX looks like."
8. Lionel Louis — Founder & CEO, AI Corner
Idea: If AI Corner is a media/education play around AI, propose a co-branded research series. You write the deep analyses (you already have 85), they distribute through their channels. Test with one piece, measure traffic, then formalize into a paid partnership or revenue share.
9. Louis Damas — Co-Founder, Hairdex
AI for haircare. Hilariously specific niche. Idea: Interview him for a "Dumb Ideas That Actually Worked" analysis — you already have a similar page. The story of building AI for a seemingly small niche is compelling content. Great podcast/newsletter material about finding PMF in unexpected places.
10. Alice Gouzalch — Fundraising Director, Inovexus
Idea: She helps startups raise money. Ask her: "If you had to pitch an open-source developer tool to French VCs today, what would the deck look like?" Get insider fundraising intelligence specifically for your type of project. Offer your 85 market analyses as research material she can share with her portfolio companies.
11. Michael Robin — Principal Software Technical Lead (AI & Core Services), Willow
Idea: Principal-level AI engineer. Ask him what internal tooling they've had to build that doesn't exist as a product yet. Every company at this stage builds internal tools that could be open-sourced or productized. You might find your next project idea from his pain points.
12. Jeremie Lebrun — Director of Finance Systems, Mistral AI
You have 69 Mistral connections. Idea: Ask what finance/billing infrastructure Mistral uses for their API. Usage-based billing is notoriously hard. If there's a gap, build an open-source usage metering tool specifically for AI API companies. Mistral + your other AI founder connections = instant market validation.
13. Benjamin Cohen — Fondateur & CEO, Le Crypto Daily
French crypto media founder. Idea: He's built a daily content operation in French. Ask him about the economics: subscriber count, CPMs, sponsorship rates, what tools he uses (beehiiv? Substack?). Apply learnings to your own newsletter ambitions. Bonus: propose a "tech" edition under his brand umbrella.
14. Damien Didier — Head of Sustainability, daphni
Sustainability at a VC fund. Idea: Propose an analysis of "green dev tools" — which developer tools have the lowest carbon footprint, which clouds are greenest, how to measure the environmental impact of your SaaS stack. You write the research, daphni gets ESG content for their portfolio, you get VC distribution.
15. Lucas Gomes de Santana — Technical Leader (Golang), Emailchaser
Go developer building an email tool. Idea: Co-author a technical blog post: "Building high-throughput email systems in Go." You bring the Go blogging audience, he brings the domain expertise. Cross-post on both sites. Establishes both of you as Go thought leaders.
Idea: Temporal is the workflow engine for distributed systems. Ask him: "What's the most common mistake companies make when adopting workflow orchestration?" Write a blog post with his answer. This gives you content + a relationship with a CTO who built a $1.5B company in Go.
17. Bu Kinoshita — Co-Founder & CTO, Resend
Idea: Resend has the best developer experience of any email API. Ask Bu to do a public "DX teardown" together — you both pick 5 developer tools and critique their onboarding, docs, and API design live. Post it as a blog/video. Positions both of you as DX experts.
18. Alexander Korotkov — Head of PostgreSQL group, Supabase
Idea: He's a PostgreSQL core contributor. Ask him: "What PostgreSQL feature is criminally underused by web developers?" Write a Go blog post implementing whatever he says. "Alexander Korotkov told me to try X — here's what happened" is killer content.
19. Kamil Ogórek — API Lead Engineer, Supabase
Idea: He designs APIs at one of the best DX companies. Ask him to review your project's API design — 30 minutes of feedback from Supabase's API lead is worth months of guessing. Offer to write up the learnings as a public "API design review" post (with his permission).
20. Lindsey Simon — VP Engineering, Vercel
Idea: Ask about Vercel's approach to developer onboarding metrics. "How do you measure time-to-first-deploy? What's the magic number that predicts retention?" Apply whatever framework she shares to your own projects. Write up "What I learned about DX metrics from Vercel's VP Eng."
Idea: PostHog is open-source product analytics. Ask Seb: "What's the #1 thing companies get wrong when setting up product analytics?" Create a "PostHog anti-patterns" guide with his input. Helps PostHog users, gives you content, opens partnership discussion.
22. Riccardo Busetti — Team Lead, Supabase
Idea: Ask about Supabase's open-source growth playbook. Specifically: how did they go from "Firebase alternative" positioning to their own category? What worked in the first 1,000 GitHub stars? Apply the playbook to your own open-source projects.
23. Joshua Smith — Senior Staff Solutions Architect, Temporal
Idea: Solutions architects talk to hundreds of companies. Ask: "What's the weirdest/most creative use case for Temporal you've seen?" Compile the answers into a "10 things you didn't know you could build with workflow engines" post. Great content, great relationship builder.
Idea: Cloudflare is investing heavily in edge computing. Ask about building Go applications on Workers/edge. Write a "Deploying Go at the edge with Cloudflare" tutorial. Cloudflare might share it in their community — free distribution to millions of developers.
25. Chris Ludden — Staff Software Engineer, Temporal
Idea: Two Temporal staff engineers in your network. Propose writing the "definitive Go + Temporal tutorial" for their docs or blog. You're a Go blogger, they need Go content. Win-win: your name on Temporal's blog, their credibility on yours.
Idea: She sells Docker to mid-market companies. Ask: "What do engineering teams actually pay for in Docker's enterprise offering?" Understanding how Docker monetizes open-source is a masterclass for anyone building OSS. Apply the learnings to your own monetization strategy.
27. Daniel Gomez Rico — Senior Mobile Engineer, Neon
Idea: Neon is the serverless Postgres company. Ask about their mobile strategy — are they building mobile SDKs? If not, offer to build a Go SDK or CLI tool for Neon. Open-source contribution + relationship with a hot infrastructure company.
3. Investors & VCs
28. Carla Pomes — VC Associate, MAIF Impact
Impact VC. Idea: Write an analysis of "impact dev tools" — tools that help companies measure their carbon footprint, accessibility compliance, or social impact. Send it to her. If she's looking for deal flow in this space, you become her go-to analyst for technical impact investments.
29. Hugo Vallespi — Avocat Venture Capital, Bird & Bird
VC lawyer at a top tech law firm. Idea: Ask him to write a guest post on your site: "5 legal mistakes French open-source founders make." He gets visibility with founders (his clients), you get authoritative legal content. Open door to get free legal advice when you actually need it.
30. Olivier Maurin — VC Scout, EPSL VC
VC scouts find deals. Idea: Offer your 85 market analyses as a sourcing tool. "Here are 85 market maps I've built — if any align with EPSL's thesis, I can intro you to founders in those spaces." You become a deal-sourcing partner, which is the fastest path to getting your own deals looked at.
31. Natalia Cebotari — Internal Venture Lead, European EdTech Holding
Builds ed-tech ventures internally. Idea: Propose a "learn to code with Go" curriculum. Go is underserved in education (everyone teaches Python/JS). A structured Go course for their platform, authored by you, with your blog posts as the foundation. Revenue share or licensing deal.
32. Richard Seroter — Chief Evangelist, Google Cloud
Idea: He's Google Cloud's chief evangelist. Pitch a collaboration: "Go on Google Cloud" workshop or webinar series. You write the Go content, Google Cloud provides infrastructure credits and distribution. You get exposure to Google's developer audience. He gets quality Go content.
Real estate tech VC. Idea: Write a "PropTech developer tools" analysis. There's an entire ecosystem of APIs for real estate (property data, mortgage calculators, valuation models) that's underanalyzed. Send it to her team. You become the technical analyst for a sector most tech people ignore.
34. Damien Didier — Head of Sustainability, daphni
Idea: Create a "Green Software Scorecard" — an open-source tool that measures the energy consumption of your CI/CD pipeline, dependencies, and cloud usage. Position it as "ESG for engineering teams." daphni could promote it to their portfolio as a sustainability tool. You get distribution through a VC fund.
35. Jean Sini — Founder & Managing Partner, Irregular Expressions
VC fund with a great name. Idea: The fund name suggests they like unconventional founders. Ask: "What's the most irregular investment thesis you've had?" Write it up as content. Unconventional VC thinking makes for great blog posts and positions you as someone who thinks differently about startups.
36. Stephane Nasser — Co-founder, OpenVC
OpenVC is a platform connecting founders with VCs. Idea: Offer to write "market analysis templates" for OpenVC's founder community. Founders need market research for their pitch decks — your 85 analyses prove you can do this. Productize it: "AI-generated market analysis for your pitch deck, powered by Alexis's methodology." Revenue share with OpenVC.
37. Denny Gabriel — Investor, Runa Capital
Runa specifically invests in open-source. Idea: Ask: "What metrics does Runa look at when evaluating open-source companies at pre-seed?" GitHub stars vs. actual usage vs. community engagement vs. contributor diversity. Write it up as "The Open-Source Fundraising Playbook" — cite Runa's framework. They get PR, you get the definitive guide.
4. Journalists & Media
38. Joséphine Boone — Journaliste Tech & IA, Les Echos
France's biggest business paper, tech beat. Idea: Pitch yourself as a source for "the developer perspective on AI." Journalists need technical sources who can explain things simply. When she writes about Mistral, she needs someone who actually uses AI APIs — that's you. First step: respond to one of her articles with a thoughtful technical take.
39. Emile Marzolf — Journaliste Tech, POLITICO Europe
POLITICO covers tech regulation. Idea: Offer expertise on "how EU regulations affect developer tools." AI Act, Data Act, GDPR for SaaS — you've researched all of this. Position yourself as the technical founder who actually understands regulation. When POLITICO needs a quote from a French founder on EU tech policy, you're the call.
40. Camille Bour-Roussi — Journaliste, Billions
Billions covers business/money stories. Idea: Pitch: "I analyzed the business models of 85 different markets using AI. Here's what I learned about what actually makes money online." A meta-story about using AI for business research is perfect for a money-focused publication.
Freelance journalist covering the French startup ecosystem for Bpifrance. Idea: Propose a series: "The Invisible Infrastructure" — profiles of the French developer tools companies nobody talks about (Scaleway, OVHcloud's Go teams, Temporal's French engineers). He gets unique stories, you get published in Bpifrance's ecosystem.
42. Elie Hervé — Journaliste pigiste, Les Jours
Les Jours does long-form investigative journalism. Idea: Pitch a long-form piece: "I built a company in public for 100 days. Here's the unfiltered truth." Your palmframe journal + private journal material would make a compelling narrative about indie tech entrepreneurship in France. Raw and honest — Les Jours' style.
43. Paul-Lionel Quiviger — Rédacteur, Conflits - Revue de Géopolitique
Geopolitics magazine! Idea: Write a piece: "The Geopolitics of Developer Tools — Why Where Your Database Lives Matters." Sovereign cloud (NumSpot, Scaleway), GDPR, data localization, US vs EU tech stacks. You have the technical knowledge, he has the geopolitical readership. Unexpected crossover content.
44. Martin Coulter — News Editor, Sifted
Sifted is THE European startup media. Idea: Become a regular source. When Sifted covers French tech funding rounds, developer tools, or AI companies, you can provide technical context. First step: DM him with a scoop or unique angle on a story he's already covering.
Tech Rocks is a French tech community. Idea: Propose a monthly "market analysis" column in the Tech Rocks newsletter. You pick one market per month from your 85 analyses, write a condensed version. They get premium content, you get distribution to their engineering leader audience. Test with one issue, then formalize.
5. Open Source People
46. Pedro Piñera Buendia — Creator & Maintainer, Tuist
Tuist is an open-source Xcode project generator (2.5k+ stars). Idea: Ask about open-source sustainability — how does he fund Tuist development? The "open-source maintainer business model" is a fascinating topic. Write a comparative analysis of how 10 different OSS maintainers monetize. Pedro's story + your analysis skills = great content.
47. Guillaume Marquis — Co-Founder, Open Source Projects
Idea: His company name is literally "Open Source Projects." Ask what they actually build/consult on. If they help companies adopt OSS, propose a partnership: you bring the technical analysis (your 85 market maps), they bring the consulting relationships. Co-sell "open-source strategy" services.
48. Thomas Gentilhomme — Open Source Maintainer, JollyPixel
Idea: Fellow French open-source maintainer. Propose a "French OSS Maintainers" podcast or blog series. Interview 10 French people who maintain popular open-source projects. Nobody's doing this in French. First episode: Thomas. It builds community and establishes you both in the French OSS scene.
Astro is one of the hottest web frameworks. Idea: Build an Astro integration or template that showcases your projects. "The minimalist personal site template for Astro, inspired by alexisbouchez.com." Your design philosophy (no CSS, semantic HTML) is actually a statement. Package it. Florian could help get it into Astro's ecosystem.
Idea: He maintains Docker open-source components. Ask about the contributor experience at Docker — what makes someone a good first-time contributor? Write a "How to contribute to Docker" tutorial in Go. Docker's blog might feature it. Your Go audience + Docker's audience = massive reach.
51. Stefanie Senger — Open Source Software Engineer, :probabl.
:probabl. is the company behind scikit-learn. Idea: Ask about the business model of maintaining one of the most-used ML libraries in the world. How do you monetize something that everyone uses for free? The answer is probably "enterprise support + managed service." Write up the playbook — it applies to anyone building OSS.
Idea: He built devrel from scratch at a database company. Ask: "If you had zero budget and needed 1,000 developers using your product in 90 days, what would you do?" Write up the answer as "The $0 DevRel Playbook." It's practical for indie makers and gets shared widely.
53. Oleg Šelajev — Developer Relations, Docker
Idea: Docker's DevRel. Propose: co-create a "Docker + Go best practices" guide. You write the Go parts, he validates the Docker parts. Publish on both blogs. Docker's distribution = your content reaches hundreds of thousands of developers.
54. Etienne Waldron — Developer Advocate, Ledger
DevRel for a crypto hardware company. Idea: Ask about doing devrel for hardware vs. software. Totally different challenge. Write "DevRel for Atoms vs. Bits" — a comparison piece. Unusual angle, shareable, positions you as someone who thinks about developer experience broadly.
Idea: Vonage does communications APIs. Propose building a "Go SDK for Vonage" or a tutorial on building voice/SMS apps in Go using their API. If no official Go SDK exists, this is a contribution opportunity. If one exists, improve it. Either way: visibility in their developer community.
56. Filip Sardjoski — Developer Relations, Interhuman AI
Idea: "Interhuman AI" is a fascinating name. Ask what they're building. If it's AI for human interactions, there's a content play: "The companies building AI to make humans more human." Counter-narrative to "AI replaces humans." Publish it, tag him.
57. Prachi Jamdade — Developer Advocate, Gravitee
Gravitee is API management. Idea: Ask about the state of API management in 2026. Is the market consolidating? What do developers actually want from API gateways? Write "The Honest State of API Management" — with input from someone who talks to API developers every day. API content gets tons of organic search traffic.
58. Mukul Mantosh — Go Developer Advocate, JetBrains
Idea: He evangelizes Go at JetBrains (GoLand IDE). Propose a joint webinar: "Building production Go applications — from IDE to deployment." You demo the app, he demos the tooling. JetBrains promotes it to their Go user base. Massive audience for free.
7. Go Developers
59. Jonathan Remy — Software Engineer (Golang & DevOps), Scaleway
Idea: Scaleway is a French cloud using Go internally. Propose a case study: "How Scaleway uses Go at scale." Co-author with Jonathan. Publish on your blog and Scaleway's engineering blog. Positions you as the Go person in French cloud. Scaleway might hire you or contract you.
60. Mark Ambrazhevich — Senior Golang Backend Engineer, River Island
Go in retail/e-commerce. Idea: "Go in unexpected places" blog series. Everyone knows Go is used for infra — but River Island? Interview Mark about why a fashion retailer chose Go. Then do 5 more: Go at a bank, Go at a hospital, Go at a media company. Great niche content.
61. Luciano Ferrari — Go Developer, Independent Consultant
Idea: Fellow independent Go consultant. Propose a "Go Consulting Collective" — a small group of independent Go consultants who refer work to each other. When one of you is busy or the project needs a different skill, you pass it along. Informal, no overhead, just mutual referrals.
62. Gabriel Bussolo — Senior Golang Engineer, McGraw Hill
Go at a publishing company. Idea: Co-author a short technical e-book: "Pragmatic Go Patterns" — 10 real-world Go patterns from production systems. You provide web/API patterns, he provides publishing/content pipeline patterns. Sell on Gumroad for $19. Split revenue.
63. Ali Mhadhbi — Développeur Backend Golang, Impakt.io
French Go developer. Idea: Start a "Go Paris" monthly meetup. Just 20 people, a bar, two lightning talks. You and Ali do the first two talks. Use your LinkedIn network to fill the room (you have 170 Go devs!). Meetups → community → consulting leads → job offers → deal flow. The ROI of meetups is insane.
Go + security. Idea: Co-write "Secure Go: a security checklist for Go web applications." Covers: SQL injection in Go, JWT pitfalls, race conditions, memory safety. SecureLayer7 gets content for their security blog, you get a security-focused Go guide. Security content has evergreen SEO value.
65. Jambul Maisupov — Senior Golang Developer, Bank CenterCredit
Go in banking (Kazakhstan). Idea: "Go in fintech" analysis. Interview Go developers at banks and fintech companies across your network. Why do financial institutions choose Go? What are the compliance challenges? Publish as a research piece. Fintech companies will find it when evaluating Go.
66. Huilen Vilches — Golang & React Developer, Cult Studio
Full-stack Go + React. Idea: Build a "Go + React starter kit" together — a production-ready template with auth, database, API, and deployment config. Open source it. There's no definitive Go+React starter the way there is for Next.js or Rails. Hundreds of GitHub stars guaranteed.
8. Designers & UX
67. Derry Birkett — Head of UX, CloudBees
UX for a CI/CD company. Idea: Ask: "Why does every CI/CD dashboard look the same? What would a truly beautiful CI/CD experience look like?" Write "The UX of Developer Infrastructure" with his insights. Developer tools are notoriously ugly — a design-forward analysis would stand out.
68. Bozena Czech — Senior Product Designer, Magma
Magma is a design collaboration tool. Idea: Ask her to redesign your personal website as a design exercise. Your site is intentionally minimal (no CSS, semantic HTML). Challenge: "Can you make this beautiful without adding CSS?" The constraint-based design exercise would make incredible content. Post the before/after.
69. FuJung Chang — Lead UX Researcher, Gogolook
UX research lead. Idea: Ask: "How do you do UX research for a developer tool when your users are engineers who hate surveys?" This is a real problem. Most dev tools guess at UX. Write "UX Research for Developers Who Don't Want to Be Researched." Viral in the dev tools community.
70. Zeh Fernandes — Founding Designer, Resend
He designed Resend's famously beautiful developer experience. Idea: Ask: "What design decisions at Resend had the biggest impact on developer adoption?" Write "How Resend's Design Drives Developer Adoption" — a design case study from the developer tools angle. Design Twitter would eat this up.
Idea: Vercel has the most recognizable brand in dev tools (the triangle, the black/white aesthetic). Ask about building a brand identity for a technical product. "How to brand a developer tool when your audience hates marketing" would be an incredible blog post.
9. Marketing & Growth
72. Arianna Young — Head of Integrated Marketing, ClickUp
ClickUp is a productivity tool with aggressive marketing. Idea: Ask: "What's ClickUp's most underrated growth channel?" ClickUp went from 0 to unicorn largely through content and community. The playbook is applicable to any SaaS. Write "What indie makers can learn from ClickUp's growth machine."
73. Adam Miedema — Head of Growth, Msty
Idea: Msty does local AI. Ask about growing an AI product when your core value prop is "runs on your machine" — you can't track users, can't do product analytics, can't A/B test. "The growth challenge of local-first software." Counterintuitive growth strategies for privacy-first products.
74. Jovy Yu — Growth Lead, Lonely Octopus
Great company name. Idea: Ask what metrics they optimize for as a growth team. Then ask: "If you had to grow an open-source project with no marketing budget, what would you do?" The answer is probably: GitHub SEO, strategic integrations, community-driven content. Write the playbook.
75. Julia Paganelli — Global Head of Field Marketing & SDRs, SBS
Idea: She manages both field marketing AND SDRs — the full top-of-funnel. Ask: "What's the conversion rate from event → demo → customer?" Understanding enterprise go-to-market metrics helps you decide whether to build for enterprises or stay developer-first.
76. Ghanva Azwar — Head of Marketing, Thageel
Idea: If Thageel operates in the Middle East, ask about marketing tech products in emerging markets. "How developer tools marketing differs by region" — US vs Europe vs Middle East vs LatAm. Useful for anyone building a global dev tool.
77. Joe Martin — Marketing Team Lead, PostHog
PostHog does marketing differently (memes, brutally honest content, no corporate speak). Idea: Ask: "What piece of PostHog marketing content has the highest ROI ever?" Is it a blog post, a comparison page, a meme? Write "The anti-marketing marketing playbook" based on PostHog's approach. They'd probably share it themselves.
10. Security
78. Kim Usher — Group Manager, Upwind Security
Cloud security. Idea: Ask: "What's the most common security misconfiguration in cloud-native applications?" Write a "Security checklist for indie hackers deploying to the cloud." Most solo developers have terrible security practices. A simple, actionable checklist would get massive organic traffic.
79. Zack Isaacson — Talent, Prophet Security
Idea: He recruits for a security startup. Ask: "What skills are security companies desperate to hire for?" If Go + security is in demand, there's a consulting or training opportunity. "Go for security engineers" course could be uniquely positioned.
80. Bleuenn Pensec — Cheffe de projets en sensibilisation à la cybersécurité, VINCI Energies
Cybersecurity awareness at a major industrial company. Idea: Ask about security training for non-technical employees. Is there a gap for an interactive, web-based security awareness tool? Could be built as a simple static HTML game (your specialty) — "Can you spot the phishing email?" Open source it.
Idea: Security research at an observability company. Ask: "What security signals should every developer monitor in their logs?" Write "The 10 log lines that tell you you've been hacked." Technical, scary, extremely shareable. Cross-post on Hacker News for maximum reach.
11. Product People
82. Aleksandre Natchkebia — AI Product Manager, Trilogy
Idea: Trilogy acquires and operates software companies. Ask: "What makes a software product attractive for acquisition?" If you build something small and profitable, understanding the exit landscape is valuable. Write "Building to be acquired: a developer's guide to making your side project acquisition-ready."
83. Perle Geoffroy-Donders — CPO, TEEPTRAK France
Industrial IoT. Idea: Ask: "How do you do product discovery when your users are factory workers, not tech people?" The answer probably involves creative research methods. Write "Product management for non-digital natives" — useful for anyone building tools outside the tech bubble.
84. Omolade Awokola — AI Product Manager, Instict
Idea: Ask about the unique challenges of being a PM for an AI product. How do you roadmap when the underlying model changes every 3 months? "Product management in the age of AI" from a practitioner's perspective. Timely, evergreen, and relevant to everyone building with AI.
85. Benoît Froment — Freelance Product Manager
Independent PM consultant. Idea: Propose a joint offering: "Product strategy + technical implementation in one package." He does the product thinking, you do the building. Offer it to early-stage startups: "Go from idea to MVP in 4 weeks." Split revenue. Targets the 2,900 founders in your network.
86. Nikolai Losev — Chief Product & Technology Officer, Banjulo.com
Idea: A CPTO (combined product + tech role). Ask: "How do you balance product thinking with technical decisions when you're one person?" Write "The CPTO playbook" — for solo founders and small teams where one person wears both hats. That's literally your situation.
12. Content Creators
87. Justin Garrison — Podcaster, Fork Around and Find Out
Infrastructure podcast with a great name. Idea: Pitch yourself as a guest: "I analyzed 85 markets using AI to find what to build next, then started building in public." The intersection of AI-assisted research + indie making + Go development is a unique story. FAFO's audience (infra nerds) would love it.
88. Joachim Mouhamad — Créateur de contenu
French tech content creator. Idea: Propose a video collab: "Build a SaaS in 24 hours using only AI." You pair-program live, he films and edits. Raw, real, no faking. The "will it work?" tension is content gold. Publish on both channels.
89. Raphaël Parodi — Créateur de contenu Web, Musical coding
Coding + music content. Idea: "Musical coding" is a fascinating niche. Propose: "Build a web synthesizer in Go + WebAssembly." You handle the Go/Wasm backend, he handles the musical/creative direction. Unique crossover content that neither of you could make alone.
90. Thomas Collart — Content Creator, Comment Coder
French coding tutorial channel. Idea: Offer to co-create a "Go for web developers" series on his channel. He has the audience (French devs learning to code), you have the Go expertise. A structured 5-episode series: "From zero to deployed Go API." You both grow your audiences.
91. Gregor Ojstersek — Founder & Author, Engineering Leadership
Engineering leadership newsletter. Idea: Guest post exchange. You write "What I learned about engineering from analyzing 85 markets" for his newsletter. He writes about engineering leadership lessons for your audience. Cross-pollination of two different but adjacent audiences.
13. Big Tech
92. Rafiu Jaman Mollah — Tech Lead, Speakeasy Experiences @ Google
Idea: "Speakeasy" at Google suggests API developer experience tooling. Ask about Google's internal approach to API design. Write "What Google's API guidelines teach indie developers." Internal Google knowledge, translated for the rest of us. Massive SEO potential.
93. Santino Medina — TPM, Office of Strategy & Incubation @ Google
Google's internal incubation team. Idea: Ask: "How does Google decide which internal projects to kill vs. spin out?" The "Google graveyard" is famous but nobody has the inside story on how decisions are made. Even a hint at the framework would make for killer content.
94. Youssef Ridene — Senior Software Development Manager, AWS
Idea: Ask about building services at AWS scale. Specifically: "What architectural patterns work at AWS scale but are overkill for startups, and what patterns scale surprisingly well from day 1?" Write "The AWS engineer's guide to building a startup." Contrarian, practical, shareable.
95. Ankur Rana — Senior Software Engineer, Microsoft
Idea: Ask about the developer tooling Microsoft uses internally. "What tools do Microsoft engineers use that aren't public products?" Internal tool discovery often leads to startup ideas. Notion started this way, Slack started this way.
Idea: Two AWS connections. Propose a blog post: "Deploying Go applications on AWS — the honest guide." Not the marketing version, but what an actual AWS engineer would recommend. Which services are worth the complexity, which are traps. AWS engineers rarely write candid public content — this would be rare.
14. LatAm
97. Lucas Shoobridge — Software Technical Leader, Mercado Libre
Mercado Libre is Latin America's Amazon (33 connections). Idea: Ask about building for Latin American markets from a technical perspective. Payment systems, logistics APIs, localization challenges. Write "Building for LatAm: a European developer's guide." There's almost zero content about this from a European perspective. Opens a whole market.
98. Mariana De Mattia — UX/UI Designer, Mercado Libre
Idea: Ask about designing for markets with lower bandwidth, older devices, and different cultural expectations. "UX lessons from designing for 300 million Latin Americans." The design constraints of emerging markets produce insights that apply everywhere.
99. Nelson Schonfeld — Golang Software Engineer, Mercado Libre
Go at MercadoLibre. Idea: MercadoLibre is one of the biggest Go shops in the world. Co-write "How Mercado Libre runs Go at massive scale" — covering their architecture, team structure, and hiring process. This is a story the global Go community would love but doesn't have access to.
100. Marlon Pérez — Golang Developer, Globant
Globant is a major LatAm tech consultancy. Idea: Ask about the Go consulting market in Latin America. Is there demand? What rates? Could you take on remote Go consulting gigs for LatAm companies from France? Timezone overlap is decent (6-hour difference), rates would be competitive, and you'd diversify your income geographically.