FestlyExplore the beta

Reference

Pilot risks

Risks, assumptions, and open questions.
APPENDIX / PILOT RISKS + ASSUMPTIONS

Six assumptions
the pilot must
test or reject.

REFERENCE POINTSLaunch hypotheses to validate
4People servedgoers · artists · sellers · organizers
3Money measuresvolume · net revenue · contribution
1Local activation hubSalt Lake City
90 daysPilot windowvalidation horizon
MARKET CONTEXTFestival commerce exists. The credible opportunity is to connect relationships that are currently split across discovery, tickets, community, fashion, merchandise, and operating tools.
Review rave, ticketing, and festival-fashion platforms →
01 / SIX TESTS

The problem, the response, and what to measure.

These are working business assumptions to test during the pilot, not published industry statistics.

01Pilot test

Festival discovery is fragmented

People jump between social posts, ticket pages, generic shopping results, artist links, and group chats to build one weekend.

FESTLY RESPONSE

Festly brings events, artists, trusted field knowledge, products, and independent stores into one festival-specific guide.

WHAT TO MEASUREUseful searches, profiles, follows, saves, event alerts, and return visits
02Pilot test

Artists borrow attention but rarely keep the relationship

A performance or popular post can create exposure without connecting the artist’s story, shows, merchandise, and audience.

FESTLY RESPONSE

Give each artist a profile, public wall, publishing tools, connected products, and followers who can return.

WHAT TO MEASUREArtist follows, product saves, event interest, finished content, referrals, and repeat participation
03Pilot test

Organizers rebuild the same operation in separate tools

Tickets, wristbands, crew gear, signs, merchandise, vendors, and event communication are often planned in disconnected systems.

FESTLY RESPONSE

Start with one event brief, then connect packages, sellers, artists, passes, and future gate operations around the same event.

WHAT TO MEASUREBriefs created, packages requested, paid services, on-time delivery, organizer renewal, and referrals
04Pilot test

A marketplace can lose the person behind the product

Anonymous listings make it hard to know who made an item, who fulfills it, or whether the festival community actually trusts the seller.

FESTLY RESPONSE

Name every store, artist, lead time, fulfillment path, and community reason attached to a product or service.

WHAT TO MEASUREAttributed sales, store follows, product saves, delivery performance, support issues, and repeat buyers
05Pilot test

Physical activations add value and operational risk

Shows and studios create trust and content, but alcohol, noise, security, rights, staffing, and property rules can overwhelm the platform story.

FESTLY RESPONSE

Use Salt Lake City as one controlled activation hub with a documented license, site, production, and publishing process.

WHAT TO MEASURESafe delivery, artist approval, useful content, repeat attendance, and contribution after direct costs
06Pilot test

More activity can hide weak economics

Marketplace volume, ticket sales, studio gross, and sponsor money can look impressive while Festly’s actual net revenue or contribution remains unclear.

FESTLY RESPONSE

Report community commerce volume, Festly net revenue, and contribution after direct costs as separate numbers.

WHAT TO MEASURETake rate, service margin, fulfillment cost, production cost, repeat purchases, and contribution by business layer
02 / HOW THE PARTS WORK TOGETHER

One useful signal can move through the whole festival scene.

COMMUNITYProfiles, follows, saves, interests, and event alerts
+
ARTIST + STOREStories, products, attributed storefronts, and audience
+
ORGANIZEREvents, packages, passes, supplies, and operating briefs
+
ACTIVATIONFestival, pop-up, studio session, market, or partner show
=
RESULTValue returns to the scene and gives people a reason to come back
03 / RISKS THE BRAND CANNOT SOLVE

The site and operating numbers still have to work.

01

Marketplace trust

Seller quality, fulfillment, returns, support, and clear attribution must work before the marketplace scales.

02

Operating scope

Community, commerce, organizer services, artist production, and live events can outrun a small team unless ownership is explicit.

03

False traction

Follower count and gross sales can hide weak retention, low Festly revenue, or negative contribution.

04

Rights + data trust

Unclear releases, unsafe events, careless data use, or uncredited creators can damage the system faster than marketing repairs it.

04 / PROOF PLAN

Four questions the first 90 days must answer.

  1. 01

    Will festival-goers use Festly to discover, save, follow, join alerts, and return after the weekend?

  2. 02

    Will artists, sellers, and organizers publish useful offers, receive value, and invite another participant?

  3. 03

    Can commerce, professional services, and Salt Lake City activations produce contribution—not just gross activity?

  4. 04

    Can Festly improve the scene without selling personal profiles, hiding the seller, or replacing local culture?

RETURN TO THE PLANReturn to the full Festly operating plan.Open business plan ↗