Impact at Webflow
4.6 years as a Senior IC across billing, platform support, and escalations. Here's how I operated and what I built.
How I Operate
Queue-first mindset with full escalation ownership. I focus on cross-functional fluency — partnering with engineering, product, and sales — and a constant instinct for process improvement.
Automated Identity Verification
Designed a Magic Link authentication system to reduce Mean Time to Resolution by ~20%, eliminating manual triage loops.
Agents spent significant time manually verifying customer identities on billing tickets. Each verification loop added minutes to resolution time and created frustrating back-and-forth for customers.
Designed an API-driven flow: customer submits billing inquiry → Zendesk webhook triggers automated verification email → customer authenticates via time-sensitive magic link → Zendesk API auto-updates ticket status.
- Designed to reduce MTTR by ~20%
- Zero manual touchpoints after automation triggers
- Shifted agent focus toward technical troubleshooting
- Eliminated manual triage loops entirely
One-Click NPO Discount Workflow
Replaced a multi-step manual nonprofit verification process with a self-service portal.
Nonprofit discount requests required manual review, multi-step email chains, and inconsistent approval criteria. This created bottlenecks in the billing queue and inconsistent customer experiences.
Collaborated cross-functionally with a billing teammate, engineering, and leadership to design and implement a self-service portal at support.webflow.com/resources/nonprofit-discount. Standardized approval criteria and eliminated manual review steps.
- Reduced manual triage cycles for nonprofit requests
- Improved billing workflow throughput
- Enabled scalable, consistent discount approvals
- Freed agent capacity for complex billing issues
Community Advocacy & Support Engineering
6-month management of high-stakes Reddit and Discourse discussions as public face of Webflow support.
Customer frustrations were surfacing publicly on Reddit and Discourse forums, often escalating before reaching formal support channels. Negative sentiment was spreading without official responses.
Established a real-time signal detection workflow: monitor r/webflow and Discourse → triage by urgency (billing loss, bugs, product confusion, crises) → post public de-escalation responses → route escalations to appropriate teams → feed community signals to product planning.
- Crisis de-escalation before formal ticket entry
- Ticket deflection through public troubleshooting
- Revenue-focused billing advocacy
- Community signals fed directly to product planning
Anyone else feel that the new animation system is extremely buggy?
erratic load animations
sef-webflow: Hey — Sef here from the Webflow Support Team...
Phone Support Number — I just lost $400
billing loss frustration
sef-webflow: I'm really sorry for the frustration here...
Site transfers causing downtime during client handoffs
billing continuity frustration
sef-webflow: We really appreciate you all chiming in...
It's mid-2025, did Webflow migrate to 'Client Seats' yet?
legacy Editor deprecation anxiety
sef-webflow: The launch of client seats and the subsequent deprecation...
Early Career Foundation
Before Webflow, I spent 7+ years across SaaS support environments handling 7–9 concurrent live chats, writing customer-facing technical guides, and building the operational instincts that shaped my later work.
Stripe, Zendesk, Jira, Asana, Slack, Glean, AI-assisted support workflows