How to hire a freelancer

You do not have to be able to program to choose a good freelance developer, someone self-employed who builds software for you under contract. Much of what you want to know you would also check with a builder or an accountant: does this person listen, can they show what they did before, and do you understand what they say?

Helsh-js is itself a one-person studio, so you can apply what follows to me as well.

Where to start

First write down what you need, even if it is short and unfinished. How to write a brief explains how, with no technical knowledge. With a text like that you tell everyone the same story, which makes the answers easier to compare.

Then ask around among other business owners who have had software built, and talk to more than one person. You learn a lot from the difference between two conversations about the same problem.

Do they ask about your problem?

In the first conversation, notice who asks the questions, and about what. I start by listening myself: what do you need, why do you need it, how do you do it now? Do you do it manually or in Excel, and why would you walk away from that? Another developer may go about it differently, but they need to know enough about your work before they can talk about technology or price.

Notice your sector’s words too. Every business has its own terms, and an “order” can mean something different for you than for your neighbour. Someone who asks about that is working to understand your work.

It is also a good sign if someone dares to say you do not need something. Feel free to ask: “What would you leave out?” The answer shows how someone thinks about what goes in a first version.

Do they show their work?

Ask for things you can open yourself: a website, an app in the app store, a demo. A working demo beats a slide deck, because you can press things. See whether it runs smoothly on your phone and whether you understand what to do.

Then ask what that person did exactly. Did they build it all themselves, or a part within a larger team? Either is fine, as long as you know what you are looking at. Good follow-up questions are what was difficult and what changed once the first users had it in their hands.

A project from your own sector is a bonus. What usually tells you more is whether someone has built something comparable, such as an app that has to work with no signal or a connection to accounting software.

Client work can be confidential. Then someone can sometimes only show the result and talk about it. Ask too whether you can speak to a former client. If you know someone with technical knowledge, they can also take a look at a piece of code for you.

How do they communicate?

The first contact already tells you a lot. Does someone explain a technical term without you having to ask? Do you get a clear written answer after a conversation, and do you understand what would happen next?

Ask as well how you will see the work grow. I show working software early, on a test address you can open yourself. A test address is a separate version of your product that is not public yet. Discuss too how often you will look at it together, and how you will reach each other.

Ask who writes the code. With me, the person on the call is the person writing the code. A freelancer can also subcontract work, so ask about that at the same time. Because it is one person, you can also ask what happens during a holiday or illness. A calm, concrete answer is enough. Whether one person is the right choice at all is covered in Freelancer, agency or in-house?

Who will own the code?

Ask that before you start, with any developer. With me, the code and the data belong to the customer. Do not take that for granted with anyone: with a freelancer, the copyright on the code can stay with the maker unless a contract says otherwise. Have a lawyer check it, because the rules depend on your situation.

Ask too in whose name the accounts will be, such as your domain name, your hosting, the place the code is kept and your app store accounts. There is more on that in Who owns your code and data?

What happens after launch

Software still needs maintenance after launch: small errors, updates, new wishes. Ask whether the freelancer stays available afterwards, and how that works. Ask as well what happens if you stop. For my part, I stay around, or I hand it over cleanly.

Start with something small

You do not have to build everything together straight away. Start with a first piece, such as a written plan, a prototype or a small part of the product. Then you see how working together goes, and you can still decide afterwards.

Compare prices on what is included. Two quotes for “an app” can be about very different things, and What makes an app expensive or cheap? helps you see that difference. Once you have found someone, take these questions with you before you sign.