We started building Wildlife Connects' land-access module the way
every CRM gets built: a users table with roles, a
permissions table, a flag for "can access property X."
Then we sat down with three landowners and one ED at a chapter office
and the whole structure fell apart in twenty minutes.
The thing landowners actually manage isn't a user. It's a lease. A lease has a season. It has a group of names, sometimes a husband, wife, two adult kids, four guests they bring once a year, and the names rotate. It has a fee. It has insurance docs that expire mid- season. It has a paper waiver that has to be re-signed if anything changes. The landowner doesn't think about who is "in the system" they think about who is on the lease, and which gate code they can share.
What we shipped instead
We tore out the user-permissions model and rebuilt around the lease as the central object. A lease has a lifecycle (drafted → signed → active → expired → renewed). It carries a roster, an insurance document set, a gate code that rotates each season, and a single signed waiver per person on the roster.
The result: when a landowner adds someone to their lease, they don't "create a user." They add a name to the roster. The system asks for the new person's signed waiver. Once it's in, the gate code goes out. The landowner sees a clean roster. The new person sees a clean member portal. Nobody talks about "permissions."
"I don't care who's in your database. I care who's on my lease this season and whether they signed."
What the operators we showed it to actually said
- The 3,800-acre landowner: "Finally something that works the way I think about it. The lease is the unit of work."
- The chapter ED: "If I can stop explaining what a 'user role' is to my board members, that's a win on its own."
- The hunt coordinator: "Show me the gate code rotation and I'm sold."
The lesson, and what we're building next
Generic CRMs lose at this work because their primitives are wrong. A user is not the unit. A lease is. A scoring event is. A patron renewal cycle is. The platform reads as "purpose-built" not because we picked outdoor-themed icons, but because the data model knows what actually happens in a season.
Up next: events. We're rebuilding banquet check-in around the night of, not the spreadsheet. More on that soon.