Launched: Coda 2.0, a simpler, cleaner, and faster doc for teams

What about “guest editors”?

Are they included in any pricing scheme?

PLease answer that because, if it is not the case, I’m going to expel all of them of my public shared docs

Guest editors count as editors when it comes to pricing. So yeah, you want to downgrade any of those to viewers to minimize impact on pricing.

I think my Coda docs just hit the price wall and died :sob:

I have a to-do list, plus some other docs that I use because it’s really handy to be able to mix text and tables. There is no team and there are no Editors. But, I get fancy with customizing things, which is why I love Coda.

Basically I would be paying $120 /year for a to-do list and some other bonus items. It’s just not worth it…

$10 a month might not seem like a lot, but $120 is half the cost of my computer.

4 Likes

Love this. When you’re getting into hundreds of customers with a simple action I would advocate a free role for one specific action and paid for more types of actions. But glad to see this is in consideration.

Agree 100% with your thoughts on the pricing model.

2 Likes

2d this on small teams. $360 /person (maker) /year is a lot for a one-person “team.”

3 Likes

That sounds like a bug. We aren’t enforcing any limits until December 1. Mind sharing more on support@coda.io so we can follow up directly?

Then you Codans need to be much more clear and explicit about this regard, or friction is going to increase greatly. Thanks for the clarification… but I had to ask about it

First of all, congrats for the new Coda! I love some of the new features and there are great additions.

But…
I was anxious about the pricing announcement, and it has come.

I don’t understand the model. Having the pro plan and having limits about the editors is terrible.

I have to give you a use case to be more specific:

I made a doc for our local video game cluster so that each member can add a simple mission like RT a Tweet or bake a Crowdfunding campaign, so that we help each others simply.
We used coda because it’s great and we gamified the thing to entertain the people.

BUT!

We are about 20/30 users. I’m the only maker in the doc and sometimes my associate add or tweak things, and everybody else are just adding some rows with some missions to do, and they push buttons.
So they are all in a way editors.

I would pay a fortune with your system, for editors that just sometimes add some text in a row and push buttons.

In one word, you just killed my doc…
Many of my docs actually. My workflow…

I have many other things to say but I’ll take more time later, I don’t have the time actually to focus on this.

And as an early adopter, I’m not satisfied by what you are gifting me.

Sorry for this Coda team :cry:

2 Likes

No bug, still works for now. You’re fast at replying :slight_smile:

One thing also is that I might use it with clients.
Since there is not locking with the pro plan (maybe you should consider adding it too :slight_smile:) using the crossdoc be useful when sharing some datas with the client.
For example you can have a bug tracker document, where your client can report datas, and see what they need to see, while the big bug tracking thing can be in a separate document, just for you, and maybe a couple of freelance you are working with…

2 Likes

I’m curious what to-do list would be exceeding 1,000 rows :stuck_out_tongue:

@nathan Thank you very for the clarifications :grin: !

Thanks for the quick and thoughtful response, Jeremy. My template has more than 50 elements (it contains various tools/calculators, even though many get used only on occasion), so that alone is a paid feature. To complete the picture, it does not use packs at the moment and copies won’t reach more than 1000 rows very quickly (although I anticipate many will in a few months time).

And yes, I agree about that particular weakness of the model. My clients too would only be required to push a few buttons and add certain rows every week; as a matter of fact I generally would prefer it if that’s the only thing they could do (i.e. not mess up the architecture/layout).

Congats with Coda 2.0

Next to all comments shared so far, I would like to take the opportunity to address the following:

  • I don’t see a reference model offered, having in mind that the users that have experience with Coda are able to on board new users / clients
  • I don’t know in other parts of the world, also private users have to pay the Value Added Tax (VAT) on top of the bill. In my region it means +20%. Companies can get this money back.
  • For the docs I created to support colleagues in this community, I will be charged to use them, because of their size? Does this mean that I will need to create for every case a separate doc and get lost? `Hopeful you will consider to create a folder “free tier” for further support this community! It’s the way around also valid, all the members that have been giving me a helping hand, might…:frowning_face:

Please consider a free tier with sponsored content, as I understand as no other, you will need to make $$$$ to keep the :candle: burning and satisfy the VC’s :money_with_wings::money_with_wings::money_with_wings:

For the pricing structure and the benefits offered for each tier, I will need some more time to come with “Non emotional” , but grounded feedback!

8 Likes

Thanks for this feedback, Stefan. I’d like to hear more about your team needs so we can hopefully find a solution that works. I just sent an email through Intercom to follow up directly.

Easy example: My daily action list routinely includes 9 habits, 2 workouts, every meeting on my calendar, and every to-do on my work task list, not to mention critical due dates and milestones throughout the month. It’s the One List to Rule Them All. Oh, and I integrated it with a time tracker. Gets to 1000 rows pretty quickly…

2 Likes

I would also agree with a limited editor role. I created a check yourself In and Out doc trying to replace our ancient magnetic slide your button to in or out with a few columns to say where you have gone and when you will return using a dry erase board. So all of our staff would just need to push the buttons to check themselves in or out and update their time of return, date of return, and where they have gone. Having to pay for an editor role just to update their In and Out status seems like a lot. I would be fine if it was restricted to them only being able to edit their own information or not being able to add any more rows or only edit a limited number of columns or rows.

1 Like

Hey Codans, how about this suggestion: instead of setting up a limit on 1000 rows per doc stored, introduce a limit on the number of new rows per day/month (per doc or universally). Or the number of edits.

AFAIK storage is cheap, computations are not.

2 Likes

@Paul_Danyliuk Satisfactory band-aid to a larger problem, but would make things more palpable.