The Team
The team is working. This page keeps itself up to date.
← all jobs

Venue case study

3 people on it · 2 results

Team is working

What you asked for

Turn one real ANC install into a case study written for a venue general manager.

We need: the situation the venue was in, what ANC actually did, the outcome, and the proof behind

each part. Then creative direction for how the page should look, using approved photography of that

venue.

Constraints: pick a venue we genuinely have assets and detail for, and say which one you chose and

why. Every number cited or cut. Nothing invented about the client's business.

How the lead split it up

All three assignments are recorded. Here is the plan. — read it

All three assignments are recorded. Here is the plan.

Shape of the plan: Three assignments in two waves. The strategist goes first and builds the case study framework for Rocket Arena — narrative structure, proof points, what must be cut, pilot framing. The copy-chief and art-director run in parallel on the second wave: the copy-chief writes the 600–900 word case study prose from the framework, and the art-director writes the page creative direction from the same framework. The proof-officer runs automatically at the end.

Venue chosen: Rocket Arena (Cavs, Cleveland). It is the only pro-sports venue in the knowledge packs with deep real assets — an engineering case study with specs and a 2005→2014→now timeline, penthouse photography, and tunnel photography ×2, all in public/dealdeck/anc-real/. Every other pro-sports venue has thinner or zero asset coverage.

Biggest risk I am watching: The detailed asset inventory could not be read. We know asset types exist (penthouse, tunnel, engineering case study) but cannot enumerate exact filenames or confirm whether we have a wide exterior, concourse, or fan-perspective shot. The art director is directed to name any missing shot explicitly — but if Ahmad has a more complete asset list, sharing it before the art director finishes would let us use the full inventory instead of working around the gap. That is the one thing Ahmad must decide or supply.

Getting started…

Who is doing what

Priya Raghavan

Vertical Strategist

Build the case study framework for Rocket Arena (Cavs, Cleveland), written for a venue general manager audience. Read the job notes first. The venue is already chosen — Rocket Arena — and the choice rationale is documented there. Your job is the strategic skeleton, not finished prose. Produce a structured framework document with these sections: 1. **Audience angle** — Why this story lands for a venue GM. What does a GM care about that this case study answers? 2–3 sentences. 2. **Narrative structure** — Map the case study into four parts: (a) The situation the venue was in, (b) What ANC actually did, (c) The outcome, (d) The proof behind each part. For each part, list the specific proof points you have from the knowledge packs (e.g., the 2005→2014→now timeline, the engineering case study with specs/dimensions, penthouse photography, tunnel photography). Be explicit about what proof exists and what does NOT exist and therefore must be cut. 3. **What must be cut** — A numbered list of claims that cannot be supported and must be omitted (e.g., specific revenue figures, fan engagement metrics, venue capacity, exact square footage if not in the packs). 4. **Pilot framing** — How to position this as a first prototype (per the verticals strategy: "first prototype, NOT the whole strategy") so a GM sees it as a model they could say yes to, not a closed book. Keep it to one page. This is a skeleton the copy-chief and art-director will build from.

Finished
what they were asked

Build the case study framework for Rocket Arena (Cavs, Cleveland), written for a venue general manager audience. Read the job notes first. The venue is already chosen — Rocket Arena — and the choice rationale is documented there. Your job is the strategic skeleton, not finished prose. Produce a structured framework document with these sections: 1. **Audience angle** — Why this story lands for a venue GM. What does a GM care about that this case study answers? 2–3 sentences. 2. **Narrative structure** — Map the case study into four parts: (a) The situation the venue was in, (b) What ANC actually did, (c) The outcome, (d) The proof behind each part. For each part, list the specific proof points you have from the knowledge packs (e.g., the 2005→2014→now timeline, the engineering case study with specs/dimensions, penthouse photography, tunnel photography). Be explicit about what proof exists and what does NOT exist and therefore must be cut. 3. **What must be cut** — A numbered list of claims that cannot be supported and must be omitted (e.g., specific revenue figures, fan engagement metrics, venue capacity, exact square footage if not in the packs). 4. **Pilot framing** — How to position this as a first prototype (per the verticals strategy: "first prototype, NOT the whole strategy") so a GM sees it as a model they could say yes to, not a closed book. Keep it to one page. This is a skeleton the copy-chief and art-director will build from.

Done means: Structured framework document, one page max, with four labeled sections: Audience Angle, Narrative Structure (with proof points per part and explicit gaps), What Must Be Cut (numbered list), and Pilot Framing. Every proof point cited must trace to a knowledge pack. Any claim that cannot be sourced must appear in the "What Must Be Cut" list, not in the narrative structure. No invented numbers. No vendor or platform names. Say "technology" not "screens" or "LED" when describing ANC's offer broadly. No stock or generic imagery references — name only the real asset types known to exist (penthouse, tunnel ×2, engineering case study material in public/dealdeck/anc-real/).

