In replying, at least I can say I built my own house. Not the Taj Mahal, but just under 3,000 sq ft 2 storey, all brick. I contracted everything that I didn't do myself. Only things I didn't do were pouring footings (I laid out and constructed the forms), didn't do foundation walls, rough in plumbing, septic bed or roof. Everything else I had a hand in or did myself (I did complete wiring, fixtures, doors, trim, flooring, windows/doors installation except for garage doors). Even constructed under garage 10,000 gal cistern and formed for the garage slab over it.
So I cannot imagine where you could ever be successful as a contractor while taking the time to
a) develop such a db in the first place, even if you had db design experience, which it seems you don't
b) populate and update all the data this would need according to your stated goal
c) maintain and modify said db according to the changes in building codes, or variations in such codes from one locale to another,
- variations in brick size (no such thing as a uniform size) or in other materials
- addition, removal of materials from the market
- material take-off variations caused by options (size/amount of rebar or other embedded material or structures alters the volume of concrete for a pour)
d) I could go on and on.
The point has already been made regarding sub contractors doing the estimating for their portion and I agree 158%. Then the customer...what will your db do for you when they say, "Ya know, we really think that wall needs to be moved, and that doorway is too small." My sincere advice is to forget your idea. Besides, if you need to do any of your own estimating, there are already lots of tools to calculate stud/joist/insulation bundles/shingles, etc required. You add a contingency factor and then your profit on top of that. You would spend WAY too much time playing around with something that will only distract from job 1 - keeping on top of your business by being out in the field ensuring suppliers and subs don't screw up.
EDIT: at most, a spreadsheet since I don't see how a database would be as useful as a spreadsheet. Of course, you do want to control costs, and accumulating/summarizing/totaling/averaging/etc. expenditures is a job for a spreadsheet.
Last edited by Micron; 09-27-2018 at 08:09 PM.
Reason: spelin and gramur
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.