All projects
Collaboration platform2025Product work · employed

A marketplace where creative work and payment live in one place

A collaboration platform connecting influencers with designers and video editors — submissions, revisions, deliveries and payments handled in a single workflow.

Alpha Factory interface

Influencers needed editing and thumbnail work. Designers and editors needed a steady stream of briefs they could actually manage. Both sides needed to get paid without leaving the platform or trusting each other first.

Alpha Factory brings all three into one workflow. I built the full-stack platform.

The influencer workflow. Upload video content, request editing and thumbnail design, track progress, talk to the assigned designer or editor, and receive the final files — without an email thread anywhere in the process.

Designer and editor dashboards. A separate view for the people doing the work: accept requests, submit drafts, handle revisions, and deliver. Each role sees the tools for its own job and nothing else.

Payments. PayPal and cryptocurrency payments covering project fees, with secure checkout, payment tracking and transaction history visible to both sides of the exchange.

Admin panel. User management, project monitoring, approvals and dispute handling — the tools that keep a two-sided marketplace running when something goes wrong.

File handling. Secure upload, storage and validation for large video files and thumbnails, with Prisma modelling the data underneath.

Interface. A responsive, role-based UI in React and Next.js, with real-time status so nobody has to ask where a project stands.

The code belongs to Alpha Factory. This is the design underneath it.

Four roles against one database. Influencer, designer, editor and admin all read and write the same tables; what separates them is a role on the session that is checked on the server for every request. Each dashboard is a different view of the same project rows, not a different application.

Influencer — writes the brief, reviews the delivery, approves it and releases payment, and can open a dispute.

Designer or editor — accepts a brief, submits drafts and revisions, delivers, and can open a dispute. Cannot approve their own work.

Admin — resolves disputes, refunds and suspends. Cannot do the work or approve on a user's behalf; moderation is not a way around the workflow.

A project is a state machine, and the money follows it. requested → accepted → draft submitted → revision → delivered → approved → paid, with disputed reachable from any state after acceptance. Keeping that progression in one place is what makes the two-sided part work: every permission question — can this user upload here, can this one be paid — is answered by the state the project is in and the role asking, rather than by a condition written separately into each screen.

Payments are recorded as transactions, not as a flag on the project. PayPal and crypto settle differently and at different speeds, so each payment is its own row with its own status and provider reference. The project asks the transaction whether it is paid; it never stores the answer itself.

No screenshots: the platform is Alpha Factory's, and every view is full of real users, briefs and payments. What the panel existed to do:

Keep the marketplace moving. Every project in every state on one screen, filtered by what is stuck — a brief nobody accepted, a draft waiting on a review, a delivery that was never approved. In a two-sided market the stalled rows are the ones that cost money on both sides.

Settle disputes. A dispute opens with the project attached: its history, its files and both sides' messages, so a decision is made on the record rather than on whoever emailed first. The outcome writes back to the project state and, where money is involved, to the transaction.

Reconcile payments. Transactions listed with their provider and reference, because PayPal and crypto settle at different speeds and "he says he paid" has to be answerable from the platform, not from a screenshot a user sends.

Manage people. Accounts by role, with suspension for the cases that need it.

The constraint I kept: an admin can unblock the workflow, but cannot stand inside it. Moderation resolves disputes, refunds and suspends — it never approves a delivery or submits work on a user's behalf. The moment support can act as a party to a transaction, the audit trail stops meaning anything.

Large video never passes through the application server. Uploads go to object storage directly, and the platform stores the reference, the validation result and who may read it. Prisma models the rest — users, roles, projects, revisions, deliveries, transactions and disputes — so the relationships that decide access are declared in one schema rather than implied across queries.

Coordinating four user roles against one shared database, while money moves between two of them, is a design problem before it is a coding problem. Deciding what each role can see and do — and making the interface reflect that without feeling restrictive — was the work that mattered most.

05 — Contact

Open to full-time full-stack and frontend roles — in Riyadh or remote — and to freelance builds. The quickest way to reach me is email; I reply to everything.