Closed editor network
Community should feel safe enough to share unfinished work.
This page frames Supercut Club as a protected collaboration layer: editors share resources, meet online, ask for critique, and build trust inside a private network that grows carefully through referrals.
Feedback loop
The core interaction is a secure frame-by-frame critique room.
The experience should make it obvious how feedback appears: a protected clip gets shared, the reviewer hovers the timeline, and comments surface against precise moments without turning the room into a public free-for-all.
Secure feedback room
Move across the timeline to see how a closed critique loop works.
1. Upload privately
Share a protected clip link that carries a visible watermark and room-level access control.
2. Review in context
Editors leave notes against specific moments so the feedback stays tied to the actual cut.
3. Keep it closed
The room is only visible to approved members, which keeps comments useful and accountable.
Community model
What members actually come here to do.
The page should communicate that this is more than a forum. It is part workshop, part network, part protected review room.
Resource sharing
A private commons for tools
LUT packs, hardware notes, and delivery checklists stay inside the club instead of leaking into public feeds.
Meet people online
Live rooms for low-pressure networking
Small calls and critique salons help editors build trust before they ever work together offline.
Feedback forum
Secure critique with timeline context
Watermarked clips live in private rooms, and every note stays tied to the frame or timestamp it answers.
Closed collaboration
Open exchange inside a trusted boundary
The system stays generous and experimental because access is approved, paid, and accountable.
Access logic
A paid, referral-led club grows slower on purpose.
Buying into the community should not mean bypassing trust. A member can only personally add one editor per month, which keeps growth deliberate and gives the network time to absorb each new person well.
Referral system
The gate is the feature, not the bug.
- 01
An existing member can nominate only one new editor per month.
- 02
The invited editor applies, pays to enter, and joins the closed feedback environment.
- 03
Every clip room gets access controls, watermark protection, and visible accountability.
- 04
Trust expands slowly, which keeps the community useful instead of noisy.
Developer build surface
What needs to exist for editors to actually connect through the product.
This is where the community stops being a moodboard and becomes an implementable system: access control, realtime room behavior, secure media review, and a model for trust that can be enforced in product logic.
Membership and referrals
Track paid membership status, invite history, sponsor relationships, and the one-referral-per-month rule.
Secure clip review
Generate expiring links, watermark overlays, and room-level permissions before a clip becomes reviewable.
Timecoded comments
Anchor feedback to timeline moments so notes are reviewable, searchable, and actionable.
Resource exchange
Support resource posts, saved collections, and category tags for gear, workflows, and vendor knowledge.
Realtime community presence
Surface live rooms, notifications, and activity feeds so editors can respond quickly without leaving the platform.
Moderation and trust logs
Keep abuse reporting, room access logs, and sponsor trails visible enough to defend the integrity of the club.
Next routes
Move between discovery, matching, and community.
These public routes should read like one product surface: discover the editor, understand the matching logic, then see how trust continues after the shortlist is made.