| Congrats! Quick endorsement (no connection to company): I discovered Retool fairly recently during a bout of frustration-with-our-designers-and-engineers-spending-too-much-time-on-internal tools. We were fighting very very elementary bugs mostly because the people implementing our internal tools were just not thrilled about that work (vs. the customer-facing stuff) and there's just a natural progression of common bugs when you're building things from the ground up. We are just about to launch our first full conversion from an internal tool to a Retool-powered one, and I'm super excited. We were able to get the project to 0 backend engineers, 1 frontend engineer (who gets some help w/ SQL queries), and 1 designer who works directly in Retool (which, to be fair, isn't as powerful as Figma, but that's actually a good thing!). And for the product guy (me), I can go in and tweak things without filing a ticket and waiting for a test-review-deploy cycle. So the whole thing is just quicker and better for this use case. Now our team can focus 100% effort (or, at least 99%) on the customer-facing stuff, which is where we're adding the most value anyway. Suffice to say I'm very pleased so far. |
Internal tools at many orgs languish as not being sexy - I’ve always found them cool and an opportunity for building some good operation secret sauce.