leknarf
The Aereo Ruling
Ken and I (Andrew) list our email addresses on our home page. Similarly, every automated email we send comes with the reply address set to one of our personal email addresses. Sometimes, people reply to those automated messages asking for things we can't really help with. I try to respond to everyone, but honestly, sometimes messages just slip through.
I've considered removing our email addresses from our web page. I'm sure that would decrease the number of messages we receive, which would increase the percentage we could reply to. But that would ultimately make us less available.
If you have any suggestions on how we can keep track of a high volume of inquires, I would love to hear them. Neither of us have run a startup at this scale before, so we're naturally trying to figure things out as we go.
We charge more for short-term trials (say 1 week), not less. Employers understand that flexibility is valuable and are often willing to pay more to avoid commitments. Conversely, they usually expect discounts for "buying in bulk", so it's reasonable to offer reduced rates for long-term (say longer than 3 months) contracts.
That said, $15/hr is way too low in any situation. There's a reason we set Lambda's minimum to $100/hr: doing so cuts out most clients that we don't want to deal with. I don't know much about your experience level, but a few years programming experience and some time spent as a startup founder should be enough for you to ask for $100/hr. I'm less familiar with the Texas market (we do business in NYC and SF), so $75/hr might be more appropriate, but I wouldn't go any lower than that.
If you send me an email, I'd be happy to hop on a quick call. We don't have many clients in Texas, so I don't think I'd be able to get you a better offer immediately, but I could give you some general negotiating advice.
You haven't told us much about your experience level, so I can't comment on whether you're qualified to land desirable freelance projects yet. I can tell you that most of the freelancers we have on Lambda (http://getlambda.com) have at least 5 years experience and have either done some client work before or are currently launching a startup. I don't think we have anyone with an empty slate.
Right now, it's much easier for developers to get in-house positions. Almost everyone I speak with is looking to expand their in-house team and they need some convincing to try working with a freelancer instead. Freelancers can make a lot more than salaried developers, but they also tend to be more experienced.
Currently, we're looking for devs for a company that helps museums keep track of their collections, another that makes it easier for people to cook healthy meals at home, and a third that's encouraging universities to incorporate 3d-printing into their curriculum.
So there's quite a bit of variety in the types of projects we take on. Social good is a vague concept that means different things to different people, but we can certainly try to match you with projects that fit your interests.
https://chrome.google.com/webstore/detail/cloud-to-butt-plus...
Once you're talking, convince them that working with you will be easier/quicker/more-effective than working with anyone else. That's the hard part, which definitely requires some practice. Pro-tip: don't try to convince anyone that you'll be the cheapest option, which is almost always a losing game to play.
If you prefer, I'd be happy to do the hard work for you. I run a startup that connects senior freelance developers with high-paying companies: http://getlambda.com.
It's an easy win on both sides. In exchange for letting me schedule automatic payments, my landlord could get much more timely payments. I think I'm reasonably responsible as folks go, but still occasionally forget to mail a check on time.
They actually become relevant for late fees, since you usually do want your fee to be punitive enough to encourage timely payments. The usual practice is set your fee to 1.5% per month or the highest percent allowed by law (i.e. just below usury if that's applicable in your state).
We're happy to take applications from developers elsewhere, but we might not be able to get back to you for a while.
I nickled-and-dimed a client on change requests, alienating that client and making myself appear less professional. ... I would have been better served by her loving me than making a little more money.
I completely agree. In fact, this is part of the reason new freelancers often regret setting their hourly rate too low. It's important that you set a high enough rate that you can throw in unbillable work now and then without destroying your earnings. The best freelancers consistently under-promise and over-deliver.
For pricing my services, I need to start high and work my way down. I generally start client conversations on my hourly rate at what I would consider a reasonable ultimate number, and then allow myself to be driven down from there — generally because the client wants a long-term contract and expects to save on my hourly based on the length of the engagement.
Constant haggling will make every new project a frustrating experience. I usually recommend setting a fair rate and then holding the line when clients ask for a discount. That's tough to do with your first few projects, but becomes easier once you're more confident about your rate and abilities.
More projects, less hourly. When starting as a consultant, I was really selling only my hours. Now Symonds & Son is a business in its own right, and I’ve hired designers and developers to help with my workload. Working with other talented individuals makes much more sense on a project basis, where I can package their (and my) hours together.
This depends on what type of projects you're looking to take on. Landing pages and presentation work will probably pay more if you charge per project (since clients won't believe you can more 10x faster than cheaper devs), but building new product features for startups is probably better at an hourly rate (since startup clients always change what they're looking to build).
If anyone is looking to get started as a freelancer/consultant or just looking to expand their existing business, take a look at our startup: http://getlambda.com.
The big problem is education. We speak with a surprising amount of people who've never hired a developer before. They often don't understand the difference between Wordpress dev and someone who's been doing high-performance numerical computing. If they tried to hire a dev on Elance, it would almost certainly be a frustrating experience for both parties, since they're unable to write a reasonable job description.
Our solution has been to take a very unsexy approach: anyone who wants to hire a dev through our service needs to first hop on a phone call and tell me a little about what they're looking for. Sometimes we reject potential clients outright (particularly if they have poor expectations about price) other times we suggest they hire a different type of dev than they initially thought they needed.
Unless Elance is willing to start offering this sort of concierge service, it's unlikely to grow into the sort of place where qualified devs will want to find qualified clients.
Recruit Engineers in Less Time
Growth versus capital efficiency
For consultants, we've had a lot of resonance with various social media channels. It's really nothing fancy or surprising, just making a consistent effort to engage with various communities (like HN) has been fantastic.
We've discussed some ideas we could start developing, but in each case, we've always been able to come up with a quicker/cheaper way to test the relevant concept without development work. Sticking to a "no code" strategy has been a good way to focus our efforts on activities that actually matter. We both like to code and would probably be happier spending a week hacking instead of taking sales calls, but the latter is more important to our company right now.
Just because you can write code doesn't mean you have to.
Lambda is a talent agency for freelance developers and designers. We help you find clients, negotiate for higher rates, and take care of the business side of freelancing.
- Exceptional talent only: $100/hr minimum rate.
- No recruiters or spam. We're developers too and we only match consultants with projects that fit their expertise and interest.
- Serious clients only: Wanna hear about a disruptive social network for cats that "just needs a coder"? Neither do we.
- Freelancers with side projects or startups are especially welcome!
If that's appealing, you can read more and sign up at: http://getlambda.com/We've posted about this on HN a few times and have been amazed by the response. I apologize in advance if it takes a while for us to get back to you -- we interview everyone personally and are still ramping up the process.
Right now, we're particularly looking for NYC Rails devs and SF iOS devs, but anyone else based in the US is still welcome to apply!
This is important, since professionalism is a huge factor in how well freelancers perform. You almost certainly want to work with freelancers that work predictable daytime hours and can thus respond quickly when you have questions.
I certainly don't mean to suggest that someone working on a weekend can't be professional (I'm on HN myself right now). But I don't think it's wise to intentionally avoid the 9-5 crowd.
Instead of posting a description that anyone can respond to, we'd setup a brief phone call where you and I can discuss your project. I'm a developer myself, so I help you figure exactly what sort of experience would be best for your project.
In NYC, I take a lot of meetings (more than 5 a week on average), but rarely need to spend more than 30 minutes in transit. I'd guess the average is closer to 15.
For the types of projects we work with, "exceptional developers" might be better described as "competent developers, great entrepreneurs". Of course, that wouldn't be ideal marketing copy :)
In general, raw technical ability isn't a huge factor in commanding higher rates. There's definitely a minimum threshold someone needs to pass, but you'd probably clear that easily if you've been freelancing for 5+ years.
Instead of learning to code faster, you'd be better served by learning to code less. Clients often have big ideas that would take 6+ months to build in their entirety, but which could be shipped in weeks by eliminating unnecessary features. Convincing them to cut those features is a skill in of itself, which is often what separates "freelancers" from "consultants".
We have a few other competitors targeting the high-end of the freelancer market, but that's still open territory.
A machine readable CV just makes it easier for someone to match keywords. Those matches are almost always terrible. I.e., I see you have the word "javascript" on your resume, perhaps you'd like this "java" job post.
Most devs I know who've broken above 150k fall into one of two categories: startup founders or freelancers. That clearly resonates with the "break from the pack" pitch in the article. The founder path is difficult and risky, but fairly understood at this point (no one is surprised if a successful startup pays their founders well).
Conversely, A lot of people are surprised by how much a successful freelancer can earn. There's still an industry misconception that the skilled people must prefer salaried work and that contractors are somehow in a second tier. But 150k is a fairly easy goal to hit for a new freelancer. Someone billing at 125/hr for 1,200 hours will reach that in pre-tax dollars.
That's only assuming a 60% utilization rate (there are around 2,000 total billable hours in a year). Booking a few more hours or slightly increasing the rate lets freelancers dramatically exceed their in-house peers. Most experienced freelancers I know are earning around 2-4x what they earned as a salaried employee.