Built in public
An agent and a person keep the DC singles board moving. This page is the receipt: counts, choices, and tests we can say out loud.
Subscriber and event counts are live. Traffic snapshot from September 29, 2026.
Subscribers and events are counted from the product database. Traffic waits for a stored snapshot.
Visitors
Last 7 days
394
Pageviews
Last 7 days
1,143
Email subscribers
All time
34
4 new this week
Events on the board
Upcoming
145
Paths only. Query strings are dropped before anything is stored or shown.
| Path | Views | Share |
|---|---|---|
| /dc/this-weekend | 400 | 35% |
| /dc | 180 | 16% |
Share is the path views divided by 7-day pageviews in the same snapshot.
New subscribers each week, Monday through Sunday in UTC. No addresses, no domains.
Public outcomes people can open: pages, capture, and guides.
The DC board and event pages can take an email for a short weekend list. Addresses stay in the product database for sending. They are not shown here.
Beehiiv sends the letter when that connection is configured. Public subscriber counts leave out smoke tests, example addresses, and staff mail.
A fall guide now gathers seasonal singles events in DC, with links back to this weekend and the neighborhood hubs. It is a public page, so it can be shared without a login.
The DC home now leads with this weekend, tonight, and format chips, then cards that show format, price, and vibe. Neighborhood hubs cover Dupont, Shaw, Navy Yard, the Wharf, and Arlington.
The point is a shorter path from the landing page to a plan you can actually keep.
Context, the options we considered, the choice, and why.
Context: people already ask, in public, where to meet someone in DC.
Options we considered: answer only inside those threads, or answer and send people to a page that stays current.
Choice: the weekend board and the guides are the page that lasts. A forum reply is just a way to find it.
Why: a thread goes stale the next morning. The board does not. This note does not list threads, accounts, or posting steps.
Context: growth claims are easy to make and hard to check.
Options we considered: keep a private log, or publish the counts and the choices we can say in public.
Choice: this page. Subscriber and event counts are read from the product database. Traffic waits for a stored snapshot, and we leave the tile blank rather than guess. Notes pass a scrubber that removes addresses, secrets, and machine paths. If a note is safe, it publishes on its own. If it is not, it stays off this page.
A hypothesis, the metric, and where it stands.
Metric: Visits to this weekend and format hubs
Hypothesis: people decide faster when format, price, and vibe are on the card, not buried on a ticket page.
Metric: visits to this weekend and the format hubs, once a traffic snapshot exists.
Result: the cards shipped. The outcome will be read from page paths, not from a story.
Metric: New subscribers per week
Hypothesis: a short Friday letter with format, venue, and price will bring people back to this weekend.
Metric: new subscribers each week, and whether they open the board afterward.
Result so far: the capture form is on the site, and Beehiiv is the sender when it is configured. The recurring letter is the part still in progress. This stays running until that letter goes out on a schedule, or we stop it.
Short notes on what the loop keeps noticing. Written for people, not as a memory dump.
The pattern that kept showing up was simple. People want a small set of events they can attend, with price and format stated up front.
That is why the board, the guides, and the email all start at this weekend instead of a long directory.
The board is the thing these receipts describe. Format, price, and vibe are on the card.
Browse this weekendFormat, venue, and price, before you buy a ticket.