[...]-on-AddEvent
Use Cases and Deployment Scope
Pros
- Enables adding of events to multiple calendar apps/sites. ( pre-"AE", we defaulted to Google only, and that was not wise nor well received by our global membership )
- Varied options for one off, semi recurring, and recurring cadences
- Embeds well in the website
- Multiple options for attendance
- Relatively easy/simple ( "B" grade ) to learn; our FTE VA picked it up well
Cons
- The person handling the setup/update from our lean core team may NOT want to be the one listed as the event POC using his/her log in details. Far as I know, we cannot use another's?
- Would it ever be possible to deploy functionality to 'sweep' old events which were previously added to calendars once said event(s) are no longer? We've had a # of cases where people point this out
- Connecting AddEvent to other SaaS or like services isn't the easiest by any means - usually requires Zapier or advacned programming creds. Big opp here as I grasp it.
- More of a branding/awareness push? NOT by the same old tired advertising, maybe using affiliates/referral programs where organizations like ours, or the people within them, can be leveraged to get the word out?
Return on Investment
- While I cannot speak at all to the organization's finances, I'd say the implicit/2nd-3rd order effects ot using AddEvent are very very green/+, as the old means ( dating to earlier 2023 or thereabouts ) had us working harder and not nearly as smart.
- ROI is clearly driven by ROE (energy) and ROT (time); the time impact has for the most part been on the right side of the equation, and minus some odd here and there situations ( mostly can be spoken for by the 2nd fractional/indp contractor, not I) , the energy input says as a charge vs. a drain.
- When we had to upgrade to accomodate a special Zapier related project late in '25 and landing/wrapping in 1Q 2026, the end result of the IT work was very solid.

