Marketplace and operations
PariJobs
A mobile-first MVP to request, agree, document, and close in-person services with clear trust signals.
- Responsibility
- Product, design, architecture, and full-stack development
- Period
- 2026 - present
- Client
- Producto propio
The problem
Validating a local marketplace required more than a contact directory: identity, traceability, evidence, agreements, and economic control had to live in one flow.
The solution
I developed the application with Next.js, PostgreSQL, Prisma, and Docker. It includes authentication, roles, profiles, service requests, invitations, evidence, claims, protected payments, administration, and an auditable economic simulator.
Outcome
The result is a functional MVP with real client, worker, and administration flows, ready to test the operating model before scaling acquisition or external payments.
What I owned
- Operating model definition
- Responsive design and trust system
- Authentication, roles, and requests
- Payments, evidence, claims, and administration
- QA, documentation, and deployment
Deliverables
- Responsive web MVP
- Client and worker panels
- Administration panel
- Economic simulator
- Functional specification and technical architecture
Technology
