Exec Sec started as a solution to a recurring administrative pain: church leaders manually tracking which members needed to renew their temple recommends and following up individually. The tool automates that entire loop — it reads the membership roster, checks expiration dates, and fires off reminders via text and email at configurable intervals before a recommend lapses. Built in Python with Selenium for any browser-based interactions, it replaced a process that previously required constant attention from a volunteer doing clerical work on top of everything else.
The broader goal was proving that automation principles from software development apply just as cleanly to community and organizational work. The same patterns behind a sales follow-up sequence or an onboarding drip campaign work for church administration. Exec Sec was an early exercise in identifying repetitive, rules-based workflows and stripping out the human overhead — a pattern that shaped how I approach automation problems today.