Leon Booker

it's only a matter of time

Building at the intersection of music, operations, and technology. Over a decade in talent development, recorded music, and publishing administration.

contact
—
woostereditorialoperations

By mid-July, Wooster’s build had shifted from adding capability to enforcing standards. Format-specific writing desks, source-grounded research, prompt traces, image provenance, visual verification, fact-check exports, and stale-media audits made the system legible where automated publishing usually becomes opaque. Wooster Heat also became a repeatable video format with editorial review built into production. The question was no longer whether agents could make media, but whether the newsroom could trust what they made.

woosterstrategyproduct

I narrowed Wooster back to its editorial core, retiring the public DealEngine valuation and standalone Open Ledger surfaces after testing them in the live system. Not every viable feature belongs in the product. The sharper choice was to protect the magazine’s point of view and operating focus.

woosterintelligenceeditorial

I reframed Conviction as an evidence system for emerging-artist judgment. Audience movement, listening behavior, cultural signals, release context, and human evidence could inform a point of view while keeping the underlying receipts visible and promotion decisions reviewable. The aim was not to automate taste. It was to give taste a defensible record.

woosterproductsystems

With the platform unified, Wooster expanded without abandoning its editorial center. Artist profiles, leaderboards, History, and short-form video all entered the same evidence and review system. I reorganized the Command Center around the decisions an editor needed to make, including review, production, publishing, artist records, system health, and spend, instead of presenting technical plumbing as the product.

woostersystemsengineering

I directed the consolidation of Wooster’s public site, Command Center, and editorial service into one production monorepo. Shared contracts and deployment rules replaced three drifting codebases, while editorial scheduling moved into the cloud service instead of remaining split across a laptop and scattered jobs. One product now had one operating base.

woosterinfrastructure

Wooster crossed from launch preparation into live operations. I moved the public site, Command Center, database, publishing services, and scheduled work into a cloud production stack, then tightened the editorial cadence around sourcing, review, imagery, and safer publishing handoffs. The newsroom could operate independently of one laptop without becoming an unattended content machine.

woosteroperations

Discord made Wooster’s early agent workflow visible, but it also exposed the limits of coordinating through conversation: handoffs collided, ownership blurred, and approval state was easy to lose. I directed the move into a Command Center with durable state for intake, research, visuals, approvals, publishing, and delivery. Agents could execute the workflow; the editor still controlled the judgment.

operationsdocumentation

I turned repeatable operating patterns into reusable skills: agent onboarding, documentation research, workspace cleanup, publishing operations, and the resume-site feed itself. I paired that with a durable achievement record. The operating principle was direct: if a process repeats, build the tool instead of setting another reminder.

designproduct

I rebuilt this site as a product, not a static document. A concise business card and dated operating log replaced the familiar chronology, making the throughline visible to a cold reader: what I have built, how I think, and where I am headed.

mediapublishing

I set Wooster’s editorial identity before its first full publishing pass, defining the formats, visual rules, and review standard that would govern the product. The first release then carried a story from signal intake through research, drafting, imagery, editorial judgment, and publication. Wooster had moved from a magazine concept to a repeatable newsroom.

operationssystems

I formalized Technology Operations inside Vantage so tools, agents, automations, and reporting had ownership instead of becoming background maintenance. Status reporting, exception alerts, and a dedicated operating lane made technical reliability a managed function, not an afterthought.

aimedia

Wooster’s first working scan took the publication from concept to operation. The system collected music and culture signals, ranked story leads, preserved the strongest ones, and routed them into editorial review. The point was not automated content generation. It was an intake and judgment system for a new kind of media property.

managementcreative

Before Vantage, I built through Built By Seven and helped move an artist from unsigned to a major-label deal. It was a development assignment, not a discovery bet: grassroots marketing, digital strategy, positioning, and negotiation working together around the artist.

aioperations

I began building an AI-enabled operating layer around my work, connecting Gmail, Calendar, Discord, scheduled jobs, and durable memory. The aim was not a chatbot. It was staff infrastructure: a system that could retain context, run recurring work, and keep projects moving between decisions.

royaltiesinfrastructure

At gamma, I translated bespoke artist agreements into Curve’s standardized royalty logic. The work was less about software than preserving the meaning of deal language through edge cases, so a manual process could become infrastructure that scaled without losing the economics it was meant to honor.

operationsinfrastructure

At gamma, I joined a recorded-music operation without mature royalty infrastructure, inherited workflows, or much institutional memory. I helped build the department while the business kept moving, establishing the pattern that still defines my work: turn operational ambiguity into a system people can run.

Leon Booker