sbTix.
Strategy note ยท v1

Getting your event found, without becoming Eventbrite.

Eventbrite's real moat isn't their software โ€” it's that when a person opens a new tab looking for something to do this weekend, they type eventbrite.com. sbTix has to solve that discovery problem while it's still early. This note walks the plan.

Author ยท sbTix Working draft
Chapter 01

The catch-22, honestly.

Events attract promoters. Promoters make events. Neither one can start without the other, and neither one shows up for a platform that doesn't already have the other. This is the shape of the problem sbTix opens with.

Eventbrite doesn't feel this pain because they solved it twenty years ago. They now sit on both sides at scale: buyers come because their friends' events are on Eventbrite, promoters come because that's where the buyers are already looking. The flywheel has been spinning since 2006. Any new ticketing platform, sbTix included, opens on the outside of that wheel.

The wrong response is to compete on software features. Every ticketing platform's dashboard does approximately the same job. Promoters do not switch platforms because the admin is slightly nicer. They switch when the new platform will visibly get their event in front of more people than the old one. That's the only feature the business runs on.

The question is not "how do we build a better ticketing tool." It's "how does an event on sbTix become as discoverable as an event on Eventbrite?" โ€” the actual question

That's what this note answers. Two moves in parallel, both starting this week.

Chapter 02

What Eventbrite has that sbTix doesn't have yet.

Eventbrite's real advantage is not any single feature. It's five compounding surfaces where a person looking for something to do lands on an Eventbrite URL without knowing they're on Eventbrite.

Surface Eventbrite sbTix, today
Their own URL indexed by Google ~200M event pages historically indexed Handful of events
A browse layer at their root domain eventbrite.com/d/ (explore) /trending โ€” shipping this week
A machine-readable feed of every event Partner-only ingestion /events.rss + /events.json โ€” public, shipping
Editors + submitters treating them as canonical Yes, since ~2010 Zero โ€” this is the ask
The verb "look on Eventbrite" in the culture Yes Long game

Three of those five sbTix can build in a week. The other two are the outcome of getting the first three right and doing it consistently for a year.

The plan below focuses on the buildable three, and treats the other two as the payoff we're working toward.

The moat is discovery. Ticketing software is not.
Chapter 03

The two-way playbook.

Two flows have to run at the same time. Neither works alone.

Flow A ยท Push out
Get sbTix events onto the surfaces where fans already look.

Facebook Event, Google Business Profile, DoNYC, Nonsense NYC, AllEvents.in, Bandsintown, Instagram, the Bushwick venues' own newsletters. Every one of these already has an audience. sbTix borrows theirs, one event at a time.

ร—
Flow B ยท Pull in
Give sbtix.net a reason for a fan to visit.

Trending page. Machine-readable feeds. Curated posts. Follow buttons. A weekly editorial. The point is not to become an aggregator โ€” the point is that when a promoter says "my event is on sbTix," the fan does not think "I don't know what that is."

Push-out without pull-in gets sbTix events discovered โ€” but on someone else's site. Fans buy the tickets, sbTix collects the fee, and no one ever visits sbtix.net again. That's Eventbrite from the promoter's side; it works, but the platform never gets its own gravity.

Pull-in without push-out builds a browse page that nobody visits, because nobody knows it exists. It's the classic new-platform failure mode: build a beautiful discovery UI and pray for organic traffic that never comes.

Both flows need to run together. Push-out earns short-term ticket sales for promoters, which keeps them on sbTix. Pull-in slowly compounds sbTix's own gravity, which is the endgame.

Chapter 04

What sbTix shipped this week.

Five pieces went from idea to code in the last three sessions. They map to both flows above.

Shipped ยท pull-in surfaces
/trending
Public browse page. Every real, upcoming, published event on sbTix. Filter chips for time window and paid/free. Demo events filtered out.
/events.rss
RSS 2.0 feed. What Feedly, IFTTT, and calendar editors auto-consume.
/events.json
JSON Feed 1.1 with a _event extension carrying schema.org Event payloads. Modern integrations, one call, everything they need.
Follow orgs
One-tap follow on public organizer pages. Follower count as social proof next to the CTA. Follow-state persists across visits without needing an account.
Like events
Anonymous-friendly โ™ฅ on every event page. Count paints on first render, animates on tap. Signals which events are getting attention โ€” future input for a hot-first sort on /trending.

Every one of these lives on sbtix.net's own domain. Every one strengthens the case that sbtix.net is a place, not just a checkout page.

