A vision for 503's next chapter — more bookings, a stronger brand, and a platform that handles everything without you having to.
"I was glued to my phone."
— Danny, on managing bookings across 100+ propertiesThere's no way for a client to check availability, request a date, or confirm a booking on their own. Every transaction requires a human in the loop — and that human is almost always Danny or his assistant.
A chunk of bookings come through Peerspace and Gigster — platforms that take a cut and own the client relationship. Every booking there is a booking that didn't happen on 503's own turf.
503 is built on a Luxury Presence real estate template. It looks like a property listing service. For a brand with this portfolio and this reputation, that's leaving real money on the table.
The API is already built. The booking system, calendar, HubSpot integration, pricing engine, add-ons — it all exists. The new site is the front end it's been waiting for.
Date, time, guests, booking type — clients complete the full request without a phone call. The widget connects directly to the existing API.
HubSpot and the calendar system are already tracking when properties are booked. The site surfaces that — no double-booking, no back-and-forth to confirm a date.
Purpose, budget, guest count, requested add-ons — all collected before anyone sends a message. Danny's assistant handles qualified requests, not intake forms.
Bookings from the site, Peerspace, and Gigster all flow into the same system. One calendar, one pipeline, one place to manage it all.
100+ premium properties, years of five-star reviews, a portfolio that spans rooftops to estates. The site should feel like that.
Every property page still leads with the shot that sells the space. The images don't go anywhere — they finally get a frame worthy of them.
Serif display type, obsidian backgrounds, gold accents. The visual language of a premium brand — not a listing platform.
Every property looks like it belongs to the same brand. Specs, amenities, booking widget — the same structure, every time.
When a production coordinator Googles 503 DTLA, what they find should close the deal before they even make contact.
No platform fees. No support tickets to change a photo. No limits on what you can build next.
A clean content admin means Danny's team can swap photos, update copy, adjust pricing, or publish a new listing without opening a ticket.
Every constraint you've hit on the current site is a constraint their platform built in. The rebuild removes the ceiling entirely.
Everything managed in a single place. No more switching between the site CMS, HubSpot, and third-party platforms to get a complete picture.
New property type, new market, new membership tier — these become configuration changes, not rebuilds.
Brooklyn and Manhattan aren't aspirational — they're live. Both markets already have membership pages and active Stripe links. The rebuild makes them real destinations.
100+ property pages need their photos, descriptions, specs, and add-on options moved from the current site into the new system. It's the biggest lift of the project — and it's a one-time job. Once it's done, the new admin makes every future update easy.
The API, HubSpot connections, and calendar logic are already built. The work here is connecting the new front end to that existing infrastructure — not building it from scratch.
A new visual identity, a new component system, a new property page template, a booking widget, and a content admin. Scoped, scheduled, and delivered in phases so the site can launch with the core and grow from there.
The rebuild doesn't create that — it finally shows it.
If this direction feels right, the next step is a full scope and timeline. Everything above gets defined, sequenced, and delivered — starting with what moves the needle fastest.