Property marketplaceOwn product · pre-launch
Real Estate Patagonia
A property marketplace for Patagonia, covering homes, commercial property and land across the Argentine and Chilean sides of the region. The landing page is live and collecting interest, and the marketplace behind it is not yet public.
Visit the project (opens in a new tab)- Role
- Own product: architecture and full stack
- Year
- 2025
- Status
- Live
- Stack
- Full stack
- i18n
- Next.js
- PostgreSQL
- Mercado Pago
The brief
Open for interest before the listings are ready
The goal is one place where anyone can browse homes, commercial property and land, with everything listed drawn specifically from Patagonia, on both the Argentine and Chilean sides of the region. The marketplace, mostly built but not yet public, is a single Next.js app: search with filters for location, property type, price, bedrooms and extras such as a pool, listing pages with galleries and maps, agent and buyer profiles, and a paid flow that lets agents publish a listing.
Rather than wait for the marketplace to be finished, I launched a landing page first and started collecting interest: a form with schema validation and a reCAPTCHA check on the server, leads flowing into Airtable, and the SEO groundwork already in place (structured data, a sitemap, and a file that tells AI crawlers what the site is about). Every other route points to the landing page until the marketplace opens.
Underneath, one schema defines the data model and its access rules for users, agents and admins (only the owning agent can edit a listing, and an enquiry is visible only to its owner, the listing's agent and admins) and also generates the API specification. Searches live in the URL, so they can be shared and bookmarked, with accent insensitive matching for Spanish place names. Paid listings go through a Mercado Pago checkout that returns agents to the right step of the listing wizard, and photos are resized in the browser before uploading straight to storage.
Outcome
- 18Components in an in-house design system built on Radix
- 3Roles (user, agent, admin), each with its own access rules
- 17Data models in one schema that also generates the API specification