Elena Marsh

Copy Chiefafter strategist

Write the case study copy for Rocket Arena (Cavs, Cleveland), aimed at a venue general manager. Read the job notes first. Then build on the strategist's framework (depends on it). Write finished prose — not an outline — covering four parts in this order: 1. **The Situation** — What the venue was working with before ANC's involvement, and what the operational or fan-experience challenge was. Only state what the knowledge packs support. If the packs reference a 2005 starting point in the timeline, use it. If the specific pre-ANC condition is not documented, keep this section to what is provable and cut the rest. 2. **What ANC Did** — Describe the installation and the evolving relationship (the 2005→2014→now timeline is documented). Describe what the viewer experiences — the technology, the integration, the penthouse, the tunnel — using "technology" not "screens" or "LED" for ANC's offer broadly. No vendor names, no platform names, no engineering jargon. 3. **The Outcome** — State only what is supported. If no revenue, engagement, or capacity numbers exist in the packs, write the outcome qualitatively: what the relationship demonstrates, what the venue now has, what a peer venue can take from it. Do not fabricate business results. 4. **The Proof** — A short closing section that names the real proof behind the case study: the engineering case study material, the photography of the penthouse and tunnel, the documented multi-phase timeline. This is where you make the case study credible to a GM who wants to see receipts. Total length: 600–900 words. Write in terse, professional, shipped-tense prose. No preamble, no closing pleasantries, no blockquotes, no cheerleading, no "imagine" language. This is a case study a GM reads in three minutes and believes.

Working
what they were asked

Write the case study copy for Rocket Arena (Cavs, Cleveland), aimed at a venue general manager. Read the job notes first. Then build on the strategist's framework (depends on it). Write finished prose — not an outline — covering four parts in this order: 1. **The Situation** — What the venue was working with before ANC's involvement, and what the operational or fan-experience challenge was. Only state what the knowledge packs support. If the packs reference a 2005 starting point in the timeline, use it. If the specific pre-ANC condition is not documented, keep this section to what is provable and cut the rest. 2. **What ANC Did** — Describe the installation and the evolving relationship (the 2005→2014→now timeline is documented). Describe what the viewer experiences — the technology, the integration, the penthouse, the tunnel — using "technology" not "screens" or "LED" for ANC's offer broadly. No vendor names, no platform names, no engineering jargon. 3. **The Outcome** — State only what is supported. If no revenue, engagement, or capacity numbers exist in the packs, write the outcome qualitatively: what the relationship demonstrates, what the venue now has, what a peer venue can take from it. Do not fabricate business results. 4. **The Proof** — A short closing section that names the real proof behind the case study: the engineering case study material, the photography of the penthouse and tunnel, the documented multi-phase timeline. This is where you make the case study credible to a GM who wants to see receipts. Total length: 600–900 words. Write in terse, professional, shipped-tense prose. No preamble, no closing pleasantries, no blockquotes, no cheerleading, no "imagine" language. This is a case study a GM reads in three minutes and believes.

Done means: Finished prose, 600–900 words, four labeled sections (Situation, What ANC Did, Outcome, Proof). Every number or factual claim must trace to a knowledge pack — if it cannot, the sentence is cut. No invented venue capacity, revenue, engagement metrics, square footage, or partnership duration beyond what the packs state. No vendor, platform, library, or host names. Say "technology" not "screens" or "LED" when describing ANC's offer broadly. No stock photography references. No blockquotes. No preamble or closing pleasantries. Voice is terse, professional, shipped-tense. Include a short parenthetical after any claim sourced from the packs noting which knowledge entry it came from (e.g., "per anc-verticals").

Theo Nakamura

Art Directorafter strategist

