Quick context, since this comes out of the blue: we haven't met, there's no role posted, and I'm not applying to anything. I'm Ridha — a founder who builds revenue and growth from zero. I'm writing because I think Slite is about to need exactly that. The whole case is on this page, so you can read it on your own time — no call, no meeting.
Here's the argument in one line: you brought in a fractional CRO to steady revenue — smart. But in 2025 you went multi-product with Super, a new product in a new market. That's not a steadying job, it's a building one — and that's what I'd come in to do.
The best time to bring in a builder is before you write the job description.
Slite is at the inflection every PLG company hits once: the core product works, and there's a second, bigger bet — Super — that needs its own go-to-market from zero. AI search is a real category now, the intent is exploding, and nobody owns the SMB-and-mid-market distribution for it yet.
That's the exact problem I'm built for. I took an enterprise SaaS company upmarket when it had no upmarket motion, then left to found my own product and took it 0 → €100K ARR in nine weeks — writing the code, the landing pages, the SEO layer and the funnel myself. I don't advise on the motion. I build it, and I carry the number while I do.
Not a knock on the fractional model — it's the right call for a steady core. But launching Super is a different problem, and it's worth being precise about the difference.
The fractional model
Great for interim strategy
A builder-operator, full-time
Built for 0 → 1
You likely want both, in sequence. I'm making the case for the second one — and for starting it now, while Super is young.
The way Slite marks a doc: verified, or honestly not yet.
Founded a product and took it 0 → €100K ARR in nine weeks. Stood up an enterprise upmarket motion from nothing. New motions are the work, not the exception.
To me PLG is product clarity — the shortest path to a first "aha." I've built the signup→activation funnel and instrument it to the step. Your first verified answer is that aha.
Solo: an SEO/GEO pipeline (prerender, JSON-LD, sitemaps), landing pages, an outbound agent, and a console tracking the funnel. I ship the stack, not a brief.
My product is a multi-model AI engine with agents and tool-calling. I understand what Super is really selling — trustworthy answers on top of messy company knowledge.
15 years in B2B SaaS revenue — €200M+ managed, €20M+ closed myself. A builder who also closes, so the growth ideas stay honest about money.
You're reading the proof. This case is a document, not a calendar invite — the way Slite has worked since day one.
My SaaS depth is revenue-tech, not docs. I'd ramp on the category fast — but I'd rather flag it than oversell it. The growth muscle transfers; the domain I'll learn in weeks.
A hypothesis to argue about, not a finished plan. Three bets I'd open with:
Make activation the growth team
Self-serve is the top of funnel. I'd instrument signup → first connected tool → first verified answer as the activation spine, cut every step that doesn't earn its place, and turn the moment "Super answered something my search couldn't" into the share that pulls the rest of the team in.
Own the AI-search shift with Super
"AI search across all our tools" is a category being formed right now — high intent, no clear owner. I'd claim it with narrative + programmatic/comparison SEO + a connect-your-tools free wedge, and land Super into the existing Slite base before chasing net-new.
Land-and-expand, not land-and-pray
Knowledge tools live or die on seat expansion. I'd build the admin→team virality loop, wire sales-assist onto only the accounts that light up, and make NRR a number we design for, not one we read after the quarter.
Remote-first means the motion has to be legible in writing and run without me in the room. That's a constraint I'd design for from day one — it's how I already work.
Same story, printable — a one-page CV and a founder-to-founder letter.
Cover letter · for ChristophePDF · 1 pageFounder to founder — the raw version, in writing.
Open Ridha Mami · one-page CVPDF · 1 pageThe numbers, the builds, and how I work.
OpenAsync is fine — reply whenever it suits. If it's easier to read than to meet, that's rather the point.
No role is open, so there's nothing to apply to — which is why I built the argument instead of sending a résumé into a void. If the timing's wrong, a one-line "not now" is a gift and I'll take it well. If any of this landed, the fastest next step is a reply, in writing, on your schedule.
Let's build it →