Keen Muppets

[Clippy]

Agreed.

If the client does not automatically extend, make sure he is aware the door is open for him to call you when the sh11t inevitably hits the fan.

If the technology is as niche as you say, you may not have to wait long.

[sasguru]

So, how should I deal with this?

My current gig was to produce a prototype system using GeeWhizz (names changed to protect the innocent), then hand over development to a couple of internal devs. Prototype was produced, client happy, started to do the hand-over in good time before end of contract (4 weeks).

Problem is, the 2 permies here have no experience of the technology, and both are reasonably fresh devs. Both keen to learn, but I have no doubt that they will come a cropper something awful in 4 weeks. This isn’t some desperate vanity. I’ve 5 years experience in this reasonably niche technology, and 20 years dev.

What do I do?

I guess I should have said something at the start of the engagement, but I often find I’m a bit too keen . So, how do I tell the client that they will be tuliped if they don’t extend me? How do I sound like I’m not trying to hang them over a barrel? Or should I even try – perhaps I’ll just do my best and cross fingers.

My gut feel is that I should just tell the client now about the risk.

Been there more times than I count. You should say something - but the trick is to do it without sounding vindictive or grasping. You should praise the guys (sounds like they have enthusiasm). Don't mention an extension - it's up to the client to decide that.
By speaking you have behaved like a proper consultant, not a fly-by-night operator.

[AtW]

In which case you might want to increase your rates, CUK styley

[johhnysalad]

Before making the prototype you should have checked with the client that they have the skills among permies to take on full work IF prototype was successful.

They had already selected the technology, signed contracts (based on the technology), and attempted to reach the first contract milestone (which was a prototype). They saw the impending failure (and loss of first big invoice), and that's when they brought me in.

They already knew.

All I saw was extension

[AtW]

Before making the prototype you should have checked with the client that they have the skills among permies to take on full work IF prototype was successful.

[johhnysalad]

My gut feel is that I should just tell the client now about the risk.

Done. They had the first dry run at a deploy cycle today. It was pitiful. .

[johhnysalad]

So, how should I deal with this?

My current gig was to produce a prototype system using GeeWhizz (names changed to protect the innocent), then hand over development to a couple of internal devs. Prototype was produced, client happy, started to do the hand-over in good time before end of contract (4 weeks).

Problem is, the 2 permies here have no experience of the technology, and both are reasonably fresh devs. Both keen to learn, but I have no doubt that they will come a cropper something awful in 4 weeks. This isn’t some desperate vanity. I’ve 5 years experience in this reasonably niche technology, and 20 years dev.

What do I do?

I guess I should have said something at the start of the engagement, but I often find I’m a bit too keen . So, how do I tell the client that they will be tuliped if they don’t extend me? How do I sound like I’m not trying to hang them over a barrel? Or should I even try – perhaps I’ll just do my best and cross fingers.

My gut feel is that I should just tell the client now about the risk.