Write the creative direction for how the Rocket Arena case study page should look, using only real, approved ANC photography of that venue. Read the job notes first. Then build on the strategist's framework (depends on it). Produce a creative direction document that a designer could execute from. Cover: 1. **Page structure** — Section-by-section layout: what goes where on the page, in order. Map the four case study sections (Situation, What ANC Did, Outcome, Proof) to visual treatment. Name which real asset type goes with which section (penthouse photography, tunnel photography, engineering case study material — all in public/dealdeck/anc-real/). 2. **Visual treatment per section** — For each section, specify: image treatment (full-bleed, inset, split, overlay), text placement relative to imagery, and the emotional register the visual should carry for a GM audience (e.g., authority, scale, proof, partnership). 3. **Brand application** — ANC brand kit application: dark theme (#0A0F1C bg, #101A2E surface), Space Grotesk headings, Inter body, IBM Plex Mono for labels/eyebrows, ANC blue #0A52EF for accents/buttons, cyan #00AEEF for highlights. Logo: anc-white.png on dark backgrounds. Specify where the logo sits and how the color system is applied. 4. **Missing assets** — Name any specific shot you need but cannot confirm exists in the asset inventory. The asset list could not be read, so you know asset types (penthouse, tunnel ×2, engineering case study) but not exact filenames. If you need a wide venue exterior, a concourse shot, or a fan-perspective shot that you cannot confirm, say so explicitly and name what is needed. Do not produce the page itself — produce the direction. No stock photography, no generic arena imagery, no AI-generated visuals.

Finished
what they were asked

Write the creative direction for how the Rocket Arena case study page should look, using only real, approved ANC photography of that venue. Read the job notes first. Then build on the strategist's framework (depends on it). Produce a creative direction document that a designer could execute from. Cover: 1. **Page structure** — Section-by-section layout: what goes where on the page, in order. Map the four case study sections (Situation, What ANC Did, Outcome, Proof) to visual treatment. Name which real asset type goes with which section (penthouse photography, tunnel photography, engineering case study material — all in public/dealdeck/anc-real/). 2. **Visual treatment per section** — For each section, specify: image treatment (full-bleed, inset, split, overlay), text placement relative to imagery, and the emotional register the visual should carry for a GM audience (e.g., authority, scale, proof, partnership). 3. **Brand application** — ANC brand kit application: dark theme (#0A0F1C bg, #101A2E surface), Space Grotesk headings, Inter body, IBM Plex Mono for labels/eyebrows, ANC blue #0A52EF for accents/buttons, cyan #00AEEF for highlights. Logo: anc-white.png on dark backgrounds. Specify where the logo sits and how the color system is applied. 4. **Missing assets** — Name any specific shot you need but cannot confirm exists in the asset inventory. The asset list could not be read, so you know asset types (penthouse, tunnel ×2, engineering case study) but not exact filenames. If you need a wide venue exterior, a concourse shot, or a fan-perspective shot that you cannot confirm, say so explicitly and name what is needed. Do not produce the page itself — produce the direction. No stock photography, no generic arena imagery, no AI-generated visuals.

Done means: Creative direction document with four labeled sections: Page Structure, Visual Treatment Per Section, Brand Application, Missing Assets. Every image reference must be to a real ANC asset type known to exist (penthouse, tunnel ×2, engineering case study material in public/dealdeck/anc-real/) — never stock, never generic, never AI-generated. Brand application must use the exact hex values and font families from the ANC brand kit. The Missing Assets section must explicitly name any shot needed but unconfirmed. No vendor, platform, or host names. Say "technology" not "screens" or "LED" where ANC's offer is described broadly. No blockquotes.

Results

Brief: Venue case study — Vertical Strategist

strategist · copy

Not checked yetYour call

---

Venue: Rocket Arena (Cavs, Cleveland)

Chosen because: It is the only professional-sports venue in the approved asset inventory with deep, named photography and an engineering case study on file. No other pro-sports venue in the packs carries a comparable proof set.

---

1. Audience angle

A venue general manager owns the tension between long-term infrastructure decisions and day-to-day revenue pressure. They care whether a technology partner stays past the ribbon-cutting. This case study answers one question directly: what does it look like when a partner is still inside the building twenty years later, upgrading instead of replacing?

---

2. Narrative structure

(a) The situation

The venue needed a technology partner who could evolve with the building across multiple eras — not a one-time installation.

Proof on file: The engineering case study documents a relationship arc from 2005 through 2014 to the present.

Gap: The knowledge packs reference "real specs/dimensions" in the case study material but do not reproduce the actual numbers. Specific dimensions, pixel pitch, and square footage cannot be asserted without access to the underlying document. These must be held as cited attributes of the case study, not as extracted facts.

(b) What ANC actually did

ANC designed, built, and operates large-format technology throughout the venue, updating systems across multiple phases instead of walking away after the initial installation.

Proof on file: The 2005→2014→now timeline demonstrates phased work across two decades. The penthouse and tunnel photography show the physical scope of the install.

Gap: No detailed scope list (number of displays, specific zones beyond penthouse/tunnel) is enumerated in the packs. The art director must confirm exact shot coverage in public/dealdeck/anc-real/.

(c) The outcome

The partnership is still active, with ANC providing ongoing operation and technology upgrades rather than a handoff.

