If you enjoyed this article, get email updates (it's free).
Join over 77,235 Subscribers Today.
In the glorious field of web design there are far too many prices, skillsets, levels of professionalism, and difference in deliverables for any client to really understand them all or even comprehend where to start. We live and work in a field that is ever-changing and as hard as it is for us to keep up with technology, clients can’t possibly be expected to. This post is going to be the start of a series on the entire process of building a website for a client. It will entail many phases from initial meeting to design mockups to development, testing, and launch. Within each of the articles there will be pertinent information for anyone in the freelance field whether you’re a full-timer or not. My simple goal is to provide information for each of you that will aid you in streamlining the process and help cut out some pitfalls along the way. I’d also like to ask for your feedback on each of the phases I’ll be outlining here. There is no “right way” to do things so give your thoughts and opinions, no holding back. Let’s get started.
We’re going to assume you have contact for a potential client and that’s where this article will start to help you out. And now that you have that contact, you’ll inevitably have to setup a meeting with them to discuss what they are looking for and what you can provide. There are some things to note here and keep in mind when meeting with the client that I believe are contrary to much of the “traditional” information out there.
So now that we have those tips in mind, lets talk about the process a bit. The initial meeting, as I said above, is an interview from the client to you…and from you to the client. Don’t let them have the upper-hand here as it will only set you up for failure down the road. They’ll think they can walk on you and you’ll end up being their photoshop puppet to get the job done.
If you’re meeting with the client on the phone or skype, just make sure you’ve looked at their site thoroughly and done some research on their industry. But if you’re meeting in person, there’s a very simple list of things you’ll need for the meeting.
And that really should be it. I never take a computer unless the client tells me to specifically. This helps to establish that you are a creative and not just someone that knows how to work a computer design program. The sketchbook and marker are your best friends at this point of the process.
This is important, probably more so than even finding the needs for the project. You’ve got to have some sort of connection with the client and if you don’t, the project will feel stiff and you’ll have little passion for it. Now I realize there are people out there that will disagree with me when I say that we need to connect with our work and get involved and passionate about it. But I’d venture a guess that many people in the creative field, professionals that is, will agree with me here. If you don’t have fire about what you’re working on, you’re creative is stifled. You’ll have no desire, no passion, no connection. The creative field breaks all the traditional ties that many other fields have. We don’t wear suits, dress in Armani shoes, or carry a briefcase everywhere we go. I’ve found that I get more attention from clients when I walk in wearing street clothes (but be presentable) and have my sketchbook and marker in hand. They’re hiring you to be creative and I don’t wear a suit at my desk so I don’t wear one to meetings either.
I won’t say this will work for all clients, but small to medium sized businesses typically don’t care how you look as much as they care about how you work and how your work looks. And to be honest, if they’re going to judge me on my looks and not my character or skillet, I don’t want to work with them anyway. So with that said, keep it presentable, but be yourself and you’ll get more attention and they’re much more likely to remember you.
However you look and dress is becoming less important these days. Clients want someone they can trust. Someone that will be honest with them and will deliver when and what is promised. Ultimately, you have to convey that you are, in fact, the most capable and trustworthy person they’ve met with for the job. This is what getting acquainted is all about. It’s about connecting and seeing if you’re right for the client and if they’re right for you.
I urge you to take notice of the above title…notice it says needs, not wants. We’re professionals here or at least striving to be so it is our job to tell the client what they need. Not all sites need a blog. Not all sites will require a link every social media site available. Not all sites will require social media at all. This is where you’re professionalism is to shine through. If you’re straightforward with the client, tell them your position on what you think would be best for them and what would work best for their users, you’ll get picked almost every time. And if you don’t, they are probably one of the clients we described above and you don’t want to work with them anyway.
The initial meeting is imperative to be able to establish the needs (and some wants) of the client. I’m not saying you can’t give them anything they want, but be reasonable…no dancing frogs on the homepage…unless they breed frogs or something strange like that. Talk with them about what they are trying to accomplish with their site. Below are some questions to keep in mind as you talk with them about their project.
There’s plenty more questions that can be asked and can come up in discussion…these are just a few. You’ll learn over time that every client is different and you’ll have different questions for each one. I used to have a small packet of about 20 questions I asked all my clients. It helped to find out information from them that I would need. But as time went on, I realized that many of the questions wouldn’t apply to all clients and that the ones that applied to one client had no application to another. So needless to say, I scrapped it.
So take this time to really dig into the project with the client. Figure out their needs, write them down, and make notes of everything they say. They’ll remember what they like and want and you’ll be expected to as well.
Yes we all know that no one wants to talk about how much a site will cost. You’ll ask them for a budget and they’ll tell you they don’t have one or want you to give them a quote first. You can explain to them that in order for you to be able to tell them right now if you can do the job or not, you’ll need to know what they are expecting to spend. They have an idea somewhere in their head. If they still won’t tell you, drop it and do your quote as if they had an unlimited budget. At this point you’ve done all you can and if they come back on you saying it’s too much, then they already started out your relationship with a lie because they had an idea of the cost. Keep in mind that most companies work off budgets and if they don’t spend the entire budget allocated for something, they lose it at the end of the year.
I used to believe that you never gave a price up front for how much something will cost because it will lock you into that rate. But I’ve found that not to be true over time. For one, people will often pick you because you were the only one they talked to that had an idea of the cost. That shows you’ve got enough experience to tell them a ballpark figure. It also shows you’ve researched their industry a little bit (which you should do before the meeting) and understand a bit more than even what you’ve talked about in the meeting. With that said, it takes time to get your pricing down. So if you’re starting off as a freelancer, you may keep the price to yourself until the you’ve worked it out on paper and done the proposal.
Now that you’ve had the initial meeting, gotten the vibe you want to work with the person, and (hopefully) established a budget, it’s time to move onto the next phase. It’s best to give them a timeframe of a few days for the proposal and then make sure you get it to them within that time. If you’re late, they may take it as a key factor for what will happen during the project.
So that’s all for now. We’ll touch on the topic of the proposal in the next article and incorporate some proposal software pros and cons as well. I sincerely encourage you to give your feedback and rip my article apart, but please be gentle. I’m not saying this is the only way to do things…but it works for me and my research has shown several points in here work for other people as well. Let’s get conversing!
Join over 77,235 Subscribers Today.
I'm a designer, husband, father, and Christ-follower for life. Usability is key, sandwiches are awesome, and there's just no beating a Starbucks white chocolate mocha. You are cordially invited to be a twitter stalker of mine and I hope you love the articles so much it makes you want to share them every 15 seconds for the rest of your life. That would be some serious sharing going on. Drop me a line on my site even if it's just to say "Hey!"