CEO at Slite (YC18) | We build the first knowledge base on autopilot, in remote since 2016!

I'm the founder of Slite & Super (YCW18) 👉 Super.work 

Super.work turn all your company data into answers & AI agents for your whole team.

It comes with the recipes and tools for your team to get instant benefit from AI at work

Slite is your team dead simple yet crazy powerful knowledge base, since 2017 🔥

I'm fortunate to lead a diverse team of exceptional individuals spread across 10+ countries 🇮🇳 🇬🇷🇱🇹 🇦🇷 🇬🇧 🇳🇱 🇫🇷 🇳🇴 🇺🇸 🇪🇸 🇩🇪 🇨🇦 🇵🇹 . Our journey includes going through YC W18 batch, raising $15M+ in funding from top-tier investors like Spark Capital and Index Ventures, and serving tens of thousands of teams monthly.

Christophe Pasquier

This is my first multi-agentic workflow.
Of course, it makes the job easier but more so, it feels like the future.

Here's the setup.
I connected Claude Code to two MCPs.
1. Sanity, which is our CMS
2. Super, which holds our product knowledge, positioning, and messaging.

And here's what actually happens.
1. I ask Claude Code to QA a content page.
2. It pulls the full page from Sanity, every field, metadata, structure, all of it.
3. It calls Super as a fact-checking agent and cross-references the page against our actual product knowledge base.
4. It comes back with a plain language review of what's off, what's outdated, what's missing.
5. It pushes the approved fixes directly back to Sanity through the MCP.

The whole loop runs without me opening the CMS once.

Claude Code is an incredible general agent. 
It can orchestrate, plan, read files, execute tasks. But it's not purpose-built for anything. It doesn't know your product, your positioning, your company's source of truth.

When you pair a general orchestration agent with a purpose-built knowledge agent, the quality of output changes completely. The orchestrator handles the workflow. The specialist handles the judgment.

That's the pattern I think we'll see everywhere. Not one super-agent that does it all, but multiple agents that are good at different things, working together.

CEO Slite & Super (W18) | Most accurate search & workflows on team data

A semi-viral tweet was praising Linear's Slack agent last week
Jori Lallo quote-tweeted it with one line that's been stuck in my head since.
"Linear agent is soon just Linear."

He went on to explain that the agent will eventually have full feature parity with the UI. Everything you can do in the product, the agent can do too.

If you sit with that for a second, it reframes what a software product even is.

The UI becomes one client among many. Slack is a client. Claude Code is a client. A script someone wrote on a Sunday afternoon is a client. They all talk to the same system underneath, and they're all equally valid ways to use the product.

Most SaaS companies were built the other way around. The interface was the product, the API was an afterthought you shipped because enterprise customers kept asking. Jori is describing a world where that's completely inverted, where the system of record is the product and every interface, including the one with pixels, is just a client.

We're building toward the same thing at Slite. We shipped our MCP recently and we're still expanding it, exposing more endpoints, making more of the product fully programmable through agents. The vision is to turn Slite into a collaborative Obsidian for company knowledge, where agents search, update, reorganize, and verify docs just as naturally as a teammate would.

All SaaS products built on data as a moat are an API now, whether they like it or not.

Folks! Wanna catch up irl in Berlin next week?
I'm speaking at MCP Connect on March 3
And I'm genuinely excited for 2 reasons.

It’s college friends organising this, the founders behind Alpic, they’re moving fast on being the reference platform for anyone building MCPs and apps in the GenAI majors and it’s a blast to share stage with them. 

And ofc - Viktor Zamaruiev, Director of Engineering at Superhuman, is also speaking!

He's giving a talk on how they're thinking about AI at Superhuman. I've been a Superhuman user for years, and with their recent moves joining Grammarly and reshaping a new kind of AI productivity suite I’m extremely curious to see how they approach the connectors topic. 

I'll be talking about progressive tool calling in Super, basically what we've been figuring out at Slite and Super while building agentic RAG for company knowledge.

I'd love to see more folks who are building in this space there.
Register here: https://luma.com/olsyxsvn

Company context is the last unsolved layer in the AI stack.
The model layer is mature. Frontier reasoning is a commodity.
And that's why, today, we're announcing Super's MCP

The moment you try to deploy that reasoning inside a real company, you hit a wall that has nothing to do with model capability but everything with context.
Models need your company's entire context to do useful work.

