Questions to ask a freelancer or agency before signing anything, and red flags in offers that are reason enough to say no thanks.
Price is the least important difference
Two offers for a “business website” can differ several times over and both be fine, because they describe different things. Instead of comparing amounts, compare the answers to a few questions. A good developer will answer them without hesitation, because they ask themselves the same questions on every project.
Questions about ownership
- Who will the domain be registered to? It should be you or your company.
- Will I get the code and all the passwords when the project is handed over, at no extra charge?
- Where will the site be hosted, and can I move it to another provider?
- Are the templates, photos and fonts licensed to me or to the developer?
Questions about the work
- How does the quote work: one amount or split into stages? What is in scope and what is not?
- How many rounds of revisions are included, and what happens after them?
- Will I see the site while it is being built, at a test address, or only at the end?
- Who will build it: you, a team, or a subcontractor I won’t meet?
- How do you check the site on a phone and how do you look after its speed?
Questions about what happens after handover
- What if something breaks after launch? Do you fix your own mistakes for free, and for how long?
- Who updates the system and plugins? Is maintenance mandatory, and can I opt out?
- Will I get instructions on how to change content myself?
Red flags
- Domain or server registered only to the developer, with no access for you.
- No written scope. “We’ll make a nice website” is not a scope.
- A mandatory subscription, after which the site disappears or stays with the developer.
- A guarantee of first place in Google. It can’t be promised, because nobody except Google controls it.
- A portfolio with no working sites, only mockups or screenshots.
- A deadline of “tomorrow” for a site you don’t yet have the text for.
How to check a portfolio
Open the portfolio sites on your own phone, ideally on an ordinary mobile connection. Check whether they load fast, whether the form works and whether you can use them with one hand. Paste one address into PageSpeed Insights. If you can, ask one of the developer’s clients what working together was like after the site was handed over, because that is when you learn the most.
Key takeaway
Compare answers, not amounts. The domain in your name, the code and passwords after handover, a written scope and clear rules after launch are the minimum without which it isn’t worth starting.