# Voice Brand Linkedin Post Stephane

> Use when drafting LinkedIn posts on behalf of Stephane (founder of HAQQ Legal AI / Louis) for HAQQ-related content. This skill defines Stephane's LinkedIn voice — first-person, insight-driven, MENA-aware, and substantive — along with structure, content rules, what to avoid, and the hashtag strategy for reaching the LegalTech and MENA legal audiences.

- Skill: `sboghossian-mini-claude-for-legal/voice-brand-linkedin-post-stephane` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sboghossian-mini-claude-for-legal/voice-brand-linkedin-post-stephane`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sboghossian-mini-claude-for-legal/voice-brand-linkedin-post-stephane/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: sboghossian (https://skillmd.com/u/sboghossian-mini-claude-for-legal)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/sboghossian-mini-claude-for-legal/voice-brand-linkedin-post-stephane

---


# LinkedIn Post — Stephane's Voice

## When this applies

Use this skill whenever writing a LinkedIn post in Stephane's voice: product updates, observations about the MENA legal market, LegalTech commentary, customer stories, or founder reflections on building HAQQ Legal AI.

## Voice characteristics

Stephane's LinkedIn voice is:
- **First-person, conversational** — writes as a practitioner and builder, not a marketer.
- **Insight-driven** — every post contains one clear, defensible observation. Not a list of facts.
- **Specific over generic** — references real customers, real jurisdictions, real deal types. Generalities are not Stephane's style.
- **Opinionated but grounded** — states a view and explains the reasoning. Does not hedge every sentence.
- **MENA-contextual** — when MENA is relevant, it is named specifically (UAE, KSA, LB, DIFC, not vague "Middle East").

## Post structure

There is no rigid template, but most high-performing posts follow this shape:

### Opening line (the hook)
- Written for the preview snippet — the first 1–2 lines before "see more."
- Should create tension, state a surprising finding, or raise a question the reader wants answered.
- Do not open with: "I'm excited to announce…", "Thrilled to share…", or any boilerplate.

Good:
> "Most MENA in-house legal teams still review vendor contracts manually. That's about to change."

Bad:
> "We've been working really hard on something special and I'm excited to finally share it!"

### Body (the substance)
- One key insight, observation, or story per post.
- Mix of observation and opinion — state what you see, then say what you think it means.
- Mention specific case studies or customer outcomes where consent is given (or anonymize to "a GCC sovereign fund's legal team" or similar).
- 150–300 words is the sweet spot. Under 100 feels thin; over 400 loses most readers.

### Tag relevant people
- Tag co-founders, customers, partners, journalists, or collaborators — but only with their permission or when clearly appropriate.
- Do not tag people just for reach. It reads as spam and damages relationships.

### Closing (CTA or question)
- Optional but recommended.
- Invite response with a question, or point to a next action (demo link, blog post, whitepaper).
- Do not hard-sell. "What's your experience?" performs better than "DM me to get started."

## Content types that work

| Type | Notes |
|------|-------|
| Product milestone | "We shipped X. Here's why we built it the way we did." Focus on the reasoning, not just the announcement. |
| Customer outcome | A specific result from a real customer (anonymized or named with consent). Numbers are gold. |
| Market observation | A trend in the MENA legal market with Stephane's take on what it means. |
| Behind-the-scenes | How a specific decision was made — engineering, design, business model, pricing. |
| Hot take / opinion | A disagreement with received wisdom in LegalTech. Well-reasoned, not contrarian for its own sake. |
| Founder lesson | Something learned the hard way, stated directly with what changed as a result. |

## What to avoid

- Corporate-speak and startup buzzwords ("disrupting", "ecosystem", "synergy", "world-class").
- Salesy CTAs in every post — some posts should give value with no ask at all.
- Generic hot-takes that could have been posted by anyone.
- Virtue signaling that doesn't connect to actual work.
- Posting just to post — frequency without substance destroys the brand.

## Hashtag strategy

Minimal and focused. Use 2–4 hashtags maximum:
- `#LegalAI` — primary, always on product and AI posts.
- `#MENA` — when the post is explicitly about the region.
- `#LegalTech` — on posts addressing the broader market.
- `#Startups` — on founder/building posts, sparingly.

Do not include hashtags that are irrelevant to the post content for reach purposes.

## Frequency guidance

Two to four posts per week is optimal for an active founder brand. Below two loses momentum; above four risks quality dilution unless there is genuinely material news.

## Related skills

- [[voice-brand-tweet-thread-launch]]
- [[voice-brand-email-cold-outreach-mena]]
- [[voice-brand-press-release-tone]]
- [[voice-brand-email-investor-update]]