1. Describe the result before the job title
“We need a designer” is a starting point. “We need a five-page website that explains our services and collects enquiries” is a scope you can discuss. Note your audience, current situation, required deliverables and deadline. Include a budget range if you have one, and name any constraints such as a required platform or brand system.
2. Separate essentials from optional work
Make a short must-have list and a separate later list. Confirm who provides copy, images, access and feedback. A freelancer cannot give a reliable delivery date when key inputs are still unknown. If the problem itself needs investigation, consider a paid discovery stage with a defined output before commissioning the full project.
3. Shortlist using relevant evidence
Choose portfolio examples that resemble your problem, not just the visual style you like. Ask what the freelancer personally did and what was outside their role. Reviews can add context, but read for communication, delivery and relevance. Avoid requesting unpaid custom work as a substitute for assessing an existing portfolio.
- Ask for a walkthrough of one relevant project.
- Confirm availability, working hours and the preferred feedback channel.
- Discuss who will do the work if a team or subcontractor is involved.
- Ask what information is needed to produce a firm proposal.
4. Compare proposals on the same basis
Compare deliverables, exclusions, revision rounds, schedule, payment stages and handover. The cheapest total may cover less. Ask candidates to clarify gaps rather than assuming they included everything in your brief. For larger projects, agree milestones that produce something you can review, such as an approved structure or a working feature.
5. Keep feedback specific and consolidated
Use one place for decisions and one person to consolidate comments. Describe what is not working and why rather than sending contradictory redesign instructions. When the scope changes, agree the effect on price and timing before work continues. Keep a written record of approvals so both sides know which version is current.
6. Check the handover before closing the project
Review the work against the original acceptance criteria. Confirm that the files open, access is transferred appropriately and instructions are understandable. Agree how any final issues will be handled. If ongoing support is needed, define that separately instead of assuming it is included forever.
- Receive the agreed editable files and exports.
- Test important journeys and links where applicable.
- Document account ownership and ongoing service costs.
- Record any outstanding tasks with an owner and due date.
Common questions
Should I start with a small project?
A small paid milestone can help both sides test collaboration when it produces a useful result. Keep its scope and acceptance criteria explicit; do not treat it as a request for free speculative work.
What if I do not know my budget yet?
Describe the outcome and ask which parts could fit into a first phase. Compare a reduced scope with a fuller version rather than asking for an unlimited project at an unspecified price.