Commercial strategy · 31 July 2026

Four things ANC can sell to the clients it already has

Grounded in ANC's live pipeline, closed-won history, open service tickets, contracted-service catalogue and display registry — not in a market report.

1. What the data actually says about ANC

What ANC sells

Three business units carry the open pipeline: Technology (400 open deals, ~$704M), Venue Services (203 deals, ~$31M) and Media & Sponsorship (37 deals, ~$9.8M). Hardware and integration dominate the money; services and software are the long tail — and the long tail is where the recurring revenue lives.

The contracted-service catalogue is explicit — eleven toggles per venue: White Glove, Break/Fix, Event Support, Walkthroughs, Operations, Scheduling, Tech Support, LiveSync, VisionStats, Parts, Game Day Support. Two of those eleven are already products, not labour.

ANC already sells software licences — that is the most important finding

The commercial precedent for "a venue pays ANC an annual fee for software" is established and signed. Nobody has to invent the motion — only extend it.

What clients buy after the install

Closed-won history is repetitive in a way that is very easy to productise:

What actually goes wrong after the install

The open ticket queue is the clearest product brief in the business. Of 28 open tickets: sections and cabinets out (Arkansas ribbon, Maine, Florida Panthers marquee), pixels (Westfield WTC), devices that stopped responding to polls (WMATA, repeatedly), KVMs not responding (Yum! Center), transmitter not visible, content blacking out (UMass Lowell), renders lagging (Maine), pitch data not working (Maimonides), LiveSync and UI updates (Gainbridge, Rutgers).

The tell: two of the highest-priority open tickets are voicemails — "Voicemail from (231) 590-7128", unassigned, critical. And WMATA's tickets carry the client's own incident and work-order numbers, because WMATA polls the devices and tells ANC. Today the client's phone system and the client's monitoring are ANC's fault-detection layer.

What ANC already holds that a software company cannot get

Where the money is currently leaking

2. The long list, and what I killed

Fan-engagement app / second screen. Killed. Crowded, owned by team digital departments, no ANC advantage, and it competes with the client's own vendors.
Venue digital twin / 3D operations model. Killed. Impressive, no budget owner, long build, and nobody's bonus depends on it.
Standalone white-label client portal. Killed as a product — nobody pays for a portal. It is the delivery wrapper for everything below, not the thing sold.
Energy / brightness optimisation and sustainability reporting. Parked. Real, but the buyer is diffuse and the savings are too small to survive a procurement cycle in the US market today.
Programmatic advertising network across venue screens. Parked deliberately. ANC has the OOH relationships (Orange Barrel, New Tradition) to make it credible, but it puts ANC in direct competition with its own clients' sponsorship sales teams. Channel conflict kills it as a first move.
Spares-as-a-service as its own product. Folded, not killed. The MetLife pattern proves the demand, but it is a pricing change to the service agreement, not a separate product — so it becomes a revenue line inside Opportunity 1 rather than a fifth pitch.
Selling the proposal engine / RFP intelligence to other integrators. Out of scope here — that is our SaaS, not ANC's client revenue, and it arms ANC's competitors.

3. The four that survive

Opportunity 1 — ANC Assurance recommended first

A monitored-estate subscription: ANC watches every display it installed, detects failures before the venue does, opens its own tickets automatically, and reports uptime against an SLA every month — plus a rolling spares and lifecycle forecast.

1 · Product concept

A collector runs on the LiveSync/control-system machines ANC already installs, polling processors, players and the display estate. Faults raise an alert, which becomes a ticket in ANC's service system, dispatched before the client calls. The client gets a live view of every display, its health and its history, plus a monthly SLA report and a 12–24 month replacement forecast built from real failure data.

2 · Buyer

Venue operations / facilities — the person who already signs the ANC service agreement. Budget line already exists; this is an uplift, not a new line item. Secondary sign-off: venue IT for network access.

3 · Pain

A dark board during a nationally televised game is a political event, not a maintenance event. Today the venue finds out from a fan, a broadcaster or an executive in a suite, then calls ANC and waits. Every hour of downtime is contractual exposure for the venue's own sponsor commitments.

