Role design and job descriptions for Subscription software businesses: Clear Roles Between Support, Success and Sales
When support, customer success and sales each think the customer belongs to someone else, renewals suffer. Clear roles and written handovers make it plain who owns the customer at each stage.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsWhy role design and job descriptions matters in subscription software businesses
Subscription companies tend to grow their roles by accident. A support agent starts advising on upgrades, a salesperson answers technical questions, and a customer success manager spends the week resolving tickets. Titles say one thing and the daily work says another. When a customer is unhappy, each team points to the next, and the person who has to explain it to the customer is rarely the one who knew the facts.
Role design starts from the customer's path: signing, setting up, using, struggling, renewing, upgrading or leaving. For each stage it names who owns the customer, what they decide and what they pass on. The job descriptions are then written to match, with the handovers described as steps, not hopes. The result also helps hiring, pay and promotion, because everyone can see what each level is expected to do.
How to set it up
1. Map the customer path
Draw the stages from sale to renewal on one page and mark the person who leads each stage today. Note the gaps and overlaps.
2. Name one owner per stage
Decide who owns the customer at each stage, who supports them and who is told. Keep the number of owners to one.
3. Write each role in plain terms
List what the person does daily, decides alone and escalates, with the measures used. The role design work outlines the format.
4. Describe the handovers
For each handover, such as sales to onboarding or support to success, write the information passed on and the time within which it moves.
5. Test with the people doing the jobs
Read each description with two holders of the role and fix anything they say is untrue.
Check these first
Before changing anything, find out what is true today. These take an afternoon and use your own records.
- Ask a support agent, a success manager and a salesperson who owns an unhappy customer.
- Compare an old job advertisement with what the person now does.
- Look at five recent handovers and mark what was missing.
- Check whether any role's measures conflict with another team's goals.
GullyHR can do this with you. Read how we approach role design and job descriptions in general, or share your requirements and we will tell you where to start.
Questions owners ask
Not always. A small team may combine them. Once volume or the number of accounts grows, a split lets support solve problems quickly and success think about outcomes. Decide by workload, not by fashion.
Detailed enough that a new person knows what they own and what they pass on, and short enough to be read. One or two pages is usual. Include the measures and the main handovers.
At least once a year, and whenever a new product, pricing change or team structure alters the work. Out-of-date descriptions lead to unfair appraisals and confused hiring.