The lead marketplace, live

The short version

A lead is the one thing on Tour Dash where the person who posts is the one who gets paid. Every other charge runs poster-pays. This is the first rail where the responder pays, and it has its own checkout, its own release, and its own dispute path because of it.

• There is a way in. The nav item is "Leads" now, not "Buy Leads". The board has a "Sell a lead" button and a Selling tab. The form at /sell is reachable without typing a URL.
• The form has the contact. It used to say "leave the name and number out" and had nowhere to put them. It now has name, phone, email and notes in their own section, marked as shown only after purchase, plus the price band and the buyer cap on a shared lead.
• Posting posts. One row in lead_listings, one in lead_contacts. If the contact fails to save, the listing is taken back down, because a lead with no contact is a product nobody can be sold.
• Buying charges a card. A new stripe-lead-checkout function refuses a seller with no payouts, reuses an abandoned session, and sends the buyer to Stripe. The webhook marks the purchase paid, and the contact policy opens on that row.
• Selling pays out. Seventy-two hours after a sale, the seller presses Collect and stripe-lead-release transfers their share, idempotent on the purchase id.
• Disputes stop the money, not the person. A buyer disputes inside the window through a database function that checks the window and freezes the payout. A human refunds from Stripe or tells the seller to collect. The command center lists every open one.

What it looks like

How the money moves

The fee curve is the one already in fees.ts: $2 plus 12%, which is 20% on a $25 lead and tapers to 13% at $150. The command center now sums lead fees beside job fees, shows leads as live in the marketplace card, lists open disputes in the queue, and has a Lead sales tab.

What has to be run live

The page is deployed and the demo walks the whole loop. On the live site, posting a lead will fail until the tables exist, and buying will fail until the functions are deployed.

-- 1. In the Supabase SQL editor
supabase/lead-marketplace-migration.sql

# 2. From ~/tour-dash, after `npx supabase login`
npx supabase functions deploy stripe-lead-checkout
npx supabase functions deploy stripe-lead-release
npx supabase functions deploy stripe-webhook --no-verify-jwt

• The migration adds the three tables, the dispute function, the board view, a license_verified column on profiles, and a lead_purchase_id column on the ledger. It ends with verification queries.
• The webhook must be redeployed. Until it is, a buyer's payment would be captured and the purchase would stay pending, with the contact locked. That is the one outcome worse than not shipping, so deploy it in the same sitting as the checkout function.
• No new Stripe configuration. The lead checkout uses the same account endpoint, the same signing secrets and the same Connect accounts as bookings.

What it does not do yet

• Lead vendors as a third account type. Cold-calling shops and ISA desks are the supply the design describes, and today only agent accounts can post. The insert policy grows by one value when lead_vendor is added to profiles.account_type and signup.
• Automatic release. The seller presses Collect. A daily job that calls the release function for every purchase past its window is a small follow-on once there is volume.
• Delisting sellers. The board still shows a seller's dispute rate and greys them out above 15%, but nothing sets a listing to delisted yet. That is an admin action to add to the command center.
• Referrals. Unchanged, still the sample, still tracked rather than escrowed. The sell page points at them and says why.

Verification

• Types and build. tsc --noEmit clean; npm run build clean.
• The loop, driven in the demo. Opened a lead, unlocked it, saw the contact and the dispute box. Switched to Selling, pressed Collect on the sale past its window, saw the payout land in the rail. Filled the sell form, posted it, and found it at the top of Your leads with Withdraw beside it. No horizontal overflow at 1440 or 390.
• The command center shows Leads as live with three demo sales in the window holding $21.60, and the headline fee figure reads jobs and leads apart.
• Verified live, later the same day. The migration and the three functions were run and deployed from the CLI, then exercised with two throwaway agent accounts against the live database: the seller posted a $10 lead and its contact; the seller could read the contact and the buyer could not; the buyer could not alter the lead and the seller could not change its price or sold count; the checkout refused the seller as not payable and refused the seller buying their own lead; once the seller was marked payable the checkout returned a real live-mode Stripe session (fee $3.20, payout $6.80), a second attempt reused the same purchase, both sides could see it pending, the contact stayed locked, dispute and release were both refused on an unpaid purchase, and withdrawing the lead took it off the board. Twenty-two checks, twenty-two passes. The first deploy of the checkout failed to boot on an import that did not exist in the shared fees file; fixed and redeployed before the test.
• Not verified. The paid half: the webhook marking a purchase paid, the contact unlocking, and the release transfer. Those need a card, and the keys are live, so nobody paid. The first real purchase is the test of that path.

Files