The projects in this section use the skills you've
| 1) |
Identify what audience you need to
|
| 2) |
Identify on-line promotional activities. Is it necessary to play the search engine
|
| 3) | Identify linking options. Are shared linking options available? How will you utilize paid banner advertisement? |
| 4) | Consider measurement options for your effort. What information will you retrieve from server logs? What information will be captured to profile end users? |
We have always known that heedless self-interest was bad morals; we know now that it is bad economics.
-Franklin Delano Roosevelt
The objective of this chapter is to provide you with enough information to know that laws do apply to activities on the Web and to know that even common situations may have significant legal implications. Most of the situations discussed in this chapter are based on U.S. law, although international laws apply. International law is a complex area outside the scope of this book.
This chapter is not intended as a substitute for legal advice, nor does it contain professional legal advice. An attorney is best suited to respond to the specific circumstances of your situation.
Legality and illegality are based on the specifics of each unique situation combined with federal, state, and local laws and regulations and current case law. Do not hesitate to go to an attorney, and the earlier in the situation, the better. A good attorney prefers to practice preventative law rather than trying to practice much more expensive damage control in a courtroom. If your target audience is outside of the United States, select a law firm with expertise and experience in the laws of that country.
Before you dive eagerly into your
A contract is the basic building block of business relationships. Fortunately or
We are aware that we are making a contract.
We know the rules that apply.
We understand the negotiation process.
If everything goes well, then the contract is just a piece of paper (or several!) with signatures on it. If things do not go well, or if a question arises during the course of implementation or paying for the service, then the contract is extremely useful (or should be). A written contract is more effective for obvious reasons ("I never agreed to that! "), and is highly recommended. In general, very few businesspeople object to contracts because they know that contracts usually prevent more misunderstandings than they cause, and a good fair contract protects all the parties. Of course, signing a contract will not make an honest person out of a dishonest one, but it can describe the penalties, or "remedies," if the terms and conditions ("t's and c's") of the contract are not met.
Often, the process of documenting the "deal" in the contract is extremely useful by itself. This is where everyone's assumptions should be described and examined. This documentation process helps eliminate many points of confusion that could become nasty
At a minimum, a Web development contract should describe
Who has ownership, and when the ownership transfers
What is to be accomplished
Who is responsible for doing what
The time frame, or time
frames The price and terms of payment
With everything "out on the table," the parties should have a clearer understanding about what is going to happen and what is expected of everyone. There should be less confusion and more cooperation. The key is to agree on the terms and conditions. If there is something you do not like about an aspect of the deal, discuss it and negotiate something with which you can agree. Or walk away.
Traditionally, a contract is defined as an agreement among two or more parties, who know each other, and who promise to perform a transaction with each other. This is
A contract is comprised of three basic elements. If one of the elements is missing, then there is no contract. If all of the elements are in place, we have a contract.
You participate in contracts all the time, as an offeree or an offeror. The process is so well established in our world that we participate without even being aware that we have made and executed a contract. For example, you go to a computer store to shop for a new printer for your office. The store is making thousands of offers, constantly, by
Suppose that you find the exact printer that you want at the store, but the price is too high and the only one left in stock is the one on display. So you take the "floor sample" printer to the salesperson and make an offer to purchase that specific printer at a price lower than the posted purchase price. When you do that, you have exchanged roles with the store. You have become the offeror (by offering to purchase the printer at a price lower than the posted price) and the store has become the offeree. If the store clerk accepts your offer by agreeing to accept the lower price, you give the clerk your credit card; you sign the sales slip at the agreed-upon price; and you leave with your new printer. The transaction is completed. The store
A contract does not have to be in writing to be a contract. There is such a thing as verbal contract, but it is usually much harder to enforce than a written contract.
Frequently, you sign some kind of slip of paper as you complete a transaction (like the credit card charge slip). That's a contract, or part of it! Often, you don't even notice the contract and its terms and conditions because they are such a common part of your daily life.
Some contracts are more noticeable than others. The contract is painfully obvious when you buy a house (tons of paperwork and lots of
The contract is also obvious, and usually much less intimidating, with the apartment lease-what
There are some requirements associated with contracts, to make them enforceable by a
When beginning any type of business relationship with a client or vendor, the project and financial arrangements are usually informally discussed first. But it's a good idea to begin formal negotiations over a contract as soon as possible. In the hype and vapor world of Internet communication, discussing what, when, and how much is a very good idea. And since anything is possible using this communications method, defining projects and responsibilities is very important.
Once you've begun developing a new situation with a client or vendor and need to move forward, help your attorney draw up the contract that you want, or review a contract submitted to you, by outlining the "deal" and the important issues. Describe your goals, what you need to have included, what should not be included, etc. In addition, if you already have a contract draft from the other party, read it and highlight clauses that bring up questions or concerns.
The following are important points for everyone in a contract negotiation:
Be sure to
Be prepared to have the other party dispute some contract clauses and come back to you with a revision to your draft contract. Ask them to highlight the changes that they made, and then read the contract, again, completely to see if any other changes were made. Again, the wisest way to proceed in such situations is to have your attorney review the revised contract, too. A change in words or even punctuation can appear meaningless to you but may, in fact, be significant.
If the other side prepares the first draft, you need to read it very
Over time, you can develop your own standard contracts that contain the terms and conditions with which you are comfortable and under which you usually work.
Also know what your price limit is, recognizing that things like payment terms, content source, or technology may affect the actual cost. It is most rational to think in terms of the overall total cost of the project, including not only the purchase price but also cost of maintenance, hosting, software, etc. Figure out your limit (as either the buyer or the seller), and know that going beyond that limit will
The following are important points for the sellers in a negotiation:
Many businesspeople are not comfortable negotiating a contract, but unless you want to trust that everyone else will
Unfortunately, some people and some companies, as part of their corporate culture, negotiate for a "win-lose" solution, where they "win" and you "lose." This negotiation strategy is not good for a long-
Research and experience show that "win-lose" is usually transformed into "lose-lose" experience in the long run. "Win-win" is a better goal, both ethically and practically.
The best contract negotiation is actually just documentation, in proper format written (or at least reviewed) by an attorney representing each party, of the terms and conditions that have already been discussed and agreed to by all parties involved.
When you think about traditional contracts (interactions involving an offeror, an offeree, and consideration resulting in an agreement among two or more parties, who know each other, and who promise to perform a transaction with each other), you have many examples in daily life to guide you. In cyberspace, it starts to get more complicated. How often do the parties "know" each other and come to a meeting of the minds?
You are a Web developer and have a potential new client. After a couple of long discussions with you, the client has asked you for a proposal, delineating what the Web site will contain, how it will be organized, when it will be done, and how much it will cost. You also include some options for the client to consider-monthly maintenance, training, additional sections, and functionality (a shopping cart, an e-mailed newsletter). Each option is priced separately.
| a) |
You do not have a contract yet, but you have some of the elements. What elements of a contract do you have?
__________________________________________________________ __________________________________________________________ |
| b) |
What element is missing?
__________________________________________________________ __________________________________________________________ |
| c) |
If the client likes your proposal but suggests a lower price, what has
__________________________________________________________ __________________________________________________________ |
| d) |
You did not
__________________________________________________________ __________________________________________________________ |
After reading most of a contract, you, as the developer, sign the contract, collect the agreed 30% deposit, and begin work. You immediately hire two subcontractors: a graphics designer to prepare graphics for the site and a Java programmer to develop a couple of custom applets. Thirty days later (when you are about 60% done with the initial development effort and your subcontractors have completed their efforts), the client submits their notice to cancel the contract in a week. They do not tell you why they are canceling, and they tell you that they don't need a reason. They reference a clause in the contract that you had not noticed:
"This Agreement may be
| a) |
Can they cancel this contract?
__________________________________________________________ __________________________________________________________ |
| b) |
Can they cancel the contract without telling you why?
__________________________________________________________ __________________________________________________________ |
| c) |
Assuming that you have already invested more than the 30% deposit, can you recover for the investment you made in the graphics and the Java development?
__________________________________________________________ __________________________________________________________ |
There are two other clauses in the contract that you missed when you reviewed it:
"Work may not be subcontracted or
"Client shall reimburse Developer for reasonable out-of-pocket expenses incurred at the specific request of Client."
| d) |
If you do not have the client's written approval to use the subcontractors, what are your
__________________________________________________________ __________________________________________________________ |
| e) |
Will you read the
next
contract more carefully before you sign it? Are there some clauses that you would have negotiated "out" of the agreement? Are those clauses deal killers?
__________________________________________________________ |
| a) |
You do not have a contract yet, but you have some of the elements. What elements of a contract do you have?
__________________________________________________________ __________________________________________________________ |
| Answer: |
You have two of the three elements of a contract.
Contracts have three elements: an offer made by an offeror, an offeree who accepts the offer, and some consideration. You have made an offer (the proposal), and you have indicated the consideration (pricing) that you feel is appropriate. |
| b) |
What element is missing?
__________________________________________________________ __________________________________________________________ |
| Answer: |
The only missing element is the acceptance by the offeree.
If you wanted to withdraw the proposal (say you made a mistake in the pricing), now would be the time-before the offeree has accepted it. If you discover the mistake after acceptance, you are dependent upon the cooperation of the offeree to allow you to correct your error. The offeree is not required to cooperate. |
| c) |
If the client likes your proposal but suggests a lower price, what has happened? What are your options?
__________________________________________________________ __________________________________________________________ |
| Answer: |
The offeree has, by
You are now the offeree and your client is now the offeror. When they make a counteroffer, you have several options: Accept their counteroffer, accept their counteroffer and request a change to something else (a
|
| d) |
You did not indicate an expiration date on your proposal. Do you have any long-term exposure as a result?
__________________________________________________________ __________________________________________________________ |
| Answer: |
If you have not limited the time frame that your offer is
Reasonable is not defined and is usually dependent on the circumstances. So you could be in the position of maintaining a very different Web site from that in the proposal but at the price in the proposal. An argument could be made that by rejecting your initial offer, the client also rejected the options. But since they were priced separately, the client could easily make an argument that it was only your main proposal that was rejected. So, be sure to indicate an expiration date or "offer, including options, effective until . . ." date in your proposal. |
| a) |
Can they cancel this contract?
__________________________________________________________ __________________________________________________________ |
| Answer: | Unless there is something else in the contract that describes specific situations where this clause does not apply, the answer is yes. They definitely can cancel this contract. |
| b) |
Can they cancel the contract without telling you why?
__________________________________________________________ __________________________________________________________ |
| Answer: | Again, unless there is some other clause in the contract that is contrary to this one, they do not owe you any explanation. They are canceling for their convenience. |
| c) |
Assuming that you have already invested more than the 30% deposit, can you recover for the investment you made in the graphics and the Java development?
__________________________________________________________ __________________________________________________________ |
| Answer: | Maybe and maybe not. It depends on the rest of the contract (e.g., any progress payments terms). |
| d) |
If you do not have the client's written approval to use the subcontractors, what are your chances of being reimbursed for the costs of their efforts? Why?
__________________________________________________________ __________________________________________________________ |
| Answer: |
If you are in violation of the first clause, requiring prior written permission by the client, the chances of recovery may be slim to none.
Hopefully, you can pay for their efforts out of the 30% deposit. If not, you are probably out of luck. Obviously, you should have either objected to that clause before you signed the contract or complied with it and gotten the client's written permission first. It might be argued that the second clause, allowing reimbursement for reasonable expenses, should cover you. But the first clause is pretty clear. |
| e) |
Will you read the
next
contract more carefully before you sign it? Are there some clauses that you would have negotiated "out" of the agreement? Are those clauses deal killers?
__________________________________________________________ |
| Answer: |
You should answer yes, yes, and maybe. A wise person would also indicate the need for an attorney to do a review of the contract prior to signing it.
Most developers would find the specified clauses unacceptable as they are written. You should be able to soften or eliminate them in a negotiation. In many cases these draconian clauses are included because they are "standard terms" included in every draft agreement. There may even be an expectation that they will be eliminated from the final agreement, as bargaining "chips" in the negotiation process.
They could also be included because the client always operates this way. Many very large companies and the U.S. federal government have these clauses in their contracts because they use the same draft terms and conditions over and over. They are also used because these very large customers have so many
|
In order to test your progress, you should be able to answer the following questions:
| 1) |
Which are two reasons to use a written and signed contract in a Web development project?
|
| 2) |
You may withdraw an offer
|
| 3) |
A client may cancel a contract
|
Quiz answers appear in Appendix A, Section 7.1.