The agent workforce

Meet the workforce.

Bluestuff is run by a workforce of specialised AI agents — each with a real job, working together on a platform that makes their output production-ready. This page is the org chart. It keeps growing: new agents ship as new functions need them.

Not a feature list

What makes this a workforce, not a feature list

Three things separate a workforce from a feature list: the agents do the work rather than suggest it, they hand off to each other like any functioning team, and they sit on a platform with real APIs, real player data, and real compliance workflows — the unglamorous reason their output goes live while most AI agents produce demos.

01

They do the work

Every agent owns an outcome, not a suggestion. That’s the whole difference between an assistant and a colleague.

Brand OrchestratorSuggests a brandCreates, configures, and deploys one
Frontend DeveloperAutocompletes a componentArchitects a production casino UI
QA AgentLists what you should testWrites the tests and runs them

Deliverables, not drafts

02

They work together

Requirements flow down a real handoff chain, and every stage has an owner that can hand work back.

  1. 1Product HeadPRD
  2. 2DesignerDesign tokens
  3. 3Frontend DeveloperProduction files
  4. 4QA AgentTest run
  5. 5ReviewerVerdict
  6. 6API AnalystLive wiring

Output of one is input to the next

03

They sit on a real platform

The agents run against the same production systems your operation runs on — nothing is mocked for the demo.

Real APIsThe same SDK the platform itself runs on
Real player dataProduction accounts, wallets, and sessions
Real compliance workflowsLimits, exclusions, and approvals enforced

Why the output goes live

By function

The workforce, by function.

Coverage is what matters, not a count — the workforce grows as new functions need agents.

BuildBuilding & launching

Brand and site built rather than configured from a template — a production casino and sportsbook front end, wired to the platform and shipped.

Brand OrchestratorCreates, deploys, and configures the operator’s brand, end to end.
Product HeadRequirements, competitor analysis, evaluation, quality gate.
Product Manager AgentStructured, buildable tickets.
Designer AgentDesign tokens, component hierarchy, coherent design system.
Frontend Developer AgentProduction React/TypeScript casino and sportsbook interfaces.
QA AgentWrites and executes functional tests, replicates manual testing.
Reviewer AgentSeven-dimension code review before anything ships.
API Analyst AgentSDK integration and API plumbing done right.
TradeTrading the book

Trading decisions on the sportsbook — prices set, liability managed, and limits adjusted in real time.

Trading AgentMonitors liability across every market, moves prices as money and results come in, and adjusts limits — with the operator’s risk appetite as the boundary, not a suggestion.
GrowGrowing the brand

Acquisition run across the channels that bring players in — organic, paid, and social — with operator approval on everything that spends.

SEO & Content AgentOrganic reach, content, and landing pages.
Meta Ads AgentCampaigns, budgets, A/B tests, with operator approval on every move.
Social Media AgentChannels, posts, and community.
RetainLooking after players

Player support that resolves the query instead of deflecting it — and stays on afterwards as a companion, not a widget.

The central intelligence

The central intelligence

Underneath the workforce sits the thing that makes it more than the sum of its agents: a real-time intelligence layer with access across the whole estate, connecting the business view to the technical view. When revenue moves in a market, it traces the movement to the journey, the application, the query, and the code line.

It’s how the workforce sees.

Access across the whole estate
AppApplication logs
InfraSystem logs
SignalsMetrics
BusinessBI
SourceCodebase
ContextDocumentation
all six, one system
Central intelligenceBusiness view and technical view, in one place, in real timeLive
One trace, end to endStep 5 / 5
SignalRevenue moves in a marketThe signal that starts the trace
1
The journeyWhich player path changed
2
The applicationWhich service sits behind it
3
The queryWhat it actually returned
4
The code lineThe line moving the number
B2B Roster

The agents that build and run your operation.

Tap any agent to see its full capabilities. Filter by category.

  • B2B · Build

    Brand Orchestrator

    Creates & deploys brands

    Creates, deploys, and configures the operator's entire brand identity — name, logo, colour palette, typography, tone of voice — and pushes it live to the frontend.

    Capabilities
    • Brand creation from brief
    • Design token generation
    • Multi-brand management
    • Live deployment
B2C Agents

The Player-Facing Agents

The agents that talk directly to your players — turning support into a product, and idle moments into engagement.

24/7 player companion
CS Agent++
24/7 personalised companion — deposits, bets, game analytics, match analysis — all in the player's language.
End to end
Resolved, not deflected
Read more
The Workflow

How they work together.

Every agent sits on enterprise-grade infrastructure. Real APIs. Real player data. Real compliance workflows. That's why the output goes live.

