Calvin Report · Decision Maker

Wilcoxson Platform: the wiring plan

Turning the Wilcoxson House site into a thing other friend groups can join. Accounts, payments, the beta model, and a live Sample Group that mirrors the real site with every real detail scrubbed.
Updated Sun / 2026-08-02 / 5:40 PM CTv1.0.0Prepared on Calvin
2
Accounts you create
4
Decisions to make
$0
To start (beta is free)
1
Build ready to start now
The 20-second read. Sign-in: Google first (free, everyone has one), Apple second later when the iPhone app happens. Payments: Stripe (it gives you Apple Pay and Google Pay as one-tap buttons, plus the subscription logic your beta discount needs); a Venmo link is the 2-minute stopgap for a donation this week. The model: free during beta, and beta testers lock 6 months at 50% off when it goes paid. The Sample Group is a deterministic scrub of the real site: your name stays, everyone else gets a comically fake alias and jumbled facts, and it re-scrubs automatically on every push to prod.

1Sign-in (your question: Google, Apple, or Facebook?)

You have three real options for "sign in with one tap." Here is the honest ranking and my pick.

OptionReachCost / frictionVerdict
GoogleNearly everyone has a Google accountFree. ~15 min of setup you do once.START HERE
AppleEvery iPhone owner, expected on iOSNeeds the $99/yr Apple Developer account. Apple requires it if you offer any other social login inside an iOS app.ADD WITH THE iOS APP
FacebookDeclining, younger folks have leftDeveloper-hostile review, privacy baggage, worst long-term betSKIP
LOCKED · L1  Google sign-in now, Apple later, skip Facebook.

Google is free, universal, and unblocks everything today. Apple rides in for free on the $99 developer account you already need for the App Store, so it is a "same day as the iPhone app" add, not a separate project. Facebook login is a dead end. To wire Google I need one thing from you: an OAuth Client ID you create in about 15 minutes (steps in the action block at the bottom).

2Payment (your question: Apple, Google, or Venmo?)

Small but important reframe: Apple Pay and Google Pay are not separate payment companies you sign up with, they are buttons that ride on top of a processor. The processor is the real choice, and for a website that needs donations now and subscriptions later, that is Stripe.

PathDonationsSubscriptions / beta discountSetup
StripeYesYes (this is what the beta model needs)Account + I wire it
Apple Pay / Google PayYes, through StripeThrough StripeOne-tap buttons, free with Stripe
Venmo linkYes, instantlyNo. Cannot do subscriptions or unlocks.2 minutes, zero code
LOCKED · L2  Stripe is the spine; a Venmo link is the instant stopgap.

Stripe gives you cards, Apple Pay, Google Pay, and the recurring-billing engine the "50% off for 6 months" logic runs on, all in one account, ~3% per charge. To take a donation this very week while Stripe's business verification finishes, drop a Venmo (or Ko-fi) button on the site: real money in minutes, no code. Then Stripe becomes the real product payment once it is live.

Note: activating Stripe fully (bank, tax, business entity) is your legal/operational lane, which you said you are handling. I only need the account to exist plus its keys to wire the code.

3The platform: friend groups + the beta model

The shift is real: the Wilcoxson site stops being "one private site" and becomes "a template other friend groups can each get their own copy of." Here is the shape I would lock.

LOCKED · L3 · the structure
LOCKED · L4 · the beta offer
OPEN · D1  What is the price the 50% is off of?

The beta discount ("50% off for 6 months") needs a real number to be half of. It does not have to be final, just a placeholder to build the math around. Common shapes for a small group product: a per-House monthly (say $8-15/mo for the whole group) or a per-person annual. You can also say "decide later, just capture beta testers for now" and I build the capture without a price.

say: "D1 $12 a month per house" (or any number), or "D1 decide later"
OPEN · D2  Who can start a new House during beta?

Two flavors. Invite-only: a group only gets in if you hand them a code (keeps it curated, feels exclusive, protects the beta). Open signup: anyone can create a House (more reach, less control, more scrubbing/moderation to think about). For a beta among friends-of-friends I lean invite-only.

say: "D2 invite only" (recommended), or "D2 open signup"

4The Sample Group (the public demo that lies about everyone but you)

This is the piece I can build first, because it needs no accounts and no payments. Here is exactly how it works and what the scrub does.

How it stays in sync. The real profiles live in one file (guys/guys-data.js). The Sample Group is a scrubber that reads that file and writes a fake twin. It runs on every push to prod, so the demo always shows the same shape as the real site (same sections, same layout, same features) with none of the real facts. Add a real section to the Wilcoxson site, it appears on the sample the next push, already scrubbed.

