Tour Dash
System map · 4 September 2026

Every moving piece, and how they connect

Tour Dash is no longer a single website. There is a landing page, a waiting list, a signed-in application, three social channels and an email system that ties them together. The front door is about to change: until launch, tourdash.io will show the waiting list rather than the pitch. This is all of it in one place, arranged around that switch.

Live at tourdash.io Backend Supabase Email Resend
01

The switch that is coming

Until Tour Dash goes live, the job of the home page is to collect emails, not to sell a product nobody can sign into yet. So the waiting list moves to the front and the landing page moves to an address you can hand out deliberately.

TODAY AT THE SWITCH tourdash.io the front door Landing page the pitch, a market flown by scroll /waitlist typed, or a link in a bio Waiting list nothing on the site points at it tourdash.io the front door Waiting list name, side of the market, email /preview handed out deliberately Landing page unchanged, just at a new address
02

Everything that exists, in three layers

The pieces stack. A visitor touches the top layer, a member lives in the middle one, and both rest on the same four services underneath. The top layer is drawn as it will read after the switch.

4
Public pages, no account needed
12
Screens once you're signed in
10
Database tables
3
Social channels
WHAT A VISITOR TOUCHES Waiting list tourdash.io — name, side, email Landing page /preview — a market flown by scroll Sign up /signup — agent or vendor Sign in /login — and password reset WHAT A MEMBER USES Agent side Post a job across nine service types, read applicants, hire vendors, track listings Vendor and covering agent Find open work on a live map inside a radius they set, apply, track what they've won Shared by both Calendar, wallet, profile and reviews, settings, plus an internal admin screen WHAT IT ALL RUNS ON Supabase Accounts, 10 tables, storage Mapbox GL Geocoding and radius filtering Resend Every outbound email Cloudflare Pages Hosting for tourdash.io

The amber outlines mark what moved or was rewired this week: the two pages trading addresses, the sign-up flow, and the email layer under all of it.

03

How a lead travels once the waiting list is the front door

Two doors lead in and both end in the same inbox. Somebody who is ready creates an account; somebody who is only curious leaves an email. Either way a row is written and the team hears about it within seconds. After the switch the waiting list is what most people meet, so it becomes the wider of the two doors.

The path a lead takes Traffic that gets them there
REACH PUBLIC PAGE ROW WRITTEN SENT BY LANDS WITH Instagram @tour.dash TikTok @tour.dash YouTube @tourdash_yt Sent a link broker, investor, client Waiting list tourdash.io Landing page /preview Sign up /signup A waiting list row public.waitlist A new account auth.users → profiles Resend noreply@tourdash.io mikegomes@tourdash.io lead alert angelcruz@tourdash.io lead alert The person who signed up confirm your email address
04

The public surface

Four pages a stranger can reach without an account. The two addresses in amber are the ones that trade places at the switch.

PageAddress todayAfter the switchWhat it is for
Waiting list/waitlist/The soft ask. Name, which side of the marketplace, email. The landing scene held at its opening frame.
Landing//previewThe pitch. A real market over Short Hills, flown by scroll, explaining coverage to agents and work to vendors.
Sign up/signupunchangedThe real ask. Agents give a brokerage and licence; vendors give a trade, radius and insurance status.
Sign in/loginunchangedReturning members, plus the password reset.
05

Inside the application

Which side of the marketplace someone signed up as decides their navigation and every query the app runs for them. An agent is never asked for a trade licence, and a cleaner never sees the posting form. None of this changes at the switch.

Agent side

  • Post a job across nine service types, from a showing to an appraisal
  • Read applicants side by side and accept one
  • Hire vendors from a directory of ten trades
  • Track listings and invite vendors straight to one

Vendor and covering agent

  • Find work on a live map, inside a radius they set
  • Apply to anything open near them
  • Track what they've won and what is still pending
  • Carry a profile agents filter by trade, distance and rating

Shared by both

  • Calendar — confirmed jobs land on both parties' calendars
  • Wallet — earnings and transaction history
  • Profile and reviews — the reputation the next match depends on
  • Settings, and an admin screen that only internal accounts can open
06

The email system

Every message the product sends now leaves through Resend on a verified tourdash.io, rather than through Supabase's built-in mailer. That mailer was capped at two messages an hour, which is what made sign-ups fail silently during testing. This matters more after the switch, when collecting emails becomes the whole job of the home page.

PieceSettingWhy it matters
Sending domaintourdash.io, verifiedDKIM, SPF and the feedback address all pass, so mail arrives signed rather than suspect.
Transportsmtp.resend.com port 465Wired into Supabase Auth, so confirmation and password-reset mail uses it too.
From addressTour Dash <noreply@tourdash.io>One sender for both the automatic mail and the lead alerts.
Hourly ceiling60, was 2Testing sign-up repeatedly no longer walls off the account.
Lead alertsmikegomes@, angelcruz@Fired by the database on both a waiting list row and a new account.
The API keySupabase VaultNever in the repository and never in the browser; the trigger reads it at send time.

Recipients live in one place. A single function returns the address list for both alerts, so adding info@tourdash.io later is one line rather than an edit in two triggers.

07

Social channels

Three accounts exist and all three are linked from the foot of the waiting list page. After the switch that page is the home page, so those links sit on the front door.

ChannelHandleAddress
Instagram@tour.dashinstagram.com/tour.dash
TikTok@tour.dashtiktok.com/@tour.dash
YouTube@tourdash_ytyoutube.com/@tourdash_yt
08

Three things to settle before the switch

None of these is a fault today. Each one starts to cost something the moment the waiting list becomes the front door.

1

The waiting list has no way through to sign up

Its only outbound link points at /, which is the landing page today. After the switch that link points at the waiting list itself, and a real agent who arrives ready to open an account has nothing to click. The page needs a quiet route to /signup, or to /preview for anyone who wants to read more first.

2

Mail goes out from an address that has no mailbox

Everything sends from noreply@tourdash.io, but the mailbox that exists is no-reply@tourdash.io, with a hyphen. Sending is unaffected. The one who pays for it is a member who replies to a confirmation email, because that reply has nowhere to land. Either add the hyphenless address or point the sender at the mailbox that already exists.

3

The word changes halfway through

The landing page and the waiting list both say vendor. The sign-up page still asks people to create a contractor account, and the directory inside the app is still called Contractors. A visitor reads one word on the way in and meets another at the moment they commit.