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

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...

77% of leaders say their teams need AI skills urgently. 64% say their organization plans to train current employees rather than hire new ones. So far, so reasonable. The part that surprised me is who's been put in charge: 34% of those leaders say IT and engineering own the AI skills mandate. Learning and Development or HR own it at 7% of organizations. That's roughly five-to-one in favor of the people who understand the tools, over the people whose actual job is teaching adults how to learn new ones ...

In the ever-evolving digital landscape, enterprises are increasingly focused on enhancing their observability stacks to gain deeper insights into their IT environments. Observability has become a cornerstone of modern IT operations, enabling organizations to monitor, diagnose, and optimize their systems with unprecedented precision. However, a critical piece of the puzzle often goes unnoticed in this transformation: IBM i ...

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

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...

77% of leaders say their teams need AI skills urgently. 64% say their organization plans to train current employees rather than hire new ones. So far, so reasonable. The part that surprised me is who's been put in charge: 34% of those leaders say IT and engineering own the AI skills mandate. Learning and Development or HR own it at 7% of organizations. That's roughly five-to-one in favor of the people who understand the tools, over the people whose actual job is teaching adults how to learn new ones ...

In the ever-evolving digital landscape, enterprises are increasingly focused on enhancing their observability stacks to gain deeper insights into their IT environments. Observability has become a cornerstone of modern IT operations, enabling organizations to monitor, diagnose, and optimize their systems with unprecedented precision. However, a critical piece of the puzzle often goes unnoticed in this transformation: IBM i ...