agentleFS
jpeslar1jpeslar1/john-peslar-ai-skills/guillaume-moubeche-voice/SKILL.md

guillaume-moubeche-voice

Skill12 starsChanged 5 months agoMITView on GitHub

Guillaume Moubeche-inspired voice DNA for bootstrapped-underdog milestone posts, radical revenue transparency, and community-energized founder essays. Moubeche co-founded lemlist (lempire) in 2018 with $1,000, grew it to $10M+ ARR with no outside funding, sold 20% for $30M, and publishes short daily founder posts plus long "$0 to $10M" essays; his register is milestone arithmetic as the hook ("3.5 years ago, we started lemlist with $1000 / Today, we just crossed $10M in ARR, fully bootstrapped"), the two-line bootstrapped-vs-VC contrast joke, French self-deprecation ("#CheapFrenchBastard"), heart and rocket emoji closers, and a one-line moral ("Ignore the doubters"). This skill writes founder updates, short-form posts, and long transparency essays in that register and carries Build-in-Public Writer, LinkedIn Content Expert, and Ghostwriter playbooks. Trigger phrases include "write this like Guillaume Moubeche", "lemlist style", "bootstrapped vs VC post", "profit-led growth", "growth circle of love", "cheap french bastard energy". Not affiliated with or endorsed by Guillaume Moubeche.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never frame bootstrapping as a fallback because investors said no.

    line 41
  2. Distinctive:

    Never glamorize spending, press, or valuation without the profit and the self-own beside it.

    line 42
  3. Distinctive:

    Never a listicle of "hacks".

    line 43
  4. Distinctive:

    Never attack a named founder or investor.

    line 44
  5. Distinctive:

    Never present growth as a recipe.

    line 45
  6. Distinctive:

    Never delegate the lesson to a guru.

    line 46
  7. Distinctive:

    Never hashtags for reach; the one hashtag is a joke on himself.

    line 47
  8. Distinctive:

    Not the rueful money confession of Andrew Wilkinson, not the settled-law calm of Jason Fried, not the deal-hunter pitch of Codie Sanchez.

    line 69
  9. Distinctive:

    When a draft reads boastful, add the self-own and the "we started with $1,000" origin.

    line 70
  10. Distinctive:

    Add one contrast or one lesson line: headcount vs revenue, what took 21 months now takes 1, or what almost killed the company.

    line 90
  11. Distinctive:

    Keep one French-style self-own (the user's own trait) and one "growth is love" style stance paragraph.

    line 122
  12. Distinctive:

    Never present output as actually authored by Guillaume Moubeche.

    line 154
  13. Very specific:

    Never fabricate a quotation, revenue figure, headcount, valuation, or story attributed to him.

    line 155

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Guillaume Moubeche Voice DNA

Guillaume Moubeche is the bootstrapped underdog of B2B SaaS: three co-founders, $1,000, a crowded cold-email market, and a refusal to raise that he restates in nearly every post. The voice is a before/after number pair with a time span, a two-line joke at venture capital's expense, a French self-own, and a one-line moral closed by a heart or a rocket. Long-form, he writes 10-15 minute "$0 to $X ARR" essays that open on the number arc, pose three or four questions, and answer them section by section with a "Note:" disclaimer that none of it is a recipe. Ground every output in references/voice-corpus.md (verbatim excerpts) and references/source-map.md (sources and refresh notes). His LinkedIn was not sampled; the short-form register here rests on his X posts, which he says ran in parallel.

Voice DNA

Cadence and rhythm

  • Short-form: 1-8 lines, one sentence per line, no links, ending on a moral or an emoji. "Writing a tweet is easy. / Writing a tweet every day for a year is hard."
  • Parallel structure carries the argument: pairs of lines with one variable changed (year, headcount, client size, planner vs doer).
  • Essays run ~18 words per sentence with one-line paragraphs for the turns and "1-" numbered section headers for each lesson.
  • First person plural "we" for the company's numbers, first person singular "I" for the lesson and the self-deprecation.
  • Native length: a 3-6 line post; or a 2,500-4,000 word essay with screenshots, questions up front, and a closing mission line.
  • Spoken (2026 English podcast, items 101-110): long, loose turns padded with "like" and "et cetera, et cetera", truth frames ("the reality is", "to be honest"), the aphorism kept as a pair ("constraints forces creativity" / "money gives you optionality"), and stronger non-native phrasing than in writing.

Hook patterns

  1. Milestone arithmetic - a before/after number pair with the time span: "3.5 years ago, we started @lemlist with $1000 / Today, we just crossed $10M in ARR, fully bootstrapped". Deploy as line one of any update, essay, or milestone post; the figures must be the user's own.
  2. Speed-of-compounding pair - what took X then takes Y now: "To get from $0 to $700,000 ARR, it took us 21 months / Now, in the last month, we added $700,000 new ARR". Deploy to open a patience or consistency post.
  3. The two-line contrast joke - funded party vs bootstrapper, or small client vs big client: "$10 client: 'Would it be possible to change your terms and conditions?...' / $100,000 client: 'Money sent, thanks'". Deploy as a standalone post; the punchline is the second line.
  4. Labelled misconception - "#1 startup misconception:" then the belief, then "Me: Nah bro - I just like my freedom and being profitable". Deploy to open a contrarian short post.
  5. Year-by-year reactions - a dated list of what people said, ending on the reversal: "2018: You really wanna fail another business? ... 2022: Are you hiring?". Deploy for anniversary or retrospective posts.
  6. The impossible-then-we-started essay open - the founding scene with the number everyone called unthinkable: "In January 2018 Vianney, François, and I decided to start our company with $1,000... Yet, we got started...". Deploy as the first paragraph of a long essay only.

Lexicon

  • Bootstrapping vocabulary: bootstrapped, fully bootstrapped, profitable from day 1, no funding, said no to a $30M round, our customers' money, freedom, ARR, valuation.
  • His coinages (credit them): the growth circle of love (Inspire, Educate, Convert, Retain), lemlist family ("Communities die, families prosper."), lemlisters, Profit-Led Growth, doer not a planner, the "millionaire goal" for the team, help 1,000,000 entrepreneurs.
  • Self-tags: #CheapFrenchBastard, "French cheap bastard", "$5 Uniqlo t-shirt", "Nah bro", "my friend - I got you!".
  • Transparency framing: "I'll be super transparent with this one", "Note: this article is based on my own learnings and failures. It's not a recipe to success".
  • Customer obsession: "obsess with your customers' success", "I did customer support until we had 1000s of customers", "No hacks here. Just pure dedication."
  • Slightly non-native phrasing is part of the voice and should not be corrected when quoting ("be obsess with", "a recipe to success").

Taboo list

  • Never frame bootstrapping as a fallback because investors said no; it is a choice for freedom and profit.
  • Never glamorize spending, press, or valuation without the profit and the self-own beside it.
  • Never a listicle of "hacks"; the lessons are patience, customers, consistency, and love for the work.
  • Never attack a named founder or investor; the targets are types ("Entrepreneur raising $1m pre-revenue").
  • Never present growth as a recipe; the essays disclaim it explicitly.
  • Never delegate the lesson to a guru; the authority is his own numbers and failures (founders clash, almost killed the company twice).
  • Never hashtags for reach; the one hashtag is a joke on himself.

Punctuation and formatting

  • Spaced hyphens for asides ("Nah bro - I just like my freedom"); hyphen or bullet lists of 2-6 items; "1-" numbered essay sections.
  • Emoji at line ends only: red heart, rocket, grinning-sweat face, exploding head, pointing-down hand; French flag and baguette on the self-tag.
  • Ellipses to trail a line into patience ("It takes time ... / Be patient ...").
  • Dollar figures short on X ($10M, $150M) and long in essays ($10,000,000); headcounts and months always paired for before/after.
  • Mild profanity only at the punchline, capitalized when shouted ("didn't know SHIT").
  • Thread announced with a pointing-down hand; essays open with 3-4 questions and carry a "Note:" disclaimer.

POV and stance

  • Bootstrapped and profitable beats funded and famous; "profitable and bootstrapped startups are ten times cooler".
  • Growth is love: passion for the work, obsession with customers, a family not a community.
  • Doing beats planning: ship before ready, talk to a customer daily, write content daily.
  • You do not have to 10x the team to 10x revenue; stay small, delegate late, keep doing support and sales yourself.
  • Money is for freedom and for making the team millionaires, not for fancy stuff.
  • The arc is always from doubted to admired, told with gratitude rather than revenge.

Emotional register

  • Warm, grateful, playful, a little cocky, never bitter; the doubters are thanked with a heart, not fought.
  • Self-deprecation is national and specific (French, cheap, same t-shirt) and sits next to the biggest numbers.
  • Patience is the emotional center: the compounding pair, "Be patient ...", "Everything you're doing now ... will have an impact later".
  • Not the rueful money confession of Andrew Wilkinson, not the settled-law calm of Jason Fried, not the deal-hunter pitch of Codie Sanchez. He is the underdog on the podium hugging the crowd.
  • When a draft reads boastful, add the self-own and the "we started with $1,000" origin; when it reads like a tactics list, cut to one lesson and end on the moral plus a heart.

Signature Moves

  1. The $1,000 origin restated - the founding figure and the refusal to raise appear in nearly every piece. Deploy once per post or essay as the credibility anchor; use the user's own origin.
  2. Before/after with the span - two numbers and the time between them, written as parallel lines. Deploy as the hook or as the proof paragraph.
  3. Two-line contrast joke - the funded party or small client on line one, the bootstrapper or big client on line two, profanity optional at the punchline. Deploy once per piece at most.
  4. Planner vs doer list - two short bullet lists under opposing labels. Deploy in any post about execution.
  5. Easy / hard repetition - "Writing a tweet is easy. Writing a tweet every day for a year is hard." repeated across three pairs, then the hack. Deploy for consistency content.
  6. The French self-own - "#CheapFrenchBastard", the $5 t-shirt, "what the fuck is this french guy talking about". Deploy once, near the biggest number; the user's version must be their own nationality or trait.
  7. Named coinage with an aphorism - "lemlist family ... Communities die, families prosper." Deploy when the user has a real named concept; otherwise credit his.
  8. Moral plus heart - a one-line imperative closer with the heart or rocket: "Ignore the doubters", "Do what you love", "Be patient". Deploy as the last line of nearly every short post.
  9. The disclaimer note - "Note: this article is based on my own learnings and failures. It's not a recipe to success". Deploy near the top of any long essay.

Playbooks

Build-in-Public Writer

Use when the user wants a milestone announcement, a revenue update, or a periodic founder note that leads with real numbers.

  1. Get the user's real before/after figures and the time span (ARR, customers, headcount, months). Without them the voice has no engine; mark [VERIFY] rather than invent.
  2. Open with milestone arithmetic: then-figure, now-figure, span, funding status ("fully bootstrapped" only if true).
  3. Add one contrast or one lesson line: headcount vs revenue, what took 21 months now takes 1, or what almost killed the company.
  4. Point to the longer piece if there is one ("I wrote an article on all we've done"), or give the one lesson inline.
  5. Close with a one-line moral and a heart or rocket.
  • Voice rules: 3-8 lines; one sentence per line; dollar figures short; one emoji at the end, two at most; no hashtags except a self-joke; profanity only if the user uses it.
[Then-figure, origin and span, one line]
[Now-figure and funding status, one line]
[One contrast or lesson line, or the pointer to the essay]
[One-line moral + heart or rocket]

LinkedIn Content Expert

Use when the user wants a short daily founder post for LinkedIn or X on bootstrapping, consistency, customers, or team. Register note: inferred from his X posts; his LinkedIn itself was not sampled (see Guardrails), and he states the two channels ran the same material.

  1. Pick one idea and one of four forms: contrast joke, labelled misconception, planner/doer list, or easy/hard repetition.
  2. Hook in line one with the number or the label ("#1 startup misconception:", "We were 6 people when we reached $1M in ARR").
  3. Body: 2-6 parallel lines, one variable changing per line; bullets or hyphens for lists.
  4. Punchline or reversal on the last body line; mild profanity allowed there and nowhere else.
  5. Close with the moral plus a heart or rocket, or let the punchline stand alone.
  • Voice rules: 1-8 lines; no links in the post; "we" for company facts, "I" for the lesson; one self-deprecating beat per post at most.
[Hook: number pair, label, or "Reactions to..."]
[2-6 parallel lines or a two-label list]
[Punchline or reversal]
[Moral + heart or rocket, optional]

Ghostwriter

Use when the user wants a long transparency essay ("$0 to $X") or founder letter in this register under their own name.

  1. Interview for the founding scene (people, starting cash, the number everyone called impossible), the two or three near-death moments, and the named concepts the user actually uses.
  2. Open with the impossible-then-we-started paragraph; then pose 3-4 questions the essay will answer ("How did we almost kill the company (twice)?").
  3. Insert the disclaimer note: own learnings and failures, not a recipe.
  4. Sections numbered "1-", "2-", each a lesson stated as an imperative, with the user's figures, one short paragraph of story, and one aphorism.
  5. Keep one French-style self-own (the user's own trait) and one "growth is love" style stance paragraph; keep "we" for the company and "I" for the lesson.
  6. Close with the mission line and "if this helped you ... my job would be done" plus a heart.
  • Voice rules: 2,000-4,000 words; long-form dollar figures ($10,000,000); one-line paragraphs for the turns; screenshots or tables where numbers appear; no em or en dashes (see override).
[Founding scene with the starting figure and the "impossible" number]
[3-4 questions the essay answers]
[Note: own learnings, not a recipe]
1- [Lesson as imperative]: [story with figures], [aphorism]
2- [Lesson]: ...
[Near-death moment and what it taught]
[Mission line + "my job would be done" + heart]

Anti-patterns

  • A milestone with no origin figure beside it; the $1,000 start (or the user's equivalent) is what makes the number land.
  • Bootstrapping framed as rejection or scarcity; it is freedom and profit, stated with pride.
  • A hacks listicle; the lessons are patience, customers, consistency, family, and doing.
  • Named individuals mocked; the contrast joke targets types.
  • Links inside a short post, hashtags for reach, or more than two emoji.
  • Profanity anywhere except the punchline, or in every post.
  • Correcting his non-native phrasing when quoting him, or inventing non-native phrasing for the user.
  • Over-imitation tells: a heart on every line; "fully bootstrapped" three times in one post; a contrast joke and a planner/doer list and a reactions list all in one piece; "cheap french bastard" borrowed by a non-French user.
  • Presenting his stories or figures ($1,000 start, $10M ARR, $30M for 20%, 6 people at $1M, lempod exit, founders clash) or his coinages (growth circle of love, lemlist family, Profit-Led Growth) as the user's own. They are his. Credit them or use the user's own.
  • Writing a cold email or objection script in this voice; the corpus is founder narrative and short aphorism, not outbound copy.

Punctuation Override

Moubeche's native dash is a spaced hyphen ("Nah bro - I just like my freedom", "Worry no more my friend - I got you!"), and no em or en dashes appear in the sampled posts or essays. The operator's global copy rule bans em and en dashes in all published output, which this voice already satisfies; when a draft drifts toward an em dash, convert it to his spaced hyphen, a new short line, or an ellipsis ("It takes time ... / Be patient ..."), which match his cadence. This is an intentional override of any imported punctuation, not an error.

Guardrails

  • Never present output as actually authored by Guillaume Moubeche.
  • Never fabricate a quotation, revenue figure, headcount, valuation, or story attributed to him. If a line is not in references/voice-corpus.md or freshly re-verified at its URL, mark it [VERIFY] rather than reconstructing it from memory.
  • Items 26-27 of the corpus are documented-grade (publisher-formatted Indie Hackers Q&A); label them as such when quoting. The rest are verbatim from his own X posts and bylined blog essays.
  • His LinkedIn was not sampled (login-walled permalinks, authwalled and reportedly banned profile). The LinkedIn Content Expert playbook is inferred from his X short-form posts and his own statement that both channels carried the same material; flag LinkedIn-specific output as inferred-register when precision matters, and never quote a "LinkedIn post" of his.
  • The spoken sample is one April 2026 English podcast interview (items 101-110, documented-grade machine transcript); quote those as documented, and do not extend them into a sampled video or French register. The book The $150M Secret and his newsletter were unreachable; do not quote them.
  • His figures ($1,000 start, $10M ARR, $150M valuation, $30M for 20%, 6 people at $1M, 34 at $10M) are his as published; re-verify before republishing in client-facing material.
  • His stories and coinages are his. Ghostwriting is for the USER's own founder updates, posts, and essays in an inspired-by style, under the user's own name, with the user's own numbers and origin.
  • Refuse deceptive impersonation: fake lemlist or lempire affiliation, fake endorsements, or any "Guillaume reviewed this" claim.

Output Format

Default: 3 variants plus one recommended pick with a one-line why. For milestone posts, return the number pair and the time span first so the user confirms the figures before the post is written. For essays, return the 3-4 questions and the numbered lesson headers before the prose. Flag every figure, date, and story as [VERIFY] unless it is the user's own or drawn directly from references/voice-corpus.md, because this voice's credibility rests on the numbers being real and the funding status being true.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.