Pipefy

At KPMG, I used Pipefy mainly for handling support and requests. I handled job and project tickets for partners and managers, taking care of all the administrative work, reputational and financial research for a given client, and then I carried out the entire research process. Afterwards, at the end, I forwarded it to the manager and partner to evaluate.

I used Pipefy mainly for handling projects and jobs that I provided within the Pipefy platform for managers and partners.

I received the ticket through Pipefy, where I conducted the entire analysis of that request. Each job came with a certain theme. I performed research, as mentioned, reputational research, financial research, so each ticket had its own particularity. Within Pipefy, I received the task with a specific theme, such as Know Your Client analysis, and then I carried out the entire research process, all the form filling within Pipefy, where I received this job. After finishing the whole process, I would close it and then send it to the manager and the partner to review. My part within Pipefy was the service and handling.

I used the entire Pipefy platform. The part I used the most and that was very efficient for me was the email automation feature. I could send, within the ticket itself, the completion email or some request for some document that was missing within that process, and then all my communication was done entirely within Pipefy without the need for me to leave the platform to send an email. This added a lot in terms of time. I optimized time in communications with the partner and manager, which made my work more accurate and faster to complete.

Pipefy adds a lot of value. It reduced rework, both for the team and for each person who uses it. I could easily master the platform, and it gave me a much more strategic and efficient view regarding management as well. Management also had better control through the use of Pipefy. Additionally, I had free access to the Pipefy team, and everything that I wanted to add within Pipefy that would help optimize my work, I had that support. I had the opportunity to participate in some processes and in some change requests within Pipefy, things that would optimize it for me. I always had this direct contact with the team and with leadership to make these adjustments and improve my work.

For me, the most important point of Pipefy, beyond all of its formatting and layout helping me, is the email automation, which is key. Today I have many problems because I use another tool where I use my corporate email, and then I use communication inside the platform I use now. This results in a lot of rework; I have to leave there and check emails. Pipefy brings this ease, the fact that it unites the corporate email together with the platform, which greatly optimizes things, so I don't have to be replying to emails all the time and I receive everything within the ticket itself. I have this control where everything I receive I can respond to immediately.

I have been making adjustments daily. At this specific moment, leadership is still looking for ways to optimize it much more, of course, but I do not feel a lack of features because I have everything at hand there. Whenever there is something I need, I get in touch with the Pipefy team to see if it is possible to make these adjustments. Apparently, at this moment, Pipefy has all the necessary features for my use. In my case, for what I need on a daily basis, it covers everything.

I used Pipefy for four years, where I handled the tickets from the managers and partners and did the whole process within Pipefy itself, including receiving emails related to those tickets.

The control aspect of Pipefy for leadership also helps so that we do not get lost, because since there is a very high workload, this helps us have better organization. The automation and control of having visibility into what is a priority and what is not helps a lot within the platform. All the control I have in the platform is something that adds to the outcome of my work. The email aspect is what helps me the most on a daily basis, where having email within the platform makes all the difference. This optimizes things a lot, besides the ease I have to reorganize my day regarding email.

Pipefy has this openness for me to explain my needs and for the platform itself to help with these issues. I highly recommend Pipefy and I really miss it. Today I do not use it, but it is something I really miss. In fact, I have even mentioned this at the company where I currently am; they do not use the platform, and I even suggested that they check the possibility of contracting it, because it really adds a lot to my daily control and organization.

Personally, Pipefy adds a lot of value, both for management and analyses. I can clearly understand what the client is asking for, which really makes my work easier. Pipefy is a platform that helps me organize, optimizes my work and, above all, the people who manage my work end up with better control over the entire team.

Pipefy positively impacts not only the team but the entire team on the partners and managers side. It does not just help the team that is on the administrative side; it handles the whole management part and also supports the request for demands from other departments, which makes a total difference for everyone on the team and for the company, because the entire company uses Pipefy.

The outcome I have is higher revenue. The company uses Pipefy not only for billing but also for the administrative and management part. They also forward things to other departments that handle projects. Pipefy is an important platform for the company itself. It definitely increases the workload for the department, where the team even grew because the work volume increased. This growth is also due to the use of Pipefy, which is an important tool.

Pipefy helps with error reduction and time optimization. I ended up shortening the response time and, consequently, bringing benefits to the requester. It is a combination that ends up impacting everyone. Pipefy helps the entire management area, the operational area, the projects area, and it is constantly bringing significant changes to all the teams that use it.