4 · Why ANC wins

A software company monitoring these screens has to be let into the venue, learn the estate, and integrate with equipment it did not install. ANC installed it, holds the as-builts, owns the control system, and already has the technician who fixes it. Nobody else can close the loop from detection to repair inside one contract.

5 · Revenue model

6 · Sales path

Three doors, all of them existing: (a) the service-agreement renewal — Montana, ASU and UMass all renew annually; (b) attached to a live capital project where the client is already approving millions; (c) the post-incident conversation, which is the easiest sale in the business — sell it the week after a board goes dark.

7 · Workflow

Fault detected → alert raised → ticket auto-created and routed to the venue's ANC tech → client sees it in the portal already in progress → repair logged against the display → monthly SLA report emailed, showing uptime, mean time to detect, mean time to repair, and what is trending toward failure.

8 · Integrations and data

Processor and controller APIs / SNMP (Brompton, NovaStar, Colorlight, Daktronics where present), LiveSync server telemetry, player and scaler status, venue network access (VPN or outbound-only agent), the existing venue_screens registry, maintenance logs, and the ticket system. Everything on the ANC side already exists.

9 · MVP (30–60 days, one venue)

Outbound-only agent on the LiveSync machines at one venue reporting reachability plus processor status; alerts into the existing ticket system; the client-facing display board that is already built in the customer portal switched from text-matched health to real telemetry; one automated monthly SLA PDF. No ML, no prediction, no new hardware.

10 · Expansion

Telemetry depth (cabinet-level, brightness drift, thermal) → predictive replacement and the spares plan → capital planning reports the client uses to defend budget → the same data spine feeds Opportunity 2 → estate-wide contract for multi-venue operators.

11 · Risks

Venue IT will resist an agent — mitigate with outbound-only, no inbound ports, and a security one-pager. Older estates may expose no usable telemetry — the MVP must degrade to reachability plus manual walkthrough data. An SLA promise creates real liability, so v1 reports uptime rather than guaranteeing it. Support load rises; alerting must be tuned or it becomes noise ANC pays to ignore. And ANC must be willing to be measured — that is the deeper cultural risk.

12 · Score

RevenueSpeed to MVPStrategic fitEase of saleRecurringDefensibilityOps complexity (10 = simple)
891091096

Opportunity 2 — Verified Impressions

Automated proof that a sponsor's content actually played: which asset, on which display, how many times, for how long, at which events — turned into a sponsor-ready report and a yield view of unsold inventory.

1 · Product concept

LiveSync already decides what plays on every surface. That playback log, joined to the display registry and the event calendar, becomes a verified record of delivery: 41 ribbon runs, 12 centre-hung takeovers, 3 concourse loops, timestamped, per game. Reports go out under the venue's brand to each partner, and an internal view shows which inventory is going unsold.

2 · Buyer

Partnerships / sponsorship sales and the CRO — a revenue budget, not a cost budget, which approves faster and larger. Secondary: the marketing partnerships team at the brand itself.

3 · Pain

Sponsorship contracts promise counts of in-venue exposure, and renewal conversations turn on proving delivery. Today that proof is screenshots, spreadsheets and trust. Brands increasingly demand measurement, and third-party platforms measure what a camera can see — not what the control system knows it played.

4 · Why ANC wins

Everyone else infers exposure from video. ANC has the source of truth: the log of what the system actually rendered. That is a categorically stronger claim, and it costs ANC nothing to collect because ANC wrote the software that produces it.

5 · Revenue model

6 · Sales path

Not through operations. This goes through ANC's Media & Sponsorship relationships, or through an ops client's introduction to their own partnerships team. Strongest opener: run one month of retroactive proof from existing logs for free, then show the CRO what their renewal deck could have said.

7 · Workflow

Map sponsor assets to playlist items once → the system counts plays per event automatically → partnership manager opens a per-sponsor report before a renewal meeting → exports it branded → sees a yield board of surfaces that ran house content instead of paid content.

8 · Integrations and data

