Selected work

Flagship 01 / Client product build

From AirBTC to a stay worth holding onto.

A Bitcoin-native travel idea evolved into a broader global marketplace, connecting the guest experience with the operational system required to run it.

hodlstay.comClient project · Live
HodlStay global booking marketplace homepage

The premise / More than a booking page

A marketplace is the customer experience and the machinery behind it.

The visible product only works when inventory, trust, availability, payment state, partner supply, and operator decisions agree. HodlStay was shaped around that whole system.

AirBTC → HodlStay

Change the frame.
Keep the signal.

01

Reframe

Move beyond the niche without erasing the roots.

AirBTC had a distinct community and a clear Bitcoin origin. The product direction evolved into HodlStay: a broader premium travel proposition with Bitcoin-friendly booking built into the experience rather than treated as the whole experience.

02

Rebuild

Treat every side of the marketplace as one product.

Guest discovery, stay dossiers, host onboarding, calendars, booking requests, payment state, reviews, and internal operations were shaped as one connected system instead of a collection of isolated screens.

03

Transfer

Build toward ownership, not dependence.

The engagement is a client product build prepared for handover on completion. Product decisions, operating logic, launch preparation, and documentation are structured so the client can own what comes next.

Product architecture / One operating view

One product.
Five connected systems.

Every surface is designed around the state changes and responsibilities on both sides of the marketplace.

01

Guest discovery

Destination, date, guest, category, and inventory paths that lead into a credible stay decision.

02

Stay dossier

Property story, media, host context, availability, fiat and sats pricing, and booking entry in one surface.

03

Host operations

Onboarding, listings, calendars, booking responses, reviews, payouts, and the operational views behind them.

04

Booking and settlement

Availability checks, acceptance state, BTCPay checkout, verified webhooks, settlement, and payout records.

05

Inventory and migration

Native supply, eligible partner inventory, iCal blocks, and legacy records reconciled into the launch system.

Depth over decoration

Four hard problems, connected.

01

Unified inventory

One discovery layer can present native HodlStay supply alongside eligible HotelPlanner and Dtravel partner inventory.

02

Availability safety

Imported iCal blocks, manual host blocks, and internal bookings are checked together to reduce double-booking risk.

03

Bitcoin payment lifecycle

Host acceptance connects to BTCPay checkout, signed webhook verification, booking settlement, and a traceable payout record.

04

Operational migration

Legacy WordPress and founder spreadsheet records are reconciled into a structured launch pipeline with explicit exception handling.

MaydaLabs contribution

One accountable build partner across the product.

This is client work, not a MaydaLabs-owned venture. The role is to shape, build, prepare, and hand over a product the client can operate and continue.

Product
Strategy, information architecture, release shaping
Experience
Brand evolution, UX, interface system, responsive behavior
Engineering
Marketplace application, data, payments, partner integrations
Operations
Host and guest lifecycles, migration, launch preparation
Engagement
End-to-end client build, prepared for handover
Open for new client work

Have a product with this much complexity?

Bring the messy system.
We will find the signal.