Skip to page content or skip to Accesskey List.
Search evolt.org
evolt.org login: or register

Work

Main Page Content

Collecting Your Dues

Rated 3.88 (Ratings: 8) (Add your rating)

Log in to add a comment
(4 comments so far)

Want more?

 
Picture of beltrini

Marc

Member info | Full bio

User since: January 17, 2001

Last login: January 17, 2001

Articles written: 2

November, 2001

Company Rep: “Fred, we could use your expertise on this upcoming project. We think it's something you would enjoy.”
Fred Freelancer: “My workload isn't too heavy, sure, tell me more.”
[snip]
FF: “Wow! That sounds really great. I'd love to be a part of this. I do have one more question though. How much will you be paying?”
CR: “I can't say for sure. But it will be something fair.”

March, 2002

CR: “The project was a great success. I talked to my higher-ups and they definitely want you on board for future projects. I reminded them you need to be paid.”
FF: “Great. Thanks.”

April, 2002

FF: “I'm sort of concerned that the project was completed a month ago and you still have not addressed payment for my work.”
Boss: “ Fred, I understand you worked on the project, but you never actually had an agreement with me personally regarding payment.”
FF: “That is true. But I spoke to your representative about it…”
Boss: “I was not aware of how much you contributed to this project. But that doesn't interest me anyway. I accept that you were a part of it, and I recognise that we owe you something. I appreciate the commitment you have shown to our company, and I definitely want you to be a part of the company's future. Of course before we move forward, we will have to settle those outstanding issues. But I am really busy and cannot focus on that right now. I will get back to you at a later date.”

The Moral

What was Fred Freelancer thinking when he agreed to this project?

“Pickings are rather slim these days. I shouldn't let this get away. Plus it's exactly the sort of project I would like to be involved in and it'll be a great experience. And it doesn't hurt that I've worked with these guys before and I personally know the principals of the company.

“So what if they haven't finalised a figure as yet. I can trust them.”

Good faith, the love of the job, trust that one's commitment will be rewarded – admirable and noble philosophies in theory. Assuming and naïve bases for business decisions.

How difficult do you think it was for Mr. Freelancer to raise questions about what he would be paid? After all, he doesn't want to nag anyone, or worse yet, give the impression that the money is all that matters.

It's too simple for many of us to think this way, trusting our own personal principles and ethics are common practice in the business world. For most of us, especially those just starting out in the business, web development is sheer nirvana. We seek nothing more than to bury ourselves behind our monitors and get to work. Meetings with clients go by in a haze as visions of HTML tags and CSS properties dance behind our eyes. That's how we forget to bring up the subject of compensation. Or some of us, fair-minded, trusting suckers that we are, assume that Mr. Client will actually pay us promptly and fairly when we deliver his website.

Not without an agreement, preferably a signed contract, he won't! And remember, once you deliver the finished goods to the client, you've got no bargaining power – except that contract. The one you agreed upon before you started work.

So what kind of payment terms should you seek? There are several options, and of course different situations have different requirements. These suggestions may help point you in the right direction.

  1. Always agree on the figures before you commence work, or at the latest, no more than one week after this date. Notice, agree on the figures. Not vague promises like our friend, Fred.
  2. In cases where the figures are based on an hourly rate, ensure that the client has a clear understanding of the scope of the project. An exact number, e.g. 10 hours, is not always a must. An educated estimate, e.g. 10-15 hours, will usually suffice. This ensures that there will be no unpleasant surprises for the client that may translate into ill will or mistrust. If you ever encounter a situation where your estimated hours are way off, inform the client immediately and clarify the situation.
  3. If you are a freelancer, remember that your fees must not only cover development time. You need to cater for administrative tasks — attending meetings, corresponding with the client, invoicing, accounting, etc — and other incidental expenses.
  4. Work out a reasonable schedule of payment. Yes, you will be paid $x,000 for the project. But does this mean you won't see a dime of it until it is completed? Or will you see 15% now, 85% on completion. Payments made in installments should be complemented on your side by deliverables supplied.
    Put yourself in the client's shoes. Which sounds better?

    “Pay me 10% now, 45% in a month, and the remaining 45% when it's done”
    or
    “A downpayment of 10%, 45% on acceptance of the site layout templates and artwork, and 45% upon approval of the finished project”

    Adjust the number of payment points and percentages paid to suit. Obviously more trustworthy or longstanding clients could be offered lower downpayment terms than newer, riskier business.
  5. Provide the client with, and record for yourself, proper paperwork for all transactions — invoices, receipts, etc.

