Basecamp is a web-based project-management tool. Basecamp offers features standard to project management platforms, as well as mobile accessibility, unlimited users, and 3rd party integrations. Basecamp is priced by space requirements and concurrent projects.
$15
per month per user
Nintex
Score 8.0 out of 10
N/A
Nintex offers a platform that helps companies discover, automate, and optimize business processes.
Basecamp is a wonderful tool for teams of varying degrees of technical knowledge, teams managing lots of different types of "agifall" and waterfall projects, and teams that are remotely distributed. It's probably less useful for more strictly agile-focused development teams, compared to other more flexible software applications like Jira and Asana.
We use Nintex to automate fundraising outreach at scale. It helps us send personalized emails to a large contact list, and we’d also like to automate follow-ups when there’s no reply. If you need highly customized solutions or clean, fully controllable code, I wouldn’t recommend Nintex. It has many features, but it’s not the same as building your own system from scratch. That said, it can save a lot of time for standard automation workflows.
Task management - It is very easy to add, organize and discuss tasks within Basecamp's interface.
The "Campfire" function is great for communicating when you just have a quick question for someone on the team.
Notifications - Basecamp lets you decide how often and about what you'd like to be notified. The ability to respond to messages in Basecamp directly via email saves a lot of time.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
High Learning Curve. It's true that it can be easy to use, but to use well and effectively takes some time to learn. It's recommended to have an agreed-upon system in your team of what tools to use and when.
Notification Overload. If people aren't careful they could send a notification to everyone when only a couple people were meant to be prompted. And since emails are sent by default, you could have your mailbox overloaded with unnecessary updates. This is where it takes a bit of training in your team to have an agreed-upon system.
Lack of organization with Archived Projects. I will often need to reference an archived project to make a new one, but there is only a list of archived projects in alphabetical order, with no way to organize by archive date, or even search.
If you are creating a process with parallel subprocesses, there's no way to see, in a single view in Nintex, all the steps for the subprocesses. You have to view each sub-process in its own view, so it's hard to see what's going on at a high level.
There isn't an easy way to filter the processes by another user (not yourself) in Nintex. There is a report that shows processes and objects by user, but that's not as convenient. This is something that I've seen in other tools (OpenPages by IBM) so I am surprised that it is missing.
Nintex doesn't really have a way to capture iterative processes (which we have a lot of). It's designed for linear processes.
When I bring new people onto a project, it's immediately obvious how to use Basecamp. I don't have to worry about teaching them the features or walking them through it, it's just incredibly user-friendly. For this reason, I'll continue to renew my subscription even as new people are brought onto production jobs or the client changes.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
It is easy to use, even for clients who have no experience with the platform. It can only get a little cumbersome to ensure that a client can't see certain documents you might want to keep in the Docs & Files folders. And sometimes, getting a client to actually use an unfamiliar platform can be a challenge.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
I've never experienced downtime while using Basecamp, or been unable to access it when I needed it. That's not to say they've never had downtime, but I've been lucky enough not to encounter any, and I work odd hours, including late nights when maintenance is often undertaken.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
For the many reasons I've given, Basecamp is a very strong program. There are a few features I can imagine that might make it even better, but I don't have a basis for comparison to be able to say that there is definitely a better one out there. I've noticed that Basecamp has evolved a bit from the time I started using it until now, so that makes me think that the producer of this program values it and believes in continuous improvement. If you could use the features offered by Basecamp, I would think you could use it with confidence.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
Decide the process before implementation - i.e. when it's due 8/9 does that mean 8am, noon, 5pm, 11:59pm? Check your to-do list frequently Set-up templates - just not with the dates (they can be funky)
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
Pretty good, but [Basecamp] has its drawbacks. Honestly I find the interface non-intuitive and sometimes have trouble figuring out how to change the status of a task. Perhaps it has something to do with the way it was originally set up by the admin, but I'm not sure. I liked Jira's drag and drop obvious functionality, but the project management side of the software was lacking. Smartsheet has excellent project management functionality, but the task management isn't as good.
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
It has saved me time when having to get the same message out to multiple restaurants
It has helped us make smarter operational decisions because we can all collaborate on an answer in a shorter amount of time (instead of calling a meeting!!!)
The calendar function allows us to plot out our marketing agenda for the month and add/change it together as needed. The chef will post his recipe, the managers will cost it out, the social media manager will post pictures on it, and ultimately we will get that information out on an info sheet to the staff by printing the page.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
