What to prepare before you hire a developer
You need less than you think. A few sentences about what you want, who it is for and what you like. Here is what helps, and what to ask.
By Isaac Oluwayinka · · 3 min read
You need less than you think. A few sentences about what you want to happen, who it is for, and some examples you like is enough for a useful first conversation. You do not need technical words, a design, or a finished plan. Working those out is the developer's job.
What you do not need
You do not need to know which technology to use. You do not need drawings of every page. You do not need a long document. People often delay getting in touch because they feel they must have all of this first, and then lose weeks. A rough idea is a perfectly good place to begin.
What does help
The more of these you can say, even roughly, the faster we get to something real:
- The problem, in one or two sentences. "Customers keep phoning to ask whether we are open. I want them to see it and book online."
- Who will use it. Your customers, your staff, or both? Roughly how many?
- Examples. Two or three websites or apps you like, and one you dislike, with a few words on why.
- What you already have. A domain name, a logo, an old site, accounts with a payment provider, photos, written text.
- Who decides on your side. One person who can say yes, so work does not stall waiting for five opinions.
- What "done" looks like. How will you know it worked? More enquiries, fewer phone calls, orders coming in without you?
Questions to ask any developer
A good developer will welcome these, and the answers tell you a lot:
- Who exactly will do the work, and will it be the same person all the way through?
- How will we talk, and how often will I see progress?
- Will I see something working along the way, or only at the end?
- Who owns the code, the domain name and the accounts when it is finished? (The answer should be: you.)
- What happens after it goes live if something breaks or I want a change?
If a developer cannot answer these in plain words, treat that as information.
About the money side
I do not publish fixed packages, because every project is different. We settle the terms in conversation once I understand what you want, before any work begins. You do not need to arrive with a number in mind.
Questions people ask
›Do I need a design before I contact a developer?
No. A design is part of the work, and it is better made together once we understand the goal. Examples of things you like are more useful than a drawing.
›Should I write a long brief?
No. A short message in your own words is better than a long document. We can shape the details together in the first call.
›What if I do not know what technology I need?
That is normal, and it is my job to know. I will explain the options in plain words and recommend one, with the reasons.
When you are ready, ask for a free consultation and tell me what you have so far. If you are still deciding what to build, start with website or app: which does my business need?, or read about technical advice for choices you want a second opinion on.
Thinking about a project of your own?
Tell me what you have in mind and we will talk it through. The first consultation is free.
More to read
- What is an MVP, and do I need one?
· 3 min read · Planning your project
An MVP is the smallest version of your idea that real people can use. It shows you whether the idea works before you build all of it.
- Website or app: which does my business need?
· 4 min read · Planning your project
Most businesses should start with a website. Here is how to tell when an app is worth building, and when it is not.
- Why is my website slow?
· 3 min read · Keeping it healthy
Slow websites are usually slow for a few ordinary reasons: big pictures, too many add-ons, struggling hosting. Here is how to check and what fixes it.