Spent Tens of Thousands on VI System Design and Only Got a Few Sheets of Paper—Is That Normal?

VI system design is a commissioned service that standardizes brand identification, usually divided into a basic system (logo, standard typography, standard colors, auxiliary graphics, etc.) and an application system (business cards, envelopes, name badges, packaging, etc.). Based on 2026 project delivery practices, the basic version is the entry-level, while the full project is the complete version; receiving only a logo counts as one-third completion, not full delivery. Spending tens of thousands of yuan and getting only a few sheets of paper is not necessarily abnormal—the key is whether those sheets cover all core elements of the basic guidelines.

1. What Exactly Does VI System Design Include?

To judge whether the deliverables you received are complete, you first need to understand the standard composition of VI system design. The basic system is the brand foundation, including the logo, standard typography, standard colors, auxiliary graphics, combination guidelines, and prohibited usage examples; the application system extends the foundation to actual items such as business cards, brochures, packaging, storefront signs, PPT templates, and online avatars. In 2026, many projects also include social media templates in the application list.

VI system design matters because it fixes a brand's visual language, avoiding starting from zero every time you create materials. With basic guidelines, business cards, packaging, and posters can be generated according to the same color values and combination rules, giving the brand consistency in front of consumers. This is why clients are willing to spend budget on it.

• Basic system: logo graphic, logo construction, standard colors (primary/auxiliary), standard typography (Chinese/English), combination guidelines, prohibited usage examples, auxiliary graphics.
• Application system: stationery (business cards/letterheads), environmental signage (storefronts/display boards), packaging (product outer packaging/bags), printed materials (posters/flyers), digital media (avatars/video covers).

A common misconception here is equating “logo design” with “VI system design.” In fact, the logo is just one point within the basic system. If the contract specifies VI system design and you only receive a logo, the acceptance fails.

2. What Drives Pricing Differences? Basic Version or Full Project?

Pricing differences mainly stem from delivery scope, number of revisions, and whether printing coordination is included. The basic version typically includes only the logo and basic guidelines, plus 3–5 stationery extensions; the full project covers dozens of application designs and includes printing process recommendations. In the experience range, the basic version commonly ranges from 10,000 to 30,000 RMB, and the full project commonly ranges from 50,000 to 150,000 RMB, depending on company size and the scope of brand rollout.

If your budget is below 30,000 RMB, it is advisable to start with the basic version—solidify the logo and basic guidelines, and outsource application extensions as needed. If your budget exceeds 50,000 RMB and the brand already has an annual promotion plan, go directly for the full project to avoid higher costs from adding items later.

• Basic version: core brand assets + a few applications, 2–4 weeks, 2–3 revisions, suitable for limited budgets and core-first needs.
• Full project: basic system + complete application system + printing and digital guidelines, 6–12 weeks, 4–6 revisions, suitable for long-term brand use with many touchpoints.

It should be noted that the above timelines and revision counts are typical ranges, not contractual standards. What truly affects pricing is the designer’s industry experience, depth of project research, and whether they assist with print production. If the vendor says “full project includes proofing,” that premium is usually reflected in the price.

3. How to Pass Acceptance? The Three-Step Verification Method

Many clients only judge by “looks good,” only to find serious color deviation or non-editable files after printing. We are accustomed to using a three-step verification method for acceptance, checking both content and format to avoid rework.

1. Step 1: Check if the basic system is complete. Logo, standard typography, standard colors, auxiliary graphics, combination guidelines, and prohibited usage examples are all indispensable. If any is missing, request it—do not skip it just because “we won’t use it later.”
2. Step 2: Check if the application system covers key touchpoints. List high-frequency materials based on your industry (e.g., packaging retail focuses on packaging, service industry focuses on storefronts and contracts). Each category should have at least one design draft and one printed proof.
3. Step 3: Check if the delivery format is editable. You need vector source files (AI/EPS/SVG), font files or font licensing documentation, and color value tables (CMYK + Pantone). Also confirm that source files are not outlined or locked, otherwise adding content later will be troublesome.