Proof on file: The timeline extends to "now," framed as a 20-year relationship. Stevie Dohm, the venue manager, is the first external arena-manager user of ANC's venue platform, validating that the relationship is operational, not historical.

Gap: No business outcome metrics — revenue, fan engagement, sponsorship yield, or operational savings — are in the knowledge packs.

(d) The proof behind each part

  • Timeline credibility: engineering case study material in public/dealdeck/anc-real/.
  • Visual evidence: penthouse photography, tunnel photography ×2, both in same directory.
  • Operational validation: Stevie Dohm's adoption of the venue platform as first external user.
  • Live frame reference: the vertical-worlds prototype at [internal build reference] shows how the story module renders.

---

3. What must be cut

  1. Specific engineering dimensions. The packs confirm a case study with specs exists but do not reproduce the numbers. Cite the case study as source material; do not quote dimensions.
  2. Venue capacity, attendance figures, or square footage. Not in packs.
  3. Revenue or ROI outcomes. No uplift, sponsorship yield, or ticket-sales attribution exists.
  4. Fan engagement metrics. No dwell time, interaction rate, or social data.
  5. Pixel pitch or technical specifications of the hardware. The engineering case study may hold these, but they are not surfaced in the knowledge packs.
  6. Photography beyond the confirmed set. Reference only penthouse, tunnel ×2, and engineering case study material. Do not imply additional angles exist until the asset inventory is readable.

---

4. Pilot framing

Present Rocket Arena as the first prototype — a single venue that proves the case-study format, not a finished library. The GM reads it as: "This is what ANC built for Cleveland. Give us your building's photography and engineering history, and we turn the same framework around for you in one cycle." The collaboration lane stays open: ANC Design owns brand polish and final asset selection; this skeleton is the experimental storytelling layer they can adopt or reshape without added workload.

---

Ahmad must supply: Access to the engineering case study document in public/dealdeck/anc-real/ so the copy-chief can extract and verify specific dimensions before the prose layer ships. If those numbers are needed in final copy, they must come from that document, not from the knowledge packs.

They wanted you to know: Captured automatically — the agent finished the work but did not call save_deliverable.

Brief: Venue case study — Art Director

art-director · copy

Not checked yetYour call

Creative Direction — Rocket Arena Case Study Page

1. Page Structure

Hero — Situation

Full-bleed establishing image anchored to the viewport top. One confirmed tunnel photograph from public/dealdeck/anc-real/ fills the frame. A bottom-weighted gradient overlay carries the section text. This is the entry point: it tells a GM they are looking at a building like theirs, not a product catalog.

Section 2 — What ANC Did

Split layout, 55/45 image-to-text. The confirmed penthouse photograph from public/dealdeck/anc-real/ occupies the left column, uncropped at full height. The right column carries the narrative on a solid surface panel. The penthouse shot proves physical scope — it shows ANC technology installed in the venue's premium sight lines.

Section 3 — Outcome

Full-bleed second tunnel photograph from public/dealdeck/anc-real/. Text is bottom-right aligned with a left-side gradient to preserve the image's architectural lines. This section carries the proof of continuity: the same building, years later, still operational. The tunnel angle reinforces that the partnership lives in the building's circulation paths, not just the main bowl.

Section 4 — Proof

Inset module, not full bleed. Engineering case study material from public/dealdeck/anc-real/ is displayed as documentary evidence — a contained frame on a darker surface panel. Text runs alongside or below, citing the 2005→2014→now timeline and Stevie Dohm's platform adoption. This section reads as verification, not storytelling.

---

2. Visual Treatment Per Section

Hero / Situation

  • Image treatment: Full bleed, minimum 100vh. The tunnel photograph is cropped to emphasize depth and vertical scale — the architecture should pull the eye toward a vanishing point.
  • Text placement: Bottom-left quadrant, anchored with 6% viewport padding. Two lines maximum: eyebrow above, headline below.
  • Overlay: A graduated black-to-transparent scrim rising from the bottom, reaching 60% opacity at the base, fading to 0% at center frame. This keeps the image dominant while holding text at WCAG-compliant contrast.
  • Emotional register: Authority and stakes. The GM should feel the scale of the infrastructure decision before reading a word.

Section 2 / What ANC Did

  • Image treatment: Inset split. The penthouse photograph is displayed at native aspect ratio, left-aligned, with no artificial widening. If the source image is vertical, the text panel breathes beside it; if horizontal, reverse the split to 45/55 image-right.
  • Text placement: Vertically centered in the right panel, left-aligned, with generous internal padding (minimum 64px).
  • Border treatment: A 1px rule in rgba(255,255,255,.075) separates image and text panels only if the image lacks a natural edge.
  • Emotional register: Capability and precision. The penthouse is premium real estate; the layout should feel considered, not loud.

