contracts

[Chilly]

So I'm in the part time contract programming game and I'm getting to the stage where the money and time involved are significant and it's no longer sensible to wing it with regards to contracts of work and support etc.

I'm referring specifically to support contracts. If I carry out a piece of work, which the client and I both agree on and agree to a list of key requirements and implementation choices, how far am I obliged to support that work? Once I've fulfilled the requirements and the client has signed off, I assume I am zero obligation to the client and the project? I'm not having any problems atm or anything, just curious that if or when this kind of thing happens (perhaps the client is a cock - or he doesnt like me, or whatever) I know where I stand.

Who else is in the game and does this kinda thing on the regular?

 

[rynnor]

Ideally this should be written in to the original contract that you'll agree to do maintenance/updates at £X per days work or fraction thereof.

Alternatively you can set a flat maintenance rate but make sure you dont end up out of pocket and make it clear that any changes/new features must all be paid for seperately.

Its always a good idea to offer this service as it keeps clients sweet but also more importantly they are more likely to dump poorly supported software and finally its often a major source of income

I would talk to your clients and offer them a maintenance contract.

 

[Tom]

Bear in mind that paperwork can often start arguments. I find that when people ask me to sign contracts, they tend to be arsey and anal about everything. Its rare that I do.

If a client asks you to do something outside your contract, don't immediately presume to charge them for it. Think about that client, the amount of work they'd like you to do outside the contract, and if offering that service as a favour will get you more work. Oh and people don't like it when they see inexpensive things itemised on an invoice (like when your car is serviced and they charge you £0.05 for a washer). If you supply them with a £2 cable, you don't need to put it on your invoice, some things you can absorb.

If they're a load of ***** though, fuck em and charge them whatever you like.

 

[RandomBastard]

I work for a small software house (well ish 4 full time employees including me but currently 34 students working here as well... for free... mmm slave labour) and we will often do small maintenance work for free in order to keep our client happy. But for major stuff we do require them to sign a maintenance agreement which is usually x amount for x days of support and maintenance.

I do agree with rynnor though, make it clear that extra features are not part of any maintenance agreement, free or otherwise, unless you're being duly compensated by said agreement.

 

[lecter]

Chilly you numpty for this sort of thing you should ask me.

There are two ways of doing support that are pretty much standard within industry. I would personally give them the option of either when negotiating.

a) 15% of the initial price yearly for support
b) Time and materials: at the same daily rate you charged for the project, pro rated for the length of time, with a minimum call out time.

 

[Milkshake]

The one time I did do some contracting stuff was through a friend - and that was a bit of a nightmare. I didn't get things written down, and it was difficult to go back to her and explain that the changes she wanted were entirely different features.

On another note - and apologies for a slight hijack Dave - but do any of you people need to outsource any work/need another set of hands? I'm a Software Engineering graduate (Masters no less) and I'm now working in a sysadmin/source control policeman admin type role - but I wouldn't mind keeping my hand in with a bit of development (can't decide if sysadmin is really my thing).

 

[Chilly]

Cheers for the intel guys, some useful stuff.

Milkshake: I'll keep an eye out, not impossible I'll have stuff to put your way.