[consulting] Proper Collections Procedure

[Larry Garfield]

On Wednesday 16 August 2006 10:51, Trevor Twining wrote:

> For all my clients I charge deployment separately from development. I
> don't release any code until the development project is completely
> signed off and paid for. Then I charge a nominal fee for deployment on
> outside servers. That way I maintain control over the product until I am
> compensated, and if they stiff me on deployment, I'm not out for the
> entire project.

I'm not an independent consultant currently, but I want to second the 
multi-stage billing.  Everything I've read or seen on the subject says that 
billing per-stage is critical, as it provides a milestone for you,  for the 
client, and for your wallet.

After the spec is finalized, there's a billing milestone.  Work does not 
continue until it's paid.

After the beta is released, there's a billing milestone.  Work does not 
continue until it's paid.

After the final release, there's a billing milestone.  Presumably if you got 
here, they're good for the money. :-)

What breakdown and milestones you use will depend on your situation, work 
process, clients, etc, but the concept itself is sound.  Bill in stages.

-- 
Larry Garfield			AIM: LOLG42
larry at garfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of 
exclusive property, it is the action of the thinking power called an idea, 
which an individual may exclusively possess as long as he keeps it to 
himself; but the moment it is divulged, it forces itself into the possession 
of every one, and the receiver cannot dispossess himself of it."  -- Thomas 
Jefferson