Questions to Ask Before Choosing Your Creative Partner

Six questions to ask before you hire an agency, studio or freelancer, what good answers sound like, and how to compare proposals that don't match.

Most businesses start this search the same way: typing "creative agency," "brand consultancy," or "web design company" into Google. But what they're actually looking for underneath that search term varies enormously — and the label someone puts on their business (agency, studio, freelancer) tells you far less than the six questions below will.

This piece is written to be used as a checklist. In each section you'll find not only the question to ask, but how to judge whether the answer is a good one, which answers should be read as warning signs, and when the question doesn't matter at all.

"Agency," "Studio," or "Freelancer" — What's the Real Difference?

An agency typically means account managers standing between you and the people doing the actual work, and a broad roster of clients handled at scale. A freelancer means one person, one set of hours, and a hard ceiling on how much they can take on. A boutique studio sits in between: a small, selective team that works directly with founders, and takes on fewer projects on purpose. None of these is universally "better" — the right one depends on what you actually need.

Make the distinction by three concrete criteria rather than by the label: capacity, continuity, and scope. Capacity is how many people can work on you at once. Continuity is what happens when the person doing the work takes a month off. Scope is whether your need is served by one discipline or requires several working together.

A rough mapping does the job:

• One clear, contained deliverable (a landing page, a set of illustrations) — a freelancer is usually the fastest and most economical route.
• Brand identity, web, and content designed as one system — a boutique studio works at that intersection.
• Continuous high-volume production and multi-channel media management — agency structure exists for this.

A label isn't a promise about structure; a three-person team can call itself an agency, and a forty-person company can call itself a studio. Which is why the useful question isn't "are you an agency," it's "how many people will work on this, and what happens if one of them leaves."

When does this distinction not matter?

On a small, well-defined job, interrogating the structure is a waste of time. For a logo refresh, a single-page campaign site, or adapting an existing identity to a new medium, what matters isn't the structure but the work the individual has done in that specific area. The structure question earns its place when the project spans several disciplines and creates a relationship that continues past delivery.

What Should You Clarify Before the First Call?

Before the first conversation, settle three things internally: what you want this project to change, who makes the final decision, and your budget range. Any proposal written while those are unclear is guesswork, and guesswork can't be compared.

"What do you want to change" isn't a design question. "Our site looks dated" is an observation; "half of our quote requests leave without completing the form" is a problem. The client who says the second one gets noticeably better work, because the other side knows what it's solving.

Don't hold back the budget. When it's hidden, the other side writes either the most expensive or the cheapest scenario, and neither helps you. A range, plus what would make that range flex, is enough.

Name the decision-maker up front. An executive who joins the conversation halfway through reopens every decision made so far. One of the most common causes of delays and overruns is a decision-maker who arrives late, not bad design.

How do you write the brief?

A brief doesn't need to be long; it needs to be clear. Picture a five-person accounting practice asking for a new website: even a half-page document lets the other side write a comparable proposal, as long as the six headings below are filled in.

1. Where things stand today: what the current site is, which pages exist, what it does for you. 2. The problem to solve: which behavior you want to change, and how you'll measure it. 3. The audience: who is searching, what they already know, what they're trying to decide. 4. Scope boundaries: write down what's excluded as explicitly as what's included. 5. Timeline and fixed dates: name the trade show, launch, or season start now, not later. 6. Budget range and decision-maker: who approves, and how many people are involved.

A common mistake: writing the solution into the brief

Plenty of businesses write their imagined solution into the brief instead of the problem: "we want a five-page site with a sliding gallery on the homepage." That switches off the other side's expertise and prevents anyone proposing something better. Convert the solution sentence back into a problem instead: "we want to show our work, but right now nobody can tell at a glance what we actually do." The first sentence is an order. The second is a brief.

Checklist: are you ready for the call?

• Can you state the problem the project has to solve in one sentence?
• Do you know what you'll measure success with?
• Will the person giving final approval be in the meetings?
• Do you have a budget range, or are you "waiting to see the numbers"?
• Is it settled who supplies the copy and the images?

Question 1: Who Will You Actually Work With?

Ask directly whether you'll be talking to the person doing the design and development, or to an account manager relaying messages back and forth. Every layer in between adds delay and dilutes the original idea.

The sharper version of the question is: "Who will work on this project, and how often will I speak to them directly?" The senior name in the pitch meeting is frequently not the team that ships the work. That isn't a flaw on its own, but it's something to know in advance.

Follow-up questions:

• How many people will work on this, and in what roles?
• Can I be in the same meeting as the person doing the work?
• How many projects is this team running concurrently right now?
• If the person assigned to me changes, how will I be told?

How do you judge the answer?

