Accelo vs. Nuclino

Accelo is a system that can do it all. It's extremely sophisticated. Depending on the sophistication of your organization, or specifically the abilities of the people you put in charge of the implementation, it can almost be too sophisticated. It all just depends on your situation. The more you use it, the more data you give it, the more you'll be able to see and do. It's incredibly powerful. But it's definitely not a tool that would be appropriate for smaller boutique type organizations that have only basic needs.

Incentivized

Nuclino is suitable for just about any company. It is intuitive and helps keep any company organized.

Incentivized

• Timing Client Work: You are able to better manage your time on your clients.
• Housing Client Info in one Area: You can view all you need for any given client in one area.

Incentivized

• Workspaces are helpful to segment information.
• Being able to download files directly from Nuclino is useful.
• Having the ability to link to external docs is useful.

Incentivized

• Accelo is excellent on the adaptation to its deep functionalities.
• Managing multiple project is very challenging.
• Not easy to collect multiple reports across platforms.

Incentivized

• No real offline use is possible.
• For small teams it's ok, but pricing is too high if lots of employees need to work with it.

Incentivized

Looking forward to seeing more refinement of features provided and upcoming features promised :)

I love Nuclino's usability. The layout is clean, simple, easy to follow, and bright. I like that there is a read-only account option so that less-tech savvy people can still use it and they won't need to worry about deleting key information from the database. Similarly, I like the features that allow multiple contributors to have the same features to edit.

Incentivized

From the beginning the Accelo team has been very invested in ensuring our success and overall happiness with the platform. The initial implementation specialists and trainers did a fairly good job of learning our company and needs, and tried to tailor the trainings accordingly. However, once we made the formal switch to the platform, meaning we no longer were using our legacy systems, we found that we had a lot of questions....and a lot of ideas and recommendations. The support team is extremely responsive and seemingly happy to receive our continual feedback. And if we encounter an issue that seems to be a system issue, they work diligently to fix it (we've actually had an engineer join a call with us to learn of the issue - and subsequently fix it)

Incentivized

The Nuclino knowledge base is good. Most answers to your questions can be found there. I didn't need to contact support at all.

Incentivized

Accelo doesn't really exceed any competitors in any one area of their product, but in 2015 when we made the move this was the best option that included all the tools we wanted. However, user adoption was low in some areas due to the UI, so we scaled back Accelo and added other tools.

Incentivized

Nuclino is the clear winner when it comes to ease of use for both the administrator and user. Less setup time and less "training" time. The streamlined interface is quick and intuitive to learn and is not cluttered as compared to Confluence. Every tool you need to use to create a page or administer the workspace is available immediately on screen or by right-clicking. In contrast, Confluence buries many tools in administrative interfaces and only allows use of some features once you make several clicks to include a "macro" or "plug-in". We use both tools and I get complaints constantly from my team about how complicated Confluence can get just to author a quick page.

Incentivized

• It substantially reduced the number of systems we use to run our business.
• It reduced the need to train our staff on a variety of platforms.
• It gave us the ability to have a client-facing portal that directly integrates with our backend systems.

Incentivized

• Having a central documentation allowed users to find data more quickly, which resulted in 50% less "question" type bugs that would appear in our queue.
• Collaborating documentation before development resulted in less bugs; this is part process but the ease of sharing and making related documentation easy to access encouraged users into adapting the process.
• Increased use in documentation allows support response time to be higher for triage since supporting documentation is ready to go.

Incentivized