Enter the access PIN Ernie sent you.
The full picture of what is built, what is live, what you can test this weekend, and the handful of calls I need from you. Open any section, chop it down when it is handled, and drop me a note right inside it.
Prepared for Frank by Ernie and the Circuit HQ team · July 6, 2026
This is one app that runs on both iPhone and Android from a single codebase, so we are never building the same thing twice. What you are getting first is the iOS build through Apple TestFlight.
What "scaffolded" means: the screens, the plumbing, the login, the live data, and the real features are all there and working. What is not final is the polish and the branding skin. Think of it as the machine fully assembled with a plain coat of paint. It will not always be pretty yet, and something may break. That is the point of you being on it early. I am on speed dial when it does.
This is what is on the phone today. All of it pulls from the same live system as the website, so a score entered on the phone shows up everywhere.
This is the operations layer we talked about. It is built into the same app and gated so only an admin or course official can touch the setup tools.
Straight talk on status: all of this is coded and running on the phone. It has not yet been tested on a real mapped course for accuracy. That is exactly what this weekend is for (see A5).
Golf courses have terrible signal. So scoring is built to work fully offline: every stroke is saved on the phone first, then synced up the second there is a connection. The scorer never waits on a spinning wheel and a junior's round can never get erased by a dropped signal. We specifically went back in and hardened this so a bad connection can never delete a round.
The no-install web scoring link still exists as a backup, so a volunteer with any phone can score from a text link without downloading anything.
Everything is staged so you can test on the course Saturday. I loaded a live 18-hole test tournament and gave you a login that can set pins. It does not need to be perfect. Walking a few holes and setting a pin tells us a ton. If it breaks, it breaks, I am on speed dial.
frank@circuithq.test / FrankTest!2026 (also in section C, it can set pins).The software is called Circuit HQ, and USJGT runs on it as the first tour. It is not a landing page, it is the whole operating system for the company: public tournament pages, results, rankings, the parent portal, and the admin and operator back office. When Bolt buys the next tour, it plugs in as configuration, not a rebuild.
It is built to hold every player, parent, course, registration, dollar, score, and message in one place. It is live now at circuithq.app with real payments running through it.
Real registration and card payments run through the platform today (Stripe), including free versus paid event splits, refunds, and promo codes.
We pulled the entire historical payment record out of ShotStat and reconciled it to the penny: $36.3M across 118,858 payment rows, and wrote the real dollar amounts back onto tens of thousands of historical registrations so the admin dashboard becomes the company's true ledger, not a guess.
This is the data moat: 18 seasons of history plus every new score and shot we capture natively. Nobody else can offer these families performance insights and recruiting exports off that.
One item still needs your call: a small set of older "ghost" tournaments and a few ambiguous payment groups need your real-versus-leftover judgment before we finalize those last dollars. Low stakes, but it is yours to confirm.
These are throwaway test logins so you can see every view on the app and the website. They are not real families. Use the same email and password on the phone app or on circuithq.app.
| View | Password | What you see | |
|---|---|---|---|
| Frank (you) | frank@circuithq.test | FrankTest!2026 | Use this on course. Admin + can Set Pins (course official) |
| Parent | api-v1-test@circuithq.test | ApiV1TestPass!2026 | Schedule, tournaments, players, profile |
| Player | test-player@circuithq.test | TestPlayer!2026 | Own schedule and profile, score own round |
| Admin | test-admin@circuithq.test | TestAdmin!2026 | Events and admin view (no pin tools) |
| Course official | test-official@circuithq.test | TestOfficial!2026 | Admin view plus the "Set pins" GPS tools |
Want your own named admin login instead of these test ones? Tell me the email and I will set it up.
To publish the app to the public App Store and Google Play, it should live under an Apple Developer and Google Play account owned by the company entity (Bolt Ventures or USJGT), not under my shop. Testing on TestFlight does not need this, but the public launch does. Tell me which entity owns those accounts and I will get them set up or transferred.
Good news: all your remaining 2026 events (August 1 through December 27) are already in the system and matched to your schedule. To make them registerable for real money I need your pricing. I will not guess a live price.
A starting proposal from your own history (adjust anything): Open events $249, Major or Invitational $299, College Prep $199, Adult-Child $99, three round or National $349. Or give me a flat number, or a sheet.
I also want to confirm the divisions per event and go live on the August events first, verify registration end to end, then roll the rest.
Send me everything you have on the shared drive: logos, sponsor assets, signage. I will organize it and build the standardized sponsor system we talked about, where a sponsor uploads a logo, sees their sign, approves it, and it goes straight to print and out to the fulfillment center for the trailers.
I also want to lock the October 1 plan: that is when everything flips to USJGT branding and the new membership, price returns to $299 for 2027, and the new schedule drops. Everything from now until October runs as the current HJGT campaign, and the big creative package we build lands for October.
This is your catch all. Bugs, ideas, "can it do X," priorities for the two week build, whatever. You said it best: sit here, chop it down, tell the team what we need. That is exactly how we build the machine.