How to Sell a DB

[speakers_86]

I am almost through with version 1.0 of my database, thanks to the help of the fine folks on this forum. Besides having it implemented at the place I work at now, I believe there is more that I can do with it. I think this db could be useful to other businesses in the same industry. What I dont know is how can I make it available to the other businesses. I guess I could start my own site and sell it myself. Or I could approach a software developer to purchase from me. Whats the best approach?

If I do decide to try and sell it myself, how could I get it packaged into an installer package? Ex., creating a desktop shortcut with the correct image, setting the trust in access so that the code will run, etc.

I'm no professional, and this is my first db, so how could I have this checked to make sure that it is ready for distribution? There are certain things that I have not addressed yet like error handling and archiving. So I would definitely need a pro's help.

 

[gemma-the-husky]

the main thing is, is that if you have built a database on works time, for work, most likely it belongs to your employer, not you

secondly, it is often the case that the development for your current employer will be tailored to their requirements, and will not include some more general or specific things that other users may require.

it realy depends what sort of app it is. if it is large and complicated, most likely it will cost a lot, and you will need to install it yourself, and have some sort of maintenance mechanism in hand.

if its small, cheap and cheerful, then you won't want to do that, but its hard to make something that is robust and reliable, and doesn't need any management from time to time. - especially as you would want to turn it into an mde, to prevent your users copying it etc.

 

[irish634]

If you work for a large corporation, be careful. It is highly likely that you signed an NDA (Non-disclosure agreement) when you were hired which prevents you from doing this if they can prove you developed even one line of the database at work or on a work computer.

Usually, anything developed for work (in cases like yours) is owned by the company you work for.

I would do your homework to make sure you are ok to do this.

Good luck

 

[speakers_86]

I work for a small business that my dad owns. So not much concern there.

As far as this being tailored for us, I would imagine that most companies in our industry have very similar needs, if not identical.

 

[gemma-the-husky]

good luck

i think the biggest difficulty is making it 100% resilient - because you need to support anythying that goes wrong - and its very hard not to have things go wrong

 

[Rabbie]

good luck

i think the biggest difficulty is making it 100% resilient - because you need to support anythying that goes wrong - and its very hard not to have things go wrong

If only because users can be very ingenious in what they do

 

[Mike375]

I work for a small business that my dad owns. So not much concern there.

As far as this being tailored for us, I would imagine that most companies in our industry have very similar needs, if not identical.

Quite a few that I do are for people selling insurance. From a data base point of view their activities are all identical. But I can tell you that not one of these data bases are the same. Certainly the "core" is the same but then lots of differences.

In my opinion it all comes down to how much you charge. You are either selling something that is like an "off the shelf" product and for a low price and hence people will put up with it not being exactly what they want or you charge a lot more and then it becomes a customised data base. In my opinion the latter is the way to go because even if you make an el cheapo you will still get calls from the people. The buyers know that it is much easier to call you than something like Microsoft etc and they also expect more.

Initially you need to spend a lot of time until you eventually have most variations made or at least close to anything that will be required.

i think the biggest difficulty is making it 100% resilient - because you need to support anythying that goes wrong - and its very hard not to have things go wrong

So true

and one of the reasons being

If only because users can be very ingenious in what they do

 

[speakers_86]

Cant really argue with that.

Ill keep working on it though. Either way it looks very promising.

 

[speakers_86]

Okay, version 2.0 is now installed at the office I work at. I guess I can clue you guys in now, the db is made for the emergency restoration industry. Basically, if your home floods, or catches fire, or anything catastrophic like that, any company that does that work may like this db. Companies like this are Serv-Pro and Paul Davis Restoration. The one I work for is a local one in Florida. It seems to me like the most popular software on the market is called ESC. My company used to use it, but stoped for whatever reason (my dad has ADD!, who knows why we stoped).

Anyway, I have this program that looks very good, and I dont really know what to do with it. When I go and open my own business, I'll probably use Chaos (thats what I called it). But, in the mean time, I would love to be able to make some money off of all the hard work I put into this. What I may do is market it to our local competitors. My dad told me there is one around us that doesnt have any computer system, maybe he will like it.

If you guys have any suggesstions, feel free to share.