FestlyExplore the beta

Roadmap and status

Build what is useful. Prove what is repeatable.

The roadmap separates what is available in the beta, what is being tested in the pilot, and what must be proven before broader rollout.

See current status
Festly weekend discovery page shown in the customer-facing beta
Beta product screenshot

Current beta surface

The product is being tested through real screens, not just a plan.

Status

Current, pilot, next, and later.

Available now

Beta product surfaces

Profiles, storefront previews, event presentation, discovery, follows, and pilot onboarding.

In pilot

Real operating learning

Reviewed participation, managed launch work, seller workflows, customer support, and reporting.

Next

Prove the first offers

Complete useful launches, marketplace activity, direct-cost measurement, and repeat behavior.

Later

Scale only after proof

Broader payouts, fulfillment automation, production ticketing, advanced community systems, and expansion.

90-day pilot

Measure the work that proves the next decision.

Salt Lake City is the first controlled learning environment, not a claim of completed traction.

Onboard5–10 serious artists, sellers, organizers, or partners.
Launch3–5 complete storefront or managed-service examples.
DeliverAt least one paid managed service with a documented scope.
MeasureRepeat visits, revenue, direct cost, contribution, and support needs.

Before scaling

Expansion depends on evidence, not follower count.

  • Verified operating responsibility and customer support
  • Clear contribution after direct costs
  • Repeatable onboarding and publishing
  • Local partner and venue readiness

Keep the work honest

See the detailed assumptions behind the plan.

Pilot risks and assumptions Expansion gates