Sales answers product questions one way, support answers them another, and the documentation says a third thing entirely. Critical product knowledge lives scattered across old Slack threads or inside key employees' heads. Maybe you've even tried building internal wikis before, but they quickly fell out of date and lost team trust.
Give every campaign a question and a metric, reviewed on a fixed cycle, to know what worked and decide what to fund next.
Measuring success isn't about a single number. It's about telling a complete story with data.
Maintain one source of company answers, updates, and onboarding material to keep every employee on the same story.
Build workflows, automations, and AI tooling around how the team already works to get full use from the tools you bought.
Train every employee on the company message and equip them with talking points and content to tell it publicly.
Define roles, write job specs, and evaluate candidates against the plan to build a team with clear lanes and enough capacity.
Allocate spend across channels, tools, and headcount based on accepted benchmarks and other key drivers to build a predictable marketing budget.
Update, fix, and maintain the website, landing pages, and platform on a regular cadence to keep the site accurate and converting.
Document company knowledge in one structured source to answer repeat questions consistently and feed LLMs accurate information.
For teams big enough to feel disorganized and small enough that we can still fix it, seed to Series C.
Brand and product read better in one voice, especially for technical products.
New approaches every time, based on your business needs specifically.
Tell your story uniformly to anyone, using clear, persuasive language adapted by persona.
I'll give you my honest opinion every single time.
We'll agree together on how to manage the engagement, based on your business needs.
I learn super fast, and I'm pedantically attentive to the small details simultaneously.
Products whose primary value is the technology itself, and where the buyer or first discoverer is often technical: cybersecurity, AI and computer vision, developer tools, fleet and operations platforms.
Practically, this usually means that copy should be direct and technical - at least for that part of your audience.
My engagement with each company changes depending on the business needs!
A project, a quarter, or the long haul: this can be anything from hands-on execution through to fractional marketing leadership.
I write it. That is the point of the arrangement: the strategy and the technical writing that makes it credible come from the same person.
When volume genuinely needs more hands, I bring in and manage contractors, but the through-line stays mine.
Further than most strategists go: docs-as-code, analytics, product and UX specs, and content structured so that LLMs can read it.
Developer portals, product documentation and release notes are inside the work, not adjacent to it.
AI accelerates work that I have always done myself but didn't really need to, and makes me available to do the work that only an experienced human can do. AI workflows, skill systems, pipelines and automations.
I also teach it, including to marketers who are wary of it. Judgment about when not to use it is part of the job.
Products whose primary value is the technology itself, and where the buyer or first discoverer is often technical: cybersecurity, AI and computer vision, developer tools, fleet and operations platforms.
Practically, this usually means that copy should be direct and technical - at least for that part of your audience.
My engagement with each company changes depending on the business needs!
A project, a quarter, or the long haul: this can be anything from hands-on execution through to fractional marketing leadership.
I write it. That is the point of the arrangement: the strategy and the technical writing that makes it credible come from the same person.
When volume genuinely needs more hands, I bring in and manage contractors, but the through-line stays mine.
Further than most strategists go: docs-as-code, analytics, product and UX specs, and content structured so that LLMs can read it.
Developer portals, product documentation and release notes are inside the work, not adjacent to it.
AI accelerates work that I have always done myself but didn't really need to, and makes me available to do the work that only an experienced human can do. AI workflows, skill systems, pipelines and automations.
I also teach it, including to marketers who are wary of it. Judgment about when not to use it is part of the job.
Yes. For marketers and technical writers: breaking in, using AI with judgment, and building systems that get used.
There is no upsell attached to it and no catch.
Metrics depend on what we're working on together.
For example, for internal enablement, we might look at engagement and adoption after implementing a new platform. For a new social media platform, we might track traffic, engagement and conversion. It all depends on the project and goals.
We'll establish scope and measurements at the start of the project.
Tell me what you're working on. I'll help you understand how I can help you find the right solutions.
