01 / Technical Product Marketing
Building the system behind the message.
I built the strategic foundation that turned Bolt Liquidity’s technical complexity into a clear market narrative, then carried it across documentation, web experiences, articles, and campaigns.
- Interviews
- Research
- Analysis
- Shared product language
- Website
- Documentation
- Campaigns
- Interviews
- Research
- Analysis
- Shared product language
- Website
- Documentation
- Campaigns
- Research
- Positioning
- Messaging
- Claims Governance
- Technical Documentation
- Web Content
- Campaign Direction
Before the message comes the foundation.
Before a product can be explained externally, it needs a shared internal language.
For Bolt Liquidity, I built that language from stakeholder interviews and product research, shaping the positioning, claims, proof points, and narrative architecture behind every public-facing expression.
The work grew into a multi-document marketing foundation.
- 00 Stakeholder Interviews Cross-functional leadership input
- 01 Strategic Foundation Brief Product foundations
- 02 Target Buyer Analysis Audience and use cases
- 03 Market Pain Points Research Market tensions and unmet needs
- 04 Target Audience Psychology Motivations and decision drivers
- 05 Competitor Analysis Market context and differentiation
- 06 Product Positioning Positioning system
- 07 Brand Archetype Strategic character
- 08 Claims Log Claims and proof
- 09 Messaging Hierarchy Messaging architecture
- 10 Brand Tone of Voice Verbal expression
- 11 Brand Lexicon Language system
Once the product language is clear, it guides every expression that follows: the website, technical documentation, articles, campaigns, and content that bring the product to market.
Website
I mapped the experience from the opening section to the final CTA, wrote the complete website narrative, shaped its scroll behavior and interactions, and defined the partnership journey and form flow. Working closely with design, I guided each revision through a complete rebuild and launch in two weeks.
Technical documentation
I rebuilt the documentation from the ground up, moving it from an outdated GitBook into a purpose-built Mintlify documentation system. I owned the architecture, technical writing, cross-references, calls to action, MDX build, and GitHub publishing, working across engineering, growth, and design to make complex product information useful, accurate, and appropriate for public release.
Selected views from a broader documentation system
Documentation overview
One branded Mintlify system in place of outdated GitBook documentation, organized from product understanding to implementation.
Interactive architecture
I developed the early diagram with engineering, validated it with the liquidity team, refined its structure, filtered out internal-only information, briefed design, and wrote every pop-up explanation.
Developer SDK
The existing SDK code was preserved while the surrounding structure, explanations, cross-references, navigation, and presentation were rebuilt.
One minute to make the product clear.
I conceived the campaign, mapped the one-minute narrative from first frame to final CTA, built the storyboard, and recorded reference voiceover tracks that guided the finished AI-generated narration. I worked closely with design through each revision, then coordinated amplification across partners, ecosystem accounts, and creators.
First 48 hours after launch
- About 14% engagement rate
- 84% of impressions from non-followers
- +140% website traffic
- +153% technical-documentation traffic
- More than 16x typical post reach
- Recognized and amplified by key ecosystem foundation accounts
Product clarity carried into the market.
The same product fluency behind the positioning, website, documentation, and campaign also helped build Bolt’s ecosystem footprint. I translated its value and architecture into partner conversations, direct integrations, and downstream paths across Sui. As that footprint expanded, the protocol grew from zero to more than $300 million in processed volume.
Direct aggregator integrations
+ Additional downstream integrations
One foundation. Every expression aligned.
The work began with a shared product language and carried across the full public-facing system, from the website and technical documentation to campaigns, articles, content, and every expression built from the same strategic foundation.