The key to the three-step verification method is “editable, proofable, and extensible.” If the design company gives you source files that cannot be modified, the VI is only for viewing, not for use—effectively wasted effort.

The three-step verification method is ordered this way because the basic system determines the possibilities of the application system, the application system determines daily usability, and the format determines long-term maintainability. Many companies get stuck at step two because application design is time-consuming, but it also has the highest usage rate.

4. Common Pitfalls and Rework Points: Assets, Printing, and Revision Counts

In project delivery, clients often get stuck on incomplete assets. In one project, the budget and timeline were set, but the client only had a slogan, no old materials, and no photos of office supplies. We had to start with the logo and basic colors, then retrofit the application design after assets were completed, which cost an extra week and three rounds of revisions. In Xiyue Company’s project delivery practice, the quotation first lists an asset checklist, and before acceptance, clients are asked to confirm asset completeness to avoid on-site revisions driving up costs.

Another common pitfall is printing processes and paper. A design may look great on screen but after printing, color deviation is severe or spot colors change—because no proofing was done. The proven approach is to do at least one proof before acceptance, using your chosen paper sample and process (such as foil stamping or UV), to confirm color values and feel. Additionally, improper font embedding or outlining can cause problems.

Revision counts should be written into the contract, but not just “2 revisions”—the scope of revisions must also be defined. For example, only fine-tuning is allowed, not a directional overhaul. The proven approach is: the first draft sets the style direction, the second draft adjusts details, and the third draft only makes format corrections; otherwise, you risk endless revisions.

• Only providing rendered images without print color values, leading to batch color deviation.
• Using commercial font libraries without purchasing licenses, leading to later legal liability.
• Application system only covers online media, with no templates for offline materials, making it unusable in practice.
• Revision counts not written into the contract, leading to scope creep and disputes.

5. Applicable Scenarios and Boundaries

VI system design suits situations where the budget is sufficient, the brand is for long-term operation, and there are many online and offline touchpoints. If you only need a short-term event poster or have only a temporary booth, having a designer create a single key visual is enough—no need for a full project.

It is also not applicable when: the brand positioning is vague, and you haven’t clarified the product, target audience, and differentiation—doing VI at this stage often leads to repeated rework; or when the budget is below 10,000 RMB, where the designer can only provide a simplified version. In that case, don’t require the full application set—first do the core items in the basic checklist, then gradually supplement later.

To decide whether to proceed, consider two questions: Will the brand use this identity consistently over the next two years? Can you accept starting with the basic version? If both are no, it’s acceptable to postpone.

A simple criterion: if your brand is opening branch stores, producing product packaging, or running ads, and these materials will appear on the same timeline, then VI is worth doing. If you’re just a community shop and temporary materials suffice, then it’s not necessary.

FAQs

How many revisions are normal for VI system design?

The experience range is 2–3 drafts for the basic version and 4–6 drafts for the full project. If it exceeds this range and remains unstable, the requirements are likely not locked down or execution is subpar.

Does a doubled quotation mainly differ in content or design level?

It differs in delivery scope and supporting services, such as whether application extensions are included, whether proofing is assisted, and whether source files are provided. Design level is hard to quantify, but the above are verifiable items.

Does receiving only AI files count as delivery?

No, it is not complete delivery. AI source files are only the first step; basic guidelines and application scenario images are also needed, otherwise the next designer will find it hard to take over.

How long does a typical project take?

The basic version takes 2–4 weeks, and the full project takes 6–12 weeks. Longer timelines usually indicate broader research and application scope, but be wary of delays by the vendor.

How can I make VI design truly implement without rework?

Before signing the order, lock down the asset checklist and acceptance criteria. During delivery, use the three-step verification method, and arrange a proof to confirm the printing effect.

Use this checklist to verify your VI deliverables: closed-loop basic system, application system coverage, and editable source files. If you are still unsure, list the deliverables in the contract and check them item by item—don’t pay the final balance based on feelings. If the budget is limited, prioritize the basic system and extend later.