St. Louis on May 13th turns one hand-built event into something that has to be repeated. Before suggesting anything we went through the whole account, the automations and the public site. This is what we found, and the two ways to run two cities.
Each one is in Wings 4 Water's own colors, with the real 2026 results, real sponsors and real photos. Every look has the same five pages for St. Louis and Kansas City, and there are three screens for your team on event night.
Open the three looks
Read only, nothing changed. The event works because people carry it. The system underneath was built one year at a time.
The year is part of the names: sponsor level fields for 2022 to 2025, tags like 2024sponsor, a new sponsors page each season. Every sponsor needs its own $10, $50 and $100 products. Copying the account for St. Louis copies all of that, and each change after is made twice.
Vote totals are running numbers on each sponsor that are reset after the event. In 2026 the 181 online and QR purchases were added to the board by hand, and the revenue report was rebuilt from 1,953 payments because a payment is only labelled by its product name.
Both keep contacts, emails and payments in the CRM and in Wings 4 Water's own Stripe. The difference is what guests and sponsors touch.
St. Louis gets a copy of the Kansas City account from the master snapshot. It is proven and it is already running on a test site, so sponsors can sign up now. The cost comes later: two sites, two sets of sponsor products and two leaderboards to keep in step, and a third copy for the next city.
The site, sponsor pages, voting, leaderboard, door and reports become one build. A city is a small block of facts: name, date, place, sponsors. One vote checkout takes the sponsor and the amount, so every dollar is labelled when it is paid and the report is a page, not a project. The desk keeps working in the CRM.
The strongest event sites show the date, place and one button on every page, explain voting in a sentence, and run a leaderboard made for the big screen. Among the ones we studied, we found none that joins the three things Wings 4 Water already has: every vote is a donation, each sponsor has its own vote link and QR code, and the same system runs the door.
The same night your guests know, with the hand-work taken out.
Totals stay on record after the event, so next year's "last year's winners" page and the money report come from the same numbers.
Proposed timing. St. Louis sponsors are not left waiting on the new build, and Kansas City is not touched until St. Louis has proven it.
The copied account takes applications and keeps the manual approval. It is on a test site today and goes live on your word.
wings4water.org with both cities, in the new look, reading the event details from one place.
Each approved sponsor gets its page and QR codes without new products, and every payment carries its sponsor, city and kind.
A practice event with test sponsors and test votes, run by the same people who will run the night.
If any part of the new build is not ready, that part runs the way it ran in Kansas City. Kansas City moves over after, for its 2027 date.
The rebuild changes what guests and sponsors see, not where the money and records live.
This page is a direction to react to. Once you and Chris have seen it, we size the work together, phase by phase.
Reply A or B
Four answers unlock St. Louis on both paths.
The Stripe account and bank for St. Louis sponsor invoices and votes. Sponsor invoicing waits on this.
The person who gets the new application alert and presses approve.
The pages say "Location to be announced" and 6 to 8:30 pm until you confirm.
The site only has the logo on a white square, and no photo of the people the votes help. Both would lift the new look.
A keeps the copied account as the plan for May and beyond. B starts the new build alongside it, with the copied account as the safety net. Sponsor sign-up for St. Louis is ready on the test site under both.