FestlyExplore the beta

Reference

Expansion gates

Evidence required before scaling.

Festly expansion project / community before real estate

Enter each city
as a community.
Earn the room.

Salt Lake City proves the complete Festly loop. Denver and Reno begin with local artists, stores, organizers, festival people, and paid partner activations—not promised venue openings.

01 / NETWORK

Connect the scene

ARTISTS · STORES · ORGANIZERS · GOERS

Build useful local discovery, profiles, event knowledge, storefronts, and organizer relationships.

02 / ACTIVATE

Make it real

PARTNER-LED · PAID

Run a creator capture day, showcase, market, or organizer package with existing local venues and production partners.

03 / REPEAT

Build a node

MONTHLY · LOCAL

Repeat the programming and commerce through a trusted partner node while Festly measures return behavior.

04 / OPTIONAL HUB

Earn the room

ONLY AFTER PROOF

Lease, own, or deepen a permanent space only when recurring contribution and community density support it.

01 / What actually scales

The Festly system travels.
The scene stays local.

CENTRAL FESTLY SYSTEM

What travels

  • Festival Field Guide and community experience
  • Profiles, follows, saves, alerts, and permissions
  • Artist publishing and attributed storefronts
  • Organizer briefs, commerce, and operating workflows
  • Brand system, reporting, support, and data standards
LOCAL FESTIVAL SCENE

What belongs to the city

  • Artists, taste, events, makers, and field knowledge
  • Organizers, vendors, venues, and production partners
  • Pricing, programming, calendars, and collaborations
  • Staff, safety, neighborhood, and community trust
  • Alcohol, entertainment, occupancy, and event approvals

Festly should make the local scene more valuable to itself.The platform connects people and demand; it does not erase local identity or turn every city into the same venue.

02 / The first three city jobs

One platform. Three different proofs.

These are candidate scene launches, not lease announcements. Denver and Reno remain unscored until local evidence exists.

FLAGSHIP SCENE01

Salt Lake City

Prove the full Festly relationship: trusted local discovery, artists and storefronts, organizer services, three weekly artist sessions, community events, and licensed local hospitality.

FIRST JOB
Prove the complete community-to-commerce loop
PHYSICAL ROLE
Content lab + community activation hub
SUCCESS SIGNAL
Repeat use + positive contribution
STATUS
Flagship · working plan
Review the Festly process ↗
SCENE CANDIDATE02A

Denver

Test whether Festly can organize a larger, more competitive creative market around trusted discovery, artists, event partners, storefronts, and paid activations.

START WITH
Local organizer + artist + store network
FIRST ACTIVATION
Partner capture day + showcase + market
DO NOT ASSUME
A Festly-owned venue is required
STATUS
Candidate · not yet scored
See the artist system Denver would use ↗
SCENE CANDIDATE02B

Reno

Test a smaller market where resident community, independent events, artists, sellers, and destination traffic can strengthen one another without depending on tourism alone.

START WITH
Local event + venue + maker partnerships
FIRST ACTIVATION
Partner showcase + organizer package
DO NOT ASSUME
Late-night rules equal guaranteed demand
STATUS
Candidate · not yet scored
See the organizer system Reno would use ↗

03 / The market scorecard

Measure a scene before pricing a lease.

Community usefulness and paid repeat behavior lead the score. Property diligence matters only if the city later earns a hub.

TESTWEIGHTEVIDENCE REQUIRED
Festival-community demand20

Local profiles, follows, saves, event alerts, repeat visits, and useful city-specific contributions.

Artist + seller network20

Active local artists, attributed storefronts, publishable work, product offers, and credible referrals.

Organizer + event partners20

Organizers with real events, service briefs, ticket or merchandise needs, and a reason to renew.

Conversion + contribution20

Paid activations, merchandise, tickets, packages, or services with positive contribution after direct costs.

Local operating capacity10

A trusted city lead plus venue, production, fulfillment, security, and community partners.

Central Festly capacity10

The platform, onboarding, rights, customer service, content, and reporting teams can support another city.

80–100 Eligible for a recurring partner-node plan if every hard gate passes65–79 Continue community building and paid pilotsBelow 65 Pause the market and protect central capacity

04 / City-entry gates

No market advances on follower count alone.

  1. 01

    Salt Lake City proves the complete loop: useful discovery, active creators and stores, organizer demand, paid conversion, and repeat behavior.

  2. 02

    The candidate onboards a credible starting network of artists, independent sellers, organizers, venues, and festival people.

  3. 03

    The city completes at least three paid partner activations across two or more formats before Festly considers permanent space.

  4. 04

    Commerce volume, Festly net revenue, and contribution are measured separately; the candidate cannot advance on gross sales alone.

  5. 05

    A local operating lead is accountable for community trust, partner delivery, safety, rights, and customer follow-up.

  6. 06

    A permanent hub is optional. It advances only after recurring partner programming proves that local demand justifies the property and license risk.

05 / If a city earns a hub

Then begin property diligence.

A permanent local room still needs written zoning, occupancy, alcohol, entertainment, fire, acoustic, and operating approval. Those facts remain hard gates—but they are not the first definition of Festly expansion.

NEXT DECISIONApprove the Salt Lake City proof loop and a partner-first city scorecard.Return to the Festly process ↗