SheepCRM Standard Contract

Standard Sheep Contract

Contract

Between us Croftsware Ltd and you Client

Summary:

We will always do our best to fulfil your needs and meet your goals, but sometimes it’s best to have a few things written down so that we both know what’s what, who should do what and what happens if stuff goes wrong. In this contract you won’t find complicated legal terms or long passages of unreadable text. We have no desire to trick you into signing something that you might later regret. We do want what’s best for the safety of both parties, now and in the future.

In short

You (Client) are hiring us (Croftsware Ltd) located at 40 Barrington Close, Witney, OX28 5FL to develop a database solution for the price outlined in our accompanying correspondence. Of course it’s a little more complicated, but we’ll get to that.

What do both parties agree to do?

As our customer, you have the power and ability to enter into this contract on behalf of your company or organisation. You agree to provide us with everything that we’ll need to complete the project including spreadsheets, text, images and other information as and when we need it and in the format we ask for. You agree to review our work, provide feedback and approval in a timely manner too. Deadlines work two ways and you’ll also be bound by any dates that we set together. You also agree to stick to the payment schedule.

We have the experience and ability to perform the services you need from us and we will carry them out in a professional and timely manner. Along the way we will endeavour to meet all the deadlines set but we can’t be responsible for a missed launch date or a deadline if you have been late in supplying materials or have not approved or signed off our work on-time at any stage. On top of this we’ll also maintain the confidentiality of any information that you give us. 

Getting down to the nitty gritty

Browser Support

We will not test old or abandoned browsers, unless otherwise specified. If you need us to consider these older browsers, we will charge you at the daily rate set out in our original estimate for any necessary additional design work, development and testing.

Changes and revisions to bespoke development

We know from plenty of experience that fixed-price contracts are rarely beneficial to you, as they often limit you to your first idea about how something should look, or how it might work. We don’t want to limit either your options or your opportunities to change your mind.

The estimate/quotation prices from our proposal are based on the number of days that we estimate we’ll need to accomplish everything that you have told us you want to achieve. If you do want to change your mind, add extra pages or templates or even add new functionality, that won’t be a problem. You will be charged the daily rate set out in the estimate we gave you. Along the way we might ask you to put requests in writing so we can keep track of changes.

Technical support

We want you to be happy with your database and will provide you with all the support you should reasonably need to use the database. Email support requests to us and we’ll respond as quickly as we can (we work Monday to Friday 9.00 5.30 UK time).

Access to data

In the event of the contract being terminated, Croftsware will provide your data stored in the database in a standard format (CSV) for transferring into another system.

Legal stuff

We can’t guarantee that the functions contained in any web page templates or in a completed web site will always be error-free and so we can’t be liable to you or any third party for damages, including lost profits, lost savings or other incidental, consequential or special damages arising out of the operation of or inability to operate this web site and any other web pages, even if you have advised us of the possibilities of such damages.

If any provision of this agreement shall be unlawful, void, or for any reason unenforceable, then that provision shall be deemed severable from this agreement and shall not affect the validity and enforceability of any remaining provisions.

Phew.

Copyrights

You guarantee to us that any elements of text, graphics, photos, designs, trademarks, or other artwork that you provide us for inclusion in the web site are either owned by your good selves, or that you have permission to use them.

We love to show off our work and share what we have learned with other people, so we reserve the right to display and link to your completed project as part of our portfolio and to write about the project on web sites, in magazine articles and in books about web development.

Payments

We are sure you understand how important it is as a small business that you pay the invoices that we send you promptly. As we’re also sure you’ll want to stay friends, you agree to stick tight to the payment schedule outlined.

But where’s all the horrible small print?

Just like a parking ticket, you can’t transfer this contract to anyone else without our permission. This contract stays in place and need not be renewed. If for some reason one part of this contract becomes invalid or unenforceable, the remaining parts of it remain in place.

Although the language is simple, the intentions are serious and this contract is a legal document under exclusive jurisdiction of [English] courts. Oh and don’t forget those men with big dogs.

Everyone should sign above and keep a copy for their own records.

Contract adapted from the following: http://stuffandnonsense.co.uk/blog/about/contract_killer_the_next_ hit / http://24ways.org/2008/contract-killer

Company Details

SheepCRM is owned and operated by Croftsware Ltd incorporated in England.

Registered Address

40 Barrington Close, Witney, West Oxfordshire, OX28 5FL

Web

SheepCRM

Email

[email protected]

Phone

01993 764 323 / 07526 558900

Twitter

@jwebster

VAT Number

104 4603 57

Company Number

07423886

Payment Details

Bank

HSBC

Account Name

Croftsware Ltd

Sort Code

40 47 07

Account Number

8162 8380

Public Document

Number of times Signed
1
Number of Saves
0
Number of Downloads
579
Number of Views
1.8k

This is version 1, from 4 years ago.

Suggest changes by making a copy of this document. Learn more.

Create Branch

Originally branched from:

See Changes