Section 3 / Outcome

  • Image treatment: Full bleed, 75vh minimum. The second tunnel photograph should be composed differently from the hero — if hero is wide and vertical, this is horizontal and human-scale, or vice versa. The variation proves breadth of coverage.
  • Text placement: Bottom-right, aligned to the same grid margin as the hero's left anchoring, creating visual rhythm across the page.
  • Overlay: A diagonal or left-to-right gradient that preserves the tunnel's right-hand architecture. Opacity peaking at 55% on the left, 0% on the right.
  • Emotional register: Continuity and operational proof. The technology is still in the building, still working, still maintained.

Section 4 / Proof

  • Image treatment: Contained inset, maximum 800px wide, centered. Engineering case study material is shown as a document — a photograph of a spec sheet, a dimensional diagram, or a project photo from the case study file. A subtle 1px border in rgba(255,255,255,.14) frames it like evidence.
  • Text placement: Below or beside the inset, in two short blocks: one for the timeline, one for the operational validation (Stevie Dohm).
  • Background: Step down to surface-2 #15213A to signal a shift from story to verification.
  • Emotional register: Credibility and documentation. This is the folder a GM opens during budget review.

---

3. Brand Application

Color system

  • Page background: #0A0F1C
  • Primary surface panels (text blocks): #101A2E
  • Secondary surface (proof module): #15213A
  • Primary text: #EBF1FC
  • Secondary text: #93A2C2
  • Accent fills / buttons: #0A52EF
  • Accent highlights / eyebrows: #00AEEF
  • Dividers: rgba(255,255,255,.075) and rgba(255,255,255,.14)

Typography

  • Eyebrows / labels / timeline dates: IBM Plex Mono, 11.5px, uppercase, letter-spacing 0.3em, color #00AEEF
  • Headlines (all sections): Space Grotesk, 600/700, letter-spacing -0.02em, color #EBF1FC
  • Body copy: Inter, 400/500, color #EBF1FC; secondary lines in #93A2C2
  • Button / CTA (if used): IBM Plex Mono, 13px, #FFFFFF on #0A52EF, pill radius 999px, padding 10px 18px

Logo

  • Asset: anc-white.png (1060×272, transparent, checksum 1007844288 5618)
  • Placement: Top-left of the page, pinned at scroll, 32px from top and left edges. Scales to 160px wide on desktop, 120px on mobile.
  • Treatment: No effects. Flat white mark on the dark field. On the hero image, the logo sits directly on the photography above the text block, separated by a minimum 48px clearspace.

Negative space

  • Minimum section padding: 120px vertical on desktop, 80px on mobile.
  • Text never touches the edge of an image. Minimum 48px padding between type and any image boundary.

---

4. Missing Assets

The asset inventory could not be read; the following shots are required to complete the direction as specified but cannot be confirmed in public/dealdeck/anc-real/:

  1. Wide exterior of Rocket Arena, dusk or night. Needed for an alternative hero option that establishes the building from the outside. Current direction relies on interior tunnel photography; an exterior would let the GM recognize their own potential starting point.
  1. Concourse or circulation-area photography showing technology in a fan-use context. Needed for Section 3 (Outcome) if the second tunnel shot is too similar to the hero tunnel shot. The two tunnel photographs are confirmed to exist, but their angles and coverage are unknown. If they overlap in composition, a concourse shot would provide the necessary visual variation.
  1. Close-up detail of ANC technology installed at Rocket Arena, showing hardware craft or mounting. Needed for Section 2 to prove build quality at a human scale. The penthouse shot shows scope; a detail shot would show precision. Not confirmed in inventory.
  1. Stevie Dohm portrait or candid in the venue, preferably near the technology. Needed for Section 4 to attach a human face to the operational proof. The knowledge packs confirm Dohm's role as the first external arena-manager user of the venue platform; no photography of him at Rocket Arena is confirmed.
  1. Before / during-installation photography from the 2005 or 2014 phases. Needed if the engineering case study material does not contain archival images that show the timeline visually. The packs confirm the timeline exists; they do not confirm visual documentation of earlier phases.

Ahmad must supply: Exact filenames and dimensions for the penthouse, tunnel ×2, and engineering case study photographs in public/dealdeck/anc-real/, plus confirmation of whether any of the five missing shots above exist in that directory or elsewhere in ANC's approved library. Without that confirmation, the designer must execute using only the four confirmed asset types and leave placeholder modules for any unverified shots.

They wanted you to know: Captured automatically — the agent finished the work but did not call save_deliverable.