6 ms·
I am a professor in a CS department. * Easy: ask your dept for a job or RAship to continue to support and build the app and grow its utility. We pay students a
by abhv 4y ago
I am a professor in a CS department.
* Easy: ask your dept for a job or RAship to continue to support and build the app and grow its utility. We pay students all the time to build website infra for us in the cs dept. It is usually a ~20$/hr rate, though, so you won't make too much, but it will fund your improvements.
* If you built the app on your own laptop, and you've published the app to the app stores on your own account, you likely own all the rights. Good for you. If the app is hosted in anyway on university resources, then you should be careful if you want to grow this into a business.
* From my own experience, it is very difficult to sell to individual university departments. Much easier to get hired as a consultant. But "enterprise software" that is sold by a license may require the "university procurement" people to get involved. They will went some evidence you'll be around for 3-5yrs, etc...
* Look into how Piazza, Gradescope, Overleaf are doing with university-wide account sales. From what I know, those sales processes are slow and expensive, even though the apps bring enormous value to faculty (e.g., i end up paying for my own single accounts and expensing them against my research budget).
Use your network to find someone at those companies to do more research.
Good luck!
btw, happy to try your app and give you feedback
- jmathai 4y agoI’ve been through the university procurement process. My experience wasn’t too bad. There’s a bit of red tape but the folks who want your solution are probably willing to minimize the process as much as they can (though you’ll still need to complete it). I would also consider charging for non recurring engineering fees (sort of like consulting). Instead of $16/mo/user charge a few thousand $s for integration or custom development. Paying for labor is something companies understand very well.
- KyeRussell 4y agoThis is the first “boots on the ground” thing I learned being subject to a procurement process: if someone - or the right person - within an org wants your stuff, then you’ll be surprised how many on-paper “requirements” are able to just fall away.
- cldellow 4y agoOr they'll tell you the hidden requirements! I remember selling to a school board back in 2008. We wanted to issue them a bill with one line item: "Software, $100,000." Luckily, we had a champion inside who took us aside and gently proposed that we repackage it into several line items: site-wide licensing, installation support, training support, 1-year of tech support, custom development fee, etc. It tallied to the same amount, but looked a lot more "normal" for procurement purposes.
- KhoiUna 4y agoIt’s not a big app. I spent like 50+ hours making the app. So charging thousands is out of their budget.
- jmathai 4y agoDon't make the mistake of assuming the hours spent is correlated to the amount they will spend. I'm not saying they will spend thousands of dollars but you might be surprised how big their budgets are and the numbers they are used to.
- hazmazlaz 4y agoIt's not a factor of how long it took you to make it, but the value of it to the end user. If (in a contrived example) it took you 1 hour to create but saved the end user many hundreds of hours of expensive labor, it could be worth a great deal. Think about the output instead of the input when pricing your creation!
- tpoacher 4y agosome universities have a "developed using university resources" as an IP owning clause. this means if you coded this at your desk, even if on your "spare time", the university provided resources (the desk) and thus has a claim one your IP.