Sequence Diagram — Full Build Trace

User → Orchestrator → 7 specialist agents. Solid arrow = call, dashed arrow = return.

30/30
USER
ORCHESTRATOR
PRODUCT-HEAD
DESIGNER
DEVELOPER
SPORTS-AGENT
CASINO-ORIGINALS
REVIEWER
Build Hybrid — Sports + Casino + Crash
Pre-flight scan · 6 screenshots · docs · reference HTML · MEMORY.md → all confirmed
Phase 1PRD Generation26 tool calls · 91.4k tokens · 4m 39s
Generate PRD — read docs, extract tokens, design 3D concept
Vision-read 6 screenshots · catalogue 20 failure modes · design "Deep Space Launch" 3D concept
✅ PRD complete · 35 P0 features · STATUS: AWAITING_USER_APPROVAL
MANDATORY USER GATEOrchestrator STOPS · surfaces PRD evaluation · awaits user APPROVE
Surfacing PRD — tokens · sprite spec · 3D concept · reply APPROVE
✅ APPROVED — theme toggle must affect crash chrome too
Phase 2Designer Mock4-tab HTML · self-contained · 10 pattern checks
Create 4-section HTML mock — Sports · Casino · Crash 2D · Crash 3D
Vision-read 6 screenshots · read reference HTML (4 passes) · write -hybrid-mock.html · 10 banned-pattern checks PASS
✅ Mock saved → HANDOFF → product-head
Phase 3Mock Evaluation10-dimension rubric · auto-approve at ≥40/50
Evaluate mock against PRD — score 10 dimensions
✅ APPROVED — Score 46/50 · HANDOFF → developer
Phase 4Foundation + Sports + Casinodeveloper + sports-agent · 3 sub-handoffs
Build foundation — theme · Redux (8 slices) · MainLayout · modals · session restore
✅ Foundation done → HANDOFF → sports-agent
SignalR hook + sports Redux + betslip + market config
✅ SignalR + sports Redux ready → HANDOFF → developer
Build Sports + Casino pages — 2-col fixture grid · Hot Multis · real game launch
Phase 5Crash Game (2D + 3D)Canvas sprite + React Three Fiber · real socket
Build Crash — CrashApi · GraphQL init · 2D sprite (4×5) · 3D scene (stars + nebula + orbit) · state machine
✅ Crash 2D + 3D complete → HANDOFF → developer
Integrate crash · theme chrome · npm run build · tsc --noEmit
Phase 6Code Review10-dim rubric · gate at ≥80/100 · zero critical
10-dimension review · validate PRD · mock · API · edge cases · no Math.random
✅ Score 88/100 · zero critical issues · build clean
🎉 DELIVERED — Hybrid Platform (Sports + Casino + Crash)
USER
ORCHESTRATOR
PRODUCT-HEAD
DESIGNER
DEVELOPER
SPORTS-AGENT
CASINO-ORIGINALS
REVIEWER
CallReturnUser gateLane lifelineScroll horizontally to view all lanes
Working alongside your team

Working alongside your team

Agents don’t require replacing anyone. Established Operators (Tier 1) typically start with one function — CS is the usual door in — and expand as confidence builds. Your team sets direction and approves; the workforce executes.

The operators getting the most from Bluestuff describe the shift the same way: their people stopped doing investigations and started doing product.

HoldsYour team
  • Sets direction and priorities
  • Approves everything that ships
  • Owns the commercial call
ExecutesThe agent workforce
  • Does the work, end to end
  • Runs the pipeline at volume, around the clock
  • Never the final approver
The release gateHumans hold approval at every step that ships
01Brief
02Design
03Build
04Release

Agents do the work · your team keeps the control

The usual door inCS Agent++ — One function first, expanding as confidence builds
FAQ

The workforce, answered

We’ve stopped counting publicly, and that’s deliberate — the workforce grows as new functions need agents. What matters is coverage: brand, product, development, QA, games, growth, and player support are all handled today.

Something not covered?
The first conversation is a walkthrough of what you want to build — not a slide deck.
Book a walkthrough

Every Bluestuff product runs both ways.

The workforce and the intelligence underneath it are the same either way. The only question is whether Bluestuff is your platform, or sits on top of the one you already run.

Run it as your full stack, or as the AI layer on top of the platform you already have.

One layer, two basesMode A
Agent workforceThe same specialists, either way
Unchanged
Central intelligenceReal-time visibility across whatever sits below
runs on
Bluestuff platformAccounts · wallet · payments · bonusing · CRM · riskOurs
Underneath