v1 codebase + agentic dev framework — for sale

Replace your venue's PRS/PPL bill and Spotify
with AI music that fits the brand.

Atmosphere as a Service. Infinite, on-brand, license-free music — generated per moment, per zone, per activity. Pre-revenue v1 with the architecture already done.

£500–£2kannual PRS/PPL bill replaced
∞tracks, never repeating
3–6 moengineering skipped
0licensing liability
The product, live

The scheduling UI is the moat.

Brand mood → channel → zone → schedule → generated track. The buyer skips a half-year of engineering and starts on day one with the loop already closed.

venue-beats.app / schedule
SCREENSHOT schedule-calendar.png react-big-calendar with @dnd-kit, drag a Spin Class block onto the 6am slot in Studio A
/brand-mood
SCREENSHOTbrand-mood-sliders.png5 venue-level sliders
/channels
SCREENSHOTchannel-emotion.png4 per-channel emotion sliders
/zones
SCREENSHOTzone-device.pngnow-playing + device presence
The problem

Every venue pays an ambience tax.

£

The licensing tax

Every café, gym, hotel lobby, retail store and restaurant owes PRS, PPL, ASCAP, BMI, SACEM. A mid-sized UK venue: £500–£2,000+ per year just to play recorded music in earshot of customers. Globally — multi-billion.

♺

The generic playlist

Spotify's "coffee shop" sounds the same in a Shoreditch roaster as in a motorway service station. A 6am spin class and a 7pm cooldown yoga get the same beats. Brand cannot live in someone else's catalogue.

⊠

The catalogue ceiling

Soundtrack Your Brand, Mood Media, Cloud Cover: £25–£60 per zone per month, plus passthrough licensing. Royalty-free libraries: the same 4,000 tracks every other venue is also using. All three: pre-recorded, finite, generic.

The wedge

Generative audio flips the economics.

Mureka, Suno, Udio, Stable Audio now produce commercial-quality music on demand from a text prompt. Every constraint above inverts.

No PRS/PPL liability

AI-generated music with no human authorship sits outside the collecting-society repertoire. PRS for Music has stated this publicly.

Infinite catalogue

Every track is new. No repetition fatigue. No "we heard this one yesterday" from the regulars.

Brand-matched

The prompt encodes the venue's identity, time of day, zone activity, energy of the moment. Sound becomes a brand surface.

Multi-zone, multi-schedule

Lobby gets one thing, gym floor another, both shift through the day automatically. No DJ, no playlist curation.

What ships in v1

The core loop is feature-complete.

Not a wireframe, not a stub. A working v1 with the architecture done right.

Multi-tenant

Strict venue isolation, JWT auth, argon2 hashing.

ADR-081 codifies tenant isolation by venueId on every tenant-scoped query. JWT via jose, argon2 password hashing. Cross-tenant features require an amending ADR — the boundary is not accidental.

  • Route factories take a db for testability
  • Services as pure functions, db last (ADR-082)
  • AppError for domain failures
SCREENSHOTlogin-flow.pngadmin@aaas.local sign-in
Brand surface

Brand Mood + Channels + Zones — the right seam for chains.

Five venue-level sliders define sonic identity. Channels (how music sounds) decouple from Zones (where it plays). A chain with twenty physical rooms draws from a shared brand palette without copy-pasting config.

  • 5 brand-mood sliders, venue-level
  • 4 emotion sliders per channel
  • Zones reference channels, not raw config
SCREENSHOTbrand-mood-detail.pngbrand mood editor
Scheduling

Activities + Schedule Entries on a real calendar.

"Spin class Mon/Wed/Fri 6–7am in Studio A, with this energy profile." A react-big-calendar + @dnd-kit interface that drag-drops the venue's week into existence.

  • Activities = what happens (venue-level)
  • Schedule Entries = when + where
  • Cron checks the schedule, fires the queue
SCREENSHOTschedule-week.pngweek view with dragged activities
Pipeline

Generation built on Ports & Adapters.

ADR-068 defines the seams. ADR-069 makes prompt composition a single typed boundary — two entry points, Zod-validated at the Mureka edge. Swap Mureka for Suno or your own model without touching the rest of the system.

  • BullMQ + Redis job queue, retry/backoff
  • Schedule-check cron drives generation
  • Single typed prompt-composition boundary
SCREENSHOTgeneration-flow.pngjob queue / now-playing
Playback

Device presence + SSE push.

One device per zone, enforced with heartbeat. Server-sent events push now-playing and a remote-kick signal to playback devices. The venue's tablets just work.

  • Device-presence service with heartbeat
  • SSE stream — now-playing + control
  • Cloudflare R2 for favourites; Mureka URLs ephemeral
SCREENSHOTdevice-now-playing.pngplayback device, now-playing view
Under the hood

The stack a serious operator would have picked.

Server

  • Express 5 + TypeScript
  • SQLite (better-sqlite3) + WAL
  • Drizzle ORM, FK-enforced
  • BullMQ + Redis
  • JWT (jose) + argon2

Client

  • React 19 + TypeScript
  • Vite 7
  • Tailwind CSS 4
  • Radix UI / shadcn
  • React Router 7, react-big-calendar, @dnd-kit

