ProjectCase Study

First Revenue Game

Commercial proof, operator review, and reliable progression

A social execution product that helps solo builders turn one monetizable skill into first-revenue evidence through focused missions, accountable proof, and operator review.

Year2026

ExperienceLive public demo

CategoryEnterprise product + event-driven systems

Next.jsJava / SpringPostgreSQLKafkaOpenTelemetry

Open public demo

ContextThe work

One mission, then proof.

First Revenue Game turns a broad ambition into one commercially specific mission. Progress is earned through submitted evidence and an explicit review loop, so the interface stays accountable to what has actually happened.

The problem

Help solo builders move one monetizable skill toward first revenue without rewarding planning theater, while ensuring that progression changes only when submitted proof supports it.

The user

Solo builders pursuing a first paid outcome, and operators responsible for reviewing commercial evidence and unlocking supported progression.

My role

Independent product direction, UX/UI, Next.js shell and BFF, Java/Spring domain workflow, event reliability, observability, testing, and release evidence

ProofDecisions

The choices that made the product hold together.

Centered the member experience

Centered the member experience on one commercially specific mission, external evidence, and an explicit reject-revise-approve recovery loop.

Migrated the authoritative workflow

Migrated the authoritative workflow one vertical slice at a time, preserving the Next.js product contract while Spring Boot took ownership in the verified mode.

Signed short-lived viewer context

Signed short-lived viewer context across the BFF boundary and enforced role plus resource ownership inside the backend.

Committed workflow state and

Committed workflow state and event intent atomically through a transactional outbox, then made projections idempotent by event ID.

ScreensSelected work

The interface, in context.

First Revenue Game member proof pending review state — The pending state preserves exactly what the operator needs to review.

First Revenue Game operator proof review queue — Member evidence, outcome signal, notes, and supported unlocks stay together.

First Revenue Game operations dashboard — The release story closes on observable workflow health, not only a polished shell.

ReleaseProof and boundaries

What the build makes visible.

Verification

Forty-one Vitest tests and 36 passing Playwright checks cover the product shell, API contracts, responsive behavior, and member/operator workflow.
Thirty-four JUnit and Testcontainers tests exercise the backend against real PostgreSQL and Redpanda services.
The verification harness proves application-to-approval state, BFF reads, outbox drain and recovery, custom metrics, Grafana provisioning, and log privacy.

Limitations

The public demo is deployed in deterministic demo mode; managed persistence, production end-user identity, and the Java service stack are not activated on the public URL.
The demonstrated golden path uses link proof. MinIO file handling is verified separately through permission and storage coverage.
Redis is readiness-checked but owns no product workload, and production SLOs, alert routing, retention, scaling, and incident ownership remain open.

MoreCurrent case studies

Explore the other current projects where product thinking is carried through interface, architecture, testing, and release.