Current client is exploring various support models for the application I'm currently working on. Some of the options are to use internal staff (lack of technical skill/codebase knowledge) or your usual large IT companies (offshore staff/codebase knowledge/massive cost) but both as I've mentioned in brackets have their downsides as well as the upsides.
Whilst wanting to move on to a new contract at the end of this one, it feels to me that there is an opportunity to tender for some aspect of the support work/bug fixes/enhancements after I've left which would be folly to pass up - especially if it could help build up a concurrent client portfolio.
I therefore wondered if people had successfully tendered for work like this in the past and what structure they found works best? I was initially thinking a small retainer just to cover logging in daily and checking issues, and then an agreed rate per issue handled/answered as well as an agreed daily rate for any bug fixes/enhancements that are required. The obvious downside from their angle would be no dedicated person on a phone should things fail (although that could be priced in if they really required it), but they would retain the services comparatively cheaply of someone with codebase knowledge.
Whilst wanting to move on to a new contract at the end of this one, it feels to me that there is an opportunity to tender for some aspect of the support work/bug fixes/enhancements after I've left which would be folly to pass up - especially if it could help build up a concurrent client portfolio.
I therefore wondered if people had successfully tendered for work like this in the past and what structure they found works best? I was initially thinking a small retainer just to cover logging in daily and checking issues, and then an agreed rate per issue handled/answered as well as an agreed daily rate for any bug fixes/enhancements that are required. The obvious downside from their angle would be no dedicated person on a phone should things fail (although that could be priced in if they really required it), but they would retain the services comparatively cheaply of someone with codebase knowledge.
Comment