Kai John-Blunch

Built

Product work grounded in users, decisions, and production systems.

Start with three cases: employer onboarding UX taken from requirements through release, a customer-intelligence learning loop built across 100+ customer conversations and user interviews, and a contingency test that changed roadmap and positioning. The wider library remains below for review by product-management responsibility.

Selected product work

Three episodes that show how I manage product work.

See how I took employer onboarding from requirements through release, built a technical learning loop across 100+ customer conversations and user interviews, and changed the test path when pilot signal stalled.

Product episode

Designing Employer Onboarding From Requirements Through Release

Pier's product helped employers create an opportunity, invite candidates into an AI-assisted interview, and review structured evidence without delegating the hiring decision. I defined the employer-signup requirements, designed the flow and error behavior, handed the experience to engineering, and ran first-time and returning-employer QA through release.

Result: production onboarding and partner guidance aligned to the journeys used in release QA.

Open case study

Product episode

Building A Customer-Intelligence Learning Loop

Customer conversations were shaping an AI qualification product, but raw transcripts could not become the team's memory or roadmap. Across 100+ customer conversations and user interviews, I designed the learning loop, conducted interviews, built the n8n transcript-synthesis workflow, and handed source-grounded insights to Pier's technical cofounder.

Result: a reusable customer-intelligence system for product, positioning, and MVP feature decisions.

Open case study

Product episode

Changing The Test Path When Pilot Signal Stalled

When pilot partners stayed quiet, I did not lower the evidence standard or wait indefinitely. I sequenced a lower-risk contingency test, protected the highest-risk relationships, and translated the returned feedback into roadmap, engineering, and product-positioning changes.

Result: a stalled signal became a controlled learning path and concrete product decisions.

Open case study

Wider proof library

Explore by product management responsibility

Inspect ownership, roadmap, discovery, workflow mapping, QA, team cadence, product surfaces, and market judgment across the full case-study set.

PM responsibility

Customer deployments and live-use readiness

Customer-facing AI workflows, workflow design, QA, customer confidence, stakeholder communication, and release judgment before live use.

PM responsibility

Product ownership and roadmap

Sole PM ownership, roadmap shaping, backlog tradeoffs, and prioritization under constraint.

PM responsibility

Discovery and customer learning

User interviews, customer intelligence, KPI design, pilot demos, feedback loops, and partner learning.

Case study

Building A Customer-Intelligence Learning Loop

Across 100+ customer conversations and user interviews, I designed the learning loop, conducted interviews, built an n8n transcript-synthesis workflow, and handed source-grounded insights to Pier's technical cofounder.

  • User interviews
  • Requirements synthesis
  • Customer intelligence
Read case study

Case study

Building a CRM and Automation Layer

I built a CRM and automation layer so the team could keep up with a growing volume of meetings, leads, names, and follow-ups without relying solely on memory and scattered notes.

  • Sales operations
  • Workflow automation
  • CRM design
Read case study

PM responsibility

Workflow mapping and AI release readiness

Workflow mapping, QA, release-readiness judgment, agent-assisted validation, and human review gates.

PM responsibility

Execution cadence and cross-functional translation

Agile rituals, Linear ownership, founder-team translation, stakeholder communication, and source-of-truth updates.

PM responsibility

Product surfaces and market depth

Prototypes, demo surfaces, marketing website code ownership, market validation, commercial analysis, and capital-facing proof.

Case study

Campaign Attribution Tool

I turned repeated campaign link creation into a small internal tool so attribution stayed consistent before reporting depended on it.

  • Workflow design
  • Product instrumentation
  • Marketing operations
Read case study

Case study

Structuring a 48-Hour Public-Sector Bid

We had roughly 48 hours to structure and submit a custom public-sector bid for a 15,000-application program, so I used AI-agent workflows and git-managed business docs to help move the work from concept to submission.

  • Commercial strategy
  • Financial modeling
  • Scenario analysis
Read case study