How many SaaS GTM teams should you have? Hint - 2

I’m not particularly proud of this but my previous blog post on the same topic was kind of a rant. Hence, I decided to be productive on this one and propose a solution to the problem: Too many people reaching out to customers in a SaaS world.

How it works right now

Well, how do we solve a problem without defining it first? Well here’s how it works right now.

Saas-current-gtm-teams

Saas-current-gtm-teams

All that clutter, yes. See why I ranted? With so many people reaching out to the customer, we’re setting ourselves up for miscommunication. In a set up like this, bad customer experience is a disaster waiting to happen.

Let me quickly define what each of them does.

Sales rep: - The first person to reach out to the prospect - Understands the need — suggest the right solution. Identify product fit - Go to person for commercial/pricing

Sales Engineer/Pre Sales - Demos the product and showcases value to the prospect - Configures workflow and helps set up a Proof-Of-Concept - Go-to person for all tech assistance before the sales cycle

Technical Account Manager: - Single technical point of contact for the customer(ex-prospect) - Manages the product technically - Goto person to understand how the customer’s product is configured — technically - If not available, the s_upport team will step in_

Customer Success: -Proactively reaches out to understand current customer scenario -Reviews product usage and suggests the best possible ways to improve product adoption -Goto person to understand current customer pulse/emotion

Account Manager: - Responsible for managing key accounts and identifying growth opportunities - Proactively reaches out - Goto person to understand if there’s potential to expand product usage across different teams/geographies or scale the current team

The proposed model

Now, I’m suggesting bringing all of that into just two people: Sales + Support.

saas-gtm-proposed

saas GTM proposed model

Yes. Simple & Neat. That’s it.

Well, how about other teams? Let me explain how all the roles kind of merge into either Sales or Support.

The new Sales: - Takes up part of the Sales Engineer’s role of demoing the product, showcasing the value and suggesting workflows - Works with Support to set up a Proof-Of-Concept if required - Constantly engages with the customer to identify growth opportunities thus eliminating the need for a separate Account Manager

The new Support: - Provides Technical support to Sales during the evaluation phase eliminating the need or a Sales Engineer - Sets up workflows and the product pre-sales and manages it post-sales - Proactively reaches out to understand product usage and suggest ways to improve product usage - Works with Sales on new growth opportunities if they come up

What are the potential advantages?

Minimal or No information loss: Customers get annoyed when they have to repeat themselves. Workflows and technical information are the ones likely to get lost during Pre to Post sales transition. This can be fully eliminated as it’s the same person setting it up.

Better Customer experience: Customers work a lot with SalesEngineer and Sales to explain their business needs and set things up the way they want it. Once the Sales cycle ends, they’re forced to give up on the relationship and suddenly work with a new set of people. Customers can work with the same set of people right from the point of evaluation until they leave(or not)

No room for miscommunication: The more people you put between people and people, the more chances of miscommunication. It can lead to a bad experience on both the customer and the employee side. Teams tend to exist within silos and it takes a huge effort to break them down. Fewer teams, fewer silos, lesser effort.

Ideal candidates

So, what kind of people should you be looking for?

Sales: - Strong communication /relationship building skills - Strong Problem solving skills - Good business/industry knowledge - A true consultant

Support: - Strong technical/domain skills - Decent communication - Empathetic, patient and friendly - Ability to preempt problems

Potential objections

Of course, a new method, a new approach. Things aren’t going to be easy. I’ve tried to answer FAQs on this approach.

Won’t my Sales bandwidth reduce if they’re working on demos as well? A simple answer to that would be to add more people to the team. Think about it. When the leads increase, you add people to the Sales team and when you grow the Sales team, you add people to the Pre Sales team. Now, you’re just adding people 1 team instead of two.

If my Sales team is engaging with old customers, how can we get new revenue? Not always. It will majorly be the Support team that engages with the customer and the Sales team will only engage with them from time to time — proactively. It’s always better to keep in touch with your customers and who knows: if you keep them happy, they might get you a bunch of new referrals. Earlier, 1 account manager used to do it for about 3 Sales Reps leads. I’m just proposing everyone does Account management for their own accounts.

The above model is just an idea and may not be fully scalable. It might sound silly but who knows, maybe that’s what people think initially when unconventional ideas are brought up :)