01
Claim
A time-bound event Claim reserves that night’s Showment in the fan’s private Passport. Claiming does not create a Follow or grant email or SMS permission.
Investor details · Pilot design
The guided story shows the product promise. This optional Q&A layer explains the permission model, artist workload, pilot design and implementation without presenting illustrative data as results.
01 · Product mechanics
01
A time-bound event Claim reserves that night’s Showment in the fan’s private Passport. Claiming does not create a Follow or grant email or SMS permission.
02
When the reserved Showment is ready, the fan receives one transactional in-product notice tied to that item. It is delivery of something already claimed—not an open marketing channel.
03
After the Showment is Revealed, the fan may Follow for in-product artist Alerts. Email and SMS remain separate, explicit permissions.
Claim
Reserves the event Showment
Not contact permission
Transactional reveal notice
Tells the fan the reserved Showment is ready
Limited to this Showment
Follow
Enables in-product artist Alerts
Optional after value
Creates a separate contact permission
Not granted by Claim or Follow
SMS
Creates a separate contact permission
Not granted by Claim or Follow
02 · Artist workload
One rights-ready post-show asset. One review. One reveal.
Showments is designed to give an existing, approved post-show asset a more durable job. The pilot will test the real preparation, approval and support burden for an artist team—not assume it is negligible.
03 · Evidence plan
Success criteria should be set before the pilot. Every metric shown during the live pilot must come from observed behavior and reconciled costs, not demo fixtures.
04 · Category boundary
CRM begins with a contact record. Showments begins by giving the attendee something worth keeping.
Showments can complement the systems artists already use. Its first job is to create a valuable post-show return behavior; an optional relationship can begin only after that value is delivered.
05 · Pilot format
Free three-consecutive-show pilot.
Removing price friction gives one artist team enough repetition to test the full loop, improve execution between nights and decide whether the experience is worth running again.
Establish the operating baseline and measure Claim behavior.
Apply what was learned and measure Reveal return.
Test repeat collection and artist willingness to continue.
Track physical QR placements or printed materials, asset preparation and QA, storage and exports, on-site support, and any infrastructure or chain fees. The output is an observed actual cost per claimed Showment—not a pricing assumption.
06 · Rights and media
This investor demo uses real artist and event references, demo media and sample data to make the proposed experience concrete. It does not claim artist, venue, customer, pilot, affiliation, endorsement or production relationships.
A live pilot would use media supplied or cleared by the participating artist team, with approval for the Showment, its export formats and any outward sharing.
07 · Technical implementation
The working MVP supports authenticated Claims, Reserved-to-Revealed state, generated image and video exports, and Solana Devnet provenance. Solana is infrastructure—not the primary proposition, the fan-facing language or the reason an artist should adopt the product.
The pilot should judge the fan behavior, artist value and operating economics first. Provenance technology matters only when it makes the experience more durable, trustworthy or efficient.
08 · Explore