Every team that has tried to solve this pain.
Teams have tried individual tool connections with MCP and get a fragile stack that returns incomplete results, or more annoyingly so, times out.
Or assembling context by hand and created an expensive copy-paste workflow that defeats the purpose of having AI in the first place.

Today we're launching the accurate and exhaustive company search agent you can bring in all your AI tools to truly make them work.

Meet Super MCP.
It gives your AI a dedicated context agent that knows everything your company knows across Slack, Drive, Linear, Notion, Jira, GitHub, and twenty other tools.
→ It answers LLM's each question with real company data
→ It doesn't time out on MCP calls
→ It keeps your context clean
→ It works with Claude, ChatGPT, and Cursor out of the box.

We benchmarked it against real company queries before launching.
Claude with individual MCPs gives 24% perfect answers
Claude with the Super MCP gives 80%+ perfect answers while being 2.6x faster.

Same model. The only variable was the retrieval layer underneath.
Super MCP is live today for all Super users.

Read more about it here: https://www.super.work/mcp

And if you're trying to figure out the context layer for your team, happy to help.

In 2022 we published our compensation formula publicly.
We had 32 people, 25 cities, 9 countries.
4 years later, we removed a big part. Here's what we learned.

1/ Cost of life as the main criteria for our benchmark was idealistic and wrong
Our original model used a cost-of-living as the main index, which essentially answered the question "what does rent cost in Lisbon?".

While it can feel logical to aim for compensation to match the same level of life on multiple locations, it definitely does not feel fair to all, and brought hundreds of issues when negotiating salaries for existing and new teammates.

We switched from looking at cost of living to simply basing our numbers on a benchmark of actual salary data from over 1,000 venture-backed SaaS companies in our locations.

The question became "what do top companies pay a senior engineer in Portugal?" and setting a competitive number from there. Completely different framing.

2/ We kept on simplifying the structure and making it more transparent.
A comp model only works if everyone using it can explain it in 60 seconds. At first, ours couldn't pass that test.

The best way for simplicity is by exposing not only the formula but also the results. We ended up giving our team team a public datalooker sheet with all the levels/countries/roles and associated comp accessible in a few clicks.

3/ We raised our benchmark over and over as we grew, got profitable, kept on growing.
A defining moment came in 2024 when Kamsa data showed that salaries had dropped across the board.

We chose to keep our 2022 benchmarks anyway. Market data should be a guide for doing right by our people, not an excuse to quietly cut costs when the numbers give us permission to.

The rest of our calculator remained, and most of our principles still apply (go check the original piece!)

I'm sharing this because comp deserves more thoughtful attention in startups than it usually gets.

Young founders either overpay early and create expectations they can't sustain, or underpay and lose the people who built the foundation.

Both paths lead to hostile team dynamics that are incredibly hard to undo once they set in.

Youtube can teach you to implement RAG over a weekend.
So why'd we spend 2 years?

RAG is the to-do app for the AI era. 
Every developer will build one as a pet project to learn about LLM implementation. 

There's plenty of free Youtube tutorials, wire up an open source vector store, and get answers.

But that's level 1, it only works for predictable questions.

The moment your team has real questions, and knowledge scattered across Intercom, Notion, Slack, your CRM, and 6 other tools - a single retrieval method breaks down fast.

What we've spent 2 years building at Super is an company search agents, orchestrating dozens of tools and sources, adapting to what it finds and able to search in multiple different ways.

That means:
→ An LLM query planner that decomposes your question, prepare sa first series of steps, selects filters before a single retrieval even fires
→ Multiple retrieval engines running in parallel or in sequence — semantic, keyword, SQL, MCP, and hybrid
→ Permission filtering at runtime so people only see what they're allowed to see
→ Ranking, reranking, and hallucination prevention baked in — not bolted on
→ Every answer cited, verified, and source-linked

Could you build this on n8n? No. The gap between a RAG pipeline that returns chunks and a retrieval agent that thinks about your question, searches intelligently across every tool your team uses, and verifies its own answer - that gap is the product.

We didn't build a wrapper around embeddings. We built the most thoughtful multi-tool retrieval agent we could. And we keep on adding to it.

Your customers can feel the gap between your landing page and your support calls.
That gap is your actual brand.

