Automated music-marketing software for digital content operations. Posting engines, video library management, engagement scoring, marketing & advertisement, accounting & billing, and reporting all in one system.
One central clip selector feeds every platform. Priorities are set once in the weights config and propagate everywhere; each platform tunes its own cadence on top. Daily volume scales up or down per client.
Every clip carries a deterministic filename encoding its pool, a stable content hash, and its current effectiveness score. Age-based rotation rules keep evergreen material alive while quietly retiring stale clips. Library-hygiene tooling deduplicates, re-encodes, and trims long clips into platform-native chunks.
Platform scorers read live likes, comments, and views and compare each post against the account's own 30-day average — so a single viral post doesn't drown out the baseline. Re-scored clips automatically rotate up or down. The selector pulls from a queue stocked to honor active pool weights, with a daily ledger auditing actual picks vs. configured intent.
Daily reports on Meta ad spend, click-through, and cost-per-follower against the configured target. Email-list growth and welcome-sequence engagement tracked separately. Meta lead-form submissions land in the email list automatically.
Monthly internal-expense passes estimate labor hours across functional areas and produce a canonical ledger. Outcome-based client billing rules build itemized invoices. A historical reconstruction pass replays month-by-month under current rules for audit and reconciliation. Monthly narratives summarize each artist's creative output.
Two dashboards regenerate every two hours (operator + artist) and deploy automatically. The weekly investor email summarizes what shipped. Push alerts route posting failures and silent-reporter events. A self-healing responder takes the first run at known outage classes. Spotlight watches the music-production pipeline and flags the bottleneck stage in plain English.
Each client's variables — API tokens, IDs, file paths — live in their own config file. The shared programs read whichever client config they're invoked against. New-client intake produces the config file from a guided wizard.
Each chat that owns a JITRBeats program also owns a roadmap file. Items opt in to this public list with a **Public:** yes flag. Everything else stays internal.
The categories below count programs by their function (selectors, posters, reporters, etc.). Development and Production layers are tracked separately so the dev-to-prod ratio is visible.
| Layer | Programs | LOC | Avg LOC / program |
|---|---|---|---|
| Development | 214 | 83,222 | 389 |
| Production | 100 | 42,913 | 429 |
| Total | 314 | 126,135 | 402 |