Syecho Β· echoing the unseen

Where artists meet,
make, and stay.

Syecho is Linktree Γ— Partiful Γ— LinkedIn, made for artists and creative collectives. Post a backyard meetup or plan a full curated night. Keep your best work in one place. Meet the people in the rooms you move through. Leave verified reviews that travel with you β€” instead of expiring in an IG story.

The shortcut

Four things you already use, one place they all belong.

Linktree→Syecho

Your Linktree, but not static. A full editorial kit that shows your music, your press, your past events, your collaborators β€” not just a stack of URLs.

Partiful→Syecho

Post a meetup, gather the RSVPs, run the night β€” plus a team chat, a Kanban for logistics, and a persistent event page that doesn't disappear once the party's over.

LinkedIn→Syecho

The receipts of what you actually made with people, in πŸ”₯ not stars. Reviews come from collaborators you worked with on real events β€” not strangers endorsing you for skills you never claimed.

The scattered kit→Syecho

No more DropBox + Google Doc + SoundCloud playlist + a one-sheet PDF. One editorial press kit per artist, live, shareable, updatable β€” with multiple versions coming soon for different creative hats.

The problem

Most nights are built in the seams.

Group DMs. Unread voice notes. A spreadsheet nobody opens. Instagram story replies. The tech rider lives in three different Google Docs. Half the lineup doesn't know soundcheck moved. The reviews everyone got were genuine β€” and then the story expired.

The booking DM spiral

Talent negotiated in group chats. Logistics scattered across six apps. Nobody knows where the final yes lives.

The rΓ©sumΓ© problem

Emerging artists have no centralized way to show a booker what they do. A SoundCloud link and a Linktree isn't it.

The review that vanished

The night was magic. The IG stories archived 24 hours later. There's no permanent trust signal the talent can carry forward.

The prep sheet of doom

Tech rider, poster drafts, setlist, door list β€” scattered across Google Drive, Dropbox, AirDrops, and a shared Notes doc.

The shape of the answer

Events happen. Collaborations stick.

Syecho is built around one quiet idea: the night is temporary, but the people you make it with aren't. Every event becomes a container β€” chat, tasks, attachments, lineup β€” and once the lights come back on, the relationships keep going. Reviews, kits, and profile connections carry forward into the next room you end up in together.

A casual meetup and a fully curated show use the same tools. The difference is how much structure you want. Anything from "come through my place Thursday" to "headliner + opener + VJ + door +Β tech rider + post-show recap" lives here.

Inside

What you can actually do.

Kits

Press kits, but editorial.

Every artist gets a full-bleed press kit β€” stats, bio, music embeds, press quotes, past events. Multiple kits per artist coming (DJ / producer / astrologer can keep distinct packets).

Curated events

Define roles. Review applicants. Cast the night.

Post a curated night with roles (Headlining DJ, Resident VJ, Support). Artists apply with their kit. Review in-queue with slot-safe Accept / Reject / Undo. Pipeline stats double as filter chips.

Meetups

Open rooms. Seat caps. Public join.

Lower-stakes gatherings where attendance is the only role. Open-to-all or invite-gated, with seat availability tracked live.

Task board

Trello for your event.

Kanban per event with Upcoming / Open / Done columns. Each card takes file attachments (posters, tech riders, set recordings) and a comment thread the whole team can discuss in.

Attachments + comments

Files + discussion live together.

Versioned file drops per task. Threaded comments so the 'is poster v3 approved?' conversation happens where the v3 file actually lives. No more DM archaeology.

Event chat

One room, the whole team.

Host + accepted lineup drop into a shared chat automatically on accept. File attachments inline. Archived (not deleted) when the event wraps so memories + logistics survive.

Reviews β€” in πŸ”₯, not stars

Post-event trust signals that stick.

After an event ends, everyone who was in the room can leave each other reviews. Rated 1–5 πŸ”₯. Artists curate which ones appear on their kit. An internal profile shows the uncensored version β€” dignified accountability.

Music-native design

Not a SaaS. A venue.

Editorial typography (Inter + Instrument Serif). Glass-morphism cards. Ambient gradient orbs. Built from the inside of a club, not the outside of a pitch deck.

Who it's for

For people who make things together.

Artists, DJs, producers, VJs, promoters, curators, collectives, zine makers, drag performers, chefs who throw dinners, poets who host readings, bartenders who curate energy β€” anyone whose creative life happens in rooms with other people.

Syecho starts in NYC queer nightlife and club-residency culture, because that's the scene we come from. But the shape of the product is the shape of any creative collective that gathers, makes, and gathers again.

The quiet thesis

Resident Advisor shows you what's on.
Instagram shows you what you missed.
Syecho shows you how it was made β€” and lets you help make it.

Where it's going

The roadmap, loosely.

  • Kit builder

    Dark editorial press kits, multiple sections, mobile carousels.

    Shipped
  • Event Kanban with attachments + comments

    Trello-style task boards per event. Just shipped.

    Shipped
  • Application review flow

    Slot-safe accept/reject, pipeline as filter, role filter.

    Shipped
  • Verified event reviews

    Task-gated πŸ”₯ reviews that unlock at event end. In progress.

    Next
  • Internal profile with uncensored reviews

    Community-layer trust graph distinct from the curated kit.

    Next
  • Multiple kits per user

    DJ / producer / astrologer presets per artist. Pick which one is featured.

    Next
  • Voice-note reviews

    Because a 15-second voice memo is worth 400 words and has texture text can't touch.

    Later
  • Venue accounts

    So tech riders + capacity + stage plots live once, not in every group DM.

    Later
Who's behind it

Aspirin β€” a DJ, producer, astrologer, and software engineer based in New York. Syecho is equal parts personal itch (what I wished existed when booking my own nights) and systems thinking (because the platforms for underground music haven't really changed since SoundCloud).

Still early. Still opinionated. Still listening.

The ask

Tell me where it breaks.

If you made it this far: what clicks, what confuses, what you'd want before using it for a real event? A paragraph, a voice note, a roast β€” all welcome.