Buy Dreams

Buy Dreams is a production real-estate platform built to bring property discovery, internal operations, documentation, collaboration, and property analysis into one system. Roberto built the platform end to end and continues evolving it, including an active migration toward native mobile experiences.

The project started among partners who wanted a long-term business that used the team's professional capabilities. It became more than a listing site: the platform has to structure legal requirements, operational work, documentation, finances, and presentation so properties can be prepared and sold.

Different property types need different documents, permits, and workflows. The team also loads real market references — location, dimensions, and known values — so the system can suggest a preliminary price per square meter. That suggestion is a study aid, not a formal appraisal.

• End-to-end backend and frontend development
• Product and feature design
• Architecture
• Public landing
• Administration platform
• Production deployment
• Technical implementation of requirements gathered by the team
• Active React Native mobile development
• Field and operations work as partner and vice president

• Property discovery and filtering
• Full property files with characteristics, multimedia, maps, and contact forms
• Plans and 360 experiences when they exist
• Property tours and visit scheduling
• Live chat
• Legal and documentary management, including property-type-specific requirements
• Cadastral information, easements, land-use data, municipal alignments, and relevant MOPT/INVU requirements
• Grouped projects that contain multiple properties
• Weekly board, minutes, task assignment, agenda, and meetings
• Contracts and internal finance tracking
• Content management, analytics, and role-based permissions
• Geographic references for preliminary value analysis

A domain that looked like listings became an architecture problem: each property type carries different legal, documentary, operational, and commercial requirements. The work was to represent that reality without making the system unusable for the team.

Astro, Vite, React, and TypeScript on the client, with Firebase for the platform and authentication. Role-based permissions control what each profile can see. Docker and pipelines handle automatic deployment.

The team loads real property references by hand — geographic position, dimensions, and known values. The system uses those references and the subject property's location to suggest a price per square meter.

That output is a preliminary market-study aid. It is not a formal appraisal, and it is not an automated valuation model. The references do not come from an external API.

Complexity arrived as the team discovered the documents, permits, and processes each property type actually requires. The architecture evolved to represent that without making the day-to-day experience harder than it needed to be.

Unit tests, smoke tests, ESLint, and pre-commit checks. Firebase Authentication with roles and permissions by profile. Public-facing files can indicate that a document exists without letting an end user download private material.

The system is in production, used by the team, with properties actively listed.

Native React Native apps are in active development. Native 360 capture is part of the mobile direction and stays planned until implementation is confirmed.

• EurekTicketsEvent ticketing platform
• LaConfiCommerce and operations platform
• MejengónSports match-management and social platform