Events & Territory
Reps do not work assigned ground. They choose their territory by choosing which rooms to be in — the filter is the territory system.
How it works
Three stages: register the sources, harvest the events, filter them down to the ones worth attending.
1 — Source registry
A database of every app, website and platform that displays events, from concert listings to speed-dating meetups.
Needs: criteria for what qualifies a platform
2 — Harvest agent
Works each platform in the registry and records every event against the datapoint schema.
3 — Filter & calendar
Filter by time, date, location, cost, event type, demographics — in any combination.
What is recorded per event
The established datapoints. The full schema, ordered by relevance, is in docs/planning/04-EVENT-SYSTEM.md.
Name
Date
Start time range
A range, because sources publish 'doors at 7' as often as a fixed time.
End time range
Approximate duration
Derived where the source gives no end.
Location
Venue, address, or online.
Cost
Free, fixed, range or donation.
Frequency
One-time or recurring, and on what basis — weekly, monthly, first-Tuesday, seasonal, annual.
Demographic distribution
An estimated mix across Sales Funnel's dimensions, not a single label.
Needs: the data sources feeding the algorithm
Filter toolbar
Any datapoint, in any combination. This is what makes a rep's territory their own.
Time & date
Day of week, time of day, date range, how far ahead.
Location
Distance from the rep, venue type, in person or online.
Cost
Free only, under a threshold, or any.
Event type
Category and tags.
Demographics
Age, gender, race, wealth ladder, religion, politics, pride, ownership.
Attendance
Expected size, capacity, room for conversation.
Practicalities
Registration required, age restriction, alcohol, formality, parking.
Saved filters
A rep's own definition of their territory, saved and reusable.