A proposal containing only a price and a timeline gives a CEO or founder two numbers without the context needed to evaluate either one. Price without scope tells the client what the engagement costs but not what it covers, and a timeline without dependencies tells the client when work finishes but not how disciplines connect to get there. brand design agencies san Francisco teams evaluate seriously produce proposals covering four elements beyond price and timeline, each one answering a question the numbers alone leave open. Reviewing a proposal against these four elements separates agencies that plan thoroughly from those that present confidently without the substance behind it.
Scope written per discipline
Discipline-level scope states exactly what each team in the engagement will produce, in what form, and to what standard. A proposal covering brand, UX, and web design under one combined scope description gives the client no way to verify that each discipline received adequate resourcing or that the outputs from each discipline match what the project requires.
Brand scope covers the identity system components the engagement will produce, naming each deliverable and the format it arrives in. UX scope covers the research methods the team will use, the number of participants, and the outputs the research produces before interface design begins. Web design scope covers the number of pages, the template system, the responsive breakpoints, and the handover format that the development team receives.
Discipline outputs are listed separately
Each discipline in a multidisciplinary engagement produces its own set of outputs, and a proposal lists them separately so the client knows exactly what they will hold at the engagement’s close.
- Brand outputs – Logo files in vector formats, colour system documentation, typography guidelines, iconography, and brand usage rules packaged for internal teams and future vendors.
- UX outputs – Research findings report, user journey maps, wireframes for key flows, and usability test results documenting what was tested and what each finding produced.
- Web design outputs – Design files organised by component, responsive specifications for every breakpoint, interaction documentation, and a handover package that the development team can implement without agency involvement.
- Content outputs – Messaging framework, page-level copy for all pages in scope, and voice guidelines covering how the brand communicates across every channel the engagement touches.
Separate output lists tell the client which team produced what and confirm that no discipline delivered less than the brief required.
Success measures are named first
Success measures state what the engagement must achieve in terms that both sides can evaluate at the close, removing the subjectivity that price and timeline leave in place when they stand as the only criteria. A proposal naming success measures first tells the client that the agency understands the engagement’s purpose rather than only its deliverable list.
Measures get set per discipline rather than as a single engagement-level metric. Brand success gets measured against whether the identity system covers every channel the business uses and whether internal teams can apply it without agency assistance. UX success gets measured against whether research findings changed interface decisions and whether usability testing showed task completion above the threshold set at briefing. Web success gets measured against page speed benchmarks, responsive behaviour across specified devices, and handover completeness.
A proposal covering these four elements gives a CEO or founder the information needed to evaluate an agency’s capability before committing rather than discovering its limits after the work begins. Price and timeline tell the client what the engagement costs and when it ends, but scope, outputs, measures, and ownership tell the client what the engagement actually is.
