A subscription SaaS for real-estate agents. Each agent gets a personal, tap-to-open web page where they share property listings with their buyers. They hand buyers a physical NFC business card — the buyer taps it with their phone and instantly sees the agent's shared homes, with call/text buttons. The agent pays a monthly seat fee; the physical cards are sold separately.

• Monthly seat subscription — $29.95/month per agent (Stripe recurring). Unlimited digital cards while active.
• Physical NFC cards — $30 per pack of 10 (Stripe one-time). The first 10 cards ship with the agent's first paid month; more are ordered from inside the app.
• Prices are set in the Pricing & Numbering panel below (stored in the database, not the code — changing them is instant, no deploy). Individual agents can be given custom pricing from their row in the Agents list.

• Sign up → a 10-day free trial begins (software only, no payment). They appear in the Agents list below immediately, marked "Trial."
• Day 11 → if they haven't subscribed, their dashboard goes read-only ("Subscribe to Continue" screen). Their data and their buyers' live pages are preserved — only their editing is locked.
• Subscribe → they're unlocked and marked "Subscribed."
• Comp → you can give any agent a free 30-day pass from their row in the Agents list (they must sign up first). Used for founding agents and event deals. It doesn't touch Stripe.

Cards are blank printed stock (produced on an Evolis card printer). Each card is encoded with a URL like forsalenfc.com/?t=FS-0101. Card numbers are assigned automatically from the counter in the Pricing & Numbering panel (prefix + next number). When an agent activates a card, it links to their account. An agent can only claim as many cards as they've paid for.

Every buyer page quietly records how the buyer engages, so agents can see what's working and spot hot leads. Under each buyer's Activity an agent sees: which properties were opened and how many times; which channel the buyer arrived through — a physical card tap, a link the agent texted, or a link the agent emailed (each share link carries a small src tag; views with no tag simply aren't attributed to a channel and are left out of the breakdown); and directions requests — when a buyer taps the Directions button on a property, it's logged and shown as "Buyer requested directions" with a timestamp. Directions are counted separately from views, so they never inflate the view numbers or the hot-lead flag. Under the hood this is the property_clicks table (an action column marks each row as a view or a directions request), written by the record_property_click database function — the buyer page can't write to that table directly, so every write goes through that function. No third-party service or added cost is involved.

• Metrics — live funnel (signups, trials, subscribers) across the platform.
• Pricing & Numbering — set the monthly seat price, the card pack price, the free-cards-at-signup offer, the order-notification email, and the card number sequence.
• Landing Page Demo — edit the sample agent/properties shown on the public homepage demo.
• Cards Used by Brokerage — usage rolled up by brokerage.
• Agents — every signed-up agent. Click a row to comp them, set custom pricing, or grant trial cards.
• All Orders — card orders to fulfill (print & ship).
• Chatbot Conversations — logs from the website chatbot.
• Advertising Demo Cards — create/manage the physical NFC cards you hand to agents in person. Each generates a tap page ("this is what your buyers will see" + a Start Free Trial button); encode its token onto blank NFC stock.

The "Try the live demo" link and sample card on the homepage open ?t=DEMO-001 — a permanent sample buyer page with a fake agent and listings. It exists so a prospect (or a salesperson doing an in-person demo) can experience the buyer view in seconds without signing up. It's the core of the sales pitch. It uses demo data, isn't tied to any real account, and needs no maintenance.

"Advertising cards" are physical NFC cards you hand to agents during in-person selling — brokerage walk-ins, the Florida Realtors Convention, etc. You create each one in the Advertising Demo Cards panel (below), which generates a card with a unique token; you encode that token onto a blank NFC card (same printer/stock as the agent cards). When an agent taps it, they see a page headed "This is what your buyers will see" — a live sample buyer view with working Call and Text buttons — followed by a "Start 10-Day Free Trial" button that drops them straight into signup. It's the physical pitch: hand it over, let them tap and press the buttons, and the card sells the product for you. (This is the physical, hand-to-an-agent version of the same idea as the homepage's DEMO-001 online demo.)

• Front end — a single-page app (one index.html) served as a PWA. Hosted on Vercel, deployed automatically from the GitHub repo.
• Back end — Supabase (Postgres database, agent login/auth, security rules, and stored procedures). Payment logic runs as Vercel serverless functions in the /api folder.
• Payments — Stripe (subscriptions + one-time card orders), confirmed back to the database via a Stripe webhook. The card-order price is computed on the server (from the Pricing panel settings), never taken from the browser — so a tampered checkout request can't change the amount charged.
• Email — order alerts via Resend. Website chatbot — Google Gemini.
• Updates & caching — the app's HTML is served with no-cache headers and the service worker always pulls the newest version from the network, so a new deploy appears on the next load without agents having to clear anything. The site sits behind Cloudflare; in the rare case a stale page persists, "Purge Everything" in the Cloudflare cache settings clears it.

To run the platform, an owner needs access to: the GitHub repository, the Vercel project (hosting + the secret keys in its Environment Variables), the Supabase project (database + auth), the Stripe account (money), the domain (forsalenfc.com), the Resend and Google Gemini accounts, and the physical card printer for fulfillment. Secret keys are stored only in Vercel's Environment Variables — never in the code.

Optional env var — DIAG_TOKEN: the internal card-troubleshooting endpoint (/api/diag) is locked behind this token so it can't leak agent contact info. If DIAG_TOKEN is not set in Vercel, the endpoint stays disabled (returns 503), which is a safe default. To use it, set DIAG_TOKEN to any long random string, then call /api/diag?card=FS-0101&key=YOUR_TOKEN.