First, we are officially launching the beta version of our calendar to our trusted CoPilots We are looking forward to getting some early feedback. If you remember from this post about beta software, that puts our development timeline right on track.

Second, we’ve made some revisions to that timeline, and are now waist-deep in code to help you manage your writing team and your internal assignments. This is just another example of how our goals have changed based on the feedback that we have been hearing from early adopters like you. We really appreciate you following along as we build a better editorial calendar.

Third, we are getting ready for launch. Wow, it seems crazy to be talking about such things, but we are almost there! Internally, we are counting down, and we have no intentions of missing our deadline. This means that we are starting to discuss pricing and purchasing options, as well as putting together a brand new CoSchedule website.

Yay!

How about beta?

Some of you have been asking about beta access to the calendar. Currently, we are reserving beta access for our CoPilots so that we can communicate with them quickly and push out changes/bug fixes in a speedy manner. By keeping the beta field focused on a select few, we think we will end up being more efficient, and more likely to launch on time. This doesn’t mean that we won’t consider a public beta in the future, it just means that we haven’t decided yet.

Ha!

Seriously though, it is all part of the big goal, which is to solve the major headaches that come with creating and managing an editorial calendar. Every day, we are made more and more aware of the need for this sort of thing. For example, did you know that the current most popular editorial calendar plugin has at least 39 uses of the word ‘hack’ embedded in its source code?

Needless to say, we’re itching for a new editorial workflow, and we’re pretty sure that you are too.