A good answer contains names and roles: "I'll do the design, a colleague will handle development, and we'll both be in the weekly call." A weak answer substitutes adjectives for roles: "our expert team will take care of it," "a dedicated crew will be assigned to you." When you hear the second kind, repeat the question without softening it; if a name doesn't come now, it won't come during the project either. A team whose names aren't said is a team that won't share responsibility either.

Question 2: Does Their Portfolio Speak to Your Industry, or Just to Aesthetics?

A visually striking portfolio is table stakes at this point. What matters more is whether they've solved problems structurally similar to yours, not just made things that look nice.

Structural similarity isn't the same as sector experience. A yoga studio and a boutique hotel sit in different industries, yet they can share the same problem: a booking flow, location photography, multilingual content. Meanwhile two clients from the same sector can have nothing in common.

When you review a portfolio, ask them to describe the problem a project solved before describing the outcome. If nobody can say "the client wanted this, we proposed that, and here's why," what you're looking at isn't a case study but a mood board.

How do you review a portfolio, step by step?

1. Check how many of the shown projects are still live; work that's been taken down isn't a problem, but the ratio is informative. 2. Open the live ones on your own phone and see the mobile experience; the images in a deck are a desktop composition. 3. Ask which part of each project was theirs: design, development, content, or all of it. 4. Ask for the brief behind the project you liked most: what the client asked for, what the constraints were, what they changed. 5. Ask for the example closest to your problem structure, not the one closest to your sector. 6. Ask to see work in whichever service you suspect is their weakest; they'll show you their strengths without being asked.

When's sector experience genuinely required?

There's one exception to all of the above. In regulated fields — health, finance, law, pharmaceuticals — sector experience isn't an aesthetic preference, it's a compliance requirement. What can be claimed, which wording is off-limits, and which approvals are needed are all sector-specific; a team that has never worked inside those constraints can deliver you something beautiful and unusable. The same holds for multi-language, multi-market projects.

Question 3: Are the Services Disconnected, or Part of One Vision?

Branding, web design, social media, and video production handled by four different vendors rarely add up to one coherent brand. Ask whether your prospective partner can carry a single idea across every surface, or whether you'll be the one stitching it together yourself.

There's a hidden cost here: coordination. With four separate vendors, responsibility for brand consistency quietly transfers to you. You're the one carrying the color values from whoever made the logo to the web developer, the video team, and the printer — and you're the one who notices when somebody applies them wrong.

Working with one partner carries its own risk: they may not be equally deep in every discipline. Test it like this — ask to see work in whichever service you suspect is their weakest. They'll show you their strengths without being asked.

Ask whether a brand guide comes with the work. A partner who leaves color, typography, and usage rules documented lets you stay consistent no matter who you work with next.

What belongs in a brand guide?

A brand guide isn't judged by thickness, it's judged by whether it can be applied. A thirty-page document about "the spirit of our brand" does less work than an eight-page one that lists color values, font licenses, and examples of misuse. At minimum, ask for these.

• Logo files: every variation, every format, with clear space and minimum size rules.
• Color values: separate for screen and print, with accessible contrast notes.
• Typography: which typeface, which weights, used where, licensed to whom.
• Misuse examples: images showing what not to do.
• Photography and image language: what fits the brand and what doesn't.
• Application examples: social media, print material, a presentation template.

A common mistake: treating one-stop delivery as a quality guarantee

"Let's get everything from one place" reduces coordination load but guarantees nothing about quality. Some teams are strong in branding and weak in development, or the reverse; buying everything from them spreads that weakness across the whole project. Ask for work samples per discipline even when you're hiring a single partner, and stay open to sourcing the weak item elsewhere.

Question 4: How Transparent Is the Process?

Will you see work in progress, or only a "final reveal"? Will you know why a decision was made, or just be told that it was? Partners who are confident in their process are always happy to show their work.

Transparency becomes real in three places: the schedule, the revisions, and the communication rules. Pin these down at proposal stage:

1. How many stages is the project split into, and what does each stage produce? 2. How many revisions are included per stage, and how is out-of-scope work priced? 3. Where is feedback given — email, or a shared tool? 4. What's the expected response time? What happens to the schedule if I'm slow to reply? 5. If something slips, how am I told?

Be careful with a proposal that sells "unlimited revisions" as a benefit. Unlimited revisions are either already priced in, or a sign of a process where no stage ever truly closes.

How do you give feedback?

Transparency runs both ways; bad feedback breaks a good process. Feedback that works explains the reason, not the preference. Don't write: "Something feels missing, could it be a bit livelier?" Write: "The top section doesn't say what we do; our customers usually ask about price range first, and that information isn't here." Don't write: "Not blue." Write: "Blue is our main competitor's color, and side by side we don't read as different."

