What I Build

I got tired of watching
good people do avoidable work.

Customer Success Managers (CSMs) building spreadsheets instead of talking to customers. Leaders waiting days for a report someone could've automated. I started building tools to fix that โ€” and I haven't stopped. The goal: surface the right data to the right person so they can make better decisions faster.

Dozens
Automation
Tools Built
21
CS Workflow
Integrations
AI
Native in
Every Stack
Platform Work

The bigger things
I've architected.

These aren't scripts โ€” they're platforms. Each one started because I saw teams struggling with something that shouldn't have been hard.

๐Ÿค–
AI Platform

AI Security Intelligence Platform

Customers shouldn't need to be experts in your dashboard to get value from your product. I built a conversational AI platform that lets them query their own security data in plain English. Multi-agent system with specialized AI agents handling security analysis, alerting, and guided workflows.

When people can actually use the product without a learning curve, they adopt it deeper โ€” and deeper adoption is what makes renewals easy.

Outcome: Deeper product adoption, better health scores, lower churn risk
๐Ÿ”Œ
API Integration

Operations API โ€” 21-Tool Automation Layer

An MCP server that connects data across CRM, ticketing, and internal analytics into one layer โ€” 21 tools that automate touchpoints across the customer lifecycle. Instead of toggling between five platforms to answer a question, you ask once.

The point: get the data to the person who needs it in seconds, not hours. That's how you free up time for actual customer conversations.

Outcome: Hours back per CSM per week โ€” time that goes to customers instead of tools
Automation Library

The stuff that used to
eat everyone's week.

Each of these started the same way: I watched someone spend hours on something that should've taken minutes. So I automated it.

๐Ÿ””
Renewal Ops

CRM & Renewal Automation

Renewal alerts, pipeline hygiene, CRM record maintenance โ€” all automated. When a renewal hits a milestone, the right people get notified and the right tasks get created. No one has to remember to check a spreadsheet.

Outcome: No renewal falls through the cracks, no manual tracking
๐Ÿ“Š
Health Scoring

Automated Health Score Reporting

Pulls from product usage, support history, CRM activity, and engagement data โ€” then delivers weekly health reports to CSMs and risk dashboards to leadership. Nobody has to build it by hand every Monday morning.

Outcome: Every account visible, every week, automatically
๐Ÿ“‹
CS Enablement

AI-Generated CS Presentations

QBR decks that build themselves โ€” live customer data, usage metrics, ROI indicators pulled into a branded presentation. CSMs used to spend hours prepping decks. Now they spend that time on the conversation itself.

Outcome: More QBRs, better quality, less prep time
๐ŸŒ
Operations

Network & Infrastructure Diagnostics

When a customer's environment is causing product issues, you need to know before it becomes a support escalation. Automated diagnostics that identify the problem and surface it to the right team.

Outcome: Faster resolution, fewer escalations, happier customers
๐Ÿ“ˆ
Analytics

Tenant Analytics & Reporting

Usage trends, adoption benchmarks, security posture data โ€” surfaced automatically so CSMs walk into renewal conversations with real numbers instead of gut feelings. Also where expansion signals show up first.

Outcome: Data-backed conversations and early expansion signals
โšก
Workflow

The Script Library

Dozens of Python scripts that handle the operational plumbing: onboarding checklists, health score aggregation, CRM records, playbook tasks, performance reporting. The stuff that has to happen every day but doesn't need a person doing it.

Outcome: CS ops that scale without adding headcount
Philosophy

Automate the process.
Not the relationship.

I start with one question: what's keeping someone from doing their actual job? If a CSM is spending three hours building a report, that's three hours they're not talking to a customer. If a leader is waiting two days for a dashboard, they're making decisions without data.

The tools handle the mechanical work. People handle the conversations that actually drive retention and growth. That's how you scale a post-sale org without losing the part that makes it work.

Stack & Platforms

CS Platforms

Salesforce HubSpot NetSuite Gainsight Totango

Languages & Tools

Python FastMCP JavaScript SQL / Athena REST APIs GitHub Actions

AI & Infrastructure

Claude API Anthropic SDK Multi-agent Systems OpsBeacon AWS