Hi all!
CommitCRM is set up to for us to be able to use CONTRACTS for managing PROJECTS - with the advantage that the contract then acts as the 'container' enabling us to group all TICKETS for this project by associating them with the particular contract. (See here)
However, what do we do when a project - as well as other work for the customer - is being paid for via a BLOCK OF TIME, i.e., some of this block of time will be used on the project and some will be used to pay for other work NOT related to this project?
What is 'best practice' in CommitCRM for handling this situation? As I understand CommitCRM now, we can set up a contract for a BLOCK OF TIME or for the PROJECT - but we can't do both or make one contract serve both purposes (because, remember, the block of time may be used on the project but also on other tasks).
An important related issue here is how the method(s) chosen here impact QB ie., we use QB Pro 2007 along with the QB Connector, so when you set out best practice per our question above, would you also flow through the impacts of using the approach you recommend, to QB and how it will impact recording of receipt and 'drawdown' of block of time funds?
I look forward to some help/wisdom on this one, as we come up the learning curve with shoehorning our biz into CommitCRM and VV:-)!
/dwv
David W. Vaughan
www.A-1techsupport.com
Wired: 305-672-4374
Skype: a1techsupport
Cell-Tech Emergencies: 786-200-6703
Making Technology Work
CommitCRM is set up to for us to be able to use CONTRACTS for managing PROJECTS - with the advantage that the contract then acts as the 'container' enabling us to group all TICKETS for this project by associating them with the particular contract. (See here)
However, what do we do when a project - as well as other work for the customer - is being paid for via a BLOCK OF TIME, i.e., some of this block of time will be used on the project and some will be used to pay for other work NOT related to this project?
What is 'best practice' in CommitCRM for handling this situation? As I understand CommitCRM now, we can set up a contract for a BLOCK OF TIME or for the PROJECT - but we can't do both or make one contract serve both purposes (because, remember, the block of time may be used on the project but also on other tasks).
An important related issue here is how the method(s) chosen here impact QB ie., we use QB Pro 2007 along with the QB Connector, so when you set out best practice per our question above, would you also flow through the impacts of using the approach you recommend, to QB and how it will impact recording of receipt and 'drawdown' of block of time funds?
I look forward to some help/wisdom on this one, as we come up the learning curve with shoehorning our biz into CommitCRM and VV:-)!
/dwv
David W. Vaughan
www.A-1techsupport.com
Wired: 305-672-4374
Skype: a1techsupport
Cell-Tech Emergencies: 786-200-6703
Making Technology Work
Comment