MONDAY.
LET’S GET
SPECIFIC.
The weekly view. One set of numbers. Clear next moves.
PREPARED FOR KENNY / VANCOUVER BANDITS
THE BANDITS
AI GAME
PLAN.
More time for the people.
More room for the game.
VANCOUVER / BRITISH COLUMBIA / BASKETBALL
HUMAN
JUDGMENT.AI
ASSIST.
GAME PHOTOGRAPHY VIA VANCOUVER BANDITSJUDGMENT.AI
ASSIST.
KENNY, HERE’S MY TAKE.You’ve already
You’ve already
named the work.
The decks. The ticket reports. The graphics somebody needs five minutes after the buzzer. You’ve given me a pretty good map of where your team’s time goes.
I’d start there. Give your people a few well-built systems, teach them how to use them, and keep the judgment with the people who know the business.
Let’s get one useful thing working, earn the team’s trust, and build from there.
Kris Krüg ↗01BRAND, DESIGN & GAME-DAY CREATIVE
Make it look
like the Bandits.
Start with your identity. Claude Design can work from a brand system and help create layouts, decks, and prototypes. The quality comes from the material and direction we give it.
01
BANDITS ORANGE02
COURTSIDE BLACKAaTYPE WITH A POINT OF VIEW
BANDITS ORANGE02
COURTSIDE BLACKAaTYPE WITH A POINT OF VIEW
One shared brand foundation.
Approved logos. Licensed fonts. Colour values. Image rights. Sponsor rules. Asset sizes. Examples of what good looks like.
Illustrative demo · sample dataMake the next
Make the next
update yours.
Change the numbers. The design holds together. That’s the point of a proper brand foundation.
A working template demonstration. A production version would read an approved stats feed, flag missing values, and queue a graphic for review.
EXHIBITION / DEMOALL
GAME.
GAME.
BANDITS92
:VISITORS86
FROM IDEA TO A RELIABLE ROUTINE
- 01
Bring the source.
Approved scores, player stats, or ticket data. Confirm access, freshness, and who owns it.
- 02
Build the template.
Use Claude for concepts and copy. Let a fixed layout place the correct numbers, marks, and sponsor assets.
- 03
Keep a human eye.
Flag missing data. Check the output. Queue it for approval, then distribute through the agreed channels.
What we’d set up and learn together +
A shared brand folder and Claude Design system; reference imagery with usage rights; social, scoreboard, and presentation formats; example prompts; export checks; and a hands-on session using a real Bandits brief. Brand changes have one owner. Templates stay versioned. First prove one graphic workflow before connecting a whole game-day pipeline.
Claude Design capabilities ↗02SALES, ATTENDANCE & THE RAMP TO TIPOFF
Know the score.
Before game day.
Your Showpass questions are the right ones. How much have we sold? Which offers are working? Who’s using their tickets? How does this game compare? Here’s how that could feel.
BANDITS / TICKETING EXPLORERIllustrative demo · sample data
Tickets allocated2,274Selected game · net of refunds
Ticket revenue$132,682CAD · allocated package value
Scan rate75.7%1,721 unique tickets scanned
Transfer rate4.2%96 unique tickets transferred
THE RAMP TO GAME DAY
How are we pacing?
2026 sample2025 sampleIllustrative goal
In this sample, 810 tickets were sold in the final seven days. That’s the kind of buying pattern we’d examine before choosing when to promote a game.
Open the season view & metric definitions +
Same product and ticket-type filters. All six fictional games in the 2026 sample season. 112 purchase records contribute to the selected game.
15,014Net ticket entitlements sold
$882,986Net season sales · CAD
5,429Net purchase units / bundles
106Unallocated entitlements
82.5%Season scan rate
4.4%Season transfer rate
| Game | Tickets | Revenue CAD | Scan rate | Transfer rate |
|---|---|---|---|---|
| Home opener | 2,274 | $132,682 | 75.7% | 4.2% |
| Friday night | 2,357 | $137,396 | 78.3% | 4.3% |
| Community night | 2,466 | $144,248 | 80.3% | 4.3% |
| Summer hoops | 2,549 | $149,354 | 83.3% | 4.4% |
| Rivalry night | 2,603 | $156,436 | 86.7% | 4.6% |
| Season finale | 2,659 | $159,370 | 89.2% | 4.7% |
What counts: sales are net of refunded bundles, excluding taxes and fees. Package revenue is divided equally across entitlements. $3,500 remains attached to unallocated entitlements. This is a demo allocation, not an accounting policy.
Usage ≠ attendance: a Flex entitlement is redeemed when assigned to a game; a scan records attendance. Scan and transfer rates count unique tickets divided by assigned tickets. Season rates use all assigned tickets. Product sizes, ticket types, dates, and goals here are invented.
The comparison: both sample seasons use matching month/day game dates. Calendar view shows those dates; days-before-tipoff aligns purchase timing. Curves use final net sales by original purchase date, not a historical refund ledger or forecast.
kk.
This is where I’d start the real pilot.
One trusted weekly ticketing view, then a Monday deck that uses those same numbers. First we inspect two completed seasons of exports, agree product definitions and game targets, and confirm what Showpass makes available to your account. Its public organizer API docs don’t establish every historical sales, transfer, or redemption field you’re asking for. See the documented capabilities ↗
03PRESENTATIONS WITH A SHARED SOURCE
Monday morning.
Already prepared.
Stop rebuilding the same story from scattered files. Keep your facts current, your layouts reusable, and your audience in mind. Try the two versions below.
Illustrative demo · sample data
MONDAY.
Here’s the ticket picture.
2,274tickets allocated · sample gameScan rate 75.7%. Transfer rate 4.2%. Numbers match the explorer above.
What happens next?
- Review the game’s sales pace against its target.
- Choose an owner for the next ticketing move.
- Review the result at the next Monday meeting.
On-page preview, not a generated file. In the real workflow, approved templates and maintained data feed the deck; your team checks it before exporting to PowerPoint or PDF. This demo makes no claim of a live Claude or Drive connection.
INTERNAL
Tell us what changed.
Sales against targets, upcoming games, decisions, owners, and follow-ups. A maintained report feeds a repeatable meeting.
EXTERNAL
Give the sponsor a reason.
Research their business. Show a relevant opportunity. Use approved audience evidence, inventory, and rights. Check every commercial claim.
CONNECTED
Maintain the source once.
Start with a well-owned sheet or export. Add automated refresh after definitions and access are settled. Someone still owns accuracy.
THE REASON FOR THE WORK
PHOTOGRAPHY VIA VANCOUVER BANDITSKeep the people
in the game.
04THE REST OF YOUR QUESTIONS
My straight
answers.
There’s plenty we can build. The useful question is where it will make the work better, and what we need to know first.
Website & conversionCan Claude Code make our website better?
Yes. I’d start with the journey from ‘that looks fun’ to a ticket in someone’s pocket. Open it on your phone. Find a game. Compare a package. Try to buy. The friction we can actually observe becomes our build list.
Tickets & packages
Make the differences legible: who each offer is for, what it includes, and the next step. Evaluate Showpass’s existing checkout widgets before building a new purchase flow.
Data collection & contests
Use short forms, clear consent, and useful follow-up. Decide which audience fields matter before collecting them. Contest eligibility and rules still need a human owner.
Merchandise & camps
Make the shop handoff clear. For camps, put age groups, dates, location, price, and registration together. Keep information about children out of general AI workspaces.
How we work
Confirm your website platform and access. Measure the existing funnel, make one focused change in a preview, test mobile and accessibility, then compare results. Claude Code helps build and test; your team approves what goes live.
First move: walk through three real customer journeys together and pick one measurable improvement.
Source & current capabilities ↗Cash flowDo we need another QuickBooks dashboard?
Maybe. I’d want to know which decision you can’t make with the reports you already have. A beautiful chart that repeats yesterday’s confusion is expensive wallpaper.
Start with the books
Review QuickBooks’s existing cash-flow reports with whoever owns your books. Check bank reconciliation, unpaid invoices, bills, and how Showpass settlements are recorded.
Build only the missing view
A useful next step could be a rolling 13-week cash view: opening cash, expected ticket settlements and sponsor payments, payroll, travel, venue costs, and closing cash. Timing and assumptions should be editable and visible.
Keep the numbers honest
Ticket sales, cash received, and profit describe different things. Reconcile Showpass payouts, fees, refunds, and taxes to QuickBooks before combining them. A forecast is an estimate, with a finance owner and a review date.
First move: identify one cash-timing decision the current reports don’t answer.
Source & current capabilities ↗Basketball operationsCould we build a player availability module?
Yes, as a research assistant that helps your basketball people find and check leads. ‘Played well last month’ and ‘available to sign today’ are very different facts.
Start with a defined player pool
Choose the leagues, positions, date window, and stats that matter. Normalize player identities, minutes, competition level, and box scores. Document gaps instead of pretending we can see every league.
Treat contracts as evidence
Record the source, date checked, known contract dates, and what still needs confirmation. RealGM’s terms restrict commercial use without written permission. Start with permitted league sources or a licensed provider, then confirm availability with the appropriate people.
Apply current CEBL conditions
Use season-specific roster and import rules, schedule overlap, and internal budget constraints. Basketball ops confirms eligibility, contracts, salary-cap treatment, and fit. Keep salary and negotiation information in a restricted workspace.
Useful output
A shortlist with comparable performance, source links, last-checked dates, reasons to investigate, and open questions. The final roster decision stays with your basketball staff.
First move: test a small, agreed player pool with ops before investing in broad coverage.
Source & current capabilities ↗Current CEBL roster guidance ↗Drive, Gmail & daily workWhat should we actually do with Cowork?
Give it a bounded job with good source material. ‘Prepare me for this sponsor meeting’ is useful. ‘Here’s our entire business, good luck’ is a lousy brief.
Shared context, individual access
Keep approved brand files, offer descriptions, sponsor facts, and meeting templates in shared Drive folders. Connect each person’s own account. Organize Claude projects around work, with access appropriate to the material.
Email drafts worth reviewing
Pilot one category, such as routine ticket enquiries. Supply current package information, tone examples, escalation rules, and a small set of approved replies. Create drafts for a person to review. Skip commitments, complaints, negotiations, and sensitive cases.
Useful recurring work
Meeting briefs, weekly updates, sponsor research with sources, and follow-up lists are good candidates. Scheduled work needs a named owner, tested access, a review destination, and a clear failure signal. A connector alone doesn’t create that routine.
Do we need it?
Try it on the repetitive work your staff can name today. Compare preparation time and correction effort before and after. Keep what makes the job better; retire the rest.
First move: choose one recurring task per person and review the results together.
Source & current capabilities ↗05SMALL TEAM. CLEAR ROLES.
Give everyone
their own seat.
I’d begin with the people doing the work. Named accounts, shared standards, and access that fits their role. Four departments doesn’t necessarily mean four people or four subscriptions.
01
Kenny
Owner & commercial leadTHE WORK
Sales, sponsor research, meeting preparation, team standards
THE ACCESS
Own the organisation and shared reference material
THE STARTING POINT
Standard to start; upgrade if usage warrants it
02
Ticketing
Sales & serviceTHE WORK
Ticket questions, weekly sales review, customer follow-up drafts
THE ACCESS
Ticketing reports and approved customer information
THE STARTING POINT
Named users; dashboard-only viewers may need no Claude seat
03
Marketing
Brand & partnershipsTHE WORK
Claude Design, campaign concepts, sponsor decks, content drafts
THE ACCESS
Brand assets, marketing data, approved sponsor material
THE STARTING POINT
Standard to start; review design usage before upgrading
04
Ops
Basketball & logisticsTHE WORK
Player research, travel options, operational briefs
THE ACCESS
Restricted player, contract, travel, and salary material
THE STARTING POINT
Standard named seats with scoped access
My default: start actual AI users on Claude Team Standard, then review usage and work quality. Standard includes Claude Code and Cowork; Premium buys more usage. Kenny administers the organisation. Nobody shares a login.
Keep automation/API spend separate from the seat decision. Confirm current entitlements and regional terms before purchasing. Check current Team plans ↗
06HOW WE BUILD THIS TOGETHER
Start useful.
Build from there.
I’d work alongside your team: set the foundation, build the first workflow, and teach people to run it. We choose the next step from what we learn.
Set the foundation.
Brand files, source data, account access, staff roles, and a shared definition of a useful result.
WE LEAVE WITHAn approved brand kit, an access map, and one agreed pilot.Prove the weekly win.
Build the ticketing view and Monday deck together. Reconcile the numbers and run the workflow with your staff.
WE LEAVE WITHA repeatable report, a usable deck, a trained owner, and a measured baseline.Extend what works.
Add the next useful workflow: graphics, website improvements, email assistance, cash flow, or scouting research.
WE LEAVE WITHTested routines, clear review points, and a sensible next build.THE NEXT MOVEBring a real problem.
Bring a real problem.
We’ll get our hands on it.
A sample ticketing export. A Monday deck. The graphic that always takes too long. That’s enough to start a good conversation.
Our first session
BANDITS × KRIS KRÜG: FIRST WORKING SESSION 1. Pick the first useful weekly outcome: a trusted ticketing view that feeds the Monday deck. 2. Review brand guidelines, logos, licensed fonts, image rights, and a good existing deck. 3. Inspect sample Showpass exports from two completed seasons: orders, refunds, ticket types, package entitlements, redemptions, scans, and transfers. Confirm API access with Showpass. Use redacted samples for discovery. 4. Agree metric definitions, game targets, reporting owners, and what counts as a successful pilot. 5. Map actual staff, current Claude subscriptions, Google Drive/Gmail permissions, website access, and restricted financial/player information. 6. Choose the first build, review point, and staff training session. No account passwords or customer lists needed for the initial conversation.