Job Numbers and Job and Data Tracking
Question:
What is (in your opinion) the best practice for keeping a single location for data, but still having different billing numbers? Do you find your billing software drives your choices in this?
Explanation:
In the world described below, 10 job numbers are needed, because billing and time must be tracked and it is the fuel that keeps us going.
Also, submittals and communications need to be in different silos.
But the data gets spread out. This seems to be a problem for any company I have been at or talked to that has more than 5 employees.
Example:
Dreamer #1 buys X property, pays us to topo it and do preliminary feasibility
Dreamer #2 picks up the pieces of X after D#1 goes bankrupt and pays us to bring it to pre-plat
Investor #1 buys from D#2 for pennies on the dollar after the economy goes to crap
Investor #2 buys from I#2 and moves to final plat
Investor #3 buys from bank after I#2 goes bankrupt and gets the permits and final plat submitted, and hires a contractor.
Contractor #1 hires us to do construction staking (we are still working for I#3 on final plat comments, etc.)
Contractor #2 takes over after C#1 demonstrates that they cannot do the work, and hire us.
Home builder #1, #2, and #3 buys the lots after the plat and permits are complete, and hire us to stake foundations.
(One project I have has splintered into projects for three different entities, which is pretty common. So this can multiply.)
Log in to reply.