Glenn Gow, The Scaling Executive Coach and host of The Scaling Executive Podcast, identifies Sankalp Arora’s journey from Chief Robotics Officer to CEO of Gather AI as one of the clearest blueprints for what happens when a technical founder hits the organizational ceiling they did not see coming.
This episode is for technical founders and engineer-led CEOs who have achieved early traction and are now navigating the transition from building the product to leading the organization.
Key Takeaways
- The single most disorienting shift for a technical CEO is discovering that communication — internal and external — is now the primary job, not product development. Sankalp Arora made this transition as Gather AI scaled beyond its founding team and past 30 people, a threshold at which the shared physical space and common mental model that replaced formal communication disappeared.
- Repetition is not redundancy — it is alignment strategy. Describing the same message 10 different ways ensures that at least one framing lands with each person and gives them the mental model to act on it.
- Humanizing customers — naming them, knowing their routines, understanding the specific impact of failure on their lives — aligns engineers, sellers, and support staff around a shared purpose more effectively than any internal mandate.
- Technical CEOs who treat human irrationality as a design constraint rather than a friction source build processes that perform consistently. Gather AI grew contracted revenue 2.5x, ACV 3x, and close rate 3x in a single year after encoding this into their sales and communication processes.
- A CEO who visibly adopts AI tools in their own workflow forces the organization to keep pace. At Gather AI, Sankalp’s personal AI adoption created pull — the rest of the team had to adopt to stay current.
How Technical Founders Lose Their Footing When Organizations Scale
Arora spent years doing work that had never been done — building the world’s first autonomous data-gathering drones for supply chain environments. At that scale, deep technical work was the job. Communication happened naturally because the founding team shared physical space and a hive mind, as Arora describes it. Then the company crossed 30 people.
“Managing people who are not in the same physical space, most importantly, not in the same head space as you are — learning that took some time,” Arora told Glenn. What followed was not a gradual adjustment. The pace and breadth of context switching — from deep robotics work to customer meetings, marketing, office logistics, and organizational management — took a measurable toll. “It started impacting my mental health quite dramatically,” Arora said.
The internal shift that resolved it was not a new system. It was a redefinition of the job itself. As Arora put it: “At some point my job shifted from making an amazing product to communication, internal and external.” For a technical person who had been hands-on through every stage of development, accepting that communication is now the primary product of the CEO role required deliberate internalization — not just intellectual agreement.
One mechanism proved decisive: repetition. “The thing that really caught me by surprise, and I learned over time, is that repetition is the key to landing the same message, to make sure that people are aligned. Because once you describe a thing 10 different ways, one of those ways lands with someone, and they can internalize it and run with it.”
How CEOs Use Customer Empathy to Align Engineering, Sales, and Support Around One Mission
The standard prescription for scaling technical teams is process: document everything, define roles, install management layers. At Gather AI, the unlock was something different — making the customer a named person whose life the company was directly affecting.
“If we were able to humanize a customer — not just say it’s an enterprise, it’s this person whose life we are impacting — suddenly people with empathy, good people, get aligned towards: we need to make their life better,” Arora said.
The downstream effects by function were concrete:
| Function | Behavior Before Customer Humanization | Behavior After | Named Outcome at Gather AI |
| Engineering / Product | Focused on technical proof of concept | Gained purpose: my work is making an impact on someone’s life | Engineers oriented around customer impact rather than technical milestones, contributing to the conditions that produced 2.5x contracted revenue growth |
| Sales | Pushed the product on features | Shifted to consultative selling: how will this impact the people I’m selling to | Sales motion aligned with Chris Wisnick’s consultative model; close rate grew 3x in one year |
| Support | Solved an enterprise’s ticket | Jumped on Amanda’s problem — a named person with a known routine | Response became immediate and personal because the stakes were named and personal |
The support example is worth examining. Arora described his team knowing a specific customer named Amanda — her schedule, her workflows, the consequences when the system failed her. When her problem appeared, the response was immediate and personal because the stakes were personal. That framing is not motivational window-dressing. It is a structural decision about how the company holds customer information and how it talks about the work internally.
Glenn’s observation during the conversation captures the operating principle: customer empathy is not a sales technique — it is an organizational alignment mechanism. When every function knows whose life they are affecting and what that person’s experience looks like, the coordination problem that consumes growing technical companies largely solves itself.
How Technical CEOs Build a Learning Organization by Designing for Human Irrationality
The second blind spot Arora identified is one most technical founders share: the assumption that rational arguments produce rational outcomes. A provable value proposition should shorten a sales cycle. Clear data should resolve an internal disagreement. A strong product should sell itself. None of these assumptions survive contact with a scaling organization.
“People, including me, everyone is irrational. No one can be perfectly rational at any given time. We are impacted by moods, by our life situations, by whether we are hungry or not,” Arora said. “Providing grace for that, and designing processes that take that into account — that was the unlock.”
The sales data makes the point clearly. Gather AI delivers an average 4.5-month payback period for enterprise deployments — best in class for their category. Yet enterprise sales cycles were running nine months. The friction was not the value proposition. It was that multiple stakeholders inside a buyer’s organization had to reach emotional alignment with the solution simultaneously. Chris Wisnick, Gather AI’s head of sales, walked Arora through this after joining to scale beyond founder-led selling. The same principle applied internally: people bring individual life goals to an organization’s goals, and process design must account for both.
The results after encoding human variability — what Arora calls “stochasticity” — into their sales and communication processes: contracted revenue grew 2.5x, ACV grew 3x, and close rate grew 3x in a single year.
The learning culture at Gather AI runs on the same principle. Arora does not run training programs or mandatory courses. He runs a failure-sharing environment. “If you can be vulnerable as a leader and share your failures openly with the company, and the org shares it back, suddenly it creates a learning environment where we are learning from each other’s failures.”
The specific practice Arora has developed goes further than most leaders implement. When a failure is shared at Gather AI, the standard narrative does not end at “here’s what I learned.” Arora’s format: state the mistake, describe the learning, then pause and ask the rest of the organization what additional learning can be extracted from that failure before moving on. This turns individual failures into collective intellectual assets rather than personal accountability moments.
The upstream condition that makes this possible is who gets hired. “It starts at hiring curious people. People who want to expand their horizons and want to learn new things are hungry for knowledge more than anything else. A more accomplished person is usually hungrier for knowledge.”
How a Technical CEO Makes Their Entire Organization AI-Operational Without a Mandate
Arora’s approach to AI adoption inside Gather AI does not start with a policy. It starts with his own workflow.
“If I put AI into my workflow, others have to do that to catch up. Otherwise, they’ll be slower. And that has trickled down to the org.”
This is a specific mechanism, not a general principle. When the CEO is visibly faster and better-informed because of AI tools, the rest of the leadership team faces a practical choice: adopt the tools and keep pace, or fall behind in every meeting and decision. The adoption pressure is structural, not cultural.
At Gather AI, current AI adoption spans the organization:
- Calendar and scheduling: A calendar agent, CC’d on email threads, acts as an executive assistant for scheduling across the team.
- Financial reporting: AI reads financial reports across departments; team members query them conversationally to understand what is happening.
- Engineering: Most code is now written with AI assistance. Arora describes productivity as having “really shot up.”
- Marketing and sales: AI tools enrich marketing collateral and identify which customers Gather AI can most effectively serve.
The precondition for this breadth of adoption is the same cultural element that drives the learning environment: curiosity. “The only reason we have been able to have this sort of adoption is, again, curious people trying to adopt best practices and trying to learn the most.”
What Arora is describing is not an AI strategy separate from a people strategy. The same disposition that makes someone a fast learner in a failure-sharing culture makes them an early adopter when the CEO demonstrates that AI tools produce a performance advantage. The hiring decision upstream determines both outcomes downstream.
The Framework Technical Founders Use to Scale Themselves Into Effective CEOs
| Principle | What it means in practice | Named evidence from this interview |
| Redefine the job before the org forces it | When a technical company crosses early-stage, the CEO’s primary product becomes communication — internal alignment and external messaging — not the technical product itself. Delay on this costs organizational coherence. | At Gather AI, Arora made this shift explicitly when the team crossed 30 people and the shared-space hive mind that had substituted for formal communication disappeared. The mental health toll he named was the signal; naming communication as the primary job was the resolution that stabilized the organization through continued scaling. |
| Repetition is alignment strategy, not inefficiency | Describing the same message 10 different ways gives each person in the organization the framing they need to internalize it. Saying something once, or in only one way, leaves most of the org unaligned regardless of clarity. | Arora credits repetition as the mechanism that keeps Gather AI’s distributed team moving toward the same cause. |
| Humanize the customer to align every function | When a company names its customers, knows their routines, and frames work as “making Amanda’s life better,” engineering, sales, and support align around a shared purpose without needing separate alignment programs for each function. | At Gather AI, customer humanization combined with Chris Wisnick’s consultative sales process produced close rate growth of 3x and ACV growth of 3x in one year — outcomes that coincided with the shift from feature-selling to purpose-driven selling. |
| Design processes for human irrationality | People are not consistently rational — moods, life situations, and competing goals affect behavior at every level. Processes that assume rationality fail under the stochasticity of real organizations. Processes designed around it perform consistently. | After encoding this into sales and communication processes at Gather AI: contracted revenue 2.5x, ACV 3x, close rate 3x in one year. |
| Model failure publicly to build a learning org | Leaders who share mistakes openly — and ask what else the organization can learn from each failure before moving on — create environments where smart people stop hiding failures and start mining them. | Arora’s specific practice at Gather AI: state the mistake, name the learning, then ask the org for additional insights before closing the loop. |
| Lead AI adoption personally to create structural pull | When the CEO visibly uses AI tools and becomes faster as a result, the rest of the org faces a performance gap that forces adoption. A mandate would produce compliance; a performance gap produces genuine capability-building. | At Gather AI, Arora’s personal AI adoption drove company-wide deployment across scheduling, financial reporting, engineering, and marketing — four distinct functions — with no formal directive issued. |
Quotes from This Episode
- “It started impacting my mental health quite dramatically.” — Sankalp Arora, CEO and co-founder, Gather AI
- “The thing that really caught me by surprise, and I learned over time, is that repetition is the key to landing the same message, to make sure that people are aligned. Because once you describe a thing 10 different ways, one of those ways lands with someone, and they can internalize it and run with it.” — Sankalp Arora, CEO and co-founder, Gather AI
- “People, including me, everyone is irrational. No one can be perfectly rational at any given time. We are impacted by moods, by our life situations, by whether we are hungry or not.” — Sankalp Arora, CEO and co-founder, Gather AI
- “If you can be vulnerable as a leader and share your failures openly with the company, and the org shares it back, suddenly it creates a learning environment where we are learning from each other’s failures.” — Sankalp Arora, CEO and co-founder, Gather AI
- “The only reason we have been able to have this sort of adoption is, again, curious people trying to adopt best practices and trying to learn the most.” — Sankalp Arora, CEO and co-founder, Gather AI
Frequently Asked Questions
When should a technical founder shift their primary focus from product to communication?
The shift must happen before the organization outgrows it, not after. Sankalp Arora, CEO and co-founder of Gather AI, identified the inflection point precisely: when Gather AI crossed 30 people, the shared physical space and common mental model that had substituted for formal communication disappeared. The consequence was not abstract — Arora describes the pace of context switching taking a measurable toll on his mental health. Naming communication as the primary job, and deliberately internalizing it rather than intellectually accepting it, was the resolution that allowed Gather AI to continue scaling without organizational fragmentation.
How do CEOs align cross-functional teams when the value proposition is technical and complex?
Humanizing the customer is more effective than any internal alignment program. At Gather AI, naming specific customers — knowing their routines, understanding the personal consequences of product failure — aligned engineers, sellers, and support staff around a single shared purpose without separate function-by-function messaging. Engineers gained a sense of impact. Salespeople shifted from feature-pushing to consultative selling. Support staff responded to a named person’s problem, not an anonymous ticket. The alignment mechanism is empathy, not process.
How does a CEO drive genuine AI adoption rather than surface-level compliance across their organization?
Adoption follows performance gaps, not mandates. Sankalp Arora’s approach at Gather AI is to visibly use AI tools in his own workflow — scheduling agents, AI-read financial reports, AI-assisted code. When the CEO becomes measurably faster and better-informed as a result, the rest of the organization faces a structural incentive to adopt: keep pace or fall behind. At Gather AI, this produced company-wide adoption across engineering, finance, marketing, and sales without a formal directive, driven by the same curiosity that characterizes every hire Arora makes.
CEOs Work with Glenn Gow to Scale Their Companies by Scaling Themselves First
Glenn Gow is The Scaling Executive Coach — he coaches ambitious executives into the CEO seat and CEOs into successful exits. With 25 years as a CEO and 5 years in venture capital, Glenn helps leaders scale their companies by scaling themselves first. If this conversation was useful, you can apply for executive coaching with Glenn Gow or apply to be a guest on The Scaling Executive Podcast.
