# At a first meeting with web design companies, how can the same materials help compare their answers?

Source: https://www.jvds.cn/en/share/website-design/first-agency-interview-common-brief
Language: en
Published: 2026-10-08
Author: JVDS Design Studio

Before meeting web design companies, give each the same business background, page samples, and problems to solve, then compare how they explain scope, dependencies, and acceptance. This suits companies making an initial supplier selection. It makes answers comparable, but public work and verbal statements still require verification and are not direct proof of project capability.

## A shared information package is more effective than repeated introductions

Explain why the website is being built or redesigned, who its main visitors are, and the most important task they need to complete. Attach a current page or real material sample and explain which content can already be public and which needs departmental review. List the pages and functions desired for the first release and flag uncertainties.

This information does not have to be complete from the start. Questions such as ‘Do we need multiple languages?’ and ‘Are products updated frequently?’ help reveal how suppliers probe the conditions. Do not conceal content preparation, system accounts, or long-term maintenance merely to make quotations look attractive; otherwise suppliers will answer on different assumptions. See [When enterprises look for website design companies, what exactly should they compare? If one only focuses on whether a case looks good or not, it is very easy to fall into traps during the development and delivery stages](https://www.jvds.cn/en/share/website-design/choose-web-design-agency-vendor) for related checks.

![A shared information package is more effective than repeated introductions](https://www.jvds.cn/upload/2026/1004/g3/G005-i1.webp)

A shared information package is more effective than repeated introductions · Concept illustration

## Use the same task to assess the quality of answers

Ask suppliers to explain a specific route: a visitor finds a service, assesses its applicability, then submits contact information. Ask which pages, materials, and functions are needed, what the company supplies, and what the service includes. This produces more verifiable answers than the broad question ‘Are you professional?’ See [How to Write a Design and Website Development RFP](https://www.jvds.cn/en/share/user-experience/design-website-rfp-template) for related checks.

For example, when asked ‘What if product information changes frequently?’, one supplier may simply say there is an administration interface, while another asks about fields, editors, and approval procedures. The latter answer is more informative, but still needs an actual demonstration. A detailed answer is not evidence that a function is complete; buyers should record how it will be verified next.

Public work can show visual and page behavior. Verify that it is accessible, which portions the supplier handled, and whether it may be disclosed. A complex function in a portfolio does not prove the supplier performed all development and business-system integration. Nor should suppliers be asked to disclose customer secrets for projects they cannot discuss publicly.

![The same task is used to assess the quality of answers](https://www.jvds.cn/upload/2026/1004/g3/G005-i2.webp)

The same task is used to assess the quality of answers · Concept illustration

## Turn meeting notes into comparable responses

Save clear summaries that retain the meaning of each answer. For each question, record the proposed scope, prerequisite materials, company responsibilities, verification method, and unanswered points. Suppliers may use different terminology, but these common categories help distinguish different methods from omitted scope.

Suppose both companies promise content updates, but one allows only changes to existing pages while the other includes adding product entries. Ask whether categories, images, and ordering operations are included. Do not record both answers simply as ‘Has a CMS.’

When discussing a corporate website with [JVDS Design Studio](https://www.jvds.cn/en), use the same information package to confirm the boundaries of planning, design, and development. Agree separately on CMS, multiple languages, launch, and maintenance items instead of allowing service names to replace specific explanations.

![Meeting notes are organized into comparable responses](https://www.jvds.cn/upload/2026/1004/g3/G005-i3.webp)

Meeting notes are organized into comparable responses · Concept illustration

## End the meeting with evidence for the next step

The first meeting need not settle every technical choice, but it should produce a clear list of additional materials and a way to obtain subsequent answers. For uncertain functions, agree on a demonstration, sample page, or written explanation. Success means finding the scope and prerequisites for the same key question in each supplier's response, rather than a string of positive comments.

In reviews, first check coverage of necessary tasks, then discuss visual suitability and ways of working together. A lower total price does not mean the scope is identical, and fluent explanations should not distract from unanswered questions. Retaining unverified items in the procurement record makes the next discussion more specific.

## Frequently asked questions

### Can we meet suppliers before writing a complete requirements document?

Yes. Prepare at least the business objective, one real content sample, and the issue you most want to solve, and identify uncertainties. Use the first meeting to clarify scope, then add confirmed outcomes to the requirements document.

### Does refusing to produce a complete design for free indicate inadequate capability?

No. Complete design normally involves actual work. Initial selection can consider verified public work, understanding of requirements, and delivery explanations. If a trial is needed, agree separately on its scope and usage rights.