Customer Success

What you'll do

Own the post-sale relationship for a portfolio of accounts, from onboarding through renewal and expansion.

Build the onboarding and adoption plan for each account based on how that customer actually works, not a template that assumes everyone migrates the same way.

Run the health check on your accounts yourself: usage data, support ticket patterns, and a direct conversation, not just a dashboard color.

Work daily with sales on the handoff into your book of business, and with support and product when a customer's complaint turns out to be a real gap, carrying it back with the customer's context intact.

Decide when a stalled account needs a harder conversation about renewal risk instead of another check-in, and have that conversation before the contract forces it.

Manage a customer who has their own engineers self-hosting Plane and reading the same GitHub issues you are, because they will sometimes know about a bug before your own support team does.

What you'll bring

You have owned a book of customer accounts post-sale

, and you can walk us through one account you saved and one you lost, and what was different between them.

You can read product usage data and support history and turn it into an actual account plan, not a generic check-in.

You communicate clearly with both a champion inside a customer's org and that champion's boss, in writing and on calls.

You have run or contributed to a renewal or expansion conversation with real numbers attached, and know what it feels like when it does not go your way.

You can manage a portfolio of accounts with different needs at the same time , and you know which ones need you this week.

Nice to haves

You have worked in customer success, account management, or a similar post-sale role at a B2B SaaS company.

You have supported customers running a self-hosted or open-source product, where the customer's own technical team is part of the relationship.

You have contributed to Plane, run it self-hosted, or used it as a customer yourself.

You have supported customers in regulated or enterprise environments where adoption depends on more than one stakeholder saying yes.

Why Plane?

Every company says it is different. We will try evidence instead.

The scope is real.

We are a passion team serving companies of every size, including some of the largest in the world. Something you ship this month will run inside a Fortune 500 company and a 50-person startup in the same week, and you will hear from both.

The constraints make you better.

Plane runs in our cloud, in customers' clouds, and on machines that will never touch the internet. Much of the work happens in the open, where the issues, the fixes, and the roadmap conversations are public. Building software that survives all of that is harder than building an ordinary SaaS product, and it is a better education than most companies can offer.

The people-and-agents future is being built here, in production.

We think humans and AI agents will share one system of action for work. We are building that system now, for customers who already depend on it, and you will work on that problem directly whatever your role.

Your name is on the work.

The teams are deeply connected enough that credit and responsibility both find you fast. That is some pressure. Mostly it is the fun part.

If that sounds like your kind of place, we would like to meet you.

Plane is an equal opportunity employer. We do not discriminate based on race, color, religion, gender identity or expression, sexual orientation, national origin, age, disability, veteran status, or any other protected characteristic under applicable law.