4 ms·

Regarding pricing: do you offer monthly subscriptions for "view-only" users? Here's my use-case. I am fine paying $50 a month for someone to make dashboards, c

Regarding pricing: do you offer monthly subscriptions for "view-only" users? Here's my use-case. I am fine paying $50 a month for someone to make dashboards, create queries, etc. However, that's too much (and significantly above other tools) for the "users" of the product: for example, salespeople who I would like to enable to see what products their customers have used. I'd expect something in the 10-20 range per head per month for them, in exchange for more limited functionality. Some companies solve for this by charging for "creators" (dashboard designers, the people who set up the database connection, or run more custom queries) versus viewers. This encourages broader adoption within a company. $50/mo for any type of user is pretty steep.

mousetree 4y ago
This is the major problem we have with Retool. We have a handful of creators and hundreds of end-users (customer service, sales) where we're paying $50 each. Will inevitably tip the balance back to building these high usage apps by hand.
burcs 4y ago
Great point — I love the idea of creators vs viewers. We are looking into building out a view-only mode that would be much more affordable. Potentially even embedded experiences so you could share reports internally without needing to actually log into Outerbase. Would that solve your use case?
- toomuchtodo 4y ago
  > Potentially even embedded experiences so you could share reports internally without needing to actually log into Outerbase. Not OP, but this reminds me of Heroku Dataclips and I think you should strongly consider such a product feature. https://blog.heroku.com/how-dataclips-power-insights-at-heroku https://blog.heroku.com/how-dataclips-power-insights-at-hero... EDIT: Tremendous! Thanks for the reply!
  - burcs 4y ago
    One of our founding developers may or may not have helped build that out at Heroku hahaha. Definitely on the roadmap!
- mediaman 4y ago
  Yes, a view-only mode would work. Ideally it would not just be a static view, but would allow users to run some queries (perhaps constrained?) on the table, so they can get a list of their customers who ordered last quarter but not this quarter, for example, or other similar queries. But disallowing them from modifying the DB would be fine. Maybe limiting it to tables established by the Creator, and with a certain View/Dashboard arrangement, would work.
danpalmer 4y ago
We hit this pricing issue with almost every tool we used at one point or another. Tools that are priced for someone who uses it every day, but where the value comes from having open access for many people who might use it once a month.

mousetree 4y ago

This is the major problem we have with Retool. We have a handful of creators and hundreds of end-users (customer service, sales) where we're paying $50 each. Will inevitably tip the balance back to building these high usage apps by hand.

burcs 4y ago

Great point — I love the idea of creators vs viewers. We are looking into building out a view-only mode that would be much more affordable. Potentially even embedded experiences so you could share reports internally without needing to actually log into Outerbase. Would that solve your use case?

toomuchtodo 4y ago
> Potentially even embedded experiences so you could share reports internally without needing to actually log into Outerbase. Not OP, but this reminds me of Heroku Dataclips and I think you should strongly consider such a product feature. https://blog.heroku.com/how-dataclips-power-insights-at-heroku https://blog.heroku.com/how-dataclips-power-insights-at-hero... EDIT: Tremendous! Thanks for the reply!
- burcs 4y ago
  One of our founding developers may or may not have helped build that out at Heroku hahaha. Definitely on the roadmap!
mediaman 4y ago
Yes, a view-only mode would work. Ideally it would not just be a static view, but would allow users to run some queries (perhaps constrained?) on the table, so they can get a list of their customers who ordered last quarter but not this quarter, for example, or other similar queries. But disallowing them from modifying the DB would be fine. Maybe limiting it to tables established by the Creator, and with a certain View/Dashboard arrangement, would work.

danpalmer 4y ago

We hit this pricing issue with almost every tool we used at one point or another. Tools that are priced for someone who uses it every day, but where the value comes from having open access for many people who might use it once a month.