Built
Start with three cases: employer onboarding from requirements through release, customer research built from more than 100 conversations and interviews, and a pilot test that changed the roadmap and positioning. The full library is grouped by product-management responsibility below.
Selected product work
These cases show employer onboarding, customer research, and a revised pilot test.
Product episode
Pier lets employers create an opening, invite candidates to an AI-assisted interview, and review the evaluation before making a hiring decision. I defined signup requirements, designed the flow and error states, worked with engineering, and tested the experience before release.
Result: released onboarding and partner guidance that matched the paths I tested.
Open case studyProduct episode
Across more than 100 customer conversations and user interviews, I designed and ran a process that turned transcripts into traceable inputs for the technical cofounder's product decisions.
Result: a repeatable research process for product, positioning, and MVP feature decisions.
Open case studyProduct episode
When pilot-partner responses stalled, I asked a trusted friend and a strategic advisor to test the employer setup and share flow. Their feedback changed our roadmap, engineering work, and product positioning.
Result: we used feedback from two outside testers to make specific product decisions while the pilot partners remained a separate path.
Open case studyWider proof library
Review ownership, roadmap work, customer research, workflow design, quality assurance, team coordination, prototypes, and market research.
PM responsibility
Customer-facing AI workflows, workflow design, quality assurance, customer communication, and launch preparation.
Case study
I narrowed a broad procurement idea into a specific subcontractor-activation workflow, so we could test the idea without claiming the product could approve work on its own.
Read case studyCase study
I reviewed buyer and investor messages about the construction test. I removed claims the product could not support and made clear that people, not the tool, made final decisions.
Read case studyCase study
I turned a one-off validation push into an auditable playbook where an AI agent could do structured validation work while I stayed PM and human in the loop.
Read case studyCase study
When pilot-partner responses stalled, I asked a trusted friend and a strategic advisor to test the employer setup and share flow. Their feedback changed our roadmap, engineering work, and product positioning.
Read case studyCase study
I designed discovery KPIs so Pier's customer conversations measured learning velocity instead of outreach volume.
Read case studyCase study
I kept product evidence, customer signal, validation work, and capital-facing decisions in one operating loop.
Read case studyPM responsibility
Sole PM ownership, roadmap shaping, backlog tradeoffs, and prioritization under constraint.
Case study
I owned the product-management function around Pier inside a small founder team: discovery, roadmap, prototypes, QA, rituals, demos, and engineering-priority translation.
Read case studyCase study
I used customer research to plan Pier's January 2026 launch, including small-business positioning, candidate value, website copy, and MVP scope.
Read case studyCase study
I managed Pier's backlog by tying work to decision value: product evidence, customer learning, pilot readiness, value-map truth, and commitment confidence.
Read case studyCase study
I built a competitor model that turned a list of companies into a clearer view of who we were really competing with, how they differed from us and from each other, and what those differences meant for our business.
Read case studyPM responsibility
User interviews, customer intelligence, KPI design, pilot demos, feedback loops, and partner learning.
Case study
Across more than 100 customer conversations and interviews, I designed and ran a process that summarized findings for Pier's technical cofounder.
Read case studyCase study
I designed discovery KPIs so Pier's customer conversations measured learning velocity instead of outreach volume.
Read case studyCase study
When pilot-partner responses stalled, I asked a trusted friend and a strategic advisor to test the employer setup and share flow. Their feedback changed our roadmap, engineering work, and product positioning.
Read case studyCase study
I designed the employer signup flow and error behavior, handed the experience to engineering, then ran first-time and returning-employer QA through release.
Read case studyCase study
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.
Read case studyPM responsibility
Workflow mapping, quality assurance, AI-assisted validation, and human review steps.
Case study
I narrowed a broad procurement idea into a specific subcontractor-activation workflow, so we could test the idea without claiming the product could approve work on its own.
Read case studyCase study
I reviewed buyer and investor messages about the construction test. I removed claims the product could not support and made clear that people, not the tool, made final decisions.
Read case studyCase study
I turned a one-off validation push into an auditable playbook where an AI agent could do structured validation work while I stayed PM and human in the loop.
Read case studyCase study
I built a human-in-the-loop agent workflow that ran a procurement market validation test and proved a reusable way to test future customer and market questions.
Read case studyCase study
I built a second brain workflow that turns my thoughts into a searchable, reviewable queue for decisions and action.
Read case studyPM responsibility
Agile routines, Linear ownership, founder-team communication, and updates to shared product documents.
Case study
I own the operating cadence around Pier: Linear hygiene, standups, mid-days, end-of-days, planning closure, and written owner decisions.
Read case studyCase study
I kept product evidence, customer signal, validation work, and capital-facing decisions in one operating loop.
Read case studyCase study
I built an n8n workflow that turned investor updates from a multi-day manual process into a one-hour review-and-approve loop.
Read case studyPM responsibility
Prototypes, demos, marketing website code, market tests, commercial analysis, and fundraising materials.
Case study
I used prototypes, website surfaces, and demo paths to make Pier's product direction concrete enough for customers, partners, and engineers to evaluate.
Read case studyCase study
I personally shipped production code for Pier's marketing website and the SmartApply partner guide used in external testing and partner work.
Read case studyCase study
I turned repeated campaign link creation into a small internal tool so attribution stayed consistent before reporting depended on it.
Read case studyCase study
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.
Read case study