Show me where the explanation breaks

I start with the wrong name. I look at how a buyer, search result, AI answer, or sales note might misclassify the company, then I trace the artifacts causing that drift. The work usually ends in a practical repair plan tied to pages, proof, definitions, and editorial habits.

I take on B2B SaaS positioning, category language, generative visibility, AI citation architecture, comparison content, customer proof, and product narrative repair. I am especially useful for complex software that keeps getting described as a simpler tool. If the product needs careful explanation before it can be trusted, it is probably in range.

I usually reply within a few business days. A useful first message names the product, the category you want to be in, the category you keep getting pushed into, and a few links I should read. I would rather have one clear paragraph than a polished brief.

I work in focused engagements, usually a diagnostic audit, a narrative repair sprint, or an editorial operating system for teams that need repeatable thought leadership. Calls are useful, but the real work happens in the artifacts: pages, claims, examples, proof, comparison logic, and internal language the team can reuse.

My work sits in the range of serious advisory engagements, not quick copy edits. A smaller diagnostic may be at the lower end, while a deeper visibility and narrative system costs more. I give a rough scope after I understand the misclassification problem and the assets already in place.

I do not take on generic SEO retainers, volume blog production, press release writing, ad copy, social posting calendars, or theatrical founder thought leadership. I also do not write claims the product cannot support. If there is no visible evidence behind the story, I will tell you where the evidence is missing before touching the language.