Changes to Requirements After Deployment

ve

How would you handle a client, if you delivered a web based application to spec, it was approved and paid for, then months later you get a call to say that it doesn't do what they need. The missing functionality IMO is core, but is based on a key piece of information that was not declared prior to this. The client appreciates the system was delivered to spec and that it was their fault that the piece of key information was not conveyed before. Now they need the system "upgraded" post haste, and are not expecting the cost to be too high, despite the fact that this upgrade will involve a significant redesign/development of core system components.

I want to give them value for money, but I am worried that they will crap their boots when they realise how much money their mistake will have cost them.

Am I being unreasonable?

p

No, it's perfectly reasonable. You can only do what they specc'd for you.

Stick to your guns, give them a fair rate for everyone involved.

louie

What's fair is fair so it totally depends on yourself.
Just be carefully in your decision...

mneylon

If they aren't willing to pay a fair price for your work, then there's not much point in dealing with them.

Remember - if you're doing an underpriced job for one client you won't be able to do a normally priced job for another, so don't sell yourself short. Be transparent about the costs - if they can't handle them, then maybe you're better off walking away

MOH

(Not speaking from any industry experience but) If you sell yourself short now what's to stop them coming back again later with another change request and expecting it done on the cheap?

And it might save them in the long run, if they realise now the true cost of the upgrade, they might take more time getting their core specs right in future and save themselves a costlier mistake down the road.

cngamemart

louie wrote: »

What's fair is fair so it totally depends on yourself.
Just be carefully in your decision...

totally agree with him,:)

is_that_so

Always difficult to call this one and it depends on the relationship with the client. However the client does need to be made aware of the cost involved both in monetary terms and development time.

A detailed "client-focused" explanation as to what it will cost, why it will cost that much and how the new requirement will affect the project may help smooth the path and but as others have said fair pay for a fair day's work.

_ZeeK_

It was their mistake, not yours.
They'll have to pay, not you.

smcelhinney

I would approach this on the basis of whether or not it is possible that you'll get
a) repeat work from the client
b) advocacy or referral to other potential clients

No point in shooting yourself in the foot either. If the functionality and the effort to introduce it far outweigh the ancillary benefits listed above, then charge the reasonable rate for it.

HTH.