Skip to main content

Overlooking the Unsung Heroes of Tech Startups

The Importance of Customer Success Engineers in Driving Business Growth
Kannan Kothandaraman
Selector.AI

Embarking on a new tech startup can be difficult, and is like constructing an aircraft while in flight. During the initial phases, the primary focus is on sales and marketing, while the essential individuals responsible for maintaining operations — the customer success engineers (CSEs) — are frequently overlooked.

The role of customer success engineers involves overseeing the implementation and deployment of a product, as well as providing guidance throughout the technical solution's implementation. Following a successful sale, they are tasked with designing the customer experience.

Unfortunately, customer success often takes a backseat in the rush for sales and revenue, despite their foundational support to the rest of the business. As a result, many companies have teams of skilled solutions engineers and CSEs but fail to provide the resources they need to be effective.

Today's customers have more options than ever, making it essential for tech companies to have a well-trained team to deliver successful products and solutions. However, many companies overlook the three critical components of an outstanding customer success team that set them apart from the competition in the long run.

It's time to recognize the essential role of customer success engineers in driving business growth and give them the resources they need to lead companies toward sustainable success.

Issues in the Customer Success Team Can Be an Indicator of Deeper Problems Elsewhere in the Company

In my experience, customer success engineers often bear the brunt of problems within a company that originates elsewhere. Poorly defined roles, misaligned expectations, and lack of visibility between product, sales, and marketing teams can all lead to issues that reach customers during implementation. To this end, having a clearly defined customer success strategy aligned with the goals, vision, and long-term strategy is essential for creating successful outcomes across the board.

The customer success team should be seen as a crucial player in any company's business strategy. Investing in and empowering these professionals can help create cross-functional alignment for smoother implementations and better customer experiences. In addition, when everyone is working together towards common objectives, it's easier to develop transparent processes that will help prevent costly errors.

The Technical Knowledge and Understanding of Value Propositions Is Essential for Customer Success Engineers

In the tech industry, a deep understanding of the product and its workings is paramount for customer success engineers. Proper education in the form of skills, certifications, and training is necessary to ensure they can get up to speed quickly.

On top of this technical background, teams must understand the value proposition of their product and its unique capabilities. Without truly comprehending how the solution stands out from the competition, customer success engineers may not be able to deliver exceptional results throughout the entire customer life cycle.

Every business should take the time and resources to equip their CSEs with what they need to succeed — technical knowledge and an understanding of value proposition — so that they can handle any customer challenge that comes their way.

Customer Success Teams Should Have Visibility of Other Business Departments and Create Channels for Honest Feedback

When customers are not satisfied with their experience, their first port of call is often their customer success manager. The manager then addresses the issues with the solutions engineers and customer success engineers. Unfortunately, the flow of information doesn't necessarily extend beyond this point, leaving other departments without valuable feedback on the product or service.

At the same time, it's crucial for customer success teams to have visibility into other areas of the business. They must also have open channels through which they can provide honest feedback without fear of judgment. This is especially relevant in subscription-based solutions where companies must make continual tweaks to ensure customers remain satisfied and renew each year. Thus, customer success teams should be seen as a barometer for how useful a product or update will be perceived by customers and provide strategic input throughout its development lifecycle.

Kannan Kothandaraman is Co-Founder and CEO of Selector.AI

Hot Topics

The Latest

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Overlooking the Unsung Heroes of Tech Startups

The Importance of Customer Success Engineers in Driving Business Growth
Kannan Kothandaraman
Selector.AI

Embarking on a new tech startup can be difficult, and is like constructing an aircraft while in flight. During the initial phases, the primary focus is on sales and marketing, while the essential individuals responsible for maintaining operations — the customer success engineers (CSEs) — are frequently overlooked.

The role of customer success engineers involves overseeing the implementation and deployment of a product, as well as providing guidance throughout the technical solution's implementation. Following a successful sale, they are tasked with designing the customer experience.

Unfortunately, customer success often takes a backseat in the rush for sales and revenue, despite their foundational support to the rest of the business. As a result, many companies have teams of skilled solutions engineers and CSEs but fail to provide the resources they need to be effective.

Today's customers have more options than ever, making it essential for tech companies to have a well-trained team to deliver successful products and solutions. However, many companies overlook the three critical components of an outstanding customer success team that set them apart from the competition in the long run.

It's time to recognize the essential role of customer success engineers in driving business growth and give them the resources they need to lead companies toward sustainable success.

Issues in the Customer Success Team Can Be an Indicator of Deeper Problems Elsewhere in the Company

In my experience, customer success engineers often bear the brunt of problems within a company that originates elsewhere. Poorly defined roles, misaligned expectations, and lack of visibility between product, sales, and marketing teams can all lead to issues that reach customers during implementation. To this end, having a clearly defined customer success strategy aligned with the goals, vision, and long-term strategy is essential for creating successful outcomes across the board.

The customer success team should be seen as a crucial player in any company's business strategy. Investing in and empowering these professionals can help create cross-functional alignment for smoother implementations and better customer experiences. In addition, when everyone is working together towards common objectives, it's easier to develop transparent processes that will help prevent costly errors.

The Technical Knowledge and Understanding of Value Propositions Is Essential for Customer Success Engineers

In the tech industry, a deep understanding of the product and its workings is paramount for customer success engineers. Proper education in the form of skills, certifications, and training is necessary to ensure they can get up to speed quickly.

On top of this technical background, teams must understand the value proposition of their product and its unique capabilities. Without truly comprehending how the solution stands out from the competition, customer success engineers may not be able to deliver exceptional results throughout the entire customer life cycle.

Every business should take the time and resources to equip their CSEs with what they need to succeed — technical knowledge and an understanding of value proposition — so that they can handle any customer challenge that comes their way.

Customer Success Teams Should Have Visibility of Other Business Departments and Create Channels for Honest Feedback

When customers are not satisfied with their experience, their first port of call is often their customer success manager. The manager then addresses the issues with the solutions engineers and customer success engineers. Unfortunately, the flow of information doesn't necessarily extend beyond this point, leaving other departments without valuable feedback on the product or service.

At the same time, it's crucial for customer success teams to have visibility into other areas of the business. They must also have open channels through which they can provide honest feedback without fear of judgment. This is especially relevant in subscription-based solutions where companies must make continual tweaks to ensure customers remain satisfied and renew each year. Thus, customer success teams should be seen as a barometer for how useful a product or update will be perceived by customers and provide strategic input throughout its development lifecycle.

Kannan Kothandaraman is Co-Founder and CEO of Selector.AI

Hot Topics

The Latest

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ...