E72: I Collapsed My GTM Org Chart. This Is Why | Ian Tickle, CRO @ Freshworks
Ian Tickle, Chief Revenue Officer at Freshworks, joins Kyle Norton to walk through why he collapsed a split go-to-market org chart into one revenue organization covering global sales, customer success, and customer experience. Ian is a 30-year SaaS operator who took Omniture through the Adobe acquisition and RightNow through the Oracle acquisition, then joined Freshworks in 2024 to run Europe and became CRO of a nearly billion-dollar ARR business 20 months later. Topics include the symptoms that you are shipping the org chart to your customers, the 8 to 12 week design process behind the reorg, whether a revenue leader should carry the net retention number, and the three questions to ask before unifying sales and CS. Plus, why complexity is not maturity, how shadow orgs get built by well-meaning people, the monthly ritual Ian's leadership team uses to delete process, and the point where poorly connected systems turn AI into a liability.
Key Takeaways:
- Segmentation is an internal convenience, and customers experience it as friction. Freshworks previously ran separate organizations for sub-500-employee and 500-plus accounts, which produced parent-child account fights, duplicated support teams, and a customer success line that reported into neither cleanly. As Ian Tickle, Chief Revenue Officer at Freshworks, put it: "customers don't care about my org structure. They care about dealing with Freshworks and is Freshworks going to look after them?" His test for whether a redesign is needed is whether the customer is waiting on an internal boundary to get resolved.
- Complexity arrives as process that was once justified and never got removed. Ian's sharpest example is from an acquisition earlier in his career: "we would get an order, it would go through our systems, and it'd be provisioned within about 7 or 8 minutes of us, you know, checking the order and making sure everything's okay. Got acquired by one of, one of the companies, and that became a 3-week process." Same due diligence, same deal quality, four or five extra layers of approval, and nobody owned taking them back out.
- Accountability blurs in the overlap between teams, not inside them. Ian describes org growth as circles that multiply until the shared area dominates: "Then you get the Venn diagram, which is the gray in the middle, which is where you start to lose the accountability…" His counter is naming a single responsible person per task and then clearing their path, which he frames as an open standing question to his org: "tell me what's stopping you from running faster?"
- Getting faster is only a win if the reclaimed time gets redeployed. Ian is direct about tooling and AI efficiency that never converts into output: "what are you doing with that efficiency to make value out of it? Otherwise, there's like a net-net, it washes out at the back end. We're just being quicker, but we're not necessarily being more efficient or effective." He pairs that with a warning that AI layered onto disconnected systems creates a governance problem rather than leverage, and with a preference for exception-based reporting over data-state reporting.
Connect with the Hosts & Guests:
Host: Kyle Norton, CRO at Owner.com - https://www.linkedin.com/in/kylecnorton/
Guest: Ian Tickle, CRO at Freshworks - https://www.linkedin.com/in/ian-tickle-5a463a2/
The Revenue Leadership Podcast is more than a YouTube Channel:
Subscribe to The Revenue Leadership Podcast Newsletter: https://www.therevenueleadershippodcast.com/
Subscribe to Topline Newsletter: https://toplinemedia.substack.com/
Tune into The Revenue Leadership Podcast: https://www.therevenueleadershippodcast.com/
Chapters:
00:00 Introducing Ian Tickle
05:19 Why Freshworks Collapsed Two Orgs
10:11 Symptoms Of Shipping The Org Chart
14:53 The Org Design Before And After
20:04 How The Redesign Got Decided
27:22 Should Revenue Leaders Own CS
33:16 Three Questions To Ask First
35:29 Making Leaders Own Retention
42:03 Building Simplicity Into The Org
44:33 Seven Minutes To Three Weeks
49:09 Simplicity As Operating Discipline
55:16 Where Shadow Orgs Come From
1:00:31 The Monthly Delete Ritual
1:07:19 Rigor Versus Bureaucracy
1:12:23 Quickfire With Ian Tickle
Key Takeaways:
- Segmentation is an internal convenience, and customers experience it as friction. Freshworks previously ran separate organizations for sub-500-employee and 500-plus accounts, which produced parent-child account fights, duplicated support teams, and a customer success line that reported into neither cleanly. As Ian Tickle, Chief Revenue Officer at Freshworks, put it: "customers don't care about my org structure. They care about dealing with Freshworks and is Freshworks going to look after them?" His test for whether a redesign is needed is whether the customer is waiting on an internal boundary to get resolved.
- Complexity arrives as process that was once justified and never got removed. Ian's sharpest example is from an acquisition earlier in his career: "we would get an order, it would go through our systems, and it'd be provisioned within about 7 or 8 minutes of us, you know, checking the order and making sure everything's okay. Got acquired by one of, one of the companies, and that became a 3-week process." Same due diligence, same deal quality, four or five extra layers of approval, and nobody owned taking them back out.
- Accountability blurs in the overlap between teams, not inside them. Ian describes org growth as circles that multiply until the shared area dominates: "Then you get the Venn diagram, which is the gray in the middle, which is where you start to lose the accountability…" His counter is naming a single responsible person per task and then clearing their path, which he frames as an open standing question to his org: "tell me what's stopping you from running faster?"
- Getting faster is only a win if the reclaimed time gets redeployed. Ian is direct about tooling and AI efficiency that never converts into output: "what are you doing with that efficiency to make value out of it? Otherwise, there's like a net-net, it washes out at the back end. We're just being quicker, but we're not necessarily being more efficient or effective." He pairs that with a warning that AI layered onto disconnected systems creates a governance problem rather than leverage, and with a preference for exception-based reporting over data-state reporting.
Connect with the Hosts & Guests:
Host: Kyle Norton, CRO at Owner.com - https://www.linkedin.com/in/kylecnorton/
Guest: Ian Tickle, CRO at Freshworks - https://www.linkedin.com/in/ian-tickle-5a463a2/
The Revenue Leadership Podcast is more than a YouTube Channel:
Subscribe to The Revenue Leadership Podcast Newsletter: https://www.therevenueleadershippodcast.com/
Subscribe to Topline Newsletter: https://toplinemedia.substack.com/
Tune into The Revenue Leadership Podcast: https://www.therevenueleadershippodcast.com/
Chapters:
00:00 Introducing Ian Tickle
05:19 Why Freshworks Collapsed Two Orgs
10:11 Symptoms Of Shipping The Org Chart
14:53 The Org Design Before And After
20:04 How The Redesign Got Decided
27:22 Should Revenue Leaders Own CS
33:16 Three Questions To Ask First
35:29 Making Leaders Own Retention
42:03 Building Simplicity Into The Org
44:33 Seven Minutes To Three Weeks
49:09 Simplicity As Operating Discipline
55:16 Where Shadow Orgs Come From
1:00:31 The Monthly Delete Ritual
1:07:19 Rigor Versus Bureaucracy
1:12:23 Quickfire With Ian Tickle
Loading content...
Read the full transcript
Matterfact has every podcast on Apple Podcasts and Spotify: 700K+ channels, 120M+ episodes.
The candid version is on a podcast,
not the earnings call.
Matterfact turns the conversations your coverage is already having into a searchable, citable record — across every episode, not just this one.