ABOUT MUDANZA
Memory that serves the relationship.
Mudanza is an early-stage advisory platform and governed memory layer for wealth management. We are building around a simple idea: what a firm learns about its clients should carry forward, with the context and evidence that make it useful.
A client’s priorities live across conversations, notes, documents, and separate systems. Our direction brings that knowledge into one living record, connecting it to planning and the work that follows. AI should help people prepare, understand, and follow through while preserving human judgment.
Our five co-founders bring experience in advisory practices, capital markets, technology consulting, enterprise data and AI, and building businesses. We are still early: these roles will help shape both the product and the way we build it.
Why this role matters
A convincing demonstration does not automatically become a daily habit. Advisory firms need a clear path from their current systems and processes to a working environment their people trust. You will own that path: understanding the firm, choosing an initial workflow, coordinating data and access, training the team, and identifying what prevents adoption. Your work will make customer learning a direct input to the product.
The scope of your role
You will partner closely with Michael Rawls, Mudanza co-founder, and with the other co-founders, engineers, and designer. This is an early customer ownership role combining implementation, enablement, and ongoing success. It requires comfort going deep into configuration and workflow details while keeping sponsors and users aligned. You will help establish a repeatable operating approach, with an honest distinction between available capabilities, planned work, and unresolved issues.
What you’ll own
- Lead discovery with advisors, operations, compliance, and firm leadership. Map the current workflow, identify the first useful outcome, and agree on responsibilities and readiness criteria.
- Own onboarding plans, dependencies, risks, and communication. Keep customer commitments connected to confirmed product behavior and engineering capacity.
- Coordinate source-system access, migration validation, user roles, and configuration with technical owners. Make reconciliation gaps visible before go-live.
- Build practical enablement around real tasks: preparing for a review, updating a record, reviewing an AI draft, and handing work to another team member.
- Guide pilot and launch decisions using observable evidence. Track time to the first useful workflow, activation, repeated use, support friction, and unresolved blockers.
- Translate customer feedback into reproducible issues and clearly framed product opportunities. Close the loop so firms understand what changed and what remains open.
- Create implementation checklists, training material, escalation paths, and customer review routines that can support the next firm without starting over.
What you bring
- Experience leading B2B software implementations or customer success engagements with multiple stakeholders and meaningful operational change.
- The ability to translate a business process into a practical configuration, training plan, and set of acceptance criteria.
- Strong project ownership and written communication, including difficult conversations about scope, readiness, and unresolved problems.
- Comfort investigating software behavior and working with engineers on clear reproduction steps, data issues, and customer impact.
- Good judgment with confidential information and the ability to keep implementation work inside agreed access and handling boundaries.
Especially useful experience
These are helpful additions, not a checklist you must complete.
- Experience in an RIA, wealth technology provider, or another regulated professional-services environment.
- Data migrations, enterprise enablement, change management, or building an early customer-success function.
Your first 90 days
A starting framework for the role; we’ll shape the sequence around product and customer priorities.
- Days 1–30
Learn the product and map an initial customer journey, including the people, systems, and dependencies needed for a successful start.
- Days 31–60
Guide an early implementation against documented readiness criteria and build the first reusable onboarding and training materials.
- Days 61–90
Establish adoption reviews and a feedback loop that makes customer friction actionable for product and engineering.
How we approach the work
Start with the person and the problem. Make a small, complete improvement. Keep sources and assumptions visible. Test the important failure cases, and follow the work through to its actual use. We value clear writing, thoughtful disagreement, and the ability to change direction when the evidence changes.
In an early team, ownership includes the edges: documenting a decision, helping a teammate, investigating an issue, and being honest about what is ready and what is still being built.
How to apply
Tell us about an implementation you owned, a risk you surfaced early, a difficult customer conversation, and how you determined whether the rollout actually changed the team’s day-to-day work.
You do not need a particular degree, employer pedigree, or a perfect match to every useful skill. Explain the relevant work you have done and the perspective you would bring. If an adjustment would help you participate in a hiring conversation, mention it in your introduction.