I have been working with QuickSchools for close to 8 years now. The journey has definitely been interesting, as I reflect back on our accomplishments over the years. Here’s what my journey has looked like so far:

Year 1 (2009-2010)

My first day at QuickSchools, we only have a handful of early adopters to our name, and I’m tasked with onboarding these schools. We launch the product in August, and hit the conference trail hard to try and get more customers, all the while looking at the market on what to develop next.

Year 2 (2010-2011)

With the help of our customers, we improve and release new features, like the Student and Parent Portals. We continue to hit the conference trail hard in search of new customers. Around this time, we hone our target market to smaller schools, and my role as Account Manager slowly evolves to Head of Support, which incorporates an element of Product Development (mainly because I spend a lot of time speaking with customers).

Year 3 (2011-2012)

We continue to see growth year-after-year. We open our new office in Sunnyvale CA. We start work on transitioning QuickSchools from Flash to HTML5. And we begin to focus less on conferences and more on online traffic. We transition our website to Weebly, we start split testing, and spend more on online marketing campaigns. We launch our “Teacher of the Year” marketing campaign.

Year 4 (2012-2013) – HTML5

The HTML5 version of QuickSchools is fully rolled out. We introduce In-screen Video Tutorials and Online Manuals to round off our offering. With HTML5, we become cross-browser compatible. In the spirit of improving our online reach to customers, we start work on our next initiative, which is our App Store and QuickSchools API.

Year 5 (2013-2014) – App Store / API

Our new App Store is officially launched, with some support for external / custom development. Schools can start developing their own apps using the QuickSchools API and Developer Console. We also launched support for additional languages (like Spanish), and basic support for group schools. We then started work on our next initiative to further expand our reach – Online Forms.

Year 6 (2014-2015) – Online Forms

We officially launch our first version of our Online Forms, designed mainly to support Online Registration. But the relative robustness of the module should allow it to be used in a variety of scenarios and use cases. We also continue to develop our App Store offering. Around this time, we started work on our next initiative, which is to move into the public school market.

Year 7 (2015-2016) – Public School Districts

We secure our first public school district, and begin work on bridging the gap between our private school modules and public school requirements. There are internal changes within the company to help support a more project-based implementation for this pilot roll-out. We roll-out our new support site to help organize documentation and support for the new district-related features. I transition into the role of Head of Engineering, while continuing to support the new Head of Support as he takes my place in that role.

Year 8 (2016-2017) – Stay the Course

The District Implementation goes into Year 2. We successfully build all basic features required to run a public school (including state reporting). Work now moves into cleaning up the modules, and making it ready for prime time. In addition to being Head of Engineering, I take on the role of Project Manager for the District Implementation. After going a full academic year with the district, we begin our sales initiative to acquire new districts for the next school year. And we start to develop our strategy for the 2017-2018 school year.

Year 9 should prove to be an interesting year, and I’m excited to see what the year has in store for me. Wish us luck!