Loading...
Answers
MenuHow can I find clients as a beginner in freelance web designing?
I've been making small affiliate websites for myself for years and living off of my work. I'd like to start a service making small websites for others but I don't know anyone who needs a site made, and I live in a new city where I don't know many people.
How can I find people who need small sites made for them starting from scratch?
Answers
When I was starting out freelancing, I was also starting in a new city without much of a network at all.
I built my network by looking at local meetups, conferences, mixers, and pretty much anything else I could find where people would show up who were either A) doing the kind of work I do, or B) were the kinds of people I wanted to work with.
I volunteered to give small sessions to help other people in my industry, which established me as a perceived authority. This led to referrals from people in the industry who were overbooked or had a lead they weren't sure how to handle.
I met as many people in my target client group as I could, helping for free (with advice and ideas only) in person, connecting them to other freelancers when it was appropriate, and generally being nice and helpful. This led to word-of-mouth referrals.
One note: this is a slower way to start. However, once I built momentum (this took me maybe a year, and I was working a full-time job in addition to networking), it's NEVER slowed down. I have never advertised or marketed myself, and I'm nearly always booked enough that I have to turn clients away. The agency I built and sold using this method is still referral-only and profitable, even after two years of new ownership.
Running ad campaigns can be effective, but it requires constant money and attention. Building a strong network requires a lot of upfront effort, but costs little and becomes less time-consuming as you become more successful.
I'm happy to talk more on this if you want to work on a specific action plan. Hit me up for a call and we'll hammer something out.
The best way to find them if you don't have your own network is to advertise online. You need to organize what you can do into simple products, and sell them through your own site. You can try word off mouth if you have access to a specific network that would benefit from your services. We can chat on a call if you want to go into more detail.
Jason's answer is a great approach, because you get to showcase your expertise, rather than simply say: "I build websites".
You're really solving an expensive problem for them, so by asking them about that problem, rather than speaking about your service, you're in a much better place.
And, although you may be offering to build websites from scratch, you might also find that they have an old or broken website, which means that they have at least thought "I need a website." You could still create the new one from scratch.
Re: talking about the expensive problem. My local suburban butcher was getting less foot traffic due to the demographic changes. Someone said: "instead of a placeholder website, how about you start offering online orders." They now deliver to the whole of Sydney, and a simple email to their list with a video on "how to sharpen knives" or "here's how we make Irish sausages to celebrate St. Patrick's day" is enough to trigger hundreds of orders for people who think: "Oh! That's right. I meant to order meat for my party."
So, seeing the website as a solution to an expensive problem (not enough people coming in the door) made it super lucrative.
As with most problems, it comes back to talking to the client to find out what expensive problem it is they need some help with.
Of course, I'd be happy to help on a call, but it sounds like Jason would be a great fit for your situation.
Common question...
I made a video awhile back to explain my answer:
https://www.youtube.com/watch?v=XbnFcjNFr1Q
Make sure you pick your target market before you start...otherwise, you'll get stuck in the low budget level.
You will have to talk to people.
Network with people who do other things for people who need websites. Accountants, attorneys, bankers, etc... people who help people setup businesses or who know businesses that may need an update to their site.
Make sure your title on LinkedIn is concise and specific.
Create a Slideshare illustrating your work over the years and include it in your LinkedIn profile.
Connect on LinkedIn with the kind of people who would hire you--freelancers and small business owners.
Create simple websites for some friends and ask them to provide testimonials on your LinkedIn page.
Visit the websites of small businesses in your area, walk into their shops, and tell them what you'd do to improve their online presence. Think pizza shops, salons, independent grocery stores, etc.
What you’re talking about is business development. For my own business and many others, I’ve found that a blend of approaches to business development is best, and many good options are listed here already.
What appears to be missing, however, is cold calling. Yes, the gut-wrenching (for most) practice of calling many people you don’t know (or going door-to-door in denser markets) and educating them about you and your service.
Ultimately, building your business is a numbers game: The more people who know about it, the more likely you are to find someone who can use your services today, six months down the road, one year out or even three years into the future (a pleasant surprise that boosted my business significantly). Consider cold calling foundational—a core way to promote you, your services and your drive in a targeted fashion.
Sorry, I didn’t say easy or painless, but cold calling can be an incredibly valuable tool in your business development plan.
Good luck and let me know if you need more assistance.
Related Questions
-
Does Wix.com support an API from Booking.com or other API for B2B Travel Agency?
Yes Wix supports a mulitude of APIs to used for various fetch calls for your web pages. If you already have to API's in mind you can venture off within you WIX code to integrate within your application's processes. There shouldn't be any complications getting this done. Please see the link below for more information https://www.wix.com/code/home/apiAB
-
What 3 questions to pose to a developer, to gauge his expertise level?
If you're not technical yourself, then you might not be able to gauge the efficiency of a candidate's algorithms or critique her code. But there are still some higher-level, more behavioral things that a non-technical interviewer should be looking for in a strong development candidate: 1. What are some tech blogs that you follow? Explain an interesting article to me that you read from one of them. The software development world changes all the time. Best practices are constantly evolving and new libraries are regularly released which make developers more productive. If a candidate doesn't keep up with the latest software news, that might be a red flag that they're not curious or trying to improve themselves. Also, having them explain a technical concept to someone who's non-technical is a great way to gauge their communication skills. Do they seem like someone you could work with and understand easily? Do they care about pausing to make sure you understand, or do they just drone on with jargon? If you feel overwhelmed while they're explaining this answer, imagine how you'll feel when they're telling you why the product has bugs or isn't going to be done on schedule. 2. Tell me about a time you ran into a big roadblock with something you were building. How did you get past it? It's inevitable that a software developer will get tripped up or have to solve some Gordian Knot. Everyone has to bang their head against the wall from time to time. Maybe an API didn't have the data they needed or some function was running too slow and they weren't sure how to speed it up. You're looking to see how they are as a problem solver. Did they come up with a clever but hacky solution? Were they methodical or did they fly by the seat of their pants? Did they go back to the stakeholders and see if the feature's requirements were flexible? Did they work on it for hours and hours trying new things? Did they ask for help from colleagues or on the internet? No right or wrong answers here, but you want to get the sense that this isn't someone who throws up their hands when they hit some friction. 3. Tell me about your favorite project that you worked on. What work are you most proud of? By asking them about the project they're most proud of, you'll get to see what it is that they value most. Maybe one candidate is most proud of a side project they built, even if it wasn't that technically complex, while another candidate is proud of their esoteric PhD project or some specific algorithm they improved. Again, no right or wrong answers, it really depends what type of candidate you're looking for. But it lets you see into their mind a bit, and get at some of the aspects that can make someone a strong development candidate. If you want to talk more specifically about hiring for your team, I'd be happy to do a call!HB
-
How do you manage a developer who's slow, especially when you have a small budget and you don't feel like you'll get things done in time?
Usually Programmers are only slow when they don't know how to solve a particular problem. So they will spend a lot of time researching and a lot of trial & errors to solve a problem. It is important that before you engage a programmer on a project, you break down the entire project into simple, easy to understand modules. Let him give you an estimate of how many hours he will require to complete each of the modules. Example: a typical site will have a login module, registration, My account, profile etc. So let him estimate how much he will require to do the login. You can go even detail here. (e.g. how much extra time if you were to implement Facebook/Twitter Login?). Once he start developing, track his progress closely and make sure he is following his given timeline. If he goes over his budgeted time on a module, talk with him and see what went wrong. It is often seen that they may be wasting their time on something very insignificant that you may have asked him to implement, but you can totally go by without it too. So by understanding what is taking longer time, you will be able to prioritise things better. You definitely need some tools to get this done. Google Spreadsheet or Excel works just fine. But if you don't mind spending a few bucks there are many agile project management tools that you might look into. Here is a list, google them all and sign up for trials: * AgileZen * Agile Bench * Assembla * AssiTrack * Blossom * Basecamp * Breeze * DoneDone * Eidos * Fogbugz * GreenHopper * Jugggla * Kanbanpad * Pivotal Tracker Or the reason why he is slow can be purely non-technical. Sometime your developer may don't share the same level of enthusiasm as you about the idea that you are working on. They often don't often see the "bigger picture" (since you don't share everything with them explicitly). If you can somehow get them excited about what he is a part of, it will work like a drug :) He will work day and night without questioning you. But you need to work equally as hard as him. The moment he sees that you are the boss and he is just the guy doing work for you -- his mentality will shift from being part of something to being the low paid developer. Ultimately its all about motivation and making him a part of your venture. After all he deserves it, if he is really playing a crucial role in the entire development.SK
-
How can I manage my developers' performance if I don't understand IT?
Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.LV
-
What learning path do I have to take to become a "full-stack" web developer?
If I was just starting out, I'd consider learning Meteor (https://www.meteor.com/). It's just entered version 1.0 and after working with it for a little less than a year I do have some issues with it but it still makes for a very solid framework that gets you up and running very fast. You would only need to learn Javascript, and you can slowly work your way towards nodejs from there (which Meteor is based on) if you want to, or you could get the basics down and focus on learning design if you prefer.KD
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.