As a side note I found retool to be the most prohibitively expensive out of 6-7 solutions I was researching for “low code admin app builder” ecosystem.
* Forms (ie the product here) is free.
* We’ve always aimed to build a sustainable business where we charge reasonable prices and can guarantee we’ll stay in business ourselves. It’s true there are other products that are cheaper, but every single one of those companies is unprofitable and many will probably be dead in a few years. See, for example, Airplane, Interval, or Dynaboard. Dynaboard just got acquired today (their founder is apparently “thrilled” about it: https://dynaboard.com/blog/figma-acquires-dynaboard) and they’re shutting down on April 30th. If you’re a paying customer you’ll need to rebuild all your apps by then. Ouch! (I’d rather pay more and not have worry about core pieces of my business getting shut down with three months’ notice.)
I want to create customer accounts, apply settings (e.g. I delimit the data their account can access, basically adding WHERE clauses on a per-account basis), and they can access white-label read-only dashboards with their own user/pass.
Retool seemed 100% insistent on being an internal-only tool with a high cost per user.
Was curious to apply your use case and see if our pricing model maximises ROI.
Disclaimer: I am co-founder at a retool alternative platform for building internal tools and enterprise apps.
Would be more than happy to talk through your use case; feel free to reach out at antony[at]retool[dot]com.
[0] https://retool.com/pricing [1] https://retool.com/products/portals
I help companies with digital transformation, what it usually entails is deploying solutions to small teams and then growing them as we get buy in from the business. The initial users are high frequency users of the tools, and later users might be infrequent users.
The problem I found with Retool was that as I scaled to the infrequent users the cost per user remained static, so I would be punished for my tool becoming more popular.
From a Low Code product perspective, we were still able to build a beautiful and functional product. Our product unit/engineer ratio is much higher than our competition (see, for example, Retool), which allows us to provide the best value for our users. Regarding the transition, I don't see any indication from the note you posted that users will have to rebuild all their apps. Rather, the founder is saying he will provide more information and possible steps. Who knows – maybe it would be integrated into Figma? And Figma would gain great runtime and IDE capacities?
You're right that it's a big concern, but it's a pretty tough sell to solve this problem by just charging so much that it's clear you could not possibly go out of business. I had to go pretty far down the list of your top competitors to find a good one that was open source, but I did find it.
All that said, Retool's pricing at that time was MUCH worse than it is today. This is what Retool was offering us at the time: https://web.archive.org/web/20230315060042/https://retool.co... -- no distinction between developers and end users! No access controls until the $50/user/month level! That was totally out of the question. The current pricing looks a bit more reasonable, but it's too late; we already committed to the competitor offering an open source solution.
I do think there is more work for us to do — I do think especially as we get more enterprise customers (currently 4 of the Fortune 10 are customers; we're aiming to get to all 10 soon!), we'll be able to make it cheaper and cheaper for indie developers (maybe one day even totally free for up to, say, 100 users, or perhaps to introduce a plan that you can build public apps with unlimited users for free).
We have considered open-coring Retool. I think there are many pros to that (as you note). But my main fear is that it would be difficult to build a business around it, since we'd be stuck selling either hosting or support (neither of which is particularly high margin; cf. Elastic). Or we'd be forced to limit the open-source version to not have important features (e.g. SSO)... and it feels like we wouldn't be true to the open-source philosophy if so.
Thank you for considering Retool!
We were emailing back in 2021 about one of the many products you and your team have built for developers. Exciting conversation, for sure!
If anyone is interested in reading about my experience with ReTool's approach to developer tools, I have a link: https://marak.com/blog/2021-04-25-monetizing-open-source-is-...
If you don't think that's a fair reaction, would love to hear your perspective and buy you a coffee next time I'm in NYC. I'll send you an email now. :)
Keep up the excellent work, creating value with your ReTool company. I am confident you will find continued success with your sustainable approach.
FWIW I run growth for a low code platform company and we are one of the retool alternatives. One of the things I am trying to get right is getting the value proposition right for different scenarios like say building a customer portal (unlimited external users) to admin tools (few internal users). So far we have been able to do good on this front by helping customers with usage based pricing or even developer based pricing. But yet curious to hear your use case and see if there is something I am missing.