Forrest Swan III

I make operations legible: I write down how the work is supposed to flow, then build the systems that keep it flowing that way.

Now: Kasey Osman Insurance

Since June 2024 I've worked at Kasey Osman Insurance, an Allstate agency in Melbourne, Florida. I was promoted from Licensed Sales Producer to Technical Solutions Manager to Agency Operations & Systems Manager, and I own systems architecture, automation, data governance and cybersecurity.

The environment has real constraints. The agency's Microsoft 365 environment is carrier-managed and blocks add-ins and macros, so automation runs through Google Apps Script, Zapier, n8n and standalone Windows apps instead. Within that, I've built and documented nine internal software systems and led eight infrastructure and IT operations projects, from the firewall and VPN to the NAS and IT asset management. Two systems run in daily production: a file-naming compliance auditor for the agency file share and an AI-assisted underwriting-notice triage board with two-way Slack updates.

I also publish open-source tools distilled from that work and write up what I learn in technical posts.

Before

Avidyne Corporation (June 2022 – February 2023). As Customer Experience Systems Administrator at the aviation technology company, I wrote a data policy covering entry, design, naming conventions, branding and tagging, extended the CRM (Keap/Infusionsoft) and help desk (HappyFox), and provided Tier II and III support.

Paramount Foundation (March 2016 – March 2020). As Systems Administrator, Salesforce for a non-profit in Bristol, Tennessee, I project-managed two Salesforce implementations (NPSP and Enterprise), streamlined donation entry and acknowledgment with PatronManager and Conga Composer, and onboarded staff and volunteers onto the organization's technology.

Education

• University of Florida: Bachelor of Science, Sport and Fitness Administration/Management, December 2023 (Cum Laude)
• Piedmont Virginia Community College: Associate of Science, Business Administration, May 2019 (Summa Cum Laude)

How I work

• Policy as data. Rules live in versioned files (rulesets, blueprints, rubrics) so they can change without a code change.
• No guessing. When a value can't be derived, it goes to a review queue instead of being made up.
• Reversible changes. When a tool renames files, every change is journaled with an undo path.
• Tested. The larger tools ship with automated test suites, and case studies note test results where they were recorded.

Every claim about my experience here traces to my resume or the case studies; private source code is available for walkthrough on request.