Marketplaces built for trust, transactions, and operations.

Furnished Habitat

Guest search and booking on one side, host records and the operator's transaction workflow on the other.

What the client needed

Guests compare location, dates, property fit, trust, and booking conditions before they book a furnished stay. Hosts and operators keep changing inventory up to date behind that experience.

What we built

• Destination and date search
• Property and host records that carry trust context
• Booking paths for different stay conditions
• Property import, booking-derived availability, and calendar sync with OwnerRez and iGMS
• Date-level rates and minimum stays from PriceLabs, with a fallback when rates go stale
• Payments through Stripe, with payment details kept at the payment provider
• Operator visibility into the transaction workflow

Connected systems

• OwnerRez
• PriceLabs
• iGMS
• Stripe
• Amazon Web Services

The engineering record lists inventory changes, booking exceptions, integration failures, and payment state as work that continues after launch. Routeless does not publish booking or revenue figures for this engagement.

Colombia Bound

Listing data, verified inventory, and a partner directory share one market model.

What the client needed

Property buyers need current local context. Listing volume, duplicate inventory, neighborhood differences, language, and handoffs to service providers make a static editorial site go stale quickly.

What we built

• Weekly analysis of more than 26,000 listing records
• Median pricing for 60 neighborhoods, computed from that analysis
• Scheduled collection, normalization, and verification before data is published
• Verified listings and neighborhood discovery pages
• Relocation services and a bilingual partner directory
• Routing from the public site to the right local partner

Listings and service information that used to be disconnected now sit in one bilingual market layer connecting neighborhood evidence, available property, relocation help, and local partners.

American Dentists

A national directory with one canonical owner per market and practice facts that keep their sources.

The problem it solves

American Dentists is a national guide to dental care, built to give clearer answers than paid rankings presented as recommendations. It had to work nationally while regional brands keep the local pages they are best placed to maintain.

What we built

• Search by location and by care need
• Practice facts stored with their source context
• One canonical page owner for each market
• A multi-brand directory architecture shared with regional brands such as Central Valley Dentists
• Shared practice management across the network

Central Valley Dentists

The regional layer of the same network, routing each patient request to a local office.

The problem it solves

People in Merced look for a dentist by what they need, who takes their insurance, and who picks up on a Saturday. The regional brand needed its own local pages on the shared national platform.

What we built

• Patient matching: a patient describes the need once and is routed to the right local office
• Insurance-aware search
• City and practice pages owned by the regional brand
• Specialty pages
• Medically reviewed plain-English guides written for conventional and AI search