brunobannach

I believe the distance wouldn't affect the speed, but we'll check. Thanks for the feedback!

The main difference is scalability. Jestor is useful for companies once they grow, when tools for teams aren't suitable anymore.

We've built the product for hundreds of simultaneous users. There are 3 features that enable it: 1. Connect any table. You aren't limited by Workspaces. 2. Advanced Permissioning Tools. You can do it at the variable level, creating unlimited number of profiles. 3. Unlimited number of records, tables, dashboards, automations and users. They will consume actions, but there is no real limitation.

Thanks!

I love the cleaning example because it's something that's not considered "sexy", but that several hospitality businesses need to solve. Most tools want to only help with sexy topics like "movie production", "project management", etc. In my view, there are lot's of "non-sexy problems" that need to be addressed.

You're correct! It was a typo and we now fixed it, thanks!!

There are some core differences:

1. You can connect everything in Jestor. All your tools will be connected, instead of building lots of stand alone applications for each team/problem.

2. Jestor provides database functionalities, so you don’t need 3rd party services to store your data and link it to processes within the platform.

3. Our focus is no-code and non-technical teams, whereas Retool is closer to a low-code tool for engineers.

We struggled a lot to realize that complex offline operations are a much better fit for us. In the beginning we're trying to help "Any company with any problem", and we ended up building nothing for no one. That’s when we saw that our clients with really tough operational problems were extracting great value from all the features we offer. We saw this fit had two parts: the operations being complex and them being offline. The reason we focus on complex operations is because easy problems don't actually need a tool. For a small company without ops problems, spreadsheets or paper sheets will usually do the job. The offline part is because we built Jestor to run on any mobile device from day 1 (as any modern application should). And "real world problems' need to have the data on the field, not only on computers.

Performance is extremely important. I say that because we use Jestor every day here, and if it's a bit slow we immediately try to understand why and how to make it faster. About templates, did you use it straight from the website or by installing into an account? I'm asking so I can check with the team and solve it asap!

Thanks!

Hi HN, we are Bruno and Guilherme of Jestor (https://jestor.com/). We make a no-code tool for COOs that need to scale complex offline operations such as hospitals, hotels and kitchens.

At our previous company, a software development business, most of our clients asked us to build in-house tools like an "easy to use Salesforce" or a "lighter SAP" that would reflect their internal processes. They were tired of paying high prices for 20-year-old enterprise software that was slow and expensive to adapt to their operations. They would usually also say something along the lines of: "I don't want to depend on you guys, I need something that my operations team can adapt themselves". All of them were using some combination of spreadsheets and SAP/Salesforce, and were not happy. We decided to develop software to empower them to build their own tools for operations, thus killing our previous business.

We achieve this by providing essential functionality without code, and enabling more customized behaviors to be quickly implemented with basic scripting ("low-code"). We give operations teams a way of using relational databases, setting up permissioning rules, and creating dashboards, forms, tasks and automations. Low-code allows for customized behaviors and integrations such as customized UIs, which allows for applications to be run on top of our platform. Proptech companies are using Jestor to manage room cleaning operations (cleaners have a Jestor app on their phones and receive information about where they need to clean), and foodtech companies are using it for managing warehouses and logistics.

Most of our clients have field operations, like when a doctor visits a patient in their home, so everything we build is designed thinking of mobile use. For example, you can create no-code automations straight from your phone. Another thing that's really important is the ability to connect any data in your company, so you can choose to integrate data from multiple teams in Jestor.

We never liked the pay-per-seats pricing model, so in Jestor, so we only charge based on usage. We believe it's much fairer to pay according to the value we generate for the user, instead of their "team size". Also, the more people using Jestor the better it gets. We're very pumped to be here and looking forward to hear what you think! Please leave us your feedback, including criticism so we can improve!