Pipefy

I used Pipefy to organize expenses, reimbursement, and travel arrangements. When I enter the system, I can see various processes, such as travel and expenses.

I was using Pipefy for travel arrangements in my previous role as an executive secretary, where I was responsible for scheduling arrangements. In the system, I can analyze when something is not approved, and I can review all the steps to determine if it is in progress or if it has been concluded.

When I was using Pipefy for expenses, I would send the information and attach the receipts, and it would go to my boss for approval. I cannot access the steps for the expenses process, but for travel, I can check all the steps.

In my opinion, the best feature is being able to look at all the steps to see what is in progress, what is at the beginning, and what is necessary to accomplish. Because you can see the flow, and it is clear for you and for your manager or someone else.

Pipefy has had an excellent impact on my organization. When I see the steps, I can organize my routine and determine which people I need to ask to approve the next step. I can organize when the process will be concluded to have an idea of the whole process and which step comes next. For example, if something is taking too much time, I know I need to talk with my manager to approve. I can organize the process, I can organize who is the next person to approve, and if this person takes more time than necessary, then I need to find a solution. In the end, we can prepare a result.

Pipefy system works really well. A potential improvement would be for Pipefy to send a message when something takes, for example, four days with nothing happening or it is still waiting for an answer or needs approval. A notification stating something like 'It is waiting for your answer for ten days or five days' would be helpful. When you receive the message, you can see that you need to check on it.

I chose a rating of nine because if the system sent a message when someone is taking more time to approve or it takes five days without making progress, it would be really helpful for the user.

Pipefy is stable.

Pipefy handles scalability by increasing team output and improving the process, particularly when the process volume is very high. It is a proportional increase in output without a proportional increase in headcount.

The customer support was very good. Sometimes for me, it was not necessary to get in contact with customer support, so it really worked very well.

I can advise that this system is really helpful for users. The support is good, and the team support is excellent.

Before Pipefy, there was no system. We used to write emails, and we would receive a lot of emails, and sometimes it was a mess and difficult to organize. When we found Pipefy, it was an excellent solution for the organization.

After using Pipefy, there was consideration about using the Argo system, which is related to travel arrangements.

Pipefy helped me tremendously because working as a secretary, it is extremely important to see all the steps to manage my time in a good way and not waste time or negatively impact the process. It is very useful, important, and clear. This kind of system helps me with my routine.

Pipefy really improved my routine and reduced some errors. The communication was clear and faster than before. In the beginning, the process was done by email where I received the email and sent the email. With Pipefy, everything is there, and you can see all the steps.

By using Pipefy in my previous company, we improved the time significantly. It was very efficient because instead of sending emails to customers and employees throughout the company, it was very useful for everyone. I can see the steps, and the employee can see them at the same time. It is good to not waste so much time. There is a specific system for organizing travels, for example. It was excellent because in the beginning, it was difficult to deal with only using emails.

My experience with pricing is limited because I work in the administrative area, not in supply. I do not have knowledge about the license or pricing. I work only with administrative support. I would rate this product as a nine out of ten.

My main use case for Pipefy is for many things; I didn't have access to SQL, so I use Pipefy to create a database and store information there. I use Pipefy to make calls to buy and sell assets, to orchestrate processes, and to document everything related to funds by cataloging every step to ensure indicators are correct. I can use Pipefy as a document storage system similar to Google Drive, to schedule work, and to integrate email and Python with Pipefy, making various signals sendable via its API. Pipefy adapts to your needs based on your creativity. The more creative you are, the more Pipefy can accomplish.

One specific process where Pipefy made things easier for me is validating documents. When a manager sends us a document valid for six months, I use Pipefy to extract the date from the document, and using Python, I add six months to that date. If the document passes that date, it is "parecer vencido"; if not, it remains approved for the manager to buy.

The best features of Pipefy are comprehensive; the tool is excellent when you have creativity, as you can use various data types. Pipefy has strong orchestration capabilities that allow you to treat and retrieve data as needed. When you leverage this tool effectively, you can accomplish a lot.

Pipefy has impacted my organization positively by allowing us to orchestrate everything within the company. For example, at Solis, I use Pipefy for "enquadramento," integrating fund indicators with SQL data to monitor our fund's correctness in real time, enabling proactive actions based on the information.

The API integration specifically helps me because Pipefy acts as a graphical SQL interface; I retrieve and query all the fields, compose emails with Python, and send them through Power Automate. I work with data from Pipefy and send feedback back to the Pipefy card, creating a cycle of data management.

An area for improvement in Pipefy is customer support; when I encounter issues, I lack access to human assistance, and I find the training for Pipefy inadequate. The rules and automation often have bugs, which can be frustrating.

The interface is acceptable to me; as a coding person, I prefer back-end functionalities and find it useful. While I don't know how to improve the front-end, I would prefer SQL over graphical SQL for its familiarity and would love to see a chatbot feature for low-code development within Pipefy.

I would like to see improvements in the chat feature; I don't find the current chat helpful and wish there were better support options available when I need assistance with Pipefy.

I have been using Pipefy for approximately four or five years.

