Studio, freelancer, or in-house for a first serious site

For a first serious site, design agency vs freelancer is an incomplete question until you add an in-house hire. The shape of the work decides the seat. Use a freelancer when you need one narrow skill. Hire in-house when the work will not stop. Use a studio when a defined launch needs design and production code together, and you want those two in the same conversation.

The first site is usually a launch with an edge: a clear offer, a handful of pages, a shop, or a product path someone can try. It is rarely a forever backlog on day one. Matching the seat to that shape saves you from paying a team to sit, or from asking one specialist to be three jobs.

A freelancer for a narrow skill

Hire a freelancer when the missing piece is specific and you can direct it. A wordmark. An illustration set. A single feature in a product your developers already run. An audit of a page you know is failing. The freelancer is excellent when the edges of the task are visible, and when someone inside your company will receive the file and know what to do with it.

You are the project manager. That is the part founders forget. Someone has to connect the design file to the codebase, watch the domain, and decide what is out of scope. If that someone is you, budget the hours. A beautiful homepage file that nobody can build is not a site.

The common failure is a split you did not plan. A freelance designer and a freelance developer who have never worked together will invent two versions of the page unless you give them one brief and one person who can approve. If you cannot be that person, a studio is often cheaper than it looks, because the coordination is the work.

In-house when the work never stops

Hire in-house when designing and shipping is a weekly job for the life of the product. A product that changes every sprint, a brand that publishes constantly, a shop that needs a dedicated owner: those can fill a seat. The cost is not only salary. It is recruiting, managing, tools, and the months before the first person is fully useful.

A first marketing site rarely fills that seat by itself. After launch, the work often becomes edits, a page or two, and the occasional campaign. A full-time designer who spends the next quarter waiting for a brief is an expensive way to buy a website. Hire when you can describe next quarter’s work without inventing it.

There is a middle that is easy to romanticize: a first employee who “does design and a bit of code.” Some people can. Many will be strong at one and careful at the other. Look at what they have shipped, the same way you would look at a studio. A portfolio of mockups and no launched site is a signal. So is a portfolio of templates with no design decisions. You are allowed to want both.

A studio when design and build share one launch

Use a studio when the launch needs interface design and a production front end, and you want them decided together. A marketing site. A small brand system the team will actually use. An ecommerce front end, including a move off an older stack. A focused product interface. The scope has an end. The site ships. You should own the repository, the domain, and the content logins when it does.

A studio is the wrong expense when you already have a strong design and only need implementation hours, or when you already have engineers and only need a narrow visual pass. It is also the wrong expense when you want a standing department and a long strategy program with no ship date. Say that early. A defined launch is the fit.

Hanabi is that kind of studio: design and production code in one small team, for founders and small teams. The public work runs from brand sites such as Wabisabi, Thomas Bewick, and Ballarat Box Sports to the Down the Cove ecommerce migration and to product interfaces such as Got Next, Leadly, and Trade Moai. You are not buying a headcount. You are buying a launch with people who have done the path, and a handoff that includes the code and a portal for brand files, documents, and updates.

The quality bar stays the same

Whoever builds the site, the visitor does not care about the contract. Two references are enough to keep the conversation honest.

The W3C’s WCAG 2 overview is the accessibility reference. The guidelines sit under four principles: perceivable, operable, understandable, and robust. W3C also notes that WCAG applies to mobile. You should not expect a freelancer, a new hire, or a studio to hand you a ceremonial certificate. You should expect them to treat contrast, focus, names on controls, and a checkout or a form a stranger can finish as part of done.

Google Search Central’s Core Web Vitals guidance is the performance reference. For a good experience, aim for an LCP within 2.5 seconds, an INP of less than 200 milliseconds, and a CLS under 0.1. Ask any of the three seats to talk about those numbers in plain language. If the answer is a slogan about “fast, modern experiences,” you have not heard a plan.

Ownership is part of the same bar. A freelancer should hand over the source files and, if they built the site, the repository. An in-house hire works in your accounts from the first day. A studio should put the domain, the repo, and the content system in your name. If any of them hesitate, the price is no longer the price. You are renting your own site.

How to choose this month

Write one sentence: what has to exist on the day this launches, and what can wait. If the sentence is a single skill, talk to a freelancer. If the sentence is “someone who will keep designing this product every week,” open a role. If the sentence is a site or a shop that needs design and code for a date you can name, talk to a studio.

If that third sentence is yours, book an intro call and bring the sentence with you. The call should test fit, not collect a free strategy.

Once you know a studio is the seat, the next piece is how to judge one. How to hire a design and development studio covers the portfolio, the people, and the ownership in the detail this choice only starts.