Remember, yes you may truly enjoy what you do, and the sense of completion may give you a warm fuzzy feeling inside. And you may accumulate vast tracts of good karma by being trusting and all that, but neither karma nor warm fuzzy feelings pay the bills. You are in business, and you deserve to be compensated for the services you render.

In short, it's your money. Do not be bashful about asking for it.

Marc Seyon is a web developer from the Caribbean island of Trinidad. During his seven year online experience, Marc has become immune to the question, "Where is Trinidad?". So much so that he has constructed his very own T&T FAQ.

Marc is also an avid photographer with a penchant for capturing the beauty of Carnival, Trini-style on his website PlayYuhself.com.

Too true

Submitted by taracleveland on May 7, 2002 - 20:01.

I'm sure that many of us have learned this the hard way. The one thing I'd like to add is that in addition to agreeing on a figure you need to agree on scope. There's no use agreeing to a figure for updating a web page if you end up redoing the whole site for the originally quoted price. If the project scope changes, make sure that you agree on a new figure that you will be paid. And have it in writing.

login or register to post comments

Contradictory?

Submitted by luminosity on May 7, 2002 - 23:02.

How do you take 15% now if you don't know how long it's gonna take, when you're billing by the hour?

login or register to post comments

Even with a contract you'll face...

Submitted by hblair on May 7, 2002 - 23:46.

"We can't afford to pay you right now. It's tax time and we just don't have the money. Give us a call in July and we'll see what can be done." Good article, Marc. We need reminding of this now and then.

login or register to post comments

Good Stuff!

Submitted by profjj on May 8, 2002 - 00:29.

Marc,

I will not ask where TT. That is too close to home. I am from St. Lucia - just north of you.

I know exactly what you are talking about. You mentioned some very valuable points. I remember a project where I was "coerced" into lowering the price since when I started, there was no agreed upon price. It was at the start of my career, thank God, better early so that the adjustments could be made - "when people see how good our site looks we will get business for you,...etc... "if you bring it down a bit, we can get a few companies that fit in that budget for you" and I "foolishly" shrinked the end price. Of course I never got any other referral sites from that company in question - even though we have moved on much further since then. The good thing is I did not shrink the price by a sizeable amount.

One other company wanted me to start, and they will "pay everything on completion..." Another good one was and I remembered this from a comment above - "we're filing our end of year taxes so that will be the first project we take in our new financial year - but you can go ahead and layout the ground work, and we'll give the deposit to commence as soon as we get everything sorted out". That was almost 8 months ago.

And I am sure that we are not the only one's who have gone through this - practically everyone here could probably write their own article about this subject.

Suggestion I have is for web development which has prevented me from making the initial mistake i mentioned above, and what FF experienced, as with everything it is not fool proof, but a good idea is work with an estimated number of hours multiplied by a rate. This is easy to establish the more experienced you become, since you will know what takes how much work to produce... and will for OBVIOUS reasons NEVER be ACCURATE, but we can make some provisions for plus or minus a few hours.

What is also good as you suggested is not only agree, but give 2 or more payment plans (can be more), based on the time frame, all of which are needed to commence. Plan A - A percentage down for deposit to commence, balance on completion (worst plan - it sometimes puts too much strain on client most time). Plan B - Broken down over the development time. So if the project takes 2 months (8 weeks) Deposit to start, 2nd Payment after 4 wks on a agreed date, 3rd Payment after 8 weeks of a certain percentage to complete, etc...

The only downside is if you complete before the designated delivery date and the client gets any payment challenges, well no more to be said... but you can always stop if there is a default in payment.

Hope this helps anyone.

profjj

login or register to post comments

The access keys for this page are: ALT (Control on a Mac) plus:

evolt.orgEvolt.org is an all-volunteer resource for web developers made up of a discussion list, a browser archive, and member-submitted articles. This article is the property of its author, please do not redistribute or use elsewhere without checking with the author.