Reasy

Four roles. One app. And a market used to classifieds that no-one trusts.

Rental marketplaces still live on anonymous classifieds, cluttered listings, no accountability, no tools. The brief for reasy was to collapse the whole transaction into one product: a marketplace with Seekers, Partner Seekers (for roommates), Property Owners, and Real Estate Agents, all in the same app, all discoverable through a single compatibility-aware engine.

Each of those roles needed a distinct onboarding flow, a distinct data model, and a distinct set of actions. The app shipped with multi-language and multi-direction layouts built in from day one, swipe direction, chat bubble alignment, progress bars, form focus flow. Not retrofitted. Native.

Verify the human first. Then build the profile around what they're actually looking for.

Trust starts at the first tap. Every reasy user verifies a phone number before anything else, country-code selector with global coverage. The number is bound to the account and used to gate every high-stakes action later: opening a new chat, requesting a tour, publishing a listing.

After verification the profile splits by role. A Seeker describes themselves, single, couple, family, or roommate, with lifestyle preferences baked in (pets, language, notifications, shared account links). An Owner gets a dashboard-style profile instead, with access to Properties, Connections, and Transaction Summaries. Same app, different cognitive surface.

Thirty decisions. Broken into three screens the owner can actually finish.

Listing a property is where most rental apps lose their owners. The reasy flow breaks the work into three ordered steps, each numbered and checkmarked as it completes: Where is the property (city, neighborhood, street, type), Property details (price, rooms, bathrooms, parking, balcony size, amenities, accessibility, roommates permitted), and Display & description (free-text positioning plus up to four photos).

Required fields are pink-ringed with an inline error strip. Long lists collapse to chip pickers instead of dropdowns. The owner sees a visual progress bar at the bottom, and every completed step collapses to a clean Edit / Fix row when they move on. Nothing is saved as draft-and-lost: the listing persists at every step.

A 92% match, then the conversation, with the tour booked inside it.

When a Seeker and an Owner align on budget, area, and lifestyle, the engine surfaces the score at the top of every card, 92% match, not "suggested for you." If the score clears the auto-approve threshold, the connection opens; otherwise the Owner moderates from their Connections tab.

Once a chat opens, it's not a plain messenger. The first message is a structured property card, image, match badge, price, room count, chips for budget/area/lifestyle fit, with two inline actions: Approve appointment and Suggest another time. Tours are persisted to the Diary. After the scheduled time a system message asks both sides "Did the deal close?" If yes, a celebratory modal with a 5-star rating closes the loop, and contract reminders slot straight into the calendar.

The lobby is a curated feed , not a search bar.

Every visible card is already pre-ranked by compatibility. Seekers swipe through Owners; Owners scroll Seekers. Overflow menus unlock Favorites, Report, and a long-press "wait for approval" state that stops accidental double-requests.