How to hire a design and development studio

To hire a design studio, judge three things: the kind of work in the portfolio, the people who will actually do that work, and whether you will own the result when the project ends. A credentials page, a list of services, and a mood you like are weaker evidence. They describe a studio that could be anyone.

You are hiring a partner for a defined piece of work, usually a site, a brand system, or a product interface. The studio should be able to point at something already shipped that had a similar constraint. If they cannot, the fit is a guess, and a guess is an expensive way to start.

Read the work for the problem, not the style

Look for the constraint. An ecommerce migration is a different skill from a campaign illustration. A quiet brand site is a different skill from a trading interface. Hanabi’s public work is a useful picture of that range, and it is public so you can look without a sales call. Down the Cove is an ecommerce restructure, migration, and redesign. Thomas Bewick is an editorial site for a heritage craft brand. Ballarat Box Sports is a community sports brand. Wabisabi is a calm brand site. Got Next and Leadly are product interfaces. Trade Moai is a trading interface concept. None of those names is a promise that your project will look like them. They are proof of the kinds of problems the studio has taken on.

When you review any studio, ask what was hard and what was left out. A portfolio that only shows finished screens, with no decision, is decoration. You want to hear the trade: what the first version refused, what the buyer or the user had to understand, what the team kept so the site would still be editable.

Google’s guide to helpful, people-first content is written for publishers, and it is a fair lens on a studio’s own site. The guide asks whether the work shows first-hand experience, whether a visitor can tell who made it, and whether someone who arrived directly would leave able to act. Apply that to the agency you are about to email. If the site could swap in another studio’s name and lose nothing, you have not learned how they work. Specific projects, a plain description of what they design and build, and a way to talk to a person are the signs of a site made for a buyer, not a site made of adjectives.

Ask who does the work

The people on the intro call should be close to the work, or they should say who will be. In a small studio, design and production code often sit with the same few people. That is the point of hiring one. Ask who will design, who will write the front end, and who you will hear from when something slips.

If the call is only a seller, ask for the next conversation to include the person who will make the site. You are allowed to care that the craft you saw in the portfolio is the craft you will get. A large agency may staff a project after the contract. A small studio can usually name the people before you sign. If they will not name anyone, treat that as information.

Ask what you will be expected to do. A good studio needs a decision-maker, access to the current site, and a straight description of the offer. It should not need you to art-direct every margin. If the process only works when you are in the file every day, you may be hiring extra hands for a job you are still doing yourself.

Own the result

Ownership is the third test, and it is easy to skip because the pictures are more interesting. You should leave with the repository, the domain in your account, the content logins, and the analytics. Brand files — logos, type, the short guide — should live somewhere you can open after the project, not in a chat thread.

A studio that keeps the code, the DNS, or the CMS login as a condition of the relationship is a dependency. You can still choose to keep working together. You should be able to stop. Ask this before the proposal, in plain language: “What do we have in our name on the day you hand this over?” The answer should be a list, not a reassurance.

Hanabi’s own handoff includes a client portal for brand files, documents, and project updates after delivery. That is one way to make the files findable. The standard underneath it is older than the portal: you own the work. Clean code, in this context, means a later person can find the headline, the sections, and the images without a treasure hunt. Ask to see that the studio’s process aims at that, even if you never read the code yourself.

Notice the fit, including a poor one

A studio is a strong choice when you need design and build together for a launch with an edge: a marketing site, a shop, a focused product, a small brand system the team will use. It is a poor choice when you want a large retained department, a single icon, or a strategy process with no intention to ship. Say so. A careful studio would rather decline than stretch a project into a shape it does not do.

Listen for how they talk about quality. Hanabi states its standard as clarity over complexity, clean code, a process that can change, speed, and plain communication. Whoever you hire, those should show up as behaviors you can ask about. What will you see at the end of a week? Who answers when a date moves? What happens to motion when someone prefers less of it? Vague excellence is not a process.

Price belongs in the conversation once the shape is real. A studio that will not discuss how a change affects the date is hiding the only lever you have. You do not need a fake precision. You need to know what is included, what is later, and what a new page costs in time.

If the three tests are the ones you want to run with Hanabi, book an intro call. Thirty minutes is enough to tell whether the work, the people, and the ownership match.

Bring a sharper list to that conversation, or to any studio’s. Questions to ask about performance, access, and ownership is the next piece: the practical questions that sit under this hiring decision, once you know you are comparing partners and not collecting pitches.