Using Pipefy for my turn sheet made the process much faster and more effective, even easier for the management team and my leaders to carry out all the checking. Through Pipefy, it is possible to measure how the workload was, to measure whether I was able to meet deadlines, check if there were delays and what these deadlines were. From there, I had a sense of where I needed to improve. Pipefy also brings this organization aspect where I can see where I am making mistakes and where I am failing, so that I can improve the service and handling side and manage that part as well. My overall rating for Pipefy is a perfect ten out of ten.

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.

My main use case for Pipefy involves creating accounts receivable pipes, splitting tasks among the operations team, and managing projects. I duplicate the information from the financial system for accounts receivable, and from this information inside Pipefy, in a Kanban separated by time stages, I start creating tasks for the finance team.

Kanban view really helps us to have a panoramic view of what's happening in the company, how much we have coming in there, and how much can come in within a certain period.

In my opinion, the best features that Pipefy offers are the separation of forms by phase and the tag section for assignment of owners. The separation of forms by phase and the assignment of owners make my day-to-day easier by allowing me to determine small actions at each phase for a specific person, where the form will only be available in that phase. A specific form will only be available in that phase, then from the moment the phase changes, I can switch it to another person and also change the form. The updated form will be available to another person, but it is a totally different form.

Pipefy has had a positive impact on my organization by helping the collections team convert invoices that were overdue into paid invoices and, consequently, cash for the company.

I believe Pipefy can be improved by clarifying the API calls and making packages for API calls more accessible, because in my organization we have a lot of automation, but we have few API calls, precisely because we have a fixed plan and the organization, in fact, does not need that.

I have been using Pipefy for over two years.

My advice for others thinking about using Pipefy is to have defined processes, so that the migration is easier before migrating. I think Pipefy is a good tool for those who already know what they want and need to speed up processes, but in general, it is more important for you to know which data is important for you and which processes you need to define than for you to simply hire a tool. I would rate this experience a seven out of ten.

I use Pipefy mainly for workflow automation, internal process management, and organization operations requests between teams. We used it to start tasks, approvals, and record information activities for two years.

My main use case for Pipefy is workflow automation, internal process management, and organizing operational requests between teams. We use it to standardize tasks, approvals, and recording operational activities.

One of the workflows I automated with Pipefy is the flexibility of creating customized workflows and automation without requiring heavy development effort. The interface is user-friendly and helped improve visibility across processes and teams. It has improved process organization, task tracking, visibility, and reduces manual follow-ups between teams. It has also rapidly centralized the operational requests in one place.

For example, when managing internal operation requests between infrastructure and development teams, before Pipefy, many requests were handled manually through chat messages, emails, and spreadsheets, which made tracking difficult and sometimes caused delays or duplicated work. With Pipefy, we created a structured workflow where requests automatically move through stages such as triage, approval, execution, validation, and completion. Each stage had assigned responsibilities, deadlines, and automated notifications. This helped centralize communication, improve visibility, and reduce the amount of manual follow-up needed between teams. We also used automation for approvals and status updates, which reduced repetitive tasks and made the process more organized and predictable. Overall, it improved workflow transparency and helped teams collaborate more efficiently.

Pipefy has had a positive impact on my organization primarily by improving process organization, collaboration, and operational visibility across teams. One of the biggest improvements was reducing the amount of manual follow-up work. Before using Pipefy, teams often relied on chats, emails, and spreadsheets to manage requests, which sometimes caused delays, lost information, or duplicated efforts. After implementing structured workflows and automations, processes became more standardized and easier to track. Teams could clearly see task status, responsibilities, priorities, and pending approvals in one centralized platform.

In terms of productivity, it helped reduce repetitive administration tasks through automation, especially for approvals, notifications, and status updates. That allowed teams to focus more on execution rather than manual coordination. Collaboration also improved because both technical and non-technical teams had better transparency into workflows and deadlines. It reduced communication gaps and made cross-team coordination more efficient.

Another important improvement was process visibility for leadership and management. It became easier to identify bottlenecks, monitor SLA performance, and track operational metrics in a more organized way. Overall, Pipefy helped create more predictable, organized, and scalable operational processes.

