Hiring
Matching, applications, invitations, interviews and offers connected as one stateful flow.
CASE STUDY · MARKETPLACE · 2026
ZORVENAQ
A freelance marketplace built around hiring, contracts, milestone delivery, internal finance, disputes and role-based administration.
SYSTEM ARCHITECTURE
01Product UIClient and freelancer flows across matching, applications, contracts and workspaces
→02Application logicNext.js and TypeScript rules controlling state transitions and product behavior
→03Data & accessSupabase/PostgreSQL, authentication, relational state and role-based permissions
→04OperationsFinance verification, disputes, reviews, auditability and administrative controls
THE ENGINEERING CHALLENGE
A marketplace is a network of dependent states, not a collection of pages.
Matching, offers, funding, contracts, milestones, reviews, disputes and permissions all affect one another. A state transition in one system can change what another user, wallet or admin role is allowed to do.
I structured the product around explicit workflows and operational states, then iterated on the interface and implementation so both users and administrators could understand what happens next.
CORE SYSTEMS
Contracts
Commitment, milestones, workspace activity, QA and delivery health across the contract lifecycle.
Finance
Deposits, internal wallet balances, locked funds, withdrawals, transaction IDs and auditability.
Governance
Role-based administration, disputes, appeals, reviews and controlled operational actions.
ESCROW STATE MODEL
01funded
02locked
03submitted
04approved
05released
The product also handles disputed and refunded paths, permission-aware finance actions and transaction traceability so money movement stays tied to contract state.
TECH STACK
Product interfaces, route structure and responsive user workflows.
Typed product logic across contracts, finance states, permissions and UI behavior.
Authentication, relational data, application state and secure access patterns.
Local environment support, deployment workflows and production-oriented iteration.
WHAT I BUILT AROUND
Clear end-to-end transitions from matching and offers through contracts, delivery and completion.
Role-based access across super admin, finance, support, moderation and operational review.
Wallet, deposit verification, locked funds, withdrawals, transaction uniqueness and audit logs.
Edge-case testing, failure review and iteration across multi-step user and admin workflows.
NEXT CASE STUDYNAQSHA ↗