• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Offered short contract based on deliverables"

Collapse

  • WordIsBond
    replied
    Pretty simple. Get clear specs on what is to be delivered, including testing specs as noted. Estimate the time it will take you. Bid a cost.

    You take on the risk of time overruns, etc. Bid high accordingly -- enough to cover overruns of at least 10%, PLUS compensation for the risk, say another 10%. After that, it depends on how precise the specs are and how confident you are in your estimate of how long the job will take. If there is any imprecision in the specs, or you aren't confident, bid higher. And the bigger the job, the more uncertainties.

    It's just one more risk to build into what you charge. When you decide to be a contractor instead of an employee, risk is part of the game anyway, and you are paid extra for the risk of not being a permie. If someone is afraid of this risk, I'd wonder why they want to be a contractor. But if someone doesn't CHARGE for taking on the risk, I'd say he's not much of a businessman. Any client who wants you to absorb the risk should expect to pay for that.

    Also, watch your cash flow. If it is a four week job, bid it at five weeks to protect you from overruns. If it really does take five weeks, you break even and all is good, right? But will you run out out of cash before you get paid? You are probably only paid when the job is completed. If this is a problem, perhaps you can schedule an intermediate deliverable, specific targets which, when achieved, allow you to invoice half or a third of the cost.

    Leave a comment:


  • d000hg
    replied
    Originally posted by Contreras View Post
    Contract on defined deliverables, eh?

    Is that something 'real businesses' do?
    Yes, all the time.

    Leave a comment:


  • Antman
    replied
    It's a great IR35 defence (even if it's only a 4 week contract ).

    Like the others have said, if you can get acceptance criteria nailed down then you're safe and some way for handling the inevitable CRs, could also do another 9-5 somewhere else at the same time - ker-ching!

    Leave a comment:


  • Contreras
    replied
    Contract on defined deliverables, eh?

    Is that something 'real businesses' do?

    Run for the hills?

    hmm...

    Leave a comment:


  • vadhert
    replied
    Run like the wind.

    Sounds like someone left behind a load of tulip for you to sort out in a short time.

    Leave a comment:


  • yasockie
    replied
    I still wouldn't take it and propose to bill for the time and materials on daily rate.
    In 4 weeks requirements can change a lot.

    Leave a comment:


  • BlasterBates
    replied
    Delivery only with an Acceptance test specification which defines the outputs of your "bit".

    You need the acceptance test before you implement. They need to sign off on the acceptance test spec.

    Then it's water tight.

    It shouldn't take more than a couple of hours to define one when you sit down with the customer.

    General specifications are great but open to interpretation "oh I meant this" Test specs don't lie.

    If you find the test spec becoming unwieldy and larger and larger you know you have a badly scoped project.
    Last edited by BlasterBates; 13 July 2015, 14:05.

    Leave a comment:


  • northernladuk
    replied
    Make sure the criteria for signing that deliverable off is watertight so the client can't refuse to pay because in their opinion the deliverable isn't complete.

    Leave a comment:


  • cojak
    replied
    Also insist within the contract on a review of pricing should they want to change that 'finalised' specification.

    Leave a comment:


  • eek
    replied
    Originally posted by JuanSheet View Post
    Hello All,

    I have been offered a short contract that's based on deliverables. It's about 4 weeks long to join a development of a website halfway through.I have said I will need to do an assessment of what's been done before committing to any timescales.

    Has anyone else had one of these contracts? Pitfalls...

    Thanks for listening
    • Do they have a finalised specification?
    • can you do a gap analysis of what is missing?
    • is pay purely dependent on what you are deliverying or would you be dependent on the output of others?
    • Does the fee cover enough to make up for the risk of 4 weeks work without pay? (Most consultancies add a 50-200% premium for fixed rate work if they accept such work, many outright refuse)..

    Leave a comment:


  • JuanSheet
    started a topic Offered short contract based on deliverables

    Offered short contract based on deliverables

    Hello All,

    I have been offered a short contract that's based on deliverables. It's about 4 weeks long to join a development of a website halfway through.I have said I will need to do an assessment of what's been done before committing to any timescales.

    Has anyone else had one of these contracts? Pitfalls...

    Thanks for listening

Working...
X