What a good intro call should decide

A design studio intro call should end with three decisions: whether there is a fit, the rough shape of the work, and whether a proposal is worth writing. It should not be a free strategy workshop. If you leave with a pile of ideas and no answer on those three, the half hour was a meeting, not a decision.

Thirty minutes is enough for that, if both sides do the preparation a short call requires. It is not enough to redesign the offer, name the product, and settle the information architecture. Those are the project. The call is the gate in front of the project.

Fit, said out loud

Fit is whether this studio does this kind of work for this kind of buyer. A founder with a defined site, shop, brand system, or focused product is the usual match for a small studio that designs and builds. A company that wants a large retained team, or a single icon with no site behind it, is often a poor match. Both outcomes are successful calls. A clear no saves the proposal.

Say what the company does, who it is for, and what the site or product has to accomplish. Then listen for whether the studio recognizes the problem. You want specifics: a marketing site that has to explain a hard product, a shop leaving an old platform, an interface with one primary job. You do not want a generic promise that everything is in scope.

Google’s guide to helpful content asks creators to be clear about who made a page, how it was made, and why it exists. Borrow those three questions for the call, without pretending they are a sales script Google wrote. By the end you should know who would do the work, how that studio usually works, and why this project should happen now rather than later. If the “who” is still “the team,” ask for names or roles. If the “why” is only “we need a new look,” you may be a month away from a real brief.

Hanabi’s public standard — clarity over complexity, clean code, a process that can change, speed, and plain communication — should show up as how the call feels. Plain answers. A willingness to say a date moves when the scope moves. No performance of urgency.

The rough shape

Shape is not a full scope. It is enough outline to know what a proposal would contain.

Name the kind of work. A company site. A landing page. A shop. A product interface. A small brand system. Name what already exists: a live site, a name only, a Figma file, a shop on an old stack. Name the action you want from a stranger: a call, a purchase, a sign-up, a clear understanding of the product.

Name the edges you already know. The pages or the single workflow that must be in the first launch. The things that can wait. The fact that must not change, such as a name, a price position, or a checkout you are not ready to touch. If you do not know the edges, say that. A loose idea can still be discussed. It should be labeled as loose, so nobody writes a proposal for a fantasy of completeness.

A date belongs here only if it is real. “We would like to launch before the season” is a preference. “The old site comes off the contract on this day” is a constraint. Tell the difference. A studio can plan around a constraint. It cannot plan around a mood.

Budget can be a range. You do not need a number down to the dollar. A range tells the studio whether you are describing a focused launch or a program that does not fit the engagement. Hiding the range usually produces a proposal you will reject, which wastes the part of the work that should have been a five-minute correction on the call.

Whether a proposal is worth writing

A proposal is worth writing when the fit is good and the shape is clear enough to price. The next step is a written scope: what is included, what is out, what you will own, and how a change affects the date. You should know, before you hang up, that this document is coming and what it will decide.

A proposal is not worth writing when the idea is still a cloud, or when the fit is wrong. The honest next step might be a smaller paid slice to learn the unknown, or a decision to wait until the offer is a sentence. It might be an introduction to a different kind of help. “We’ll send some thoughts” with no decision is how a studio ends up doing the strategy for free and how a founder ends up with advice nobody is accountable for.

Do not ask the studio to solve the homepage on the call. A useful reaction is allowed: “that headline is doing too much,” or “this sounds like three audiences.” A wireframe, a repositioning, and a feature list are the work. Save them for a scoped engagement. You will get better thinking when someone is responsible for it, and the studio can stay fair to the clients already in progress.

What to bring, and what to leave

Bring the current site, the offer in one sentence, and the name of the person who can approve. If that person is not you, say how a decision gets made. Bring one or two references you respect, as examples of tone, not as a checklist to copy. Bring the constraint that is actually fixed.

Leave the forty-page deck. Leave a demand for a full estimate before anyone has seen the site. Leave a request for speculative work as the price of the conversation. A studio that gives its judgment away in the first call will be hard to work with later, because the boundary was never set. You want the opposite habit: clear updates, a defined next step, and no surprise scope.

If you want that kind of call with Hanabi, book a thirty-minute intro. Come ready to decide fit and shape. You should leave knowing whether a proposal is the right next artifact.

After you agree to start, the list changes. Access, the offer, and the person who can say yes start to matter in a practical way. What to have ready before kickoff is the piece for that moment. The intro call is earlier. It only has to decide whether you should have a kickoff at all.