In my opinion, some of the best features Pipefy offers are workflow customizations with low-code configuration, automation of repetitive tasks and approvals, an easy-to-use and intuitive interface, visibility and tracking across teams and processes, integration capabilities with other tools, centralized process management, notifications, and SLA tracking. One feature I particularly appreciated was the ability to standardize processes while still keeping workflows flexible enough to adapt to different team needs. Teams interact with Pipefy mainly through structured workflows for operation requests, approvals, and task tracking. Instead of relying on scattered communication through chats and emails, they use Pipefy as a centralized platform to submit requests, follow progress, assign responsibilities, or monitor deadlines. It improved collaboration between technical and non-technical teams because everyone had better visibility into the status of tasks and processes.

The flexibility of Pipefy helps my teams because our workflows often change depending on team priorities and operational needs. For example, we initially created a simpler approval workflow for infrastructure requests. Later, as the process evolved, we needed to add new validation stages, automatic notifications, SLA controls, and different approval paths depending on the request type. With Pipefy, we were able to adapt the workflow without needing major redevelopment or complex technical changes. That made it easy for teams to continuously improve processes as requirements changed. Another positive aspect was how quickly non-technical teams could understand and interact with the workflow. The visual organization and automation features helped reduce confusion and improve collaboration across departments.

I also appreciated the reporting and tracking visibility because managers and the team could easily monitor bottlenecks, pending tasks, and process performance in a centralized way.

Overall, I had a positive experience with Pipefy, but I think there are still some areas that could be improved. One area would be advanced workflow management and scalability for more complex enterprise environments. As workflows grow larger and involve many teams, pipelines and automations can become difficult to maintain and organize over time.

I also think reports and analytics could be more flexible and customizable for operational and management level insights. More advanced dashboard capabilities would be helpful for larger organizations. Another improvement could be deeper native integrations with technical and DevOps-oriented tools, especially for infrastructure and engineering workflows. In some cases, more advanced automation logic or conditional workflows require additional configurations or effort. Simplifying this experience could improve usability.

Finally, while the platform is very useful and user-friendly for non-technical users, governance and permission management in larger environments could become easier to structure and manage at scale.

While I do not have exact official metrics available, based on our internal experiences, I would estimate that Pipefy helped reduce manual follow-up and coordination work by around thirty to forty percent. Processes that previously required constant status checks through chat messages and emails became much more centralized and automated. We also noticed faster response times for operational requests because responsibilities, approvals, and deadlines became clearer inside the workflow. From a productivity perspective, automation for notifications, approvals, and task movements probably saved several hours per week for the teams involved, especially for recurring operational processes. Another important improvement was reducing communication gaps and duplicated work. Since everyone had visibility into the workflow status, teams spent less time searching for updates or clarifying ownership. Overall, the biggest gains were in process visibility, operational organization, and reduction of repetitive manual coordination tasks.

One additional improvement that could make Pipefy even better would be stronger AI-assisted workflow recommendations and automation suggestions. For example, intelligent suggestions for process optimization, bottleneck detection, or automation opportunities could help teams continuously improve workflows more proactively. I believe enhanced observability and traceability for complex workflows would be valuable in enterprise environments, especially for teams managing many operational processes simultaneously. Another area could be improving the experience for highly technical teams by offering more advanced API integrations and infrastructure-oriented capabilities while still keeping the platform simple for non-technical users. Overall, I think Pipefy already delivered strong value for workflow and process management, especially because of its flexibility and the ease of adoption across different departments.

My advice would be to start with simple and well-defined workflows first. Then gradually expand automation and process complexity as teams become more familiar with the platform. Pipefy works especially well when organizations take time to standardize processes and clearly define responsibilities, approvals, and workflow stages before building automations. I would also recommend involving both technical and non-technical teams early in the implementation process because one of Pipefy's strengths is improving collaboration and visibility across departments. Another important point is to establish governance and workflow organization standards from the beginning, especially in larger environments. As the number of workflows and automations grows, maintaining consistency becomes very important. For organizations looking to improve operational organization, process tracking, approvals, and workflow automation without heavy deployment effort, I think Pipefy can deliver strong value and a relatively fast adoption.

Overall, I think Pipefy is a strong and flexible workflow management platform that can bring significant value to organizations looking to improve operational processes, collaboration, and automations. What I appreciated most was the balance between usability and flexibility. It allowed both technical and non-technical teams to collaborate more effectively while maintaining process visibility and organization. I also think Pipefy is especially valuable for companies that are transitioning from manual process management and want a more structured and scalable operational model without requiring large development efforts. At the same time, continuing to evolve in enterprise scalability, analytics, integrations, and intelligent automation features could make the platform even stronger for larger and more complex environments. Overall, my experience with the platform was positive, and I believe it can be a very effective solution for workflow and business process management. I would rate this review an eight out of ten.

