<prompt> Human: First Time Poster,I am a supervisor in a call center of 100 employees for an online company. I have been working outside normal duties for over a year on a side project that tracks calls automatically, instantly pulls up call scripting, and also creates standardized notes with a click of a button. the tool has made its rounds to where basically the entire company uses it including the Training Department for new hires.I was Employee of the Year for 2016 and I initially created the tool as an innovation to get into upper management. After having an interview in December for a Management position, I was told they decided to hire from outside the company. Fast Forward to now, I approached the Call Center Manager about some updates to the tool and he said he said they are ready for the transition to take it off my hands so I can continue with my focus on being a supervisor and that he wants to do something Awesome for me. He stated he wasnt creative and his idea of giving is always just cash. I programmed the tool in Javascript, Html, and CSS and worked about 250 hours on it not including the designing phase.I worked on and off company hours but was never told to physically work on it.Its hard to find a programmer for under 25 an hour to even just program what I created and by my math 25 x 250 6250. I have a feeling that him doing something awesome would be a 100 giftcard of some sort or taking me out to lunch. The tool is on a server and if I wanted to I could unplug it right now and no one would have access to it. My question is whats the best approach to try to negotiate to give this to them because I initially created it as a package deal with me going into management. Thanks and sorry for the sloppy writing, my brain is a little frazzled.TLDR; Spent 250 Hours creating a tool the entire company uses now and Management wants to do something awesome for me and take it off my hands. Should I try to negotiate and if so how?UPDATE I appreciate everyones comments. What I take away from this is to not look at it from a negotiations standpoint. I worked on the tool partially during company time and so the best course of action is to document how to use the tool over 200 pages of code and try to shift into a role where I can develop internal tools and maintain others that I have already created. Thanks again for everyones advice.Assistant: How much maintenance does it take to maintain? I would document everything on how it works, which modules do what, and how to maintain it. From my experience that should be a nice sized document. Hand that over and see if the size changes their minds after you go over it. In my experience in IT, you keep doing it. However thats if you want to keep that job and I would reconsider if thats your opinion. How much do you enjoy programming? Not only do you know JavaScript, CSS and HTML, but you have developed, tested, deployed and maintained a program completely yourself in a real environment and saved the company X amount of time, which equals dollars saved. You have completed the sdlc cycle up to shutting it down and migrating away to the next thingwhich they may be doing so its something they can manage using a backend gui. I would say could could easily earn 40hr right now without to much trouble. Put a resume out there and see what you get for offers and have that as backup for incase things take a weird turn. Your boss may be giving you a promotion or a big cash payoff for helping so much. You never know, so dont slam the door untill you hear their planoffer. Human: I like how you talk about documenting how everything works into a nice sized document. The actual program itself is over 200 pages long with over 14,000 lines of codeAssistant: 14,000 lines of amateur Javascript. As a developer, Oh HELL yes Id do everything I could to make sure you got the joy of continuing to maintain this beast.Human: It sounds really funny when you talk about it. When you say amateur Javascript how many lines do you think it would take a developer?  <response>: Im going to guess a lot less than 14,000! Im being 50 tounge-in-cheek and 50 snarky. It could be great code but Im imagining a snarled mess of spaghetti callbacks, no discernible structure, manual DOM manipulation, etc... Basically, just every code smell in the book.Whatever you decide to do regarding the company, keep a copy of this code for your own viewing pleasure. If you continue learning and writing code, be sure to revisit and review the code in 6 months to a year. Youll ask yourself, what idiot wrote this crap?! Ive been slinging code for 20 years and still regularly find myself looking at some bit of code and wondering the same thing. Then I look in the version control logs and say, oh...I did, about 6 months ago. 