Printable View
I will make an accountancy software which will write/read datas to/from MySQL DB. It will only use one table and will make some mathematical count with these datas. For example it will count the taxes etc...
How much price shall I demand for such a software's source codes? ( user will get all codes for the software)
and
How much price shall I demand for such a software's setup? ( user will only have the compiled version and a serial key for the software)
erm well it depends how good the software is, your best bet would be to get a beta tester to test it all for you and ask them how much they would pay for it.
Moved.
Depends.
What will it do?
How much support can I expect?
An accounting package that uses a single table can't be very vigorous.
it will use MySQL database and it will make some counts. Maybe more if costumer wants. I will check errors and give them with a messagebox.
what do you think?
One of the first rules of marketing is to know your competition.
What does your software package do that other accouting software packages does not do?
What do comparible accounting software packages sell for?
Why should I buy yours instead of someone else's?
you are right but my costumer is my friend so he wants from me software wnd he will exactly tell me what he wants. So he wants a special software I havent spoken with him but i think it will be a simple software. 1 more thing software will check some conditions for datas, which has been read from database.
??
In this case I think it would be... price...Quote:
Originally Posted by Hack
Genom, how much time did you spend on it ?
And if you did not start on it yet, then tell the person that you will work for say $30 per hour, and you will give him/her an approximate of total time. This way your customer will have an idea on how much it will be, and when it's all done, you can charge him/her accordingly by how much time you spent on it...
That would depend on who I am. If I'm a "mom and pop" whatever store that currently does accounting via yellowed lined pad and paper then perhaps price would be a consideration.Quote:
Originally Posted by CVMichael
For a budget package perhaps but people will still be looking for a functionality first.Quote:
Originally Posted by CVMichael
I have been envolved in the software evaluation more than once and these are basically how you do it:
- you're looking for the best with no budget limitation
- you're looking to buy for a moderate price but it must offer most of functionality from the best category
- you're looking for cheap temporary solution but it must do (or be very close) what you need
You do research and fill every group with 5-6 packages. Then you try to get a demo ... and so and so forth ...
I also share Al's sentiments about accounting package having only one table... It just doesn't sound right at all.
They will drive you nuts for $100 package ... ;)Quote:
Originally Posted by Hack
Sorry about my bad english but I havent understood your sentence...Quote:
Originally Posted by RhinoBull
and thanks for your help. I will use these tips in my professional projects which I will begin this year I think...
Well, an accounting software package is usually complex program (or even system if you will) that cannot be based on the database containg only one data table - the number of tables required to write more or less comprehensive application could be anywhere from a dozen (or two) to a few hundred.Quote:
Originally Posted by Genom
A decent database design will have just one table only if there is just 'simple' data to store, and there is no repeating of data. (apart from a Data Warehouse, which is not relevant to you!)
By using a single table for anything more complex (you almost certainly will in this case) you make the program much more awkward to write/modify, more prone to error, and probably harder to use too.
See this article on Normalisation for an explanation of the "proper" method.
:lol: :lol: :lol: :lol: :lol: I see you have been there as well! :lol:Quote:
Originally Posted by RhinoBull
I don't think normalization is as important anymore - it does take care of redundancy but that's about it...
However, you may need to have a dozen or so what I call "look-up" tables for country/state/city/zip codes - just to make sure you're applying correct taxes... Not to mention that those tables along need to be part of some financial service that supplies with such information. There is lots of other information that needs to be stored in your other config/look-up tables - you name it...
So, how can one design such package with only one table remains a mystery to me. Someone must be a Genius I guess. :)
I have understood now what you tell but my friend told me that it is enough to save datas to one table. I think it is true because he hasnt a company or a business. He needs something simpe. I have seen some accounting softwares which were complex and very detailed. It's price was more then 1000 $. But I tink that 80$ is enough for my application. If you are interested in I can tell the functions of the software, when I talk with my friend?
You want to see the customer name, address, etc., for every ledger entry?Quote:
Originally Posted by RhinoBull
And keeping the program in line with the country's accounting standards is a must - outputs from programs that don't adhere to the standards will not be used by accountants, and government tax offices won't look at them, so you'll have to rewrite the books every year into a form that can be used.
Al,
you don't have to explain the basics to me - notrmalization is one way of doing things and by far not the best (it was perhaps 10 years ago).
I have system comprised of 100+ tables which are normalized upto 4th normal form I think - it's almost unmanageable.
We are in process of redesigning the entire thing and will definitely flatten database down for more simple processing and maintenance.
Second normal form is ok but beyond that it becomes really disgusting and stupid - especially when you need to write endless joins...
We aren't saying that Genom should go to extremes, just that a degree of normalisation (in addition to lookup tables) is a good thing... that may simply be having a 'Customer' table in addition to the 'main' table, or it may mean having 10+ tables... it all depends on the data requirements.
yes si_the_geek this is exactly what I think actually I won't need more then 10 tables. and it would be very hard to use and server would be very slow
10 tables? I doubt very much. Think of some "right off the shelf" software like "Quick Books" - nice an lovely interface and tons of ready-to-go functionality (even printing checks included). And you can have all that for about $40 US. Can you match it with only 10 tables? I seriously doubt.
Good luck anyway. :wave:
Have you looked at or tried MS Small Business Acounting 2006? Its very powerful and only $79.99
http://www.bestbuy.com/site/olspage....&ref=16&loc=01
Its very hard to create your own product when the competition is so powerful and yet priced so inexpensive. ;)
Nice package and you can even get it cheaper:
http://www.amazon.com/exec/obidos/AS...sim/3147335-20
I just installed it over the weekend and its really nice. Great dashboard, reports, templates, integration with other office apps etc. I wouldnt be able to compete with it at all. Its going to take a piece of the market from Quick Books. QB sucks and its tech supports sucks too as its all routed to India. :mad: I'm glad I dont have to support it anymore at any client locations :D
Genom...Quote:
Originally Posted by Genom
Forget everything everyone has said in this post :D
If you think that you can get $80 or $100 from someone to write some code that they might find useful...
And you think that is enough money to give your time and effort...
Then it's worth it's price in gold - getting the experience of working with a user - putting a simple application together - debugging it - modifying it - that had great value to you.
Do it for free if you need the experience!!
I agree but it's a whole another topic... :)Quote:
Originally Posted by RobDog888
I agree but mostly was pointing out how feirce the competition is that he would be up against. Allot of big name software companies have their own accounting software that is really cheap and of high quality.
But as Steve posted, if you can do all that work and it be justifiable to spend all that time on then by all means do it. It may pay off in other respects with that client with other jobs etc. :)
Genom, if you really want to build a good accounting software then you should start with the core... general ledger (and inventory, prioritize, if business deals with product sale or assembly). Then just build the other modules around the core. The design should be very modular and flexible. Otherwise when conditions change (eg. new taxes) and you hardcoded everything then you'd obviously run into problems updating the software and the client will realize he paid too much.
A single table accounting software is no good. The client would be better off just maintaining an Excel spreadsheet (which has rows and cols just like a table).
If you look at the competition like previously suggested, you can see what features they offer so you can offer some othe the same ones and get an idea of whats good/popular. ;)