My main use case for Pipefy is to manage processes and to follow processes with Kanban style management and for some automations such as when an activity is completed then someone gets an email asking them to complete a field or to submit another document. However, it is mainly for process reasons.

A quick specific example of a process I manage with Pipefy is that we used to first receive the suggestion of projects and then the suggestion of participants to conduct this project. Pipefy uses an automation to approve the participation of these candidates in the project with their managers and also to approve the project with the direction of the company. It is all fully automated within Pipefy.

The best features Pipefy offers include the possibility of managing the process in a Kanban style, the fields and making fields obligatory, together with the possibility of making automations, such as notifying someone if a card is in a phase of that process for a long time, then someone gets a notification. When this activity or this phase is completed, someone gets a notification. All these kinds of automations within the transition of phases is the main function that we use in Pipefy.

The automations and required fields help my team day-to-day by ensuring that we have our database always fully completed. For example, there are no blank spaces. We always have the information standardized because the way people fill the fields is standardized because of Pipefy. We have the possibility to analyze this data easily because of this standardization.

Pipefy has impacted my organization positively as we have not reduced our headcount, but we could if we wanted to because the number of people managing those processes before Pipefy was a lot. We have reduced this, and these people now have more time to focus on more strategic and tactical activities and not only on operational activities. We have more standardized data to analyze and now we have dashboards because we have a digital process and not just an analytical process. We do not have paper forms anymore, but we used to have paper forms. All of this has helped us a lot.

A specific outcome since using Pipefy is that we have reduced lead time significantly.

Pipefy can be improved with processes not only following Kanban styles but other kinds of processes that have more paths, not just a single, direct path, but they have bifurcations. Pipefy can also focus on more dashboards and the way to extract and create indicators in the dashboard section as this appears to be a gap.

I have been using Pipefy for two years.

My advice for others looking into using Pipefy is to first describe the process and the improvements in the process before developing the system and the Kanban style. Before you develop Pipefy, I suggest drawing and describing the responsibilities and describing all the process information and the instructions before the tool. I give this product a rating of 8.

Pipefy is used to handle tickets, ticketing, inquiries, and help desk pipes. I currently manage two pipes for ticket handling, and there are upcoming pipes that align with different use cases.

Reporting is a main tool I use in Pipefy, following through the tickets especially when connecting with outsourced companies to manage them. Pipefy speeds up my process significantly. Previously, managing emails was cumbersome with around 200 to 500 tickets daily. Pipefy categorizes and moves cards into various phases easily, a stark contrast to following progress in Outlook.

Pipefy's scalability is noteworthy too. It increases awareness through auto replies and emails, smooth ticket category automation, and helps different departments with additional pipes.

The user interface and ease of use are typical, much resembling a usual Kanban board. However, Pipefy requires integration with existing workflows to enhance its functionality, which is still developing. What is lacking is direct support, since I am required to go through a third-party outsourcing company to connect with Pipefy. It would also be beneficial if internal integrations were enhanced for tools such as Power BI, avoiding additional payments.

I started working with Pipefy late twenty twenty four, but I gained my admin access late twenty twenty five.

Pipefy is stable.

Pipefy's scalability is definitely noteworthy. It contributes positively to my workload, allowing me to handle more pipes.

My concern is that I am connected to an outsourcing company, so any request to Pipefy goes through this third party. This is cumbersome, and I find direct customer service with Pipefy to be lacking.

I did previously use ServiceNow in my past work, but in this current employer, it was not Pipefy; it was just Outlook email, which was the best solution for the Outlook migration.

In terms of money and time saved, Pipefy is a great time saver overall, reflecting in analysts handling additional projects beyond ticket management. This has reduced the need for more employees, as I alone can manage the growth using my admin access.

I think it is important to determine first what you need for the solutions because there are also other alternatives, Kanban solutions, or ticketing solutions that you might need; what matters most here is the usability of the interface.

Pipefy is easy to navigate, resembling a more straightforward and user-friendly Kanban board. It could have been better with more integration features in development. It is not Pipefy's fault about some support issues but rather third-party complications. For usability, Pipefy is favorable given its diverse team adaptability. However, lacking innovative features compared to other existing systems is a downside. I rated this review an 8 out of 10.