New on the Blog: How to get CTOs and CPOs on board with No-Code 🚀

Community Resources
1

Hey everyone!

I’m excited to share a piece I recently wrote for the official Glide blog.

As we all know in this community, the biggest hurdle to adopting no-code isn’t the technology. It’s the shift in mindset at the leadership level. I wanted to dive deep into how CTOs and CPOs are currently viewing the “Build vs. Buy vs. Glide” debate.

In the article, I break down:

  • Resource Reallocation: How to frame Glide as a way to free up senior engineers for core product work.

  • Governance & Security: Addressing the high-level concerns that usually stop a project in its tracks.

  • Strategic Speed: Why the role of the CTO is shifting from “The Builder” to “The Architect of Efficiency.”

Whether you’re an agency owner trying to close a deal with a technical founder, or an internal champion looking to scale Glide within your company, I hope this gives you some useful frameworks for those high-level conversations.

Read the full post here:

glideapps.com/blog/experts-cto-and-cpo

I’d love to hear your thoughts! Have you had success (or pushback) when pitching Glide to a CTO? Let’s discuss in the comments. :backhand_index_pointing_down:

#ExpertTips #Leadership #ProductStrategy #GlideBlog

2

In many of the projects I’ve been involved, it is true that I’ve been at the intersection of app builder + fractional CPO + fractional CTO. “Chief” sounds pompous, but really in a few instances I have indeed been the one setting the tech architecture, product direction, and then setting up the solution which includes building the app.

Nice shift in viewpoint. Thanks for sharing your piece here Gideon, I think I would have missed it on other channels.

@Gideon_Lahav_Busines

3

So glad you like it!

The idea came to me as I’m already a CTO officially (you can see in my LinkedIn profile https://www.linkedin.com/in/gideonlahav/), and I was thinking that I’m sure not the only one.