I think from a business perspective it's more on perceived value. If the client does not care about the choice of language, or is more concerned about being able to easily find freelance support, then Perl sounds like a Bad Idea. Most business people know only about Java, .NET, and ASP.
But if the client is stuck with legacy Perl codes, then you are in luck. My suggestion is to highlight your development experience, and how efficient your solution is going to be. That's all they want to hear. ----- Original Message ----- From: "John ORourke" <[EMAIL PROTECTED]> To: "Chris" <[EMAIL PROTECTED]> Cc: <modperl@perl.apache.org> Sent: Wednesday, December 21, 2005 1:32 AM Subject: Re: Going mod_perl hourly rate? > I don't know what US rates are like but I'd suggest taking into account > these: > > + mod_perl is a rare skill in a world full of php 'coders' > + mod_perl can bring commercial benefits (cheaper hardware, faster > sites etc) > - mod_perl is more expensive to maintain because it's harder to find > people who can > > In my (humble) opinion the rate you can charge is more down to your > sales skills than anything else. > > John > > Chris wrote: > > >Hi all, > > > >I have been working with mod_perl for a while now and want to start > >expanding into doing mod_perl only contract work. > > > >What is the going hourly rate for projects done in mod_perl? I know > >rates are based on overhead, etc but just want to get a general idea of > >what people pay. > > > >Thanks! > > > > > > > > > >
