I write the marketing and build the system that sends it.

ProcessForge is a SaaS product I built and shipped at getprocessforge.com. The first version of the landing page had the problems most founder-built pages have: two competing calls to action in the hero, a headline that described the category instead of the promise, and a cold navy interface that fought the warm brand of the page it sat behind.

I rebuilt it against what actually converts rather than what I liked looking at. One call to action instead of two. A promise in the subhead instead of a category description. A hero that agreed with what the product was claiming instead of quietly arguing with it. Then all the small things most people skip, which are usually the ones deciding whether a page feels finished.

Shipped April 2026. The point isn't that I know these principles. It's that I applied them to my own product, where the cost of being wrong lands on me.

Add before sending Drop in your real before and after numbers here: signups per week, or conversion rate, or time on page. One honest metric beats three vague claims. If you don't have clean numbers yet, delete this box and let the work speak.

Penelope June is a picture book series I write. Four manuscripts drafted, a locked character system so the art can never drift between books, and a defined palette and voice that every asset is held against.

The marketing problem with a picture book is that it sits on a shelf next to a hundred others that look the same. So I built the differentiator instead of buying ads for it: a read-along app where the child reads the book out loud and the illustration animates as they say each word. Live microphone, forgiving enough for a four-year-old's pronunciation, no narration doing the reading for them.

It costs nothing per copy, it turns the physical book into the product and the app into the reason to choose it, and it's the kind of thing a parent would tell another parent about. That's the marketing plan: build the reason to choose it instead of buying ads.

Add before sending Once the book is out, add sales, preorders, or the response you got when people tried the read-along. Until then this reads honestly as a product and brand case study, which is what it currently is. Don't imply results you don't have yet.

I run an Etsy template shop and a gift guide blog with its own email list and affiliate links, and I post on TikTok and Pinterest.

The listing images and pins come out of build scripts I wrote, so a new product's marketing starts from one source instead of a week of hand work.

I use AI on the repetitive parts so my hours go to the writing and the judgment calls.

Add before sending Add one or two screenshots of the morning briefing and a content pipeline output. Reseed with demo data first so nothing real appears. Screenshots make this case study land far harder than the description does.