I don't think SaaS has reached a consensus on what brand actually means.
Everyone uses the word. Very few people mean the same thing by it. Is it your visual identity? Your positioning? Your vibe? The feeling someone gets after using your product for a month?

After 10 years of building companies, here's the working theory I've landed on. 

Brand is the extrapolation of how you actually treat your team, your customers, and what you care about when nobody's evaluating you.

1/ A good brand is downstream of your internal culture and values
At Super and Slite, I've noticed the moments where our brand felt strongest where our tone, our design, our content just happened to match how we actually behave internally.
When your team is warm, playful, and obsessively helpful behind the scenes, and that same energy shows up in your onboarding, your docs, your error messages = something clicks.
People trust it because it's consistent in a way that's hard to fake.

2/ A good brand can't be retrofitted
Where I've seen it go wrong, including in my own work, is when you start from the market. You look at competitors, pick a lane, then backfill a personality.
The illustrations look friendly. The copy sounds human.
But then a customer hops on a call and the energy is completely different.
That gap is hard to recover from.

3/ How I keep operating
Name what's actually true about your company first. How do people talk to each other? What do you default to when things get stressful? Then take that vibe and push it into every touchpoint.

It sounds obvious written down. In practice, almost nobody does it this way because it requires admitting what you actually are before deciding what you want to be.

Still figuring this out honestly. But 10 years in, this framing hasn't let me down yet.

Our median time to close bugs dropped 60% this year.
The obvious assumption is that AI coding tools did it. 
But the actual reason is a bit more subtle, and less exciting than that.

We spent 6 months last year deleting, cleaning and refactoring.
We cut 3 features that had been creating edge cases for years.
We converted everything to TypeScript, and migrated off deprecated BrowserView entirely.
We moved from ESLint to Biome and got our linting time for the entire codebase down from what was effectively infinity to 7 seconds.
We reshaped entire core parts of our codebase.

Just cleanup. That work is what made AI truly effective afterward, and I feel every day that a mature codebase with this level of quality is the unfair advantage startups will die for in the future.

When your codebase is simple, bugs are easier to find, easier to reproduce, and easier to fix, by human and agents alike.

AI coding tools amplify that simplicity because they're working with a clean surface instead of fighting through layers of dead code and undocumented edge cases.

The compounding effect showed up faster than we expected. One of our engineers spent three weeks refactoring Super's core engine with zero visible product changes. After that architectural work, the team added Bigquery as a data source in 4 days, Salesforce in 3, and the next two sources took 2 days each. That refactor felt slow in March. By November it had saved us 8 weeks of work.

PRs merged per contributor went from around 30 per quarter to 70 last year, more than 2x output with the same team and headcount.

The reverse is also worth thinking about. If your foundation is messy, AI tools help you create bugs faster and ship technical debt at a pace that would have been impossible manually. Speed is a multiplier, and it multiplies whatever is already underneath.

Most teams I talk to right now are shipping 2-3x faster with AI coding tools, and that's genuinely exciting.

But I think the conversation about what to do before you go fast is getting skipped entirely. The 6 months we spent cleaning up felt unproductive at the time, but that unglamorous work is what actually moved our metrics.

"The important thing is not to stop questioning" – Albert Einstein

Mehdi Boudoukhane

Belgian founders have a funny trait.

They’re almost suspiciously humble. Low ego, cool to hang out with, and hard to impress.

Pair that with huge ambition and things get dangerous 😈

That’s the vibe I got spending time with Basile and Gauthier, founders of Enobase (HX26), who just joined Hexa Sprint. I’m excited to be an advisor alongside the one and only Thibaud 💪

They’re taking a swing at something big: what ERP looks like in the agent era.

For decades, companies have had to adapt themselves to systems like SAP or Odoo. You pick the closest template, then spend months configuring it, integrating it, and teaching your team how to live inside its constraints.

Enobase flips that logic.

Instead of rigid software, they’re building a platform where you can vibe-configure your own workspace using stable building blocks underneath.

Describe how your business works, shape the workflows, and just let the system assemble itself around you.

Software that folds to you.

In the agent era, companies adapting to their ERP feels exactly as wrong as it sounds 🙄

PS: Could have posted the clean professional shot but the beer pic tells the real story 🍻

No alternative text description for this image

Will vibe coding replace PM tooling?

Short answer: no. But it will absolutely reshape how it’s built.

