CONTACT
CREATOR PLATFORM · PAYMENTSFEB 2026 — PRESENT

My Persona

A social platform where creators post into niche communities and get paid for it. I gathered the requirements, designed it, and built it.

CLIENT
Black Halo Lab
ROLE
Product Designer & Developer
PLATFORM
Web · Mobile
STACK
Next.js · Supabase · Stripe
RESULTS

Live on its own domain since June 2026, moving real money through Stripe. I designed and built all of it: communities, tips, identity verification, moderation, and creator payouts.

OVERVIEW

Creators build an audience on the big platforms and still have no simple way to get paid for a post.

Black Halo Lab's answer was niches. Not one shared feed, but communities a creator and their fans join together, with the money attached to the post instead of parked behind a separate storefront. I ran the requirements sessions and took the gaps back to them until the answers held. That became the PRD: who signs up, what gates payment, and what a brand sees on a profile.

Payments were the open question. The product needed proof that a creator is a real person, a way to take money from fans, and a way to pay creators out. I recommended Stripe: one integration covers all three. The alternative was three vendors, reconciled by hand.

Design came first, then the build. I split the PRD into epics, then wrote a phased implementation plan for each with its checks written in. I ran those through Claude Code. Nothing shipped without a Playwright pass and a clean build.

Stripe Identity runs an ID and liveness check, and it gates posting as well as getting paid. Stripe Connect handles the payouts. A moderation pass clears every post, comment, and image before it publishes, not after someone reports it. The policy it enforces is safe-for-work, which is what makes brand campaigns possible.

PROCESS
  1. 01 REQUIREMENTS

    Sessions with Black Halo Lab, gaps taken back to them until they held.

  2. 02 PRD

    One spec, 1,105 lines. Everything after it points at a section.

  3. 03 DESIGN

    Screens in Figma and Claude Design, settled before a line of code was written.

  4. 04 PLAN

    The PRD split into epics, each a phased task list with checks.

  5. 05 BUILD

    Claude Code works the plan one task at a time, verifying as it goes.

  6. 06 VERIFY

    Nine Playwright specs, then a clean build. Neither optional before a push.

A FAILING CHECK STOPS THE RUN AND SENDS THE TASK BACK

The loop is the part that matters. Design is settled before the build starts, and no task moves on until its checks pass.
Three steps, and verification is the first. Getting paid is the third thing that happens, not the promise the page opens with.
Three audiences, one screen, no passwords. A fan who lands on the creator tab gets a line at the bottom pointing them at their own.
Two amounts, a custom field, and 200 characters if you want to say why. The button carries the total, so checkout holds no surprises.
The landing page on mobile.
Each step says where it stands and the last one stays locked until the ones before it are done.
Pick the community first, then write. Every check the platform runs happens after you hit Post.
There are no DMs anywhere in the product, and the FAQ leads with it. The inbox is the part of the job creators most want back.
NEXT PROJECT