sirarthurtharp
New Member
The company I work for manages government forms. That is to say, government forms come into the office, are QA'd, sent to the appropriate government office, and checked.
The company has an internal software application to automate this. It is a combination of paid software and proprietary software. It does the following
1: Tracks documents (you put in the government office it is supposed to go to, the time it should arrive, and it will send you a notice to double-check to see if it did arrive)
2: Scans documents (you scan the document in, it will save it into a secure location)
3: Data entry of documents (you define a custom form that matches the government document, define it as a template, and then you can use that form as a data entry set when "real" versions of this form arrive)
4: Reporting (you can choose a type of government form and get outputs as to who and what these forms were used for)
They do not sell this software. They use this software. It is combination of purchased software (the scanning/tracking of documents) and internal software (data entry / reporting)
I'm planning on leaving the company, but I want to replicate this entire software platform (As a single unit) and sell it on the market. I don't intend to use ANY of the existing code, this is not a question of that. But because of my knowledge it may, by nature, be similar to the software that is written (since i was responsible for making some of those decisions).
For example
3: Data entry of documents. I built this entire piece. I plan to rewrite it from scratch, but several architectural decisions may wind up being similar. For example, the choice of language (C#) and database (SQL Server) and platform (ASP.NET). These will be similar because they are my knowledge set.
But there are dramatic changes to the process. For example, I intend to have the Track documents work off a mapping API and use the FedEx webservices to really track when it is complete (not just an arbitrary number). And I intend to have the scanning of documents being stored in the database. And I intend it to be a single application, not a combination of purchased software and inhouse software.
I do not intend to go into the same market as the company. I have no interest in managing a "government form processing" station. I simply want to sell software to this industry because I have a lot of knowledge in it (been working at this company for 10 years).
I imagine the answer is "it depends on what agreements you have signed". But is there anything they could enforce? I'm not leaving to a competitor. I'm not leaving to a client. I'm not selling in their market. I'm not stealing their IP (as it will all be rewritten).
But in some places it will be VERY similar - example, the Data Entry of Documents. They create templates in Dreamweaver and save them as HTML files) those HTML files are then stored in the database and pulled when they want to enter a specific government form. This is something I came up with. I intend to rewrite the storage, method etc from the ground up but the process will be the same in my software because it is the best answer to that challenge (dynamic forms).
Oh btw - I don't intend to do any of this work until after I've left the company.
Oye!
The company has an internal software application to automate this. It is a combination of paid software and proprietary software. It does the following
1: Tracks documents (you put in the government office it is supposed to go to, the time it should arrive, and it will send you a notice to double-check to see if it did arrive)
2: Scans documents (you scan the document in, it will save it into a secure location)
3: Data entry of documents (you define a custom form that matches the government document, define it as a template, and then you can use that form as a data entry set when "real" versions of this form arrive)
4: Reporting (you can choose a type of government form and get outputs as to who and what these forms were used for)
They do not sell this software. They use this software. It is combination of purchased software (the scanning/tracking of documents) and internal software (data entry / reporting)
I'm planning on leaving the company, but I want to replicate this entire software platform (As a single unit) and sell it on the market. I don't intend to use ANY of the existing code, this is not a question of that. But because of my knowledge it may, by nature, be similar to the software that is written (since i was responsible for making some of those decisions).
For example
3: Data entry of documents. I built this entire piece. I plan to rewrite it from scratch, but several architectural decisions may wind up being similar. For example, the choice of language (C#) and database (SQL Server) and platform (ASP.NET). These will be similar because they are my knowledge set.
But there are dramatic changes to the process. For example, I intend to have the Track documents work off a mapping API and use the FedEx webservices to really track when it is complete (not just an arbitrary number). And I intend to have the scanning of documents being stored in the database. And I intend it to be a single application, not a combination of purchased software and inhouse software.
I do not intend to go into the same market as the company. I have no interest in managing a "government form processing" station. I simply want to sell software to this industry because I have a lot of knowledge in it (been working at this company for 10 years).
I imagine the answer is "it depends on what agreements you have signed". But is there anything they could enforce? I'm not leaving to a competitor. I'm not leaving to a client. I'm not selling in their market. I'm not stealing their IP (as it will all be rewritten).
But in some places it will be VERY similar - example, the Data Entry of Documents. They create templates in Dreamweaver and save them as HTML files) those HTML files are then stored in the database and pulled when they want to enter a specific government form. This is something I came up with. I intend to rewrite the storage, method etc from the ground up but the process will be the same in my software because it is the best answer to that challenge (dynamic forms).
Oh btw - I don't intend to do any of this work until after I've left the company.
Oye!
Last edited: