TECHNICAL
STORYTELLING.

Reverse-engineering is the trade craft underneath every artifact I ship. I take work I admire apart, name what makes it land, and rebuild it on my own substrate before any pixel touches my own canvas.

[THE PROCESS]

I sit with each piece of work I admire until I can name the moves it makes from memory. Paragraph cadence, hero structure, information density, tonal register, the moment a hero photograph lands, the point where code blocks start to breathe. The teardown is structured research: competitive study, jobs-to-be-done analysis, workflow synthesis, value framing. Each piece gets its own journal entry. From there I rebuild the instinct on my own substrate. Nine pieces journaled before the build begins.

Standing sub-agents push back on every direction I commit to. Their instruction is to default to first principles and treat any inherited pattern as a hypothesis. Devil's advocacy through a multi-model reflection pattern, before the building goes any further.

[THE DECK]

The investor deck I built this spring went through eight clean iterations after the scaffold was right. The scaffold itself took deeper time than the iterations: upfront discovery on VC voices, deck frameworks, format conventions across the segment we are targeting, then enough corroboration with the team that the foundational claims were defensible before any slide got drawn.

I do not start decks in Google Slides. I do the heavy design and discovery thinking up front, plot the deck out as a high-fidelity React HTML wireframe slide by slide, then emulate it in Slides afterward. The HTML is the design artifact. I get the reverse-engineering payoff in the cuts. The first three iterations are the obvious moves. The compounding shows up at iteration six, seven, eight, when the artifact starts looking inevitable to anyone reading it for the first time.

[THE BROADER SURFACE]

The same shape carries the rest. Every brand surface I have built over the past year runs on the same substrate, including the site you are reading, the company sites alongside it, and the supporting collateral that ships with the rest of the campaign.

Conference work concentrates the same problem into one week of the year. Booth screens, print collateral, QR routing, the post-show follow-up sequence. Every layer had to read as one piece, because the company gets one window with that audience. I built all of it myself. There was no one else to build it.

Advertisements compress the same instinct into the shortest unit. The unit is small, the reading time is shorter, and the inspiration set is enormous, with an active analysis folder across film, consumer, and developer-tooling brands. I borrow the instinct underneath a piece rather than the pattern itself.

The experimentation surface around the workflow stays wide. Gamma, NotebookLM, RunwayML, Luma, Stitch, variant, and whatever ships next month all earn a try. Most stay as experiments. The handful that hold get folded in.

[THE WORK STANDS]

Every artifact gets the same engineering attention. The website, the deck, the booth, the ad, the technical write-up, the proposal, the email to a senior person at a customer org. The artifact lands in the room. Underneath sits the substrate I take pride in, the part nobody sees.

The proof that travels in the public is the artifacts themselves: investor work in active circulation, the conference booth, the company websites, the ads and supporting collateral that ship alongside them, and this site. The deeper drill-down on each piece sits behind the gated portfolio.

The site and this essay came out of the same process.