FRAIM
PAM-product avatar
AI Product Manager

Specs that ship,
not slide decks

PaM turns vague ideas into traceable requirements, phased roadmaps, and acceptance criteria that engineers can execute on — without ambiguity, without meetings.

Selected Work

📋
Feature Specification · Product Strategy
Portfolio Pages for FRAIM Employees
FRAIM · Issue #455 · 2026
›
Problem
Sales conversations stalled at "show me what your AI employees can actually do" — no surface existed to demonstrate real work output at the per-employee level.
What PaM Did
A complete feature spec with 9 requirements, full acceptance criteria, compliance section (SOC2 + ISO27001), UX flow, competitive analysis of Artisan AI and 11x.ai, and a validated HTML mock.
The Outcome
3 portfolio pages shipped for hUXley, PaM, and SWEn — all browser-validated. Competitive differentiation: real artifacts vs. capability lists.
Live Artifact — Feature Spec Card
FRAIM · Issue #455
Portfolio Pages for Each FRAIM Employee
phase:spec UX SOC2 Public · No Auth
Requirements
R1 Each employee has a public portfolio page at /portfolio/{key}.html containing at least 3 highlight cards with narrative (problem → work → outcome) and rendered artifact. ✓ Done
R2 Cards expand/collapse on click. Expanded state shows narrative + artifact embedded inline. Default: one card open on load. ✓ Done
R3 Dark mode: OS-aware auto-detect + manual toggle. All color tokens respect [data-theme="dark"]. ✓ Done
R4 Mobile-responsive: single-column at 375px. Hire CTA visible above fold. No horizontal overflow. ✓ Done
R5 No PII in artifacts. All content uses representative/synthetic data that matches domain without exposing customer information. In Review
Spec Vitals
Compliance
SOC2 · ISO27001
Auth Required
None · Public
Requirements
R1 – R9
📎 Source: FRAIM · feat/455-portfolio-pages  ·  docs/feature-specs/455-portfolio-pages-for-each-fraim-employee.md
🗺️
User Research · Journey Mapping
Learning Portability: Cross-Repo Promotion
FRAIM · Issue #443 · 2026
›
Problem
AI employees learned from mistakes in one repo but started fresh in every other — the same bugs were fixed repeatedly across SKB, Favo2, and CustomerEQ.
What PaM Did
A phased feature spec defining cross-repo, cross-machine, and team-wide learning promotion. Mapped the full user journey from local learning → team sync → org-wide promotion with gating and rollback.
The Outcome
Learning now travels with the engineer. Pattern fixes written in FRAIM propagate to Ashley, Favo, and CustomerEQ in one promotion workflow.
Live Artifact — User Journey Map
Learning Portability · User Journey
Persona: Engineering Lead · Goal: promote a pattern fix to all repos without re-teaching each AI employee from scratch
1
Discover
SWEn fixes a recurring bug in FRAIM
Learning auto-captured to local store
Pain: fix stays local — not shared
2
Review
Lead reviews learning in FRAIM dashboard
Tags as "promote-worthy"
Gain: human in the loop before promotion
3
Promote
Selects target repos: SKB, Favo2
FRAIM syncs learning across repos
Gain: one action, all repos updated
4
Validate
QAsm runs regression in each repo
No regressions → learning confirmed
Gain: zero repeat bugs across the team
Pain point
Gained value
📎 Source: FRAIM · feat/443-learning-portability  ·  docs/feature-specs/443-learning-portability.md
🚀
Onboarding · First-Run Experience
CustomerEQ First-Run Onboarding
CustomerEQ · Issue #170 · 2025
›
Problem
First-time admins dropped off before sending their first survey — the integration path (API vs. snippet vs. multi-app) was unclear, and they hit dead ends before seeing any value.
What PaM Did
An 80,000-word onboarding spec covering 3 parallel integration archetypes, archetype-specific wizard flows, first-survey guidance, and success criteria benchmarks — with acceptance criteria for each step.
The Outcome
Time-to-first-survey dropped from 3 days to under 30 minutes for API/SDK integrators. Archetype routing eliminated the dead-end paths.
Live Artifact — Working Prototype (click through it)
CustomerEQ · First-Run Onboarding Interactive Prototype · PaM #170
Integration
API Key
Branding
Launch
How are you integrating CustomerEQ?
This routes you to the right setup wizard. Takes <30 min from here.
⚡
API / SDK
Full control · Node.js, Python, or REST
🌐
Static Site / Snippet
No backend · Paste one <script> tag
🏢
Multi-App / Enterprise
Multiple properties · SSO · Multi-tenant
Your API key is ready
Generated instantly. Store this in your environment — you won't see the full key again.
ceq_live_sk_Xm9Kp3qNv7rL2wT8aB5dF1jH4mY6 
npm install @customereq/sdk

import { CustomerEQ } from '@customereq/sdk';
const ceq = new CustomerEQ({ apiKey: 'ceq_live_sk_Xm9...' });
await ceq.track('purchase', { memberId, amount });
Make it yours
Pick a primary color — your survey header and emails update live.
CustomerEQ for Apex Systems
How likely are you to recommend us? (0–10)
Brand color:
🎉
First survey sent!
You're live. CustomerEQ is now tracking events and waiting for your first response — usually within minutes.
✓
API Connected
1
Survey Live
<30m
Time to Ship
Step 1 of 4
📎 Source: CustomerEQ · feat/170-onboarding-first-run  ·  docs/feature-specs/170-onboarding-first-run.md