Matt El mouktafi

CTO & cofondateur de Senthor.io.

L’IA change la manière dont le web se lit — mais les créateurs perdent le contrôle.
Senthor permet aux éditeurs de voir, comprendre et décider ce que les LLMs lisent de leur contenu.

Ancien CTO chez Lempire (valorisation 150M$) et fondateur de 20+ SaaS, je me consacre aujourd’hui à rendre le web plus équitable et transparent face aux IA.

⚡ Prêt à reprendre le contrôle (et la valeur) de ton trafic ? Essaye Senthor.io

Lead Software Engineer

Matt mouktafi

Il y a un truc qui me fait très peur avec l'IA !


Depuis que ça se développe, je vois plein de devs expliquer que c'est en train de transformer notre rôle.

On écrit moins de code, à la place :
→ on pense l'architecture,
→ on définit les bonnes pratiques,
→ on se concentre sur les besoins métiers  ...

Du coup, vraie question, vous pensiez que c'était quoi votre job avant ?

Contrôlez et monétisez l’accès des IA à votre contenu | CTO @ senthor.io

Le fichier llms.txt, utile ?
On tranche le débat 👇

Avec Senthor, on analyse des millions de requêtes depuis septembre.

Résultats :
→ + 10M de requêtes formellement identifiées comme venant d'IA
→ 104 requêtes sur le fichier llms.txt
→ 41 venant d'humains ou de bots certifiés non IA
→ 0 provenant d'IA identifiable

Les chiffres parlent d'eux-mêmes.
Aujourd'hui, le llms.txt est une légende urbaine 😉

Il y a quelques mois, nous lancions Senthor avec une mission claire : vous redonner le contrôle sur votre trafic IA.

À l'époque, c'était un pari. Aujourd'hui, c'est devenu une nécessité pour des centaines de sites.

Depuis le premier jour, on construit avec vous.

Grâce à vos retours, Senthor n'est plus seulement un outil de monitoring, c'est devenu une tour de contrôle complète pour votre data :
- Breakdown précis entre trafic Bot et IA.
- Qui scrappe quoi ? Sur quelle route ? Avec quel type de contenu ?
- Autorisez, bloquez, monétisez le traffic non humain
- Comprendre enfin la part du SEO vs GEO vs Direct.
- Identification immédiate des violations de votre Robots.txt ...

Depuis, notre produit a mûri, et notre vision aussi. Pour accompagner cette croissance et continuer d'innover à la vitesse de l'IA, nous faisons évoluer notre modèle de prix.

Nous avons conçu cette nouvelle grille pour qu'elle soit juste : Que vous soyez un blog passionné ou une plateforme média à fort volume, il y a désormais un plan Senthor qui colle à votre réalité et à votre trafic.

L'objectif reste le même : que vous ne subissiez plus le scraping, mais que vous le pilotiez.

Découvrez nos nouveaux plans ici : https://lnkd.in/dvzNYh-U

Un immense merci à ceux qui nous font confiance depuis le début de l'aventure. On ne fait que commencer !

No alternative text description for this image

Robin Labrot

The decks you need to build successful (and cool) products ❘ Founder @ListenUp!

Most tools cover ~80% of what your team needs.
That’s because SaaS vendors will always optimize for the average Joe.

(I know, I’ve been on the other side of the fence, building products that reached +$25M ARR)

Nothing wrong with that. But your business runs on specifics.

So I’m building something to close that gap.

SparkUp! → a no-code way to bring AI and automation directly into the tools your team already uses.

It lets Sales & Support Ops add custom buttons or mini-UIs inside any SaaS app to trigger their Zapier, Make, n8n, or Relay workflows right where work happens.

The result: your team boosts productivity by triggering the right actions at the right time, inside their existing habits.

Here on LinkedIn, I share how I’m duct-taping the internet one Spark at a time to help you make your stack smarter, simplify tool chaos, and bridge the gap between what your tools do and what your team actually needs.

I’m doing all this as a bootstrapped founder, sharing with radical transparency what the journey is really like.


Want to get in touch?
→ DM me here
→ or email robin@sparkup.design

Head Of Product

I closed SparkUp!'s first customer… while doing grocery shopping 🛒📱

No computer
Lots of background noise
A VERY jittery connection

Just me, my phone, and a strong desire to make it work

Ridiculous.. but it worked 😅

→ The prospect asked for an onboarding call out of nowhere
→ I was out, but said yes anyway (no “perfect setup” excuse)
→ Did the whole thing on my phone while they shared their screen
→ Answered questions, built with them live, closed!

What we built together in ~5 minutes:
→ A one-click button inside Affinity.co CRM to push a contact straight into a lemlist campaign

Why they were happy:
→ Not because the demo was polished
→ But because we showed up and got them unstuck
→ Pure determination to help them get set up, fast

Early-stage startuping looks like this.. doing things that don’t scale

Lesson: as my Leadbay (YC F25) friends Ludovic & Milan love to say: 
Always be selling!

the ‘missing button’ guy | build internal features, not internal tools ❘ ex-lemlist

It felt like a punch to the gut when I realized this:

We weren’t “almost there” 
We were just deep in sunk cost fallacy, 2 years of pushing a product that was too hard to sell fully bootstrapped

I learned that building ListenUp!

We shipped a legit product:

→ AI tool before ChatGPT dropped
→ 20+ paying companies
→ 100+ demos
→ 10+ integrations (support tools, CRMs… even a meeting recorder)

And still… the pattern was brutal:

→ Bootstrapped + sales-led + complex setup = incompatible (every deal was a mini project)

→ Cross-department tools are secretly enterprise software (you’re selling a change in habits)

→ Integration-dependent products don’t have a roadmap. They have a “one more integration” trap

→ Credibility is a feature. Bigger accounts wanted us… until they asked how big the team was (only me and Thomas, in our living rooms!)


So I’m taking a new bet with my 2nd SaaS attempt:

There are ~112 SaaS apps per company
Most tools cover ~80% of what your team needs

That’s because SaaS vendors will always optimize for the average Joe
(I know, I’ve been on the other side of the fence)

But your business runs on specifics

I’m attempting to close that gap with SparkUp! → let Ops teams add missing actions directly inside the tools their team already uses, in no-code

But I do have my doubts...

→ Broad problem… but is it urgent enough for people to actually buy?
→ No-code in the AI era… is that a risky bet?
→ Can you bootstrap an horizontal tool, or are we making the same mistake twice?
→ Will teams actually have the time (and patience) to build internal features for their own tools?
→ Or are we doing the classic founder move: building cool tech… looking for a market?

So many unknowns, but that’s what makes it fun! (and mildly terrifying)

I'll share the progress with radical transparency

By the way, what’s the “one missing action” you wish your main tool had today?

taplio

The Battle

Matt mouktafi

Robin Labrot

Followers

Posts

Engagements

Likes

Performance ScoreMatt mouktafi's LinkedIn Performance

Performance ScoreRobin Labrot's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Matt mouktafi

Robin Labrot

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Matt mouktafi's LinkedIn Performance

Performance ScoreRobin Labrot's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreMatt mouktafi's LinkedIn Performance