Case studies

Three jobs, start to finish.

A SwarmPack is a ready-made team for one kind of job. Here is how three of them hunt: what you drop in, which fish does what, and what you hold at the end. Every pack on the shelf follows the same shape.

01 · Data
Dashboard Forge

A spreadsheet goes in. A dashboard you can present comes out.

You have the numbers already — in a spreadsheet nobody wants to open in a meeting. This pack turns it into a live dashboard, and checks every figure against the source before it lets you show it.

What you drop in
  1. One or more .xlsx or .csv files, dropped onto the Files panel.
  2. A sentence about what decisions the dashboard should help with.
  3. A budget in dollars and minutes — the listing shows the typical range before you start.
Who's on the team
01
Producer Pins down which decisions the dashboard serves before anything gets built.
02
Data Wrangler Profiles your sheets: what's in them, what's missing, what looks wrong.
03
Dashboard Builder Builds one self-contained dashboard file you can open right in the workspace.
04
Numbers Checker Recomputes every displayed figure from the raw data and eyeballs the rendered result. A mismatch blocks ship.
What comes out
  • A single dashboard file that opens in the workspace and in a browser.
  • A data-rules page recording what was cleaned, dropped, or assumed.
  • The run log: who did what, in what order, and what it cost.
WHAT THE CHECKER DOES
revenue by regionrecomputed · match
churn Q3recomputed · match
pipeline totaloff by 1 row · fixed
verdictship
Good for: Finance, ops, and anyone who reports numbers to someone else.Runs on the Dashboard Forge SwarmPack, on the shelf inside the app.
02 · Product
UX Reviewer

A stranger uses your app on camera and tells you where it loses them.

Scripted tests only walk paths their author already knew. This pack gives an agent a persona and a goal, lets it get lost in your real product, films the journey, and writes the design review.

What you drop in
  1. A running copy of your app — local or a staging URL.
  2. Who the user is and what they're trying to do, in a sentence each.
  3. Optional: the parts you already know are rough, so the team spends its time elsewhere.
Who's on the team
01
Explorer A first-time user in persona: browses the live app, logs every hesitation with a screenshot.
02
Recorder Replays each discovered journey as a script with video on — reproducible footage, not a one-off.
03
Design Critic Judges the footage against the heuristics pages and writes the severity-ranked report.
What comes out
  • Annotated screenshots at every point of confusion.
  • Video of each journey you can replay and share.
  • A design review ranked by severity, with the fix suggested for each finding.
A SAMPLE FINDING
checkout · step 2no next action on empty cart
severityhigh
evidencejourney-02.mp4 · 00:41
fixempty state with a return link
Good for: Product teams shipping to people who won't read the docs.Runs on the UX Reviewer SwarmPack, on the shelf inside the app.
03 · Code
PR Inspection Line

A pull request goes in one end. Graded findings and a verdict come out the other.

Most review packs collaborate — messaging, escalating, renegotiating. This one runs like a factory line: eight fixed stations, each reads what the last one wrote, and different models catch different things.

What you drop in
  1. A pull request URL, or a branch and its base.
  2. The ticket or a one-line statement of what the change is supposed to do.
  3. Report-only by default — nothing is posted to the PR unless you say so.
Who's on the team
01
Line Foreman PR in, intake sheet out; runs the stations in order.
02
Change Mapper Diff to change map: files, hunks, symbols, call sites, stated intent.
03
Correctness Inspector Logic errors, regressions, edge cases, error handling.
04
Security & Test Inspector Injection, secrets, authorization, and the tests the change forgot — on a different model than the correctness lane, on purpose.
05
Intent Checker Does the PR do what the ticket says, and only that?
06
Gate Inspector Mechanical acceptance: schema, dedup, scope. Computes the verdict.
07
Fix Drafter Suggestion-block patches for one-hunk fixes. Never pushes to your branch.
08
Status Clerk What changed, why, what needs attention — then the verdict.
What comes out
  • A findings ledger: file and line, evidence, impact, and the fix, on every row.
  • A plain-language status note a manager can read without opening the diff.
  • A merge verdict, and the reason for it.
FINDINGS LEDGER · EXCERPT
api/routes.ts:212unchecked null on user id
db/schema.sql:40missing index for new query
testsno case for expired token
verdictchanges requested
Good for: Engineering teams who want every PR read the same way, every time.Runs on the PR Inspection Line SwarmPack, on the shelf inside the app.
Every pack, the same shape

Pick the job. Set the budget. Hold the result.

SwarmPacks has teams for finance, product, engineering, marketing, and operations. Each one shows its time and cost estimate before you start, runs in your selected local or remote environment, and leaves a log of who did what.