They are also all the raw material for Flow A. The moment we can send an editor at DoNYC or Bushwick Daily a link to sbtix.net/events.rss and a page they can eyeball at sbtix.net/trending, the pitch writes itself: "here's a live feed of nightlife events in NYC. Auto-consume it. Save your submission-form time."

Push-out surfaces still need work. That's Chapter 05.
Chapter 05

The Promote tab.

The hardest truth from the distribution research: zero of the top five off-platform channels have a working public API for creating events.1 Facebook shut theirs down years ago. Google Business Profile Posts got deprecated in 2023. Instagram DMs get accounts nuked. Posh and Partiful have no public API at all.

Full automation of "post my event to Facebook + Instagram + DoNYC + Bushwick Daily + Nonsense NYC" is not on the table in 2026. What is on the table is turning a 40-minute cross-posting chore into a five-minute one.

That's the Promote tab. One dashboard surface per event, generating every asset a promoter needs to post everywhere:

Auto-generated assets, one click each

  • Instagram caption โ€” event name, date, venue, sbTix ticket URL, three hashtag suggestions based on the event's own copy.
  • Instagram 4:5 post โ€” flyer auto-cropped from the event's hero photo.
  • Instagram Story 9:16 โ€” same flyer, story-sized, with a paste-able link sticker URL.
  • 3:4 flyer for text-thread sharing.
  • QR code as PNG. Print it, put it in the door bin.
  • A caption for TikTok โ€” same story, native format.

Deep links that pre-fill the platforms that still let you

  • Facebook Event creator โ€” facebook.com/events/create?... pre-filled with every field. Promoter clicks the button, lands on FB with an event that's 30 seconds from publish.
  • Google Business Profile Event Post deep link โ€” same treatment, opens the GBP composer with the event details ready.
  • mailto: templates for the ~10 editorial calendars โ€” DoNYC, Nonsense NYC, Bushwick Daily, The Skint, Time Out NY, Africa Everything NYC. The promoter clicks "Send to DoNYC" and it opens their mail client with the whole pitch pre-written to that editor's known intake address.

A checklist that remembers

The Promote tab tracks which channels each event has been posted to. Promoters see gaps at a glance. sbTix as a business sees, in aggregate, which channels are worth building deeper integrations for.

Building this is not a research project โ€” every asset above is trivial to generate server-side from data sbTix already has, and every deep link is public web infrastructure. It's a two-week build.

It is the single feature most likely to make a promoter say "sbTix helps me sell my event" rather than "sbTix collects my money." That's the difference between a ticketing tool and a growth tool.

Chapter 06

Operating rhythm โ€” the 30-day play.

Everything above only works if it's executed on a schedule. Distribution is not a sprint; it is a weekly obligation.

Week 01
Ship, publish, pitch. Deploy /trending, /events.rss, /events.json, Follow, Like. Seed at least one real, non-demo published event on sbTix so the feed is not empty. Email the editors at Nonsense NYC, DoNYC, Bushwick Daily, The Skint, and Africa Everything NYC2 with the feed URL and one sentence: "here's a live feed of NYC nightlife on sbTix โ€” auto-consume it if it saves you time."
Week 02
Publish the first curated editorial. A short blog-style post at sbtix.net/notes โ€” “Six things to do in Bushwick this weekend” โ€” with two sbTix events and four events on RA/Posh/Eventbrite linked out with credit. Cross-post as an Instagram carousel from the sbTix account. Repeat weekly. The point isn't traffic in week one; it's building the muscle and the archive.
Week 03
Start building the Promote tab. Ship the six auto-generated assets first โ€” those unlock the most promoter time-savings. Deep links and the editor mailto templates come in the second half of the sprint.
Week 04
Measure and iterate. Which channels drove traffic to sbtix.net/e/ pages? Which editorial post got the highest engagement? Which of the pitched editors actually consumed the feed? Cut the ones that didn't; double the ones that did. The Promote tab tracks all of this by design.

By day 30, sbTix has a live browse layer, a public feed that at least one external editor is consuming, a weekly editorial cadence, and a promoter dashboard tab that halves the effort of cross-posting. None of that is Eventbrite-scale, but all of it is the shape of the platform Eventbrite became.

Discovery compounds slowly. A weekly editorial that four people read at first is worth more than one paid boost that thousands see once. โ€” the operating principle
sbTix strategy note ยท v1 Set in Georgia + system-ui + SF Mono