Pipefy has stability challenges; the connection drops frequently, but at times it performs well, so I would rate its stability at approximately 80 percent reliability with 20 percent downtime.

Pipefy's scalability is really good; it can handle growing workloads and many users easily.

I find Pipefy's customer support really bad and unsatisfactory.

I have not used a different solution; my tools are Python, Pipefy, Databricks, and Power Automate, which are all very helpful for my work.

I cannot share specific metrics on return on investment because the team handling those metrics is different, and I only have access to limited data myself; essentially, I am aware that there is a team evaluating the value of our tool investments.

I give Pipefy a nine out of ten rating because the support team is a significant pain point for me, and the tool is quite expensive.

The real-time information from Pipefy allows me to act before others; I can anticipate issues affecting our funds before they escalate, preventing mistakes that could have significant consequences. The value of this proactive capability is immense.

My experience with pricing has been one of shock; when the bill arrives, it is apparent that Pipefy is a very costly tool, prompting discussions about whether we could recreate its functions with alternative systems.

My advice for those looking into using Pipefy is to focus on creativity; if you are creative, you can achieve a lot with Pipefy, utilizing automation and understanding how to orchestrate data flows effectively.

My main use case for Pipefy is for quotations and some automatic orders. I start by filling out the inbox part in Pipefy for quotations and automatic orders because there are several phases. In the inbox, I enter the person responsible for the request and the requester's email, which usually appears in another system. Then I have to check it to put it there in Pipefy, then send it to the next phase which would be the request analysis, where I put the details of the material. For example, the categories that material belongs to and how long the request has been open. Then it moves to another phase, the RFQ creation, where I create the quotation by entering more detailed information and selecting the suppliers I want to invite to the quotation, which is then sent automatically to all suppliers.

The best features that Pipefy offers are its various automations and it is also very detailed, with a Kanban format that makes day-to-day work easier.

Regarding automations that make my work easier, when I send the quotation, there is a button that says Send RFQ. I just click it and it goes by itself. I refresh the page and it automatically sends an email to each supplier, so I just wait for the supplier to respond to that email sent to each one.

I find the Kanban format in Pipefy very useful because it has individual phases including inbox, which is when the request enters the system, and then it goes to another phase called request analysis. There is also tax escalation for any problems with the NCM or tax issues. The RFQ creation phase is for filling in the data needed to send to the supplier, and the saving registration part is to register any discount on that purchase, among others. I find it very useful because of all these functionalities.

Pipefy has had a positive impact on my organization and it made day-to-day work much easier. Due to its various features in the phases specific to each situation and the automation, the high technology that Pipefy has is very useful in the company's daily operations and processes.

Sometimes there are errors such as outages or instabilities in Pipefy. Sometimes I have to log in two to three times a day. For example, I log in at 8 in the morning to work and by about 3 or 4 in the afternoon, the system goes down, and an error message appears. I then have to close the page, open it again, and log in again. I believe this part could be improved because this kind of error should not happen while someone is using Pipefy.

I have been using Pipefy for almost two years.

Apart from the instabilities I mentioned, Pipefy is totally stable and works fine in my day-to-day use.

Pipefy's scalability handles the volume of requests very well, and when new demands arise, it does not freeze or lag. It responds very well and rarely encounters issues; the problems I faced were more about being on the page too long, causing an unavailability error that requires closing and reopening the page to log back in. Other than that, it works very well.

Before Pipefy, we used to send quotations through Outlook, which was a manual model. Sometimes we still use it for urgent cases, but on a daily basis, we use Pipefy as the standard. When I arrived here, they were already using Pipefy because it was an investment made by the client in the project with Accenture. I know they hired me because Pipefy is widely used by companies and is very agile and useful, as well as fast.

I have obtained a return on investment with Pipefy; there is a considerable increase in productivity due to the agility of the things done through Pipefy. Due to the technology and phases for each process, the Kanban model makes it very technological, leading to increased productivity compared to something done manually, such as sending quotations by email. The time savings are large as well since things done in Pipefy are very fast because it is an agile system.

I would rate Pipefy a nine on a scale from one to ten. I did not give it a ten because of the crashing and instability issues I mentioned earlier while using Pipefy. I did not give a lower score because it is very useful in my daily work and really speeds things up a lot. All the quotations are done through it, and I really love this system for all these processes. It is very useful in my work.

There is a measurable result I can mention regarding time saved after implementing Pipefy. The process of sending a quotation via Pipefy is much faster than sending it by email or another system, which is more time-consuming. Through Pipefy, it is faster due to the practicality of just filling in some parts of the things that are requested in the phase and the fact of just clicking to send it, allowing it to automatically create the RFQ after filling in all the necessary data. I consider this a very positive impact and I think it takes very little time. The entire process takes about two to three minutes at most. I consider it very useful.

I strongly recommend Pipefy and advise others to do everything through it if possible, including automatic orders. Before, I only did the monitoring of the phases of the acquisitions, but now I do the quotations directly in Pipefy and some automated orders. I would recommend using it because it is very agile and very useful, particularly because of the Kanban model and the detailed phases, making it very organized for the company's daily work. I do not have information on Pipefy's pricing, setup costs, and licensing. My overall review rating for Pipefy is nine out of ten.