Problem
Before the MVP launch, Pier needed the website promise to match product readiness, value-map truth, and what SMB owners could understand.
Product management proof
Marketing Website As A Product Surface
I owned and shipped production code for Pier's marketing website while treating pier.so as a product-learning surface.
What I owned
I shipped the marketing website production code, moved the value map first, and used the live site as a qualitative testing surface for buyer comprehension and positioning.
Result
The website connected product, messaging, and customer learning instead of sitting off to the side as marketing collateral.
This case refers to marketing-site production-code ownership, not sole engineering ownership of the core Pier product.
The situation
The marketing website was pier.so, one of the product surfaces I owned
directly. This is where my technical ownership was literal: I personally
shipped production code for that public surface.
The PM problem was that the site could not drift away from product truth. Before the January MVP launch, we needed to validate whether SMB owners understood the problem and whether our promise matched what the product could actually support.
The approach
I treated the site as part of the product-learning loop. The value map had to move first. Then the SMB owner copy could go live as a consistency anchor for outreach and interviews.
That distinction mattered. The website was not supposed to be a conversion engine that solved distribution by itself. It was a qualitative testing artifact: provisional language, a public surface that matched current launch readiness, and a way to see which value cases and personas deserved more attention.
The current pier.so shows why that surface mattered. The site presents Pier
as institutional evaluation infrastructure: model requirements once, structure
external submissions into requirement-fit decisions, gather missing evidence
through adaptive follow-up, deliver traceable decision packets, and keep human
decision authority intact.
What I built
- production code for the marketing website
- website copy tied to the source-of-truth value map
- a public product surface for buyer comprehension testing
- launch-readiness messaging that stayed inside supported product truth
- a feedback path from website language back into product and positioning
Why it matters
A customer-facing surface should reveal what the team believes about the user, the problem, the current capability, and the next decision. If that surface drifts from product truth, the team is testing the wrong promise.
Result
The website connected product, messaging, and customer learning. It gave the team a public surface to test whether the buyer understood the problem and whether the promise matched product readiness.
What I learned
A website can be more than marketing. It can be a prototype of the product promise. If that surface drifts from product truth, the team is testing the wrong promise.