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
Google Chat
Score 8.0 out of 10
N/A
Google Chat, formerly Hangouts Chat, is a collaboration tool competing with Slack, designed to make it easy for teams to be able to get their work done in one place. From direct messages to group conversations, Chat helps teams collaborate, and with dedicated, virtual rooms to house projects over time — plus threaded conversations — Chat helps users track progress and follow up tasks. Chat currently supports 28 languages and each room can support up to 8,000 members.
N/A
Pricing
Coda
Google Chat
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
Google Chat
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.
Well suited for businesses of all sizes. HOWEVER, I would say keep the chat groups limited at the departmental level, ensure that your moderator or the individual responsible for the group keeps it on topic, and have your IT team monitor it from time to time. Google Chat gets used so much in our organization that we have rules and regs in our Employee Handbook regarding its proper use (and when used PROPERLY, it can be very effective).
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.
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.
The updates, support, general reviews on Google Chat are great everywhere. The development of the features is ongoing and this adds a great value to Google as a big company in the market. Other applications are limiting communication while Google Chat is allowing communication to grow. It is very easy to use it and teach others how to use Google Chat.
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.
It's not perfect. There are occasional glitches, drop-outs, and it takes a bit to get everything loaded and working. But it is significantly better than Zoom or GoToMeeting when you're in instructional settings. I know my teacher friends here like it and the administrators and parents seem to be satisfied too.
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.
I have not needed to contact the support folks for Google Hangouts Chat, so I can't speak to this with any accuracy. The online instructions are fairly clearly written, so it is fairly intuitive to start with. I did not feel the need to use the support people anyway.
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.
Prior to Google Hangouts, our company used Spark. Spark was not integrated into our email, therefore it couldn't be easily accessed in the same browser. With Spark we also couldn't search our emails for keywords in a conversation, searching had to be done manually. The one feature I enjoyed about Spark was a request to get a user's attention: If I had an urgent question and I wanted to ensure the recipient saw my message/question, I would request their attention and the message screen would pop up on their screen.
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.
