Daily
Fixtures & results
Official source, schedule changes and post-match closure.
A walkthrough of the sources, contracts, confidence states, automation and safeguards that connect a fixture to a decision and a measurable campaign.
Open the live productTraceability first. Automation second.
Back to commercial caseDesign principles
Logical architecture
A future CRM connection enters at the source layer through a versioned contract; it does not require rebuilding the layers above.
Today · Calendar · CampaignPlan · scorecardTerritory · demand · audience · matchweekfixtureId · campaignId · source · confidencecalendar · attendance · signals · journeysclub · WSL · weather · transport · events · calendarBuild phases
940 LSOAs scored through family potential, girls' football networks, access and competition context.
Canonical calendar, results, weather, travel friction and sourced material-change signals.
An auditable 2025/26 attendance ledger, venue split and benchmark layer with source-state awareness.
Owned-channel signals are connected while broadcast and search remain separate evidence states that may be pending or unavailable.
Versioned ticket-level contract, synthetic Brighton rehearsal and time-bound post-match closure states.
CampaignPlan contract, reusable playbooks, activation briefs, UTM joins, approvals and guardrails.
Matched GB/Spain comparison sets, an intent ladder, activation links and evidence gates for travel products.
Three configurable concepts, a non-personal intent event and launch gates that keep registration and sale blocked until approved.
Three fixture pilots, corridor scoring, aggregate privacy thresholds and a shuttle economics simulator that never presents assumptions as quotes.
Allowlisted anonymous events, test/production separation, provider-aware delivery and aggregate fixture cohorts with a minimum evidence threshold.
Four candidate-specific narratives join pilots, evidence states, value exchange, KPIs and approval gates without implying outreach or endorsement.
Time-stamped engine hypotheses can now be compared with later observable club action, dimension by dimension and without claiming causation.
Today, Calendar, Territories, Access, Experience, Measurement and Partnerships were reorganised around operator questions instead of feature inventory.
Technical source health is mapped to the business decisions it supports, qualifies or blocks.
Sources & cadence
Automation checks and preserves comparable observations. When a source fails, it exposes the failure and retains the last valid value.
Daily
Official source, schedule changes and post-match closure.
Daily / windows
Matchweek refresh without treating a forecast as certainty.
Weekly + T±
Competing events, broadcast picks and news. Social measurement stays with Blinkfire or the club’s social tool.
Post-match
Official observation, visible sample and comparable median.
Trust contract
| State | Meaning | Example |
|---|---|---|
public-verified | Observed in a cited public source. | Fixture, published attendance |
public-inferred | A planning inference, never a known customer fact. | Territory or player-led audience |
pending-source | Expected but not publicly available yet. | TV audience, missing attendance |
source-unavailable | A capture failed without overwriting or inventing a value. | Rate-limited Google Trends baseline |
validation-concept | A proposition can be tested but is not on sale. | Matchday, VIP and international concepts |
modelled-scenario | A transparent planning assumption, not measured demand or a supplier quote. | Corridor score and shuttle economics |
provider-not-configured | Events validate locally but are not stored or counted. | Experience and mobility telemetry |
prospecting-draft | A non-binding narrative for review, not outreach or a relationship. | Mobility and travel partner packs |
demo | Synthetic data that proves calculations only. | Brighton ticketing rehearsal |
requires-instrumentation | Measurable after UTMs or event tracking are deployed. | Landing-page intent |
requires-access | Needs an authorised club system. | Purchase, scan, no-show, repeat |
Data contracts
Even without real CRM access, the product defines exactly what it needs, how it validates and which calculations it unlocks.
fixture_id → campaign_id → ticket_id → scan → repeat_90d
CRM / ticketing
fixture → campaign → product → price → purchase → scan → consent-safe geography → repeat
Open JSON schema ↗Campaign plan
fixture → signals → audiences → playbooks → activations → UTMs → approvals → measurement
Open JSON schema ↗Search demand
market → window → comparison set → term → dated index → activation → decision gate
Open JSON schema ↗Experience demand
concept → fixture → origin → party → price → needs → gates → pilot decision
Open JSON schema ↗Mobility partnership
fixture → corridor → modelled score → aggregate threshold → quote → approval
Open JSON schema ↗Experiment measurement
event → validate → deliver → deduplicate → cohort → threshold → review
Open JSON schema ↗Partner commercial pack
candidate → fixture → evidence → value exchange → KPIs → gates → review
Open JSON schema ↗Pilot readiness
pack → score → owners → blockers → timeline → hold / go
Open JSON schema ↗Signal to campaign
Validation & guardrails
validate:campaignsvalidate:crm-demovalidate:public-signalsvalidate:search-demandvalidate:experience-demandvalidate:mobility-partnershipvalidate:experiment-measurementvalidate:partner-commercial-packvalidate:pilot-readinessvalidate:source-healthtypecheckVercel buildWithout CRM access
AVELA · London City technical case studyIndependent demo · Data and limits visible by design.