The blog post is written by Retool, and it is something that we (early stage startup) is adopting for internal operations. I was hoping to see Retool talk about

The blog post is written by Retool, and it is something that we (early stage startup) is adopting for internal operations. I was hoping to see Retool talk about what they see their market opportunity is, and what they think Retool is doing different, but the post only sketches out a few things on how things have changed. I don't know about SAP, but one of the main reasons we're adopting Retool internally is because our engineering team keeps deprioritizing writing internal operational tools in favor of adding features for out customers, yet our operations are becoming increasingly more complex. Something like Retool lets our end users (our own staff) be able to work with it. In a lot of ways, Retool is more like an MS Access, only it is a cloud native SAAS and from the get go, work with integrating existing databases. Writing about SAS, I think it's clear Retool has been thinking about how to grow with the organization, possibly where organizations can stay with Retool instead of trying to implement SAP. I'm also curious about how they are going to work with the increasing shift from "data lakes" to "data mesh".