Build LogCopy
#01
2026-08-105 min read

I wrote it as a quality signal. The prospect read it as a rejection.

Five copy fixes on captainrandom in 2026. Contact page, learning hub, creative sub-brand, album credits, a placeholder. Different surfaces, same root: the copy said what I intended; a first-time reader read something different.

Read post
Build LogWeb
#02
2026-08-086 min read

Copy bugs don't throw exceptions

The NAPA SEASON album page attributed production and vocals to Suno. That gave authorship to a rendering engine. The /contact timelines note filtered out prospects before they had sent a message. Neither bug showed up in any log.

Read post
Build LogConversion
#03
2026-08-076 min read

The portfolio had a shop floor. It just didn't have a till.

GA4 revealed one desktop visitor with 13+ sessions, seven minutes on /work/, and nowhere to act. A week later: hero band as shopfront, /work/ as the aisle, hire strip as the till. The retail frame isn't a metaphor — it's a diagnostic tool.

Read post
CopyBuild Log
#04
2026-08-045 min read

I wrote quality signals. They landed as rejection, ambiguity, and a wrong name on the record.

A note on timelines on the /contact/ page read, to a prospect, as a closed door — not the quality signal I'd written it as. Across /contact/, /creative/, and /learning/, the same gap kept appearing: copy written from inside the writer's knowledge of the intent, with that knowledge doing load-bearing work the prose itself wasn't.

Read post
CopyBuild Log
#05
2026-07-285 min read

Strip the sentence you wrote for yourself

Four copy fixes across five weeks. Each one stripped a sentence written from inside my own head and replaced it with one a cold reader could actually decode. The pattern only became visible after the fourth.

Read post