Operational drag
Admin product upload required too many separate steps for product details, media, and compliance documents.
Case study
Turning marketplace friction into measurable product wins.
At Only Pounds Network, I worked across admin tooling, search, authentication, role-aware profiles, and customer-facing decision pages for a regulated ecommerce marketplace.
Next.js 14TypeScriptReacttRPCPrismaPostgreSQLTailwind CSSAWS S3Playwright
Only Pounds admin
3-step flowProduct basics
Media + COA
Packaging
Search flower, prerolls, farmer inventory...
Farm Bill compliant
S3 media attached
Role scoped
Ready to publish
+59%
relative cart conversion lift
Product-to-cart conversion improved from 3.2% to 5.1%.
-68%
farmer onboarding time
Admin upload flow reduced from 25 minutes to 8.
+22pt
signup completion
Single-page auth flow improved completion from 61% to 83%.
-40/mo
support queries
Packaging page answered repeated pricing questions.
Context
The product problem
A regulated marketplace has more moving parts than a standard shop: farmers need a fast publishing path, customers need discovery and trust, and internal teams need fewer repeated support loops.
Discovery friction
Customers needed faster ways to find relevant product categories and buying options.
Account confusion
Customers and farmers needed different profile experiences without creating navigation mistakes.
Shipped work
What I built
Farmer onboarding rebuilt for speed
Collapsed product capture, media upload, and compliance document collection into a shorter admin path that operators could finish without leaving the flow.
Search tuned for buying intent
Built category and keyword search with debounced filtering and server-side query optimization through tRPC and Prisma.
Role-aware profile system
Designed customer and farmer profiles with role-scoped navigation to reduce account confusion and support tickets.
Packaging page from zero to shipped
Created a self-serve decision page for customers and B2B buyers, reducing repeated support questions around pricing.
Architecture
Engineering evidence
The work connected polished UX to backend systems: typed API calls, Prisma-backed queries, role boundaries, and S3-backed media flows.
01
Next.js UI
02
tRPC procedures
03
Prisma + PostgreSQL
04
AWS S3 media
Interview hooks
Questions worth asking me
These are the parts of the project I would enjoy walking through in a technical interview.
Prompt 01
How I collapsed an 8-step admin upload workflow into 3 steps without losing compliance capture.
Prompt 02
What changed in search when conversion moved from 3.2% to 5.1%.
Prompt 03
How role-scoped navigation reduced reported account errors and support tickets.