Technical product marketing

Building the system behind the message.

I created the strategic and editorial systems used to explain Bolt Liquidity, from internal positioning and claims governance to technical documentation, website copy, and public articles.

Bolt Liquidity technical documentation home page, headed Route with Bolt.
Documentation narrative, page structure, and MDX production led by John Cowin, developed with Phi Labs design and engineering.

Results

  • 16-document marketing foundation
  • Six structured stakeholder interviews synthesized
  • 27 technical-documentation pages drafted in MDX
  • 10 researched, written, edited, and published long-form articles
  • Website strategy, section layout, and copy for a top-to-bottom build
01

Context

Phi Labs shifted from Archway to Bolt Liquidity four months after I joined. The new protocol required a clear product story, consistent technical explanations, audience-specific messaging, and a process for keeping claims accurate as the product evolved.

02

Marketing foundation

I synthesized interviews with leadership, engineering, business development, pricing, sales, and foundation stakeholders into a 16-document operating foundation. It covered product positioning, buyer roles, messaging architecture, market pain points, competitors, claims governance, audience psychology, voice, terminology, reusable copy, and category narrative.

That foundation is internal working material, so it is described here rather than published.

03

Technical documentation

I drafted all 27 documentation pages as MDX files and pushed updates through GitHub. Engineering built the code sections, and I collaborated with design on the documentation’s visual branding.

The architecture page is the clearest example of the translation work: market data, oracle, smart contracts, and settlement explained as one sequence rather than four disconnected concepts.

Documentation page titled How Bolt Works, showing a four step diagram from market data through oracle and smart contracts to settlement.
Documentation narrative, page structure, and MDX production led by John Cowin, developed with Phi Labs design and engineering.
Sui TypeScript SDK documentation page showing the introduction, quickstart prerequisites, and the first installation code block.
Technical documentation drafted and structured in MDX by John Cowin. Code sections developed by Phi Labs engineering.
Documentation narrative, page structure, and MDX production led by John Cowin, developed with Phi Labs design and engineering.
04

Website

I led website strategy, copy, and section layout and worked with the design team on a top-to-bottom build. The work connected product positioning to the page hierarchy, narrative sequence, and final copy.

Website strategy, section layout, copy, and narrative sequencing led by John Cowin in collaboration with the Phi Labs design team.
05

Long-form articles

I researched, wrote, edited, published, and directed the visuals for 10 long-form articles. Five remain live and five were removed with the previous website.

Contact

Your product is complex. Its story shouldn’t be.

If you need someone who can carry its story from positioning through execution, let’s talk.