One more rule, about form: collect feedback in one channel and send it once. Contradictory notes arriving from three people on three different days delay a project more than any design decision does.

Checklist: process clarity

• Is the output of each stage defined in writing?
• Are the revision count and out-of-scope pricing in the proposal?
• Has a single channel for feedback been agreed?
• Is the schedule impact of your own late replies written down?
• Have you discussed how delays get communicated?

Question 5: What Happens After Launch?

The day a project is delivered isn't the day the relationship ends. Once a website is live, updates, bug fixes, backups, and domain renewals keep coming; you need to know whose job those are while you're still at the contract stage.

Points to settle:

• How many days of free bug-fixing support are included after launch?
• Can you make small content updates yourself, or does every change become a billable work order?
• Is there a maintenance or support package, and what does it cover?
• Will you get training or a handover document your team can actually use?

The real issue after launch isn't cost but dependency, and dependency is what quietly stops a site from ever being updated. A business that has to email its agency for every small copy change ends up either paying extra for months or abandoning the idea of keeping the site current. Both outcomes are bad, and the second one is worse because it's invisible.

How do you surface the recurring costs?

The invisible part of a web project is usually the monthly and annual spend; a single line in a proposal can be hiding several subscriptions behind it. Before you sign, ask about each of these and get the payer written down.

1. Domain renewal: the annual figure and whose account pays it. 2. Hosting or cloud: monthly cost, traffic limits, and what happens when they're exceeded. 3. Plugin, theme, or component licenses: do they renew annually? 4. Font licenses: is there a separate web fee, and up to what traffic tier? 5. Email, form, booking, or payment services: flat fee or per transaction. 6. The maintenance package: what it covers, and how work outside it is priced.

When's a maintenance package unnecessary?

Not every site needs monthly maintenance. For a statically published brochure site that takes no payments, has no user logins, and is rarely updated, a monthly package is usually an unnecessary expense; buying hourly support when something comes up is more economical. Conversely, on sites that take payments, host memberships, publish frequently, or carry regulatory obligations, maintenance isn't a luxury, it's a security requirement.

Question 6: Who Owns the Files, Accounts, and Rights?

At the end of the engagement, the source files, the domain, and the accounts should be yours. Put it in writing before the contract, not after delivery — handovers requested later are where most disputes start.

What to ask is short and unambiguous:

• Whose name is the domain and hosting account registered under? Who receives the invoices?
• Will you receive editable source files for the logo and design work?
• Will you have access to the code repository and the production environment?
• Under whose license were the fonts and stock images bought, and for what usage?
• Who holds admin rights on the analytics and advertising accounts?

Font and image licenses get skipped most often. A typeface without commercial rights, or an image used under the wrong license, can arrive as an invoice years later.

What should you have in hand at handover?

Handover isn't someone sending a link; it's a list being completed. In the project's final meeting, confirm each of these is genuinely in your possession.

• Admin access to the domain registrar account, with the account tied to your own email.
• Hosting and production access, the backup method, and where the backups are stored.
• Ownership of the code repository, or at minimum admin-level access to it.
• Design source files, in editable formats, together with the font files.
• Admin rights on analytics, search console, and advertising accounts.
• A list of third-party services used, whose accounts they are, and their renewal dates.

A common mistake: registering the domain to the agency's account

The most widespread and most belatedly discovered mistake is having the domain and hosting registered under the agency's own account. That creates risk even with no bad intent involved: if you part ways, or the agency closes, you can't reach your own domain. Register it from the outset in your business's name under a company email address, and give the agency admin access only. If your domain isn't registered in your name, your brand isn't yours.

What Should You Look For When Comparing Proposals?

Compare proposals by scope, not by the total at the bottom. The price gap between two quotes is usually a difference in scope rather than a difference in quality. One includes page count, copywriting, photography, and post-launch support; the other doesn't.

Before you put them side by side, equalize these: the number of pages or assets delivered, who supplies content and imagery, the number of revisions, the schedule, the post-launch support window, and any recurring costs. A comparison made without equalizing those six items will mislead you.

How do you compare three proposals, step by step?

1. Rewrite each proposal using your own scope list rather than their language, with the same items in the same order. 2. Mark every item present in one proposal and missing from another, and ask the missing side to price it. 3. Add recurring costs into a first-year total; monthly charges quietly change the headline number. 4. When comparing timelines, write down what's expected from you; a fast-looking schedule may assume weekly feedback. 5. Compare the payment plans: deposit percentage, interim payments, and what the final payment is tied to. 6. Look at price last; a price compared before the items are equalized makes the decision harder, not easier.

Warning signs

