Margot Mueller
"I help technology companies get full value from the products they've invested in. I focus on what customers are actually trying to achieve, how teams can work better together, and building the systems that make success repeatable."
This isn't a typical cover letter. Below I walk through how I'd approach Customer Success at Anthropic: how I think about driving adoption, how I've done it before, and why this role and this company are at the top of my list.
How I Drive Adoption
The JD says: "bring order to chaos and roll up your sleeves." That's how I've operated at every stage of my career.
Here are three concrete examples from my work at Stitch Fix, Opendoor, and Levitate, driving customer outcomes by turning feedback into action:
The framework
1. Start with the customer's definition of success
Before any enablement plan, I ask: what does this customer need to be true in 90 days? What are they measured on? What would make their leadership team notice? The answer to those questions drives everything, not a generic onboarding checklist.
2. Find where value is leaking
Usage data tells part of the story. Conversations tell the rest. I look for the gap between what a customer contracted for and what they're actually doing, then build a plan to close it. Underutilization is almost always a change management problem, not a product problem.
3. Build for scale, not just the account
Every account plan I build, I document in a way the team can learn from. Every champion I develop becomes a template for the next. The best CS work compounds; it doesn't start over with every new customer.
Real Examples: Driving Customer Outcomes
Stitch Fix
Customer Success / Product Operations
Styling feedback was scattered: client notes, stylist channels, support tickets. No single view of what clients needed (fit, style, inventory), so we couldn't act on it.
I built a feedback synthesis system so we could hear the customer at scale: weekly roundtables, a categorized dashboard, and routing rules so product and ops owned the right themes.
Customer outcomes: inventory and styling decisions became data-driven and reflected what clients actually wanted. Time-to-insight dropped from weeks to days, so we could respond to customer needs instead of guessing.
Opendoor
Account Health
Performance signals across 75+ vendor partners lived in 6+ regional spreadsheets and email threads. No single view of health or risk, so issues were reactive and decisions were slow.
I created a portfolio health system: (1) standardized reporting across all 12 markets, (2) a Looker dashboard tracking performance variance and turnaround time by partner, (3) monthly reviews with a single shared decision log so nothing got lost.
Performance accuracy improved 12% within 6 months. Response time to at-risk partners dropped from weeks to days, and for the first time, we could see the full portfolio in one place and make proactive decisions before problems escalated.
Levitate
Voice of Customer
When I joined, customer feedback lived in 12+ Slack channels, email threads, and support tickets. No single place to see patterns, no ownership rules, and no way to prioritize beyond "who yelled loudest."
I built a Voice of Customer system from scratch: (1) weekly CS/Sales sync with a structured template and clear owner, (2) an Airtable-based feedback dashboard tagged by type (feature request, bug, question), and (3) routing rules so requests reached Product or Engineering with context, not just noise.
~70% reduction in manual triage. Customer insights became a direct input to roadmap decisions, and for the first time, we could show which themes mapped to which customer segments, making prioritization defensible and data-driven.
How I'd Approach the CSM Role
Strategic partner to Digital Native Businesses, helping them scale usage, drive adoption, and maximize the value of their investment in Claude.
Relationships & Strategy
- Trusted advisor to key decision makers
- Deep understanding of business objectives and AI vision
- Identify optimization and expansion opportunities
Product & Usage
- Expert across API, Claude Code, and Claude for Enterprise
- Usage planning and optimization: consumption and seat-based
- Drive full value from contracted commitments
Scale & Impact
- Change management: Train the Trainer, Center of Excellence
- QBRs and success plans grounded in customer objectives
- Scalable playbooks that maximize impact across the portfolio
The Opportunity: AI-Native Wealth Management
Private wealth management is ripe for disruption. Services like Range.com charge $6,000/year for what is essentially: document parsing, tax scenario modeling, goal tracking, and periodic human advice.
Claude already excels at all of these tasks. With the right product packaging, Anthropic could capture significant market share in the $1.2T wealth management industry, while genuinely helping people make better financial decisions.
I'm a Range customer today. I live the current model and see the opportunity from the user's side.
Range.com (Today)
- Price$6,000/year
- AvailabilityWait for human CFP
- Document HandlingLimited document uploads
- Advice QualityGeneric advice
Claude (Potential)
- PriceClaude Pro: $240/year
- AvailabilityInstant, 24/7 availability
- Document HandlingNative PDF/document analysis
- Advice QualityPersonalized, context-aware
Understanding Your Customers: DNB Personas
High-Growth Tech (API-First)
Product-led, heavy API usage, multiple use cases across teams
Pain points:
- • Scaling consumption without sprawl
- • Optimizing model choice and cost
- • Proving ROI to leadership
Current solution:
Ad hoc usage, scattered dashboards
"Help us plan usage, optimize spend, and expand to new teams"
Established Tech (Claude for Enterprise)
Seat-based rollout, many departments, change management critical
Pain points:
- • Driving adoption beyond early adopters
- • Train the Trainer and Center of Excellence
- • Underutilization on contracted seats
Current solution:
Some teams all-in, others not yet onboarded
"A playbook to get everyone using Claude and realizing value"
Developer-Led (Claude Code)
Engineering-heavy, building with Claude Code and API together
Pain points:
- • Best practices across API vs Claude Code
- • Use case discovery in other LOBs
- • Technical fluency from their CSM
Current solution:
Strong in one product, unsure how to expand
"A thought partner who gets both the code and the business"
Staying Current on Claude
I've been hands-on with Claude. Here's a mock of the kind of experience I think matters for users: skills, connected context, and clear next steps.
Recent
Workspace
Tax-loss scan found 3 positions with unrealized losses. Sell orders are teed up and ready for your review; could offset ~$4.2K in gains.
I have 2,500 RSUs vesting next month. My marginal tax rate is 35%. Should I sell immediately or hold?
|
Metrics I'd Care About as Your CSM
Usage patterns, adoption, and realized value, so we can spot underutilization, drive optimization, and build the case for expansion. Both consumption-based and seat-based.
Usage & Adoption
Monitor usage patterns; proactively address underutilization and expansion opportunities.
Value Realized
Quantify value and build compelling cases for continued and expanded investment.
Change Management & Adoption
Driving end-user adoption and maximizing value within customer organizations: Train the Trainer, Center of Excellence, and scalable engagement so every account gets the right level of touch.
Train the Trainer
Enable champions inside the customer org so adoption scales beyond the initial team. Clear playbooks, office hours, and best practices they can reuse.
Center of Excellence
Help customers stand up internal CoEs: governance, use case library, and success metrics so Claude becomes part of how they work, not a one-off tool.
Scalable playbooks
Balance high-touch strategic accounts with efficient coverage: repeatable rituals, QBRs, and success plans so the whole portfolio gets the right engagement.
Why This Role, Why Now
I want this role because I believe Anthropic is building something that will fundamentally change how work gets done, and I want to be the person helping the most innovative companies figure out how to make the most of it.
Customer Success at Anthropic isn't just retention and renewals. It's being at the frontier with customers who are moving fast, pushing the boundaries of what's possible with LLMs, and building products that didn't exist two years ago. That is exactly the kind of environment where I've always done my best work: high ambiguity, high stakes, and a real opportunity to shape how something gets built.
I also care about Anthropic's mission specifically. Responsible AI development isn't a constraint I'm willing to work around; it's a reason I want to be here. I want to work somewhere where that's taken seriously, and where the people I work with are thinking hard about what it means to get this right.
After taking time away for parental leave, this is the role I'm most energized to come back for. Anthropic is at the top of my list, and this site is my way of showing why.