I’ve been in product for 10+ years. PMs have always built their own operating systems – first with spreadsheets, then with Notion, Airtable, automations. The instinct isn’t new.

Seven years ago, I built a prototype for myself with Notion + Zapier. It worked beautifully. I thought I’d turn it into a product in a few months.

Six years later, I was still learning how hard it is to transform a clever personal workflow into real, company-grade software.

LLMs and vibe coding don’t eliminate enterprise tools. They compress time-to-aha moment.  They let individuals experience the future before the product exists. They surface new UX patterns – especially when you combine structured frontends with LLM-native interactions and MCP-style integrations.

That’s real. Anyone building software should pay attention.

But a system that works for one PM is not the same as infrastructure that survives permissions, audit trails, security reviews, onboarding, org changes, and scale.

If you look at YC over the last decade, the archetype hasn’t changed. Yesterday: “Airtable for X.” Today: “AI agent for Y.”

Different primitives, but same ambition.

Some will win. Most will discover that durability, trust, and distribution are the real moat.

So no – PM tooling isn’t being replaced. It’s being accelerated. And that’s a much more interesting story.

I had a bit of a brain-fuck moment yesterday.

I was brainstorming in Slack with our designers Vlad and Adrien. Messy thread, half ideas, ambiguous product discussion – the usual design chaos.

We wondered what would happen if we dropped the thread into Gemini and asked it to turn the conversation into a design spec.

Adri copied the spec into Figma Make.

A few seconds later we were staring at a low-fi prototype that made the whole discussion suddenly click. The messy conversation had turned into a visual summary of the design problems we were wrestling with.

Vlad joked: “ok… we’re going to lose our jobs.”

Everyone laughed.

But you know the kind of joke where there’s a bit of anxiety underneath.

A lot of people feel that right now, but I think the fear is pointing in the wrong direction.

AI is removing the slow step where ideas have to be translated into specs and rough prototypes just to see if they work.

Now that step takes minutes, which means designers can test far more ideas before anything ships – and that changes the game.

If everyone can generate decent interfaces, decent interfaces stop being valuable.

What matters more is the stuff AI still struggles with: taste, judgment, micro-interactions, product identity – the details that make software feel right to humans.

Photography didn’t kill painting. It killed average portrait painters and pushed artists to reinvent what painting could be.

AI will do the same to design.

Great design was never about producing one idea carefully. It’s about exploring many possibilities, recognizing the one that actually works, and refining it until it feels right.

AI will make the exploration phase dramatically faster.

Which means the real craft becomes the discipline to try a hundred ideas – and still ship one thing that’s actually great.

“Full-stack product builders” sound exciting. They might also be a trap.

The narrative is spreading fast: AI blurs the lines between PMs, designers, and engineers. Everyone becomes a builder.

PMs code.
Designers ship features.
Engineers do everything.

It sounds incredibly efficient. But we’ve seen this movie before.

When the JavaScript ecosystem exploded, the industry fell in love with the “full-stack engineer.” One person building backend and frontend, shipping at crazy speed.

It worked great for prototypes. It also produced a lot of fragile systems.

Because full-stack narratives quietly push teams toward solo builders. And solo builders rarely scale. Add users, add engineers, add complexity – and suddenly the architecture only exists in one person’s head.

Great software doesn’t emerge from blurred roles. It emerges from teams with depth.

That’s why I still believe in T-shaped teams, not collapsed roles.

In great teams, people understand more than what they own.

A designer who can code.
A frontend engineer who understands backend systems.
A backend engineer who talks to customers.
A PM who can prototype workflows and design MCP tools.

That overlap makes collaboration stronger. But the key difference is ownership.

The designer owns the experience.
The frontend engineer owns the interface.
The backend engineer owns the system.
The PM owns the semantics.

Blur the roles too much and you get solo builders.

Keep the depth and you get systems that survive scale.

AI will expand everyone’s range. But great software will still be built by teams, not solo builders with better tools.

taplio

The Battle

Christophe Pasquier

Mehdi Boudoukhane

Followers

Posts

Engagements

Likes

Performance ScoreChristophe Pasquier's LinkedIn Performance

Performance ScoreMehdi Boudoukhane's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Christophe Pasquier

Mehdi Boudoukhane

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);}Christophe Pasquier's LinkedIn Performance

Performance ScoreMehdi Boudoukhane's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreChristophe Pasquier's LinkedIn Performance