You said time is of the essence. This is the 30-day Operational Intelligence Sprint that fixes the five structural issues blocking the 120-by-November patron number — and gives you a foundation that survives any tooling change.
Six measurable outcomes by the first concert in November — and a foundation for the seasons after.
Each campaign launches on guesswork. The sprint resolves them at the structural layer — not as a workaround.
Transactions for next season's memberships book in the wrong fiscal year. No rule exists for how to tag them.
ThunderTix does not provide one. Names mutate across orders. Duplicates get created.
Every label was created ad hoc. Reports cannot be stitched together because the fields do not agree.
A critical layer occupied by staff without the depth or context to participate in the redesign.
Strategic decisions anchored in instinct because nothing better exists. The sprint replaces instinct with definition — KPIs you can actually verify.
Until these five are fixed, every report runs through fog and every campaign launches on guesswork.
That is what the sprint resolves.You adopt them, you enforce them. They survive any ticketing change. They are the layer above any system you choose to run.
Transaction tagging rules, naming conventions, custom field schema, KPI definitions. You adopt it. You enforce it. It is permanent infrastructure that survives any tooling change.
Not a snapshot — a foundation. New data gets added under the same rules every season going forward. This is the over-time data you've been asking for.
Why it breaks, and how to work around it without waiting on ThunderTix — or anyone else — to change first.
Targeting based on actual patron behavior. Real-time intelligence on what is working while it is working. Aimed directly at your number.
Specific use cases you surfaced on the call — the ones that have been sitting in the gap between what you sense and what you can prove.
Inside one season of clean data, you can ask:
Should I just spend $15K on a new ticketing system instead?
The sprint is the layer above any ticketing system. The standards, the customer numbering scheme, and the reconciled dataset are tool-agnostic.
If you replace ThunderTix tomorrow, this work makes the migration cleaner, not redundant. A new tool inherits clean rules. A new tool on top of the current mess inherits the mess.
The data I need is over time, not one-time.
The standards document is permanent. The reconciled dataset is a foundation that grows every season.
The sprint is the one-time setup that enables continuous, reliable tracking. Without it, the over-time data you want cannot exist with any reliability — you'd be averaging fog with fog.
Who owns the intellectual property?
CMSPB owns the standards document and the reconciled dataset outright. Both are yours, fully and forever. Forwardable to a new vendor, a new ED, a new board.
ThoughtLeap retains the underlying methodology and tooling. You own the deliverable. We own the recipe.
The standards document and the reconciled dataset, outright. Yours to keep, share, hand to any vendor, retain through any leadership transition.
The underlying methodology and tooling that produces the work. Repeatable for other clients. Never re-sold containing CMSPB data.
You own the deliverable. We own the recipe. Clean line.
Reply yes today or tomorrow. Invoice goes out the same day.
Inside three business days of approval. We start with the standards.
Standards, reconciliation, choke-point map, campaign — built in parallel.
Renewal campaign targeting in hand before your stated cutoff.
Investment & next step
First working session scheduled inside three business days. Renewal campaign ready before your July 15 deadline.