Discussion about this post

User's avatar
Robin Davids's avatar

Would you say that your main arguments are more applicable to B2B SaaS vs B2C?

Various of your outlined concerns don't directly apply to a consumer.

From a customer perspective, a perfect software world would be open protocols everywhere. Everyone could vibe code their way to the perfectly personalized home screen.

Instead of relying on different algos used by different social media platforms it would be possible to aggregate from all of them and have your own personalized prompt-based algorithm. You won't need to check Instagram itself anymore. You won't need to worry if your friend is using text messages, whatsapp, telegram or signal. You just express an intent to reply to them.

Obviously, every big software player switching to an open protocol approach is unrealistic.

However, I believe that AI computer use advancements (incl. openclaw, claude's recent announcements etc) make it easier to circumvent this. Therefore, we now have a way easier time accessing these types of applications and building our own scaffolding as consumers.

Our willingness to accept small failures or mistakes is considerably higher than in a B2B setting.

Computer use especially breaks down artificial moats (such as a lack of API, insane API pricing or considerable usage restrictions).

I would love to hear your thoughts about this!

Beresol's avatar

Great framework. We're living it. I'm building Brubru, a vertical AI tool for EU public affairs professionals in Brussels. Your article reads like a mirror of our competitive thesis, so I wanted to share a practitioner's perspective: https://brubru.beresol.eu

Process power is real and compounding. I built an Akoma Ntoso legislative amendment editor, vote prediction engine, and compliance analyser: none of which exist outside EU institutions. The hard part was never the AI model. It was encoding how a specific EP committee structures its amendment review, how Council QMV arithmetic works, how trilogue dynamics play out. Better models make that orchestration layer more capable, not less relevant. That's your Harvey point exactly.

Cornered resources matter more than people think. We run 15+ scrapers against EU institutional sources (OEIL, EUR-Lex, EP committees, Council calendar, Commission document register). Each one took weeks to build and has bizarre edge cases: the Commission's document API has been returning 503 errors for months, so we built a fallback pipeline through EUR-Lex RSS. A vibe-coded competitor would need to independently rediscover every one of these quirks.

On switching costs being the weakest moat: agreed, and it's the thing that keeps us up at night. Our response is to embed deeper into daily workflows: notification engines that pull users back daily, dossier workspaces that accumulate institutional context over time, team collaboration layers. Behavioural switching costs instead of technical lock-in. And the counterpositioning point resonates strongly. Our main competitor sells per-seat monitoring dashboards. We sell modular action tools (draft this amendment, generate this briefing, predict this vote) starting at 29/month. They can't easily match that without cannibalising their own seat-based economics.

Classic Blockbuster/Netflix: one thing I'd add to your thesis is that in regulated verticals like EU policy, the data pipeline itself is a moat that AI makes harder, not easier, to replicate. Foundation models know about EU law in general; but they don't know that the OEIL XML feed has a 30-day server-side limit, or that Commission College meetings shift between Strasbourg Tuesdays and Brussels Wednesdays. That kind of domain-specific integration work doesn't get cheaper with better models.

The world is absolutely still short software. Most EU public affairs teams still track legislation in Excel spreadsheets and share amendments by email. The market isn't being disrupted, it's being created.

21 more comments...

No posts

Ready for more?