If this is your first freelancing client ever, then my guess is that just getting the client, and being able to demonstrate that you were able to deliver, is pr

If this is your first freelancing client ever, then my guess is that just getting the client, and being able to demonstrate that you were able to deliver, is probably a good first step. Your goal, in such a case, is to convince the client that you're the right person to do this job. Remember that the client probably doesn't care about technology. So don't say "I use Ruby on Rails," even if you do. Say, "I use technologies that will let me accomplish your business needs quickly. If and when those needs change, I'll be able to adapt the software quickly, too." The client's business needs should come front and center. Don't over-promise, which is something that we all do way too much. (I've learned to temper my optimism over the years.) Find out what the budget is for the project, if you can. Ask what the goals are for this project. Again, don't just ask about the software goals -- what are the business goals? How will he judge the success? Don't give a price or time estimate in the first meeting. Say that you need to go back home (or to your office, or wherever) to review things. Tell him that you'll likely have more questions before you provide him with a proposal. And when you do offer a proposal, I've become convinced (although haven't switched to it myself) that weekly billing is the way to go. My fellow podcast panelist Curtis McHale wrote it up here: http://curtismchale.ca/2013/05/23/weekly-pricing-for-web-development/ http://curtismchale.ca/2013/05/23/weekly-pricing-for-web-dev... And above all, relax and try to have fun. There are oodles of potential clients out there. If you mess it up with this one, I promise you that you'll be able to find someone else.