Send the source text that feels risky

I begin with a small source set: homepage, one or two feature pages, a pricing note, and any docs or changelog pages that carry product truth. I map what an LLM can safely extract, where it has to infer, and which sentences need rewriting before larger structure changes make sense. The guiding rule: every important claim has to be understandable once it leaves its paragraph.

I work best with B2B software, data, infrastructure, healthtech and industrial technology firms. I also take on complex service companies when the offer needs precise capability wording rather than broad brand language. The test is simple: there must be source text — a product, feature or docs page — to inspect, not just a request to be visible.

English and French must agree on capabilities before they differ in tone. Two pages describing the same product with two different levels of courage build an unstable entity for an answer engine. I work the canonical source text first — what the product does, for whom, where it works, what it excludes — then let each language carry its own voice without contradicting the fact.

I usually reply within a few working days. If the request is vague, I will answer with the smallest useful next step rather than sending a long intake ritual. If the problem looks outside my scope, I will say that plainly.

I usually run consultations as a focused source review: one product area, one extraction problem, one set of written findings. For larger work, that can become a rewrite package or an advisory sprint. Most work sits in the low-to-mid four-figure range, depending on the number of pages, languages and source conflicts; a narrow audit costs less than a bilingual rewrite or a full product-claim alignment sprint.

I do not take on generic SEO retainers, mass blog production, link campaigns, press releases, or brand voice work with no source-structure problem underneath. I also avoid claims that the company cannot support with product, docs or proof. Proof only counts when a case study names the starting point, action, metric and business outcome.