[BNM] Response to tender

[Jay Caines-Gooby]

On 9/4/07, Patrick Heath <pat at i-tools.co.uk> wrote:
> Right so, you've been asked to tender for a website/application and you want
> to produce a response. What should a good tender document contain? Apart
> from the obvious, identifying the problem and providing a solution, what
> else should you include?

Have you been tipped the nod about the tender, or did it come out of the blue?

The unfortunate truth of tendering is that generally unless you have
some existing relationship with the tendering body or someone who
works there, you are probably making up the numbers.

My advice is don't spend too much time on the tender, price it
realistically, don't do any work for free and certainly don't show any
prototype designs unless you're very confident. If you get the work,
then you've won it fair and square, if you don't then at least you
know you haven't wasted too much time.

Government and public sector (and even large corporate) tenders are
normally accompanied by quite specific directions on how to respond.
Make sure you read these clearly.

-- 
Jay Caines-Gooby
jay at gooby.org
+44 (0)7956 182625
skype: jaygooby
gtalk: jaygooby at gmail.com
AIM: jaygooby