Kai John-Blunch

Product management proof

Shipping Pier's Website And Partner Guide

I personally shipped production code for Pier's marketing website and the SmartApply partner guide used in external testing and partner work.

Read the narrative Inspect the summary
  • Production code ownership
  • Product surface ownership
  • Buyer comprehension
  • Messaging as prototype

Problem

Before the MVP launch, Pier needed the website promise to match product readiness, value-map truth, and what SMB owners could understand.

What I owned

I used pier.so as the maintained home for current product pages and partner instructions, then shipped the landing pages, analytics, feature flags, walkthroughs, and guide behavior that supported it.

Result

The production website carried current product pages and a SmartApply partner guide into live external work.

This case refers to marketing-site production-code ownership, not sole engineering ownership of the core Pier product.

What I noticed

Partners needed one maintained place to understand what SmartApply supported and what they should do next. Product pages, walkthroughs, one-off collateral, and partner instructions had drifted across several places, making it harder to keep the external experience current as the product changed.

At a glance

  • Product area: customer-facing web experience and partner guidance
  • Users: prospective buyers, partners, and product evaluators
  • Collaborator boundary: I shipped the website production code; Pier’s technical cofounder owned the core-product engineering
  • Constraint: the public product description and partner instructions were fragmented and changed as the product moved toward external use
  • Decision: use pier.so as the maintained home for product pages and partner guidance instead of relying on one-off attachments
  • Artifacts: production landing pages, analytics and CTA behavior, feature flags, product walkthroughs, and the SmartApply partner guide
  • Observable result: the published partner guide was used in live March 11 external outreach

What I owned

I personally shipped production code across the site: landing pages, product walkthrough content, PostHog CTA tracking, feature-flag behavior, and the unlisted SmartApply partner guide.

This is direct technical ownership of production website code. Pier’s technical cofounder built the core application.

The product decision

I moved customer and partner guidance toward one maintained website. A live guide could stay current after delivery; a static attachment would become stale as the product changed.

Result

I shipped the current product pages and SmartApply guide on pier.so, and the team used the guide in external testing and partner work.

What I learned

I learned that website work becomes product work when people depend on it to understand what the system does and what they should do next. Shipping the page is only half the responsibility; the rest is keeping the guidance aligned with the product people can actually use.