Dylan Korver

Zapped Records · 2026 · Internal tools

Team back-end & release automation

Behind the public site sits a team area that runs the label's week.

Release automation, a promo pool that sends invites in one command, a Telegram bot for the team, a Slack archive, and a pipeline that turns the Notion wiki into a searchable knowledge base.

Stack
Neon, Telegram, Slack, Ollama, Sanity
Walkthrough of the Zapped team area with invented data — the project orbs for releases in flight, one release's generated task list, and the DJ promo pool with its codes and feedback

The problem

The label's tools existed but weren't connected. Accepting a demo set nothing in motion: no release, no project, no catalogue number, no onboarding link for the artist.

What I built

  • Start release: one press on an accepted demo claims the next catalogue number, creates the release and its task list, and emails the artist an onboarding link. Pressing twice is safe.
  • Project orbs: every release in flight on one screen
  • A promo pool: one command creates pre-approved DJ accounts and sends the invites; DJs download with codes and leave feedback
  • A Telegram bot for the team: reminders, expiring tasks, chasing unfinished onboarding, and answers drawn from the Slack archive and the wiki
  • A Slack archive in Sanity, over 3,000 messages so far
  • The Notion wiki sorted into six categories by a local Llama model and stored as searchable articles
  • A finance ledger on Neon

→ I want something like this

Next: Australian venue — Venue sales analytics