Systems ownership
ERP, data, cloud, vendor, and change-management work for distributed users who needed dependable day-to-day systems.
Work history
A chronological view of systems ownership: ERP delivery, support scale-up, contact center tooling, reporting cleanup, and handoffs that kept operational work traceable as teams and systems changed.
ERP, data, cloud, vendor, and change-management work for distributed users who needed dependable day-to-day systems.
Ticketing, contact center, IVR, training, and process design for support teams under growth pressure.
Scripts, SQL, dashboards, alerts, and source-backed tools that reduced repeated reconciliation and manual follow-up.
Business systems and change-management work across NetSuite, Snowflake, Celigo/integrator.io, system contracts, vendor teams, ERP delivery, controls, UAT, and go-live handoffs. This work focuses on making operations stable under pressure: leading through ambiguity, seeing around corners, clarifying ownership, and leaving teams with outcomes they can maintain over time.
Ticketing, CRM, contact center, vendor, IVR, and knowledge workflows for support teams that grew from a small internal group into a larger operating function. We introduced role-based runbooks, handoff templates, and reliability checks so quality did not degrade as volume increased.
Python, SQL, Snowflake, Lambda-style alerts, document organization, mail triage, OCR-assisted review, and source-backed dashboards for repeated operational work. Each initiative was designed with repeatability in mind: clear inputs, predictable outputs, and explicit checkpoints for handoff and auditability.
Coaching through product launches, custom training, process documentation, release notes, and local-first tools across SwiftUI, SQLite, CloudKit, Python, and static HTML. The emphasis is on practical documentation and onboarding materials that preserve continuity when teams hand off roles or face new operating conditions.