Thanks for your interest in blogging for the Customer Education blog. We love connecting with customer education professionals and writers who can help us fulfill our mission to:
Be the global leading source of information for software leaders seeking ways to use customer education to help customers learn and adopt software in order to achieve their desired outcomes. To offer entertaining, educational, and effective information that software leaders can put into practice right away.
Why should I write for the Customer Education Blog?
Blogging for the Customer Education Blog may help you build your reputation as a leading authority in customer education, software adoption, and customer success. It may also help you in your work as a software leader because writing for others can help you think deeply about your profession and challenge you to try new things and share what you have learned.
Plus, our community is an open, friendly, and knowledge thirsty bunch who likes to help one another.
Customer education leaders at early to mid-stage enterprise software companies or software professionals who aspire to grow a career in customer education at an enterprise software company.
In general, we are looking for posts around these categories, as they related to starting, building, growing, and operating and customer education function and/or otherwise any topic related to how we can help customers learn how to use the software we sell so they can achieve desired outcomes in their business.
Part of our mission is to create entertaining AND educational resources that people can put to use. In order to increase your chances of having your submission accepted, make sure your post includes at least some of the following:
Have any questions? We want your post to be successful.
Your bio should be approximately 60 words and should include links to your appropriate social profiles and/or website, as well as any other relevant links you wish to display. This is a great place to include any promotional or gated links as we generally don’t allow them in the body copy.