Asana vs Procore Project Management comparison

"I like how easy it is to use the rules within Asana."

"It has helped our departments maintain visibility."

"The only thing I love about the product is that it is beautiful."

"The way it handles the task is good. The whole team needs to organize all our tasks using Asana. It helps to clarify and allows us to prioritize tasks effectively."

"Asana has helped me (as an individual contributor) organize my daily work and given me a way to plan for longer term objectives."

"It's very easy to use for everyone in the team, and they have a good tool for the portfolio aspect because we have projects in different areas."

"The general UI shows progress and data analytics for all projects in progress."

"The ability to build subtasks and break things down off of our major tasks has been very valuable. It is very stable and extremely scalable. The initial setup is very simple."

"Other companies have been using it for years, and it is a very stable platform."

"What I appreciate about using Procore Project Management is the convenience of putting everything in one location, where pictures, schedules, blueprints, drawings, change orders, and all documents are accessible in one platform."

"The financial side of Procore Project Management is better."

"The coordination between the field and the office without the need to print or physically transport drawings is very valuable."

"There just needs to be a bit more direction on how to use it at the outset."

"It would be beneficial if Asana had a predecessor feature that automatically adjusts all subsequent dates when changes are made to a timeline. For example, if I assign a designer four hours for one task and two days for another, and the completion of a task takes longer than anticipated, it would be convenient if updating one date could prompt the adjustment of all other relevant dates. Essentially, this feature would streamline the process and eliminate the need for manual adjustments."

"On the development side for technical project management, Asana is missing features. We only use it for discussing tasks and strategies, and we use it for customer to-do lists. It doesn't have the source code integration that Jira and Jira Service Desk both have."

"The main dashboard, where there is a list, needs improvement."

"There could be some improvements in terms of how projects or day-to-day work is organized. One of the challenges when it comes to rolling out to an enterprise is the way the projects are organized. It has a kind of setup where you have different projects and tasks, but it is not as organized as Smartsheet when it comes to organizing projects or different teams. It can get really cluttered really fast. JIRA has another suite to submit the support tickets. It would be good if Asana could branch out to incorporate some kind of workflow. It is great for collaboration and recording work, but there isn't any workflow. It would be useful if they can map out a workflow of who approves what. This is kind of a big ask, and it is not geared towards that."

"It's difficult to have short-term collaborations with external users because the operations team owns the final licenses, and I work for marketing."

"There is room for improvement in integrating Asana with different technology vendors."

"If you have been using a tool like Jira for many years, it make time some time to get used to the minimalist layout in Asana."

"It is not entirely intuitive, so there are areas for improvement."

"It takes time to use it. It is not entirely intuitive, so there are areas for improvement."

"It would be nice if the tool can reduce its operational cost. It would make it more competitive."

"I did not care for the platform from a user-friendly perspective because I am more of a construction professional than a computer professional."

"The price of this solution makes it quite accessible, and the plans fit my budget."

"Asana has two different types of structures: company vs workspace. Company is really best if all the users you plan to assign work to are all internal (have the same corporate domain in their user ID email address). Once one person signs up (even for a free account) with a corporate email address, Asana will automatically relate that person to that company, if it already exists. If you plan to use it for external collaboration as well as internal, then creating a workspace is a better approach."

"I can describe Asana's pricing as a sweet spot since it is neither very high nor very low, especially regarding the value Asana adds to its products...In our company, we use 50 percent of the features provided by Asana, because of which we only pay 50 percent of Asana's total cost."

"There is a free version of Asana, but we use the paid version to receive all the features we want. The overall price is reasonable."

"We're on the business tier, which is $25 a month if you're on an annual contract. It's $31 if you're on a month-to-month contract. In my experience, there are no hidden costs with Asana. I know Smartsheet has these add-ons that you can buy, which is an additional cost, but Asana doesn't have any add-ons that I know of. When you're trying to scale the product and want to add users, you have to do it in buckets of five. This is also something to consider."

"We paid a monthly licensing fee for the product."

"The price of the solution is reasonable."

"Its price is fair. Its licensing cost is cheaper than Microsoft Project. I would rate it a two out of five in terms of pricing."

"The tool is cheap and I would rate it a ten out of ten."