LiveSync playback logs (the dependency that decides feasibility), the display registry, the event calendar, sponsor-to-asset mapping (manual at first), and optionally attendance or ticketing data to convert plays into impressions.

9 · MVP

One venue, one month, ten sponsor assets: an ingest of playback logs, a mapping table, and a single clean PDF per sponsor. No impressions modelling, no computer vision, no live dashboard.

10 · Expansion

Impression modelling with attendance → benchmarking across ANC's installed base (a dataset nobody else can assemble) → yield optimisation → packaged rate-card intelligence sold to properties.

11 · Risks

Depends entirely on the fidelity of LiveSync logging — this must be verified in code before anything is promised. Where a venue already pays a measurement platform, ANC is arguing methodology, not need. Clients may consider the play logs their data, so contract language matters. And a report that proves under-delivery creates awkward conversations the venue may prefer not to have on paper.

12 · Score

RevenueSpeed to MVPStrategic fitEase of saleRecurringDefensibilityOps complexity (10 = simple)
96869107

Opportunity 3 — ANC Studio Desk

The content work ANC already does at $1,000 a graphic, sold instead as a monthly creative subscription with a request portal, turnaround SLA and a library that belongs to the venue.

1 · Product concept

A venue submits creative requests — sponsor graphics, resizes across every surface, game-day packages, banner reprints — through a portal that already knows every display's exact dimensions and pitch. ANC's designers deliver against a stated turnaround, with approvals and version history in the same place.

2 · Buyer

Marketing / game presentation, and the partnerships team when sponsor creative is involved. In colleges, one overloaded creative director; in pro venues, a game-presentation lead with a real budget.

3 · Pain

Every new sponsor asset must be resized for a dozen non-standard surfaces. Venues are chronically short of design capacity in season, and a missed resize means a sponsor asset that does not run — a contractual problem, not an aesthetic one.

4 · Why ANC wins

ANC knows the surfaces natively: exact pixel maps, safe areas and processing quirks are already in the registry. An external agency has to be told, and gets it wrong the first three times. ANC also already delivers this work — the change is packaging, not capability.

5 · Revenue model

6 · Sales path

Straight at the accounts that already buy graphics piecemeal — URI, WooSox, MetLife, Louisville. The line is simple: "you spent this much on eleven separate jobs last year; here is the same work with a turnaround guarantee for a fixed monthly number."

7 · Workflow

Request submitted with the target surfaces pre-listed → ANC designer picks it up → proof shared for approval → approved asset delivered in every required size and, where ANC operates the system, pushed to the playlist → everything retained in the venue's library.

8 · Integrations and data

The display registry for dimensions, the existing design-request and proof-share modules, the customer portal for approvals, and optionally direct delivery into LiveSync.

9 · MVP

Almost entirely built. Turn on the existing design-request and proof modules for one client, add a request-volume counter and a turnaround clock, and invoice monthly.

10 · Expansion

Add the AI-assisted creative tooling already built internally to lift throughput per designer → sponsor-facing creative packages → full game-day content operations, which is the door into running content, not just making it.

11 · Risks

It sells ANC's scarcest resource — designer hours — so margin depends on throughput, not price. Scope creep is the default failure mode; the request cap and turnaround SLA have to be enforced from day one. And it competes with the venue's in-house creative team, so it must be positioned as overflow and surface expertise, not replacement.

12 · Score

RevenueSpeed to MVPStrategic fitEase of saleRecurringDefensibilityOps complexity (10 = simple)
61078855

Opportunity 4 — Pitch Studio

The venue-transformation tool already built for ANC, licensed to the client's own partnership team so they can show a sponsor their building transformed, in a day.

1 · Product concept

A partnership seller uploads a photograph of their own venue and gets back a coordinated set of visuals — the concourse activation, the full-bowl takeover, the premium moment — plus the written pitch, all anchored on the real architecture, and a share link for the brand.

2 · Buyer

The property's partnership / business-development team. Modest budget, fast decision, and it competes with what they currently pay a creative agency per pitch.

3 · Pain