• A partner who quotes a price before hearing the brief is probably selling a template.
• Unverifiable performance figures and percentages with no source.
• SEO promises of a first-place ranking — search results can't be guaranteed.
• Pressure to sign against a deadline that isn't real.
• A proposal that covers scope in one sentence instead of itemizing it.
• Reluctance when you ask to speak to a reference client.

When's the cheapest proposal the right call?

We're not saying you should always pick the most expensive quote. If scope is genuinely equalized, the team and process are clear, and the delivery list matches, the lowest price is a reasonable choice. And if your budget is tight, reducing scope to work with a good team beats preserving scope by hiring a weak one. What's dangerous isn't cheapness — it's choosing the cheap option without knowing what's missing from it.

How Do You Manage the First Month After Deciding?

Choosing the right partner is half the job; the project's first month usually determines the rest of the outcome. During this period, the preparation on your side can matter more than the capability on theirs.

Get these in place in the first four weeks:

1. Appoint a single point of contact; all internal opinions go to them, and one voice goes out. 2. Write the content and image delivery schedule; if copy and photography slip, the project slips. 3. Fix the feedback rhythm: which day, which channel, within how many hours. 4. List the people who approve, and keep that list as short as you can. 5. Agree up front how out-of-scope requests get handled; every new idea is a decision point. 6. When you see the first stage's output, stop and assess it; this is the cheapest moment to correct direction.

None of this removes the need for good work, but it removes most of the reasons good work arrives late. A project that reaches its second month with one contact, one feedback channel, and a short approval list is already running better than the average, whoever is doing the design.

A project's most expensive delay almost never happens in design; it happens in the approval chain.

The Real Question Isn't "Agency or Not"

The real question is fit. We don't take on every project, and when the fit isn't there we say so in the first conversation — not to seem exclusive, but because good creative work requires real alignment between a founder's vision and the people building it. If you're currently asking "which agency should we hire?", the more useful question is which of the answers to the six questions above actually matches what you need.

There's a practical way to measure fit: count how many questions you're asked in the first meeting. The side trying to understand you asks more questions; the side trying to sell itself gives more answers. The second one isn't necessarily a bad partner, but a team that hasn't learned your business in the first meeting usually hasn't learned it by month three either.

To be direct about how this works on our side: before starting, we write down the problem that needs solving. If we can't write it down, we don't take the project. We itemize scope and talk openly about what falls outside it instead of burying it. At delivery we hand over source files, account access, and brand rules — we don't defend a delivery model that leaves anyone dependent on us. If those terms don't suit you, it's better for both of us that you find out in the first meeting rather than the third month.

We'll say one more thing plainly: we aren't the right answer to every job. When a project is a single deliverable with no continuity and needs one narrow specialism, and we think a freelancer would be faster and cheaper, we say so. Not taking a project is cheaper for both sides than managing one that should never have been taken.

Frequently Asked Questions

How long does a website project take?

It depends on scope, and you should ask for the timeline stage by stage. The biggest variable is usually not the agency but when content and images arrive from you; projects without ready copy and photography stretch out through waiting far more than through design.

Does sharing my budget upfront weaken my negotiating position?

In practice the opposite happens. When the range is unknown, the other side guesses at scope and you end up with proposals that can't be compared; when it's known, the proposal is built around the best possible result at that number.

Can an agency guarantee we'll rank first?

No. Rankings can't be guaranteed, because results depend on competition and algorithm variables outside anyone's control. A responsible partner commits to measurable technical and content improvements, not to a position.

Does it make sense to work without a contract?

Not even on small jobs. A contract isn't only payment protection; it defines scope, revision counts, the schedule, the handover of source files, and intellectual property. Most disputes come from unwritten assumptions rather than bad intent.

Should I work with a team in another country?

It depends on the work. For purely digital deliverables, geography rarely matters; for location photography, video shoots, or print supervision, a local team is a clear advantage. Time zones and language shape the rhythm of day-to-day communication more than people expect.

Is a paid discovery or strategy phase worth it?

It depends on the size of the project. On work with unclear scope, many stakeholders, or several disciplines, a separately priced discovery phase usually pays for itself by preventing the project from starting with the wrong scope. On a small, well-defined job, a separate discovery line item is an unnecessary cost.

I want to change agencies — what should I watch for?

The critical part of any switch is access. Before starting with a new team, confirm you hold admin rights on the domain, hosting, code repository, analytics, and advertising accounts, and take possession of the source files and brand guide. A handover made without those complete forces the new team to spend its first weeks on technical archaeology.

Fixed price or hourly — which is better?

When scope is clear, a fixed price protects you, because the other side carries the risk. When scope is undefined or will take shape through discovery, hourly or staged work is more realistic; demanding a fixed price on undefined work forces the other side to price the worst-case scenario and locks you into a needlessly expensive quote.