A branding agency presents a considered identity. The client approves it and asks in the next meeting, “Can you do the website as well?” Saying yes makes sense: the relationship already exists, and keeping creative direction together can improve the result. Trouble begins when the website becomes a price line before it becomes a scope of work.
A creative director does not need to write code. They do need to know which questions to ask, which promises they can support, and when to involve the person who will build and maintain the site. A capable technical partner extends the agency’s offer without asking it to give up its specialty.
A website is more than a brand identity exported to a browser
A brand system defines essential decisions: voice, type, color, composition and visual judgment. A website adds information architecture, variable content, forms, mobile navigation, accessibility, performance, analytics, search and maintenance. Five approved mockups do not explain who will update the content or what happens when an integration fails.
“We need a five-page website” is therefore not a sufficient brief. Five pages might mean a simple editorial site or an operation with two languages, bookings, editable profiles, lead capture and access rules. The difference changes the budget, schedule and platform.
The lowest quote may describe a different project
Getting three development quotes is reasonable. Comparing only the totals without comparing deliverables and responsibilities is not. The cheapest supplier may be quoting exactly what was provided: a design image and a list of pages. Migration, redirects, mobile testing, content revisions, accessibility, measurement, training and post-launch support may be absent because nobody asked for them.
The difference reappears as change requests, work the agency absorbs, or a difficult client conversation. The agency has put its reputation behind a budget that never described the full job.
Before selecting a supplier, ask each candidate to state assumptions, exclusions, dependencies and acceptance criteria. If one proposal includes configuration and testing for forms and another merely says “contact form,” they are not comparable yet.
Six decisions before sending a number
A scoping conversation can start with six questions:
- What must the site accomplish? “An online presence” is too broad. Is the job to generate enquiries, support a sales team, sell, take bookings or serve existing customers? How will the client recognize that it works?
- Who supplies and approves content? Copy, photography, translations, legal text and product details affect the work. Record who produces them and when they will be ready.
- Which system fits the operation? WordPress, a visual platform, a store and a static site represent different operating choices, not a designer’s taste. Consider editing, integrations, ongoing cost and who will run it. Our platform decision guide goes deeper.
- What already exists? Domain, hosting, email, analytics, indexed URLs, content and access. A redesign may need an inventory and redirects. SEO begins with the site’s structure and continuity, not a bag of keywords added at the end.
- What happens after launch? Updates, backups, licenses, support, content changes, account ownership and response times need decisions and often a separate budget.
- Who handles technical conversations with the client? Decide whether the specialist joins meetings under the agency’s brand, advises the team behind the scenes, or owns a defined part of the discussion. Protect the client relationship by agreeing on the arrangement early.
It also helps to define what “SEO” means in the proposal. Reviewing titles, structure, indexing, internal links and launch measurement is one scope. Market research, content production and ongoing visibility are another. AI answers in search do not turn either scope into a switch. Google still identifies indexing, helpful content and technical clarity as fundamentals for its AI search features.
A proposal that protects the relationship
Present a clear core—discovery, architecture, approved design, implementation, testing and launch—and separate modules that depend on open decisions. Content production, translations, integrations, migration, ongoing SEO and maintenance may each need their own scope. State who supplies what and when approval happens.
Build in a technical review before committing to a final build price if important answers are missing. “We can quote the design now and confirm development after reviewing content, platform and integrations” is more credible than a fixed price that depends on someone solving unknowns without time or budget.
If the agency subcontracts, its margin needs to cover direction, coordination, reviews and accountability to the client. Buying the least expensive hours and reselling them without a process rarely produces a dependable web offer. A specialist who understands the agency’s standards can become a repeat collaborator rather than a new supplier search on every job.
Where Smallroom fits
I work with agencies and studios that want to keep the creative relationship and deliver a website worthy of it. I can help review the brief, define platform and scope, build the site and take on technical SEO, hosting or support as agreed. The collaboration can sit behind your brand and adapt to the way your team works.
When a client asks, “Do you build websites too?”, you can answer yes with a process behind it. If a project is on your desk, let’s talk before the quote goes out or see how our white-label development partnership works.