One company.
Three products.
Every buyer. One voice.

Most SaaS copy fails because the writer never studied what your buyer compares you to.

I am an electronics engineer who writes marketing copy.

NED University, Electronics Engineering. Then a strategic marketing diploma from IBA. I did not come to SaaS writing from an English degree. I came from a field where you may not describe a system until you have read how it actually works. That difference shows up in four places.

VIDIZMO builds AI video and evidence content management software. One wrong word can lose a court case.

VIDIZMO sells to police departments, hospitals, banks, and government agencies. When the file is legal evidence, there is no undo button. A leaked face or a broken chain of custody ends a case, not a quarter. So every claim I wrote had to survive a lawyer reading it. The writing also had to respect five strict rulebooks: HIPAA for health data, CJIS for police data, GDPR and CCPA for privacy, and FOIA for public records.

vidizmo.ai →

Gartner RecognisedIDC MarketScape 255+ File FormatsCloud · On-Prem · Hybrid

Three products. Three very different worlds of buyers.

Each product speaks to a different kind of person. What they care about. What scares them. How they decide. I had to master every language at once, all under one brand.

One strategist. Three products. And a creative team I directed.

Product Marketing Strategist, July 2023 to 2024. I did the research, then wrote everything built on it: blogs, press releases, sales email series, product pages, interface text, and video scripts, across all three products at once. I worked with a team too. Some at my level, some junior. I briefed and directed the graphics and video team for videos, social posts, and infographics, and guided junior writers on their drafts.

Read the writing itself. Straight from the working files.

The writing can speak for itself. Start with the featured exhibit below, quoted at length with the brief that shaped it. Then keep reading: the film scripts live in the flagship campaign, complete first emails sit in the sales section, wire copy in the press section, and two full passages inside the blog section.

Every piece started with a brief I wrote myself, never a blank page.

Every piece started with a brief, and I wrote the briefs too. Before I drafted a single word, I ran the keyword research, checked what competitors had already published, planned the full article, and got my plan approved. This section holds all of my blog work in one place: my process, four published samples you can open for a breakdown, and two full writing passages at the end.

On a normal working day I might write for a police chief in the morning, a hospital compliance officer after lunch, and an artist by evening, while planning social posts and briefing the video team in between. These two full passages, written in the same week, show what that daily range looks like on the page. Open each one and read it whole.

Written, edited, and sent live on PR Newswire. Open a card for the full story.

I researched, wrote, and submitted each release myself: the CEO quotes, the full company boilerplate, and the AP Style formatting. Two releases are shown below with real excerpts from the wire. I wrote more. The rest of the press archive stays under my NDA with VIDIZMO, and I protect client work the same way I would protect yours.

↓ Two from the press archive. Click a card to open the full breakdown.

I led sales enablement end to end: the research, the battle cards, and the words that win deals.

A battle card is a one-page comparison sheet the sales team lives by. A rep uses it live in the middle of a call, and just as often the card is sent to the prospect as-is, so they can read it and analyze the comparison themselves. Either way, the buyer sees the exact words. That makes this work client-facing with zero margin for error: one wrong detail costs the deal and the trust.

So before I wrote a single objection line, I tested every feature myself and checked each claim against the competitor's own documents and our lost-deal notes. Twelve platforms. Twelve cards. Then I presented the whole thing to the sales team so they walked into those calls prepared.

Twelve platforms. Every buyer type in the funnel. Five compliance rulebooks. I mapped which pain points were real, which were vendor theatre, and which features we were missing. Some of what I found shipped into the product.

Email writing that converts: five months to decide means five emails, not one.

Enterprise buyers take months to decide, so one email never does the job. I wrote a full series for each buyer group, and every series starts where that buyer already is: their problem, their fear, their words. Two cards below show a complete first email, word for word. The other two show excerpts that capture how the sequence opens. Click any card for the map of the whole series and the thinking behind it.

I mapped the whole market for Redactor. Then I presented it to the CEO.

Leadership asked me to build the digital marketing plan for the Redactor line. I went further than the ask. I mapped every industry that creates redaction demand to its real buying triggers and its regulators, planned five channels, and designed the content system to support all of it.

While building it, I also found gaps in how business development was working: buyer segments we were not reaching, and channels running without a clear reason. I wrote it all up and presented the full plan to Chief Executive Nadeem Khan and the marketing team.

Click any industry to see the exact angle I built for it ↓

From feature documents to the text inside the product.

I wrote the feature documents that defined each problem, solution, and buyer. I wrote full website pages. And I wrote the interface text inside EnterpriseTube itself: every tooltip, every label. My feature briefs went deep enough that one of them defined the AI Facial Attributes capability across two products, with use-case research for every target industry, before a single page of marketing existed.

Everything I built kept compounding.