Comment by Lich | Hacker News Reader

Comment by Lich | Hacker News Reader

Parent Full thread

I'm currently working for an education startup right now. We are struggling. Have been for the past few years. The biggest problems I've noticed:

1. Cost. When you deal with school districts, you usually sell for X number of devices. So for example, all devices for 5th-7th grade, something like that. When you sell alot, schools will usually ask for volume licensing. Schools don't want to see prices above $5. This goes for devices for the quality of the devices they purchase. Often, the student device is cheap, low-powered, and in the case of Windows devices, packed to the brim with all sorts of software running in the background: web filters, virus-scanners, and some educational apps. Top that off with apps that students install like Spotify and games, it slows the machine down to a crawl or causes problems that might interfere with your software solution.

2. Different school districts have different needs. Although our software solution was initially meant to be for general use by all schools, we kept running into school district that needed very specific needs to that school or district. That lead to developing new features that only a small handful of school district would use, sometimes confusing users who did not need such features, or didn't even know we had the feature.

3. If your software solution works with student information systems data, it can often be a nightmare getting school districts to create that data.

4. School IT teams are...pretty terrible. Or rather, they're swamped with so many issues from so many products and devices, that they care very little as to learn how to deploy your product properly. Have documentation? Trust me, they probably won't read it. You will most likely get an e-mail asking how to deploy.

5. Trials, trials, trials. Schools aren't going to pay up just because they see a video demo of your product. They're going to want a trial at minimum for half the school year, maybe more. Then...

6. ...Politics. Decision to purchase needs to be approved by some board.

Coming from the grades 9-12 sysadmin side, I might be able to provide some perspective. Every school is wildly different, so I would recommend against applying my perspectives too broadly.

1. Cost: Windows licenses for student PCs are just under $20/PC/year (for us). Is your $5 software 25% as useful to students as their operating system is? Even worse, the reality is if I put your software on my 1000 computers I'll be lucky if 300 of them use it. That's something to keep in mind when working with per-device licenses. I agree installed system software bloat is a problem. That results from every department having different needs. We might be a little different in that we don't allow students to install/run foreign software (using AppLocker).

2. I agree different schools are amazingly different. I collaborate with a few other schools around me and whenever we meet I'm pretty floored by how differently each one approaches basic problems. These significant differences really add up and I can understand how supporting schools might be a pain.

3. It seems like every vendor wants access to my SIS. That's a privilege not granted lightly. I'm generally okay with automated CSV dumps of bare minimum data uploaded over a secure channel, but some vendors have the nerve to request direct LDAP or Oracle database access over the public Internet. No way!

4. I'll agree school IT teams are generally terrible. Among my peers and schools I collaborate with, I'm the only one with a degree in IT. Many are older and migrated to the role from something else (former math teachers surprisingly often). Some find themselves shoehorned into the role because they happened to be the most technically-inclined among the staff. These guys are uncomfortable in powershell/cmd and typically use contractors or local PFYs to handle technical details. Schools do not pay enough to attract decent talent. I could work for a local company and make 1.5-2x more doing less than I do here, but for now I like this environment.

5. While video demos can be helpful product overviews. I distrust video demos just as I distrust other marketing wank. I want to test drive the car before I decide to purchase it. That said, I wouldn't expect anyone to let me demo something longer than 60 days. The long time in my case is that exploring new software is usually a backburner project, and I am likely to have other things come up that take priority. I never put production data into trial software however.

6. Yes, purchasing processes are a pain. I 100% agree. I currently have a request for $60 of printer toner that's been sitting in the requisition process for over a week. Trust me, it's just as bad for us on the inside.

Thanks for providing your perspective! I've always wondered what it was like on your side.

1. I totally understand this. I've actually often wondered what a waste of funds it is when I see school districts purchase several hundred licenses of our product, but only a handful of teachers and students end up using it. I understand though that it's hard to just purchase the right amount of licenses, since you never know if another teacher/student down the line might want to start using it.

4. Yes, I've been to a few local schools for support and there's quite a few teachers who are handling the simpler IT side of things. From the IT staff that I've met in schools, I think I would like the environment too.

Reply on news.ycombinator.com