B2B trade marketplace connecting businesses, brokers, agents, and providers across payments, energy, finance, and logistics — with escrow-backed contract settlement.
B2B trade in the target sectors runs on relationships, opaque pricing, and trust gaps that delay deals and dispute resolution. The brief was a marketplace where multi-role participation, structured tender workflows, and on-platform escrow turn handshakes into auditable contracts without forcing users into a single rigid role.
Owning the full stack: Next.js 16 App Router with strict TypeScript, NextAuth 5 with role-based access (Business, Broker, Agent, Provider, Admin), Prisma 6 over Postgres with a domain model covering tenders, bids, contracts, escrow states (Locked, Partial Release, Released, Refunded, Disputed), sectors, and audit trails. Server Actions handle mutations; RSC streams the marketplace and tender browsing.
Five-role permissions matrix, tender/bid/contract/escrow state machines, sector-scoped capabilities — all written before code.
Postgres schema with explicit enums for Role, Sector, TenderStatus, BidStatus, ContractStatus, EscrowStatus.
Server Components for marketplace + tender pages, Server Actions for create/update/dispute, RSC streaming with skeleton states.
State machine for funds movement with dispute hooks, partial release support, and full audit log.
Admin panel for moderation, dispute resolution, and platform-level reporting.
Marketplaces fail when role boundaries blur. The hardest design decision was making the Role enum first-class in the data model and propagating it through every mutation rather than treating it as a session-scoped detail. Escrow followed the same principle — every state transition is named, recorded, and reversible.
Have a project that calls for this kind of work?
Start a project