Received-SPF: pass
 receiver=realpeople.com; client-ip=17.148.16.99; envelope-from=collinswo1s@mac.com
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Subject: Re: [Hx] Typical Fees
References: <list-1560331@realpeople.com>
From: Collins Owens <collinswo1s@mac.com>
In-reply-to: <list-1560331@realpeople.com>
Message-id: <1EDC876B-3B31-4EE8-A148-6A84BD1C4A69@mac.com>
Date: Tue, 24 Aug 2010 18:52:51 -0700
To: Helix Discussion List <Helix-L@realpeople.com>

Thanks, Greg. 
Their price just jumped 10% for ugly. 

Sent from my iPhone

On Aug 24, 2010, at 6:27 PM, Gregg Sanderson <gregg@mktmaster.com> wrote:

> Collins,
> 
> Well, there are as many different ways as there are Helix developers.  Here's how I do it...
> 
> I always give a guaranteed fixed price before I start.  That way, if I'm as good as I think I am, I clean up; If I'm as good as the client thinks I am, I make a reasonable fee, and if I'm not as good as I say I am, then I still get paid to learn.
> 
> In my less-than-humble opinion, charging by the hour is just another way of saying "I'm the expert, but in case I'm not, you pick up the tab."  There are those who disagree.
> 
> Assuming you're as good as I think I am.... ;-)
> 
> Always take a copy of the client's collection and get a good idea of what he/she needs.  Then practice a little in it to be sure you have the logic and knowledge for everything specified.  Keep track of your hours for that.  Then take into consideration:
> 
> How much trouble is this client to work with?
>    (If they waste your time, it costs them more).
> Do they pay their bills on time or sooner.
>    (The best client will greet you with a check when you walk in the door)
> Do they REALLy know what they want?
>    (Are they open to suggestions from your experience?)
> Are they willing to work with you as part of a team, or do they just expect you to perform?
>    (The client must beta test, and KNOW they're testing.  That can save them a bundle and you a hassle)
> Is the receptionist cute?
>    (Add 10% if ugly or male).
> 
> I've never had a case where the client didn't discover something else needed before the job was finished.  I always build in a factor for little changes that don't add function... e.g. showing a different field on a form, and extra easy calculation, etc.  I'm the one who decides what's an extra function.  I hate to "nickel-dime" the client, so I just get a factor in advance to cover those things.  Keeps me from feeling imposed upon when they ask for something.
> 
> ALWAYS look for a legitimate way to reduce the client's cost. You'll make more that way.
> 
> If it's more than a two-week job, get an advance.  Longer jobs can even work with milepost billing.
> I measure delivery from the time I receive the advance check.  For a good client, I get a head start.
> 
> Sometimes it's easier and quicker to rebuild the collection from scratch... and better service to the client.  Don't forget to explore that option.
> 
> Then what it all boils down to is what are you willing to work for, and how much is the client willing to pay?
> 
> And don't sweat the small stuff.
> --
> Gregg
> ========================================
>     The consultant's motto:  Your wish is my ka-ching
> ========================================
> 
> 
> On Aug 24, 2010, at 6:25 PM, Collins Owens wrote:
> 
>> I have been contacted by a Helix user and asked to come to their site and "upgrade" their application, all their forms, to be presentable on OS X machines.
>> 
>> They are asking the first question always asked,...  "how much will it cost me...."
>> 
>> So, Question:  What is a standard or typical rate to charge for this type of work?  They are insisting at first that I commute to their office - about 40 miles, but eventually they may let me work via timbuctu.
>> 
>> Is it more typical to charge by the hour?  How much is normal?
>> or by the job? How much per form?
>> 
>> Thanks,
>> 
>> Collins
>> 
>> 
>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> You received this message because you are subscribed to the mailing list <Helix-L@realpeople.com>.  To unsubscribe, e-mail <Helix-L-off@realpeople.com>; to switch to DIGEST mode, e-mail <Helix-L-digest@realpeople.com>; contact a human being at <Helix-L-request@realpeople.com>.  Google archive since 20 August 2006:  http://groups.google.com/group/helix-l.  Basic archive since 1 Jan 2006:  http://mail.realpeople.com:8100/Lists/Helix-L/List.html
> 
> 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> You received this message because you are subscribed to the mailing list <Helix-L@realpeople.com>.  To unsubscribe, e-mail <Helix-L-off@realpeople.com>; to switch to DIGEST mode, e-mail <Helix-L-digest@realpeople.com>; contact a human being at <Helix-L-request@realpeople.com>.  Google archive since 20 August 2006:  http://groups.google.com/group/helix-l.  Basic archive since 1 Jan 2006:  http://mail.realpeople.com:8100/Lists/Helix-L/List.html