Implementation Specialist building Salesforce architecture: integrations, single sign on, data migrations, and the security and permission design that decides whether a connector is trustworthy or a liability. A meaningful share of that work happens before any of it is technical: evaluating whether a new vendor is worth bringing in, negotiating the terms that make a partnership worth keeping past the first renewal, and staying the person both sides call when something between two companies needs resolving.

The clients I work with today are membership organizations, but the actual problem, getting disconnected systems to agree on who a person is and what they're allowed to touch, is the same one any company with more than one system runs into.

I came into this sideways: history and anthropology, a stint in an archive, years in fundraising and operations, then into the systems underneath the organizations I used to work for.

Start here

• Partner & Third-Party Integration Playbook: a full, public framework for vendor onboarding, security provisioning, incident response, and partner communication, generalized from several years doing this against a CRM + SSO platform.
• Portfolio: case studies and leadership: the work behind the résumé, in detail.
• Writing: posts archived in full.
• Get in touch: LinkedIn

Plain HTML and CSS, no build step, no framework. Served directly by GitHub Pages from index.html on the main branch.