Case Study

StreamLink Full-Stack Product Build & Research-Led Pivot

WordPress Dev UX Research Product Strategy
Full timeline90 days
Pivot triggerWeek 3 research
Decision cycle3 days to approval
My rolesProduct · UX · Dev
StackWP + WooCommerce + Stripe
StatusActive beta
Beta testing — active · 3 tested · 15 queued · nav refinements in progress
StreamLink dashboard — hero view
The Problem

Something was broken. I just didn't know what yet.

Working with independent creators as a content strategist, I kept watching the same pattern play out. Talented creators — consistent, passionate, putting in the work — were stalling out. Not because their content was weak. The platforms weren't built for them.

Creators with more time & money to dedicate to marketing got 10x more subscribers & ultimately more revenue for it. Everyone else? Lost in the noise.

The real question: was this a strategy problem, a platform problem, or both? Both. One was a resource gap. The other was structural: mainstream platforms were built to reward the already-famous.

So I asked the question: could there be another way? StreamLink was the answer. Or so I thought.

90-Day Arc

How it actually went.

Product direction change — stakeholder-approved in 3 days

We weren't building the wrong product because of bad planning. We just hadn't done enough research yet.

Week 3 surfaced a finding we couldn't ignore. Creators weren't looking for a better streaming platform — they were drowning in fragmented data across the platforms they already used. Patreon. YouTube. Twitch. Discord. Each with its own dashboard. Its own metrics. Its own incomplete picture.

The real problem was synthesis, not streaming.

Three days after presenting findings to stakeholders, we had majority approval: deprecate the streaming platform concept, build a smart fan intelligence dashboard instead. The original build didn't fail. It was always a research artifact. It just took 21 days to know that.

Research

What we were looking for vs. what we found.

  1. Creator interviews Talked to independent creators averaging under 2,000 subscribers. Algorithm invisibility came up immediately as the primary growth blocker, not content quality.
  2. Competitive platform audit Dug into YouTube, Patreon, Twitch & TikTok. One gap kept surfacing: no unified view of cross-platform performance. Creators were flying blind.
  3. Patron-side research Talked to active subscribers to understand what drove loyalty. Exclusive content & direct creator relationships indexed highest. But creators had no reliable way to identify their most loyal patrons across platforms.
  4. The Week 3 finding Deeper probing revealed the real friction: creators were manually toggling between YouTube Studio, Patreon, Twitch analytics & Discord with no unified picture of their audience. The platform wasn't the problem. The visibility gap was.
Creator interviews Think-aloud protocol Competitive audit Patron research Usability benchmarking
The Product

What we built instead.

A cross-platform fan intelligence dashboard. Connect Patreon, YouTube, Twitch & Discord and see every meaningful creator KPI in one place. No tab-switching. No manual reconciliation. Six features — every one traced directly back to something a creator told us in research.

StreamLink — Fan Insights view
  1. Fan IntelligenceAnalyzes engagement patterns across all connected platforms. Surfaces most loyal superfans & at-risk supporters automatically.
  2. Loyalty ScoringEvery fan scored on cross-platform engagement history. Top supporters identified without manual cross-referencing.
  3. Personalized EngagementSmart suggestions for shoutouts, rewards & content based on behavioral data, not guesswork.
  4. Content Strategy ToolsOptimal posting times, resonant topics & format performance from unified cross-platform data.
  5. Growth PredictionsRevenue forecasts, subscriber trends & engagement trajectories via predictive analytics across all connected platforms.
  6. Cross-Platform Unified InboxAll fan interactions in one place: Patreon comments, Discord messages, YouTube replies & Twitch chats. The feature creators asked for most.
WordPress + PHP WooCommerce Subscriptions Stripe Figma Claude Code ACF + CPT
Personal challenge · 10-day build

Custom theme. WooCommerce. Stripe. Three investor-ready pages. Solo. From scratch.

I set a personal constraint on Day 30: ship an investor-ready build in 10 days. No page builder, no starter theme. Custom PHP templates, functions.php, ACF custom post types, component-based CSS built to the new dashboard direction. WooCommerce configured for single-tier pricing. Stripe in test mode.

I wanted to know what one person could actually ship under real constraints with a lean setup. Turns out: a lot.

StreamLink — investor-ready pricing page
  1. Custom WordPress theme from boilerplate PHPFull front-end from scratch: header.php, footer.php, functions.php, ACF custom post types, component CSS from Figma design system.
  2. WooCommerce subscription setupSingle-tier subscription ($97/mo · $997/yr). Stripe test-mode processing. Branded email templates.
  3. AI-assisted debuggingUsed Claude Code throughout to cut root-cause identification time on PHP conflicts. Estimated 40% reduction in debugging cycles vs. traditional trial-and-error.
  4. Mobile-first validationAll pages tested across mobile, tablet & desktop before investor walkthrough. Lighthouse audit completed.
Outcomes — Current State

Where we are right now.

Beta testing — active · 3 tested · 15 queued
3

Users who've tested the live platform in structured sessions

100%

Hit the same navigation friction. Unanimous. Unprompted.

15

More users queued via organic word-of-mouth interest

!

Navigation friction — every single user

All 3 users hit it independently. Nobody was prompted. Nobody completed cross-screen flows without hesitating. That's the kind of signal you can't argue with — it's already driving an IA review before cohort 2 onboards.

3 of 3 · 100% consensus · IA review in progress
✓

The concept landed

Navigation friction aside, all 3 users got it immediately. The unified dashboard idea resonated. Nobody questioned whether the problem was real. They questioned how to get around in the product. That's a fixable problem.

Qualitative · 3 of 3 · concept validation confirmed
→

Word-of-mouth is already working

15 users expressed beta interest after connecting with initial testers. No formal outreach campaign. Organic. Pre-launch. Worth noting.

15 queued · organic referral · onboarding pending nav fix
Nav restructureIn progress

IA review underway, ships before cohort 2.

Beta cohort 2Queued

15 users ready, formal sessions begin post-fix.

Platform buildLive

WordPress, WooCommerce & Stripe operational.

Investor readinessReady

Full demo available today.

Reflection

What this project is really about.

The most important moment in this project isn't the 10-day sprint. It isn't the custom build or the WooCommerce architecture.

It's Week 3 — when research surfaced a finding that contradicted everything we thought we were building, and I had the discipline to follow the evidence instead of defend the plan.

A research process that changes the product isn't a failure. That's working exactly as designed.

StreamLink exists in its current form because of that finding. Not despite it.

Research-led pivot Solo full-stack build Stakeholder alignment Beta-validated Investor-ready
No fabricated outcome metrics in this case study. All figures reflect actual beta sessions. Quantitative KPIs will be populated after the 15-user cohort completes.

Want someone who ships smart under real constraints?

Let's talk →