The scrub rules (per your spec)

FieldWhat happens
Your name (Colton)Kept real. You said use your name, so the sample has a real anchor.
Everyone else's name + callsignSwapped for a comically fake alias (fixed map, see below)
Photos / portraitsReplaced with placeholder silhouettes
Kids / familyRandom-but-stable count and details, not the real ones
Schools, jobs, hometown, factsSwitched around (real-looking, wrong)
Movie lists, favorite quotes, game stats, arcade scoresKept as-is (you said these are fine, and they carry the vibe without outing anyone)
Business ideasScrubbed of any identifying specifics, kept in spirit
OPEN · D3  Approve the fake-name bit?

The device I would lock: everyone but you becomes a deadpan witness-protection action hero. Stable (not re-randomized each push), so the demo is believable. Proposed map (veto any and I will swap it):

Real (first name only)Sample alias
ColtonColton (unchanged)
PrestonBlaze Hardwick
DaveChad Bonanza
DanRip Vanderveld
David G. (Deeg)Buck Rockhold
Robby (Kiester)Lance Boyle
EthanDirk Mangrove
JoshChaz Ferrari
Jon (Burgess)Duke Sterling
Jeremy (Gargis)Rex Danger
say: "D3 names are good", or "D3 swap [name]", or "D3 different vibe" (and tell me the vibe)
OPEN · D4  Where does the Sample Group live?

Two clean options. A path on the real site (wilcoxsonhouse.com/sample): simplest, but it is publicly reachable, so the scrub has to be airtight. Its own throwaway domain (the calvinbox.com anonymized-sandbox bucket you already own): zero connection to your name, the safest home for a public demo. I lean calvinbox for a truly public "here is what it looks like" link.

say: "D4 calvinbox" (recommended), or "D4 on the real site"

5What I build, and in what order

  1. Now, no accounts needed: the Sample Group scrubber + the live demo site (pending your D3/D4 nods). This is the concrete first thing and I can start immediately.
  2. When your Google Client ID lands: wire Google sign-in + the House/account data model.
  3. When your Stripe account exists: wire the donate button and the Founding Crew beta-capture (6-months-50%-off flag).
  4. Instant, parallel: a Venmo/Ko-fi donate button so a real dollar can come in this week.

Everything here runs on Calvin and deploys to Cloudflare, the same path this page took. The two things gating me are the two accounts only you can create (below). The Sample Group is not gated, so say the word on D3/D4 and it becomes the next thing live.

Your two account actions

These two are genuinely yours (I cannot create accounts as you). Everything else I build. Fifteen minutes each.

COLTON ACTION 8-2-A, Create the Google sign-in credential
  1. Open console.cloud.google.com and sign in with your Google account.
  2. Top bar, click the project dropdown, then New Project. Name it Wilcoxson Platform. Create.
  3. Left menu: APIs & Services then OAuth consent screen. Pick External, fill App name (Wilcoxson Platform), your support email, your developer email. Save. (Leave it in Testing mode, that is fine.)
  4. Left menu: APIs & Services then Credentials. Click Create Credentials then OAuth client ID. Application type Web application. Name it web.
  5. Under Authorized JavaScript origins add: https://wilcoxsonhouse.com
  6. Click Create. A box shows a Client ID (ends in .apps.googleusercontent.com) and a Client secret.
  7. Send me the Client ID (it is safe to paste in chat). Hold the Client secret, I will tell you where to put it privately.
COLTON ACTION 8-2-B, Create the Stripe account
  1. Open stripe.com, click Sign up, use your email.
  2. You can stop after the account exists. The bank/tax/business steps are your legal lane and can finish later; I can build against test mode immediately.
  3. In the Stripe Dashboard, top right, toggle to Test mode, go to Developers then API keys, and send me the Publishable key (starts with pk_test_, safe to paste). Hold the secret key.

Not an action, a decision: whether to spend the $99/yr Apple Developer fee is deferred until the iPhone app phase (it buys both Apple sign-in and App Store access at once). Nothing to do now.

All sources read: design bible v1.24, wilcoxsonhouse repo, guys-data.js, live URLs. No access errors.
TOKEN REPORT
Usage: ~92,000 tokens (session, est.)
To completion: ~15k more to build the Sample Group once D3/D4 land
Changelog

v1.0.0, 2026-08-02, First build. Auth recommendation (Google then Apple, skip Facebook), payment recommendation (Stripe spine + Venmo stopgap), the House + Founding Crew beta model, the Sample Group scrub spec with a proposed alias map, build order, and the two account actions.