You can describe the product, but no two people on your team describe it the same way. Sales is improvising on pitch calls, the website contradicts the deck, and nobody has settled on who this is really for. Maybe you've even tried aligning the team internally, but everyone keeps falling back on their own version of the story.
Define positioning, ICP, message architecture, and brand voice in one system to give every team the same explanation of what you do.
Run competitive teardowns, buyer interviews, and market sizing, each tied to one business decision, to understand the competition and buyers.
Coordinate the narrative, campaign, events, and adoption flows for each release to get it noticed by the market and used by customers.
Build decks, scripts, battlecards, and FAQs on the same message framework as the website to give every rep one story to pitch.
Write the onboarding flows, in-app messages, and upgrade prompts inside the product to turn signups into active users.
Decide which markets to enter, how the product differentiates, and how each release reaches customers, in one plan every team works from.
Answer RFPs and technical proposals from a maintained answer library to respond fast without pulling in the whole team.
Measure where the product meets real demand, using buyer interviews and usage data, to confirm the target audience before scaling.
Publish a consistent point of view on the problem you solve, across owned and earned channels, to build credibility with prospects.
Name and define the market you compete in, in language buyers already search for, to give them a category to put you in.
Build the investor narrative, deck, and proof points on the company's positioning to enter the raise with one story the whole team tells.
Equip partners with positioning, co-marketing assets, and enablement to make every partner pitch accurate.
Set direction, priorities, and identity for all marketing in one plan to move the team from firefighting to growth work.
A brand strategy is a detailed, long-term plan for successfully developing, positioning, and marketing a brand to shape how it is perceived by your audience.
A strong brand strategy guides all creative, verbal, and visual choices, and is based on strategic positioning and business purpose, target audiences and segmentation and messaging & voice. The strategic foundation for business growth is critical, and is the foundation on which the business goes to market.
For teams with a working product and no settled story, 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.