Selling an activation that does not exist yet requires imagination the brand does not have. Renders cost thousands and take weeks, so sellers pitch with words and lose to properties that pitch with pictures.

4 · Why ANC wins

The visuals must be physically credible — the right surfaces, the right sizes, the right sightlines — and ANC is the only party that knows the venue at that level. It also seeds demand: every activation pitched is inventory ANC may later build.

5 · Revenue model

6 · Sales path

Give one seller one venue for free, let them win one pitch with it, then price it. Best introduced by ANC's Media & Sponsorship team into properties where ANC already handles inventory.

7 · Workflow

Upload the venue photo → pick the world (sponsor revenue, game day, concert) → set the objective and tone → generate → hand the brand a share link.

8 · Integrations and data

Venue photography, the display registry for surface accuracy, generation providers behind a pluggable interface, and per-client tenancy with rights language that keeps ANC clear of ownership disputes.

9 · MVP

Already running end to end. What is missing is client tenancy, a seat model, and a rights agreement.

10 · Expansion

Pitch outcomes tracked back to inventory → a library of proven activations per property → activation catalogue that feeds directly into ANC proposals.

11 · Risks

Generated imagery of a real venue used in a sales context needs clear labelling and rights language, or it becomes a misrepresentation problem. Generation cost must be capped per account. Sponsorship teams churn, so adoption depends on one internal champion. Low switching cost means defensibility rests on venue accuracy, not on the tool.

12 · Score

RevenueSpeed to MVPStrategic fitEase of saleRecurringDefensibilityOps complexity (10 = simple)
51077648

4. Recommendation — build ANC Assurance first

Why first. It sells to the buyer ANC already invoices, on a contract that already renews, using data ANC already owns, through a portal that is already built. It converts ANC's biggest unpaid cost — reacting to failures — into a priced product, and it builds the telemetry spine that Verified Impressions and lifecycle planning both need. No other option scores this well on speed and defensibility at the same time.

Best pilot. Gainbridge Fieldhouse (Indiana Pacers) — LiveSync is installed and actively maintained, tickets are live this week, ANC people are on site, and there is an engaged operator who will give real feedback. Run the paid expansion at Cal Berkeley, which just signed a five-year agreement, or WMATA, whose estate already generates device-level incidents and would immediately understand the value of ANC seeing them first.

What we build. An outbound-only collector on the LiveSync machines, an alert-to-ticket bridge into the existing service system, real telemetry behind the display board already in the customer portal, and one automated monthly SLA report.

What ANC sells. "Monitored estate" as an upgrade to the existing service agreement: ANC detects and dispatches before the venue calls, reports uptime monthly, and forecasts what needs replacing next season.

What the client pays. $8–15K setup, then $1,200–$2,500 per venue per month — roughly a 20–34% uplift on an agreement of Berkeley's size. Free for year one when attached to a capital project, converting at renewal.

Evidence the pilot worked. Share of incidents ANC detected before the client reported them (target: over half by day 60), mean time to detect, mean time to repair against the pre-pilot baseline in the ticket history, truck rolls avoided, and one written line from the venue operator saying they would pay for it.

What can be demonstrated in 30 days. One venue's displays live on a board with real status, an alert that became a ticket before anyone phoned, and a signed-off monthly SLA report — using the ticket history already in the system to show the before-and-after.

What not to build yet. No predictive-failure ML, no CMMS replacement, no custom hardware, no multi-tenant billing, no mobile app, and no sponsorship measurement — that is the next product, not this one.

Next five actions.

  1. Read the LiveSync server and processor stack at one venue and confirm exactly what telemetry is reachable today — this decides the whole product, and it is a day of work.
  2. Baseline the last twelve months of tickets for the pilot venue: how many faults, how they were reported, and how long each took. That table is the pilot's scoreboard and the sales deck.
  3. Write the one-page security brief for venue IT — outbound only, no inbound ports, what is collected, what is not.
  4. Take it to Joe as a service-agreement upgrade with a named pilot venue and a fixed 60-day scope, not as a software project.
  5. Build the collector and the alert-to-ticket bridge against that one venue, and switch the existing portal display board to live status.