Freelancer or agency?
Choose the people.
Choose a freelancer when the skills and availability fit the project. Choose an agency when its coordination adds value. Either way, know who is doing the work.
The right partner can explain your business, demonstrate relevant judgment, and take responsibility for the agreed scope. Company size is useful context. It is not a substitute for those things.
When is a freelancer a good fit?
Consider an individual specialist when the project has a focused scope and their work demonstrates the skills it requires. You might already have approved writing and photography, a clear design direction, or an internal team that can own the remaining decisions.
Ask what that person will handle directly and where they need help. Design, writing, development, content entry, and testing are different responsibilities. A freelancer may cover several of them well, but the proposal should make the boundaries clear.
Also discuss availability during the actual project. Who responds if something breaks after launch? What happens during time away? The point is to agree a workable support arrangement, not to assume that working with one person is inherently risky.
When does an agency add useful value?
An agency can be a useful choice when several types of work need coordination and the business wants a clear point of responsibility. Ask who will lead the project and which people will make the design, content, and technical decisions.
Do not assume the people on the sales call are the people doing the work. Request an introduction to the project lead. Understand how decisions move between you and the team, and how the lead resolves disagreements or missing information.
The value should be visible in the plan. A coordinated project should explain how writing informs design, how design handles the real customer journeys, and how the finished experience will be tested. Additional layers only help if they make the result easier to achieve.
How do you compare portfolios fairly?
Look for evidence that matches your problem. A beautiful store is not, by itself, proof of experience with a complex appointment journey. A technically involved product may tell you little about whether the team can present your brand with care.
Ask what the provider actually did on each example. Was it the complete build, one page, a concept, or a collaboration? Open the current site on a phone. Follow the important links. Request the reasoning behind a decision that is relevant to your business.
Our Northside Dental case study identifies the website scope and the practice's appointment journey. Our Back to 30 case study describes a different challenge across multiple clinics. Those details make the work easier to evaluate than screenshots alone.
What should every proposal make clear?
Give each candidate the same brief. Describe the audience, the main customer task, the existing systems, the content you can provide, and the intended launch. Ask them to identify what they would change and what they would keep.
Compare the proposed page types and journeys, not only a total page count. A repeated service layout and an integrated booking flow require different work. Confirm who writes the copy, supplies the images, enters the content, and checks the details before launch.
Discuss revisions and approvals. Decide who can sign off on the business side and what happens when new requirements appear. A defined scope makes a quote easier to judge and gives both sides a practical way to handle change.
If your uncertainty is about the amount of custom work, read our custom website vs template comparison. Choosing the team and choosing the design approach are related decisions, but they are not the same decision.
How should communication and handoff work?
Agree how you will review progress before choosing a partner. Ask to see the kind of material you will approve: page structure, design direction, content, and a working site. You should understand what your approval means at each point.
Bring a real content change to the handoff discussion. Ask how your team will edit a service description, replace a photograph, or publish a new article. If updates will remain with the provider, agree how requests are made and how they are priced.
Confirm control of the domain, hosting, analytics, source files, content, and connected accounts. Where a platform or licensed asset imposes limits, have those explained. Our monthly vs one-time build guide separates ownership questions from payment schedules.
What is a useful final interview?
Bring one customer journey to the conversation. Ask the prospective lead to walk through how they would improve it and what information they need from you. Listen for questions about the business before a proposed solution.
Then ask how they will prove the work is ready. Useful answers describe specific review points, actual mobile testing, the transition from the old website, and verification of inquiries or bookings. “We handle everything” is difficult to evaluate until the work is named.
Finally, ask who remains responsible after launch. You should leave knowing the person to contact, what ongoing support includes, and what would require a new scope. Choose the partner whose responsibilities are clear enough to compare with the others.
At WTM Studio, founder Ray Hussain leads every project personally. Our published engagement explains the design direction and flat-quote approach. Explore website design. We are based in Davie, Florida and work with businesses nationwide.