# Why Two Website Quotes for 100 Product Pages Cannot Be Compared Directly Source: https://www.jvds.cn/en/share/website-design/product-page-quote-work-units Language: en Published: 2026-10-08 Author: JVDS Design Studio Two proposals both specifying “100 product pages” may mean different things: one may cover entering 100 prepared records, while another includes different templates, material preparation, and language content. Before comparing them, define template structures, product records, language scope, and material preparation separately, then confirm each party’s responsibilities. Equal page counts do not establish equal deliverables. A company can give suppliers the same set of actual materials and ask how they will design the pages, who organizes the content, who confirms facts, and who enters it. Establish the same task scope before discussing cost. Prices for someone else’s website are unnecessary for determining what this project should cost. ## Template Counts Describe Different Information Structures A template is a page structure that multiple products can use. Models with similar information may share one structure, while products with substantially different specifications, combination relationships, and download tasks may require different presentations. One hundred URLs do not necessarily mean 100 independent designs, nor do they imply that one template can cover everything. Ask suppliers to use actual samples to identify shared fields and exceptions. One product type may primarily present specifications, another may need compatibility relationships, and another may explain configuration differences. Calling all of them “product details” is insufficient. Without samples, a generic template name makes scope difficult for the company to assess. Also separate template design from its maintainable implementation. Specify whether the proposal provides only visual designs or also website development, field configuration, and device adaptation. A template name alone does not establish that all design, development, and content work is included. The [website design deliverables checklist](https://www.jvds.cn/en/share/website-design/website-design-deliverables-checklist) can help verify these items. ![Conceptual miniature scene showing how product structure samples determine template scope](https://www.jvds.cn/upload/2026/1004/1791060538148-698210.webp) Conceptual miniature scene showing how product structure samples determine template scope ## Count Product Records and Languages Consistently A product record is the specific object to be presented, which may be a series, a model, or an independent configuration. Business staff should first confirm how customers identify each object, then define the record unit. If one party counts by series and the other by individual model, both writing 100 does not describe the same catalog. Even when a group of products shares a template, every record still needs images, specifications, text, and attachment relationships. Shared structures reduce repeated design, but do not automatically eliminate entry and verification. If quantities remain unconfirmed, specify the initial list and items to be supplied later. Do not leave the supplier to guess all historical products. List language scope separately. Complete Chinese content with unreviewed English materials is a different starting condition from having both languages ready. Ask how many templates and records are covered, which languages are included, and who handles translation, review, entry, and version relationships. Do not estimate all work by simply multiplying URL counts. Two languages may share some images and product identities, but their text, attachments, and publication conditions can differ. Scope must identify actual objects. “Multilingual support” cannot replace a specific initial content scope. ## Does “Client-Supplied Materials” Still Include Preparation Work? Content supplied by a company may be approved copy, or it may be old web pages, multiple PDFs, specification sheets, and sales documents. Turning raw materials into web content requires identifying objects, harmonizing wording, finding gaps, and confirming applicability. Receiving an archive file does not mean the materials are ready for direct entry. Mark materials separately as approved and usable, requiring preparation, or missing. If a product group contains both complete content and objects requiring specifications to be extracted and combination relationships explained, the preparation tasks differ even if they ultimately share a structure. Describing everything as “copying a page” is inappropriate. Separate organization from confirmation of technical facts. A supplier can organize content as agreed, but the company’s responsible staff still need to verify specifications, performance, certifications, applicability, and permission to publish. Copy preparation does not mean the supplier will invent missing product data for the company. Images and attachments also require different preparation work. Selecting and cropping usable existing images differs from photography, explanatory illustration, or reworking drawings. Attractive images on a reference website do not establish that equivalent asset production is included in this project. ![Conceptual miniature scene distinguishing raw material preparation from entry of individual product records](https://www.jvds.cn/upload/2026/1004/1791060538148-763869.webp) Conceptual miniature scene distinguishing raw material preparation from entry of individual product records ## Use Varied Samples to Make Both Proposals Answer the Same Questions Select typical products, products with unusual structures, and products with incomplete information, and give both suppliers the same samples. Ask each to explain the templates used, records currently counted, materials usable as supplied, who fills gaps, and who handles initial entry and finished-page checks. Then apply their answers to the company’s actual catalog. Identify which types the samples cover and which exceptions have not yet been supplied. A small demonstration cannot represent a review of the entire catalog, and types that may be added in the future should not automatically become part of the current scope. The comparison can be recorded in a few clear paragraphs. For example, if one proposal includes only templates and demonstration records while another also covers initial material preparation, the difference is already clear and cannot be judged by page counts alone. Whether to add scope depends on whether the company has someone to handle the remaining work. Budget discussions can refer to [factors affecting corporate website design budgets](https://www.jvds.cn/en/share/website-design/enterprise-website-design-cost-guide). Identify differences in work first, then assess each proposal under its own conditions. Do not present a particular counting method as a standard industry pricing rule. ![Conceptual miniature scene using the same product materials to compare proposal scopes](https://www.jvds.cn/upload/2026/1004/1791061293684-568095.webp) Conceptual miniature scene using the same product materials to compare proposal scopes ## Specify Responsibilities, Changes, and Completion Criteria Confirm the workflow: who supplies raw materials, who organizes the content for use, who verifies facts, who enters it, who approves publication, and who checks the final pages. One person may perform multiple roles, but “both parties will cooperate” must not hide an unassigned stage. If the company will enter further content itself, delivery should include completed samples, applicable formats, and real operating instructions. Have the actual editor complete a similar task. Handing over an account does not resolve every content-preparation responsibility. The CMS and material scope can be confirmed further using [corporate website CMS selection and maintenance conditions](https://www.jvds.cn/en/share/website-design/how-to-choose-cms). Adding a model that uses an existing structure differs from adding a special template. Supplying approved text differs from reorganizing an entire set of material relationships. For changes, identify the specific object and responsibility, then follow the agreement. Do not give an unconfirmed universal pricing formula. Describe excluded items as actual work too: whether historical models, English attachments, special charts, or material photography need later handling. For unknown materials, state current assumptions and responsibility for supplying more. “Any product can be added” cannot replace checking. The completion criterion is that both parties can point to the same catalog and explain what templates, records, languages, and preparation each include. Samples and exceptions should be traceable, with owners for approved content and finished-page verification. Only then does the page count become one part of the scope rather than a misleading overall label. ## Frequently Asked Questions **Do 100 models always need 100 independent designs?** No. That depends on the information structure and user tasks. Count templates and records separately before determining the design scope. **Does sending PDFs eliminate further content preparation?** It depends on whether they can be used directly on the website. Organization, image processing, and fact confirmation may still be necessary. The existence of files does not prove the materials are complete. **Is adding a second language simply copying the first?** Do not assume so. Translation review, attachments, publication conditions, and maintenance relationships may create new tasks. Check the actual scope.