Storage & ops

  • Cloudflare R2 (favourites)
  • Mureka URLs (ephemeral)
  • Drizzle Kit migrations, auto-run on boot
  • Single-file SQLite deploy; Postgres migration path documented

Testing

  • Vitest + supertest
  • Real in-memory SQLite, not mocks
  • Server-side TDD discipline in the codebase
  • Test helpers wired
Not designing from scratch

The monetisation model is already locked.

A full set of billing decisions lives in .docs/project/prds/account-billing/. Implementation pending — the buyer is wiring up a model that has been grilled, not inventing one.

Pure prepaid wallet

Single per-minute rate in 5-minute increments. Rate bundles generation, delivery, sharing-pool credits, repeat-playback. No tiers, no platform subscription line.

BillingPort abstraction

Thin BillingPort interface. Paddle adapter first (Merchant-of-Record handles tax). Operator chooses adapter at deploy time, not the venue at checkout.

Hold & capture

Hold at job enqueue, capture at delivered cost, release on terminal failure. Mureka retries inside the job are free — provider charges only on successful delivery.

Wallet-empty soft stop

Generation halts immediately; playback loops existing inventory through the end of today's last scheduled session in venue-local time; hard stop after.

Anti-cheat violations

Scheduled session live, no registered + logged-in + actively-playing + volume-up device present — that's a violation. Randomised server-driven heartbeats. Attribution to session and assigned staff.

Cancellation lifecycle

Active → paused → restartable → deleted-on-request. Dormancy auto-pause after 7 days. Free-trial uses the shared-song pool to minimise generation cost.

What you are actually buying

v1 + a way to keep building it.

01

A working v1

Server, client, seed script, demo credentials, auth, multi-tenant isolation, generation pipeline, scheduling UI, device streaming. It runs.

02

The agentic dev framework

Project-local ADRs. A domain language file. A structured .docs/project/ tree of PRDs and decisions. Claude Code skills wired in for PRD writing, issue triage, ADR management, TDD loops, architecture review. This is how the codebase was built — and how you keep building it, at agentic speed, without quality decay.

03

No deployment, no users, no MRR

Right thing if you already know how to take a clean v1 to a first paying venue. Wrong thing if you're trying to buy revenue.

Who this is for

Operators, not first-time founders.

You already run at least one SaaS. You can stand up Redis, point a domain, wire Paddle, and sign a pilot deal with a regional gym chain or coffee group without needing a roadmap from me.

You see the licensing-tax angle and the brand-expression angle. You want the engineering already done so you can spend year one on go-to-market instead of architecture.

If that is you, the technical risk is removed. The remaining risk is the one you are good at.

SCREENSHOTdashboard-overview.pngoperator dashboard, multi-venue view
How this asset is priced

Where Venue Beats sits on the comparables ladder.

SideProjectors / MicroAcquire / Acquire.com bands, with Venue Beats positioned on architectural grounds.

$500–$2kGeneric CRUD MVP, no moat
$3k–$10kWorking v1 in a real vertical, decent code, no users
$10k–$25k Working v1 + meaningful architectural depth + clear market angle ← Venue Beats, £23,000
$25k–$75kPre-revenue with a strategic moat (LOI, proprietary data)
3–5× ARRAny MRR at all — indie SaaS multiples

Venue Beats sits in the upper pre-revenue band because: a sharp non-obvious market wedge (PRS/PPL replacement), architecture genuinely above MVP quality, multi-zone scheduling + device presence + SSE streaming is 3–6 months of engineering the buyer skips, and the agentic development framework is differentiated on these marketplaces — most listings ship code, not a way to keep building it.

Roadmap — jump on at the right step

Each step closes a risk and raises the price.

  1. 01

    Written legal opinion on PRS/PPL exposure

    PRS for Music has publicly stated that purely AI-generated music with no human authorship is not eligible for copyright and therefore falls outside their licensing repertoire. A formal barrister's note codifying this position for commercial venue use is the next priority.

  2. 02

    Live demo deployment

    Small VPS, public click-through URL — buyers experience the scheduling UI and a generated track playing in a zone.

  3. 03

    Loom walkthrough

    Brand-mood → channel → zone → schedule, ending in a generated track played live.

  4. 04

    Paddle integration

    Wiring up the already-designed BillingPort — prepaid wallet, auto-top-up, hold/capture on generation jobs, dunning, invoices. (The model is locked; this is implementation, not design.)

  5. 05

    First pilot LOI

    Any signed letter of intent, paid or unpaid, shifts the asset from "code" to "code with first customer."

  6. 06

    Build-in-public + waitlist

    Even 50 emails reframes this as a warm asset rather than a cold codebase.

  7. 07

    Postgres migration path documented

    For the buyer who needs to scale beyond single-server SQLite.

Starting price — right now

£23,000.

You get the full v1 codebase, the agentic development framework, and the architectural head-start. You take on the commercial risk that the roadmap above is designed to remove.

As each roadmap item lands, the price moves up. The legal opinion alone reframes the entire commercial thesis. The first signed LOI reframes the asset class.

Buy now

Take it at £23,000 before the roadmap lands.

Wait two weeks

Get the legal opinion in hand. Pay more.

Wait longer

Get a signed pilot venue. Pay materially more.

Contact me through SideProjectors

Working title only. No public deployment, no domain in use, no logo, no customers — nothing branded. The buyer renames it on day one.