Coda, from Coda Project headquartered in San Francisco, is a template-based document generation solution, supporting a variety of use cases presented by the vendor as ideal for smaller companies that might otherwise be relying on spreadsheets to maintain (for instance) product development, or inventory tracking. It is available free, with paid editions to support teams, automations, or for more advanced collaboration and workspace features, as well as more advanced security features.
$0
per month
HighQ
Score 7.6 out of 10
N/A
HighQ Collaborate, now from Thomson Reuters (acquired 2019) is a cloud-based enterprise collaboration platform, featuring secure file sharing but also means for sharing documents with users outside the enterprise, as well as a user-interface optimized for mobile devices and intuitive interface, with real-time communication.
N/A
Pricing
Coda
Thomson Reuters HighQ
Editions & Modules
Free
$0.00
per month
Pro
$10.00
per month per doc maker; unlimited editors (paid annually)
Team
$30.00
per month per doc maker; unlimited editors (paid annually)
Enterprise
Custom Pricing
No answers on this topic
Offerings
Pricing Offerings
Coda
HighQ
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
With Coda, you only pay for Doc Makers.
Often one person creates a doc, others edit it, and some simply observe from afar. Instead of charging for everyone, we only charge for the people who create docs.
Interested in enterprise pricing? Visit coda.io/enterprise
My organization considers Coda for a variety of business and organizational projects. Using Coda, my organization keeps a lot of data and different types of data in one place. The user interface of Coda is very fluid and easy to use. My organization has benefitted from using the efficient and effective operational functionality of Coda.
HighQ Collaborate is well suited to situations where a law firm maintains numerous documents for a client and the client needs access to them on a regular basis. For example, we may store the client's minute book (which is relatively common for a large corporate law firm to do), but the client may need access to documents in that minute book on a regular basis. Likewise, we have an internal system at the firm for hosting digital versions of closing books, however, many clients would not have a similar system because they would only receive closing books irregularly. USBs get lost and the client might not want to put the closing book on the main server where anyone can access it. By putting the closing book on the extranet site, the individuals in the client's organization who should be able to access the closing book can do so.
It takes getting used to in terms of how the formulas per column is implemented, in contrast to how we build tables in Excel. For organization/team purchase, it would be worth considering having a training for the core team of users. Right now, we do a lot of self-learning.
Inability to email charts or image without these objects being hosted on a third party. The community has been great in providing workarounds but it would be much more convenient to be able to have such ability natively.
APAC Support. I'm based in Malaysia, due to timezone differences, even with a livechat implemented, the support for each step and conversation takes up to 24 hours per response. Having some hours covered in our timezone would greatly improve customer support experience.
It is just not that exciting. We host documents on there for clients but the extranet sites have ultimately turned out to not be a product that our clients are clamoring for or that we are regularly pushing.
Coda is definitely something that has been proven to drive positive impact in our organization. We have many divisions that can benefit from this that we have yet to explore. It would definitely be worth renewing.
Coda can seem either really useful or really useless. The extremes of both ends is driven by what our own understanding of what we want to implement. If we lack this understanding, it will be easy to misunderstand Coda's usability especially in the wrong context.
We haven't done any integrations - the initial part of our experience we found that for docs with complex formulas, the page tends to load slowly but in recent months, Coda has improved and optimized the loading times in general and we generally don't find any problems in terms of speed anymore.
Mainly due to timezone differences. I think Coda's support in general is well implemented and executed. They know their stuff and are helpful. But since I'm not in the same timezone, solution rates are slower for me, and that's not something I prefer. I work in customer service, too, and more often than not, time is important. Shortening the solution time would be a much greater experience.
The interface is easy to use and overall the software seems pretty robust (I haven't had any crashes yet), so I haven't had to use the support very often. Likewise, I don't think I've ever had a client e-mail me with questions or issues - the software is pretty idiot-proof.
I'm relatively inexperienced but this experience is meaningful. It would have been nice to have some guidance from Coda so that we understood more on Coda's purpose and potential.
While all of the products listed have great features and platforms, there was always one thing missing from them that I would need to get from another application. Coda was the first one we used that really combined some of the best parts of those products and allowed us to use it in one place. I also appreciate the flexibility of creating your own framework and workflow, unlike in other tools where you have to follow how they capture data and organize projects.
I feel that HighQ does not really have any real competition in this space because it simply accomplishes its goals far better than the competition at lower cost, while requiring less training and administration.
I think scalability is definitely good here since it's based on number of doc makers. Implementation into each dept becomes simpler. That being said, due to the nature of our work, we find it easier that we have a "super user" and then a team of other doc makers. This would make the doc creation and management more efficient.