Labor
A trust-critical platform that connects agricultural producers and contractors, enabling direct discovery and service publishing.
2026
Role
Product Designer / Design Engineer
Duration
2 months
Team
Product Owner, Designer (me), Developer (for weekly consulting)
Labor is a 0→1 marketplace MVP built to validate whether a fragmented agricultural service market could be transformed into a structured digital interaction model.
Built in 2 months, the MVP centered around one core loop:
Publish service → Discover providers → Initiate direct contact
With early validation metrics defined with the client to assess whether this loop generated real engagement.
My Responsibilities
Vibe-coded implementation
Built 50% of all production features and layouts directly in code.
Complete UI system
All screens and UI patterns designed in Figma.
Product architecture
Core domain model, flows, and interaction loop definition.
Service taxonomy
Information structure and category logic for discovery.
Validation metrics
Defined early activation signals with client marketing.
AI-assisted workflow
Used AI for copy, technical exploration, and iteration speed.
Vibe-coded implementation
Built 50% of all production features and layouts directly in code.
Complete UI system
All screens and UI patterns designed in Figma.
Product architecture
Core domain model, flows, and interaction loop definition.
Service taxonomy
Information structure and category logic for discovery.
Validation metrics
Defined early activation signals with client marketing.
AI-assisted workflow
Used AI for copy, technical exploration, and iteration speed.
The Problem
Hiring agricultural services in Argentina is still fragmented and informal. Producers struggle to find reliable services, while contractors lack visibility and consistent demand.
Strategic Alignment
Through collaborative sessions with the founding team, we aligned on four strategic decisions that shaped every design and product choice.
Prioritizing problem-solution fit over monetization
Rather than building revenue mechanisms early, we focused entirely on trust signals and core utility — proving the platform's value before extracting it.
Fluid participation model
Instead of forcing users into a fixed role, we designed a flexible architecture where context determines whether someone is a producer, contractor, or both.
Design for technical feasibility & speed
We scoped the MVP to what the stack could support — Clerk for auth, Vercel Blob for media, and Google Maps for location — without sacrificing the core experience.
Validation-centric metrics
Success was defined by activation signals: listing creation, contact initiation, and return visits — not vanity metrics.
The Solution
Labor is a fluid participation marketplace where agricultural producers and contractors discover and connect directly. A guided publishing flow with service & location-based discovery and a lightweight trust loop designed to validate the product core before scaling.
Unified publishing
A guided flow that adapts to the user's intent — whether publishing a service offering or searching for one — from a single shared entry point.
- Single shared home as entry point
- Role defined contextually, not pre-selected
- Conditional fields with trust-oriented UX guidance
Location & service-driven discovery
A relevance-first architecture anchored in user location, ensuring results are immediately actionable for people working in specific regions.
- Pre-filtered by user context
- Hierarchical service taxonomy
- Direct contact externalized to validate real interaction
Lightweight trust loop
A set of lightweight signals that help users make confident decisions without requiring platform-mediated guarantees.
- Service imagery (up to 3 photos)
- Guided service descriptions
- Peer reviews surfaced on profile
