Sinh Vũ Studio
Connect with Sinh Vũ
Package 04 · Long-term operations

Keep the brand consistent for years

You already have a brand, but many departments, dealers and partners make materials, so each looks different. This package sets up how the work is done so the brand stays consistent over the years.

Get a proposal for this packageSee the steps
  • from 6 monthstimeline
  • 4parts of work
  • 14approvals by you
  • 11items you receive
  1. 1Brand operating system
  2. 2Brand guidelines
  3. 3Digital design system
  4. 4Monthly brand care
The steps

Part by part, approved step by step

When a step needs approval, Sinh Vũ waits for you to approve before going on. Tap each step to see what Sinh Vũ does and what you approve. Weeks are estimates, and some parts run in parallel.

Steps with this mark need your approval.

  1. Part 1 · Weeks 1 to 6

    Brand operating system

    Organise the file library, rules and ways of working, so the company keeps the brand consistent without depending on one person.

    What you prepare: One person who will look after the brand after handover. This package needs that person to work.

    1. Bring files into one placeYou approve

      Every file in one library, sorted and named consistently.

      Sinh Vũ does

      Gather every brand file scattered around into one library, with consistent naming.

      You approve

      Approve how the library is organised.

    2. Write the rulesYou approve

      Rules stating clearly who does what.

      Sinh Vũ does

      Set who may upload files, who approves new materials, what happens to old files.

      You approve

      Approve the rules.

    3. Set up daily ways of workingYou approve

      Requesting files and approving materials now runs in the company.

      Sinh Vũ does

      Set up the common tasks: requesting files, approving new materials, updating versions.

      You approve

      Approve the way of working.

    4. Trial with one teamYou approve

      Trial results, to decide whether to expand.

      Sinh Vũ does

      Let one team try it first. Expand only when that team uses it well.

      You approve

      Approve the trial results.

    5. Expand and trainYou approve

      Every department works the new way, each with an owner.

      Sinh Vũ does

      Roll out department by department, train people and choose an owner in each.

      You approve

      Accept and receive the handover.

    You receive
    • Organised brand file library
    • Written brand management rules
    • Guides for each group of users
  2. Part 2 · Weeks 6 to 8

    Brand guidelines

    A guidebook on using the logo, colours, type and images, so everyone in the company uses them correctly.

    What you prepare: All the logos, design files and materials you have today.

    1. Gather materials and plan contentsYou approve

      List of what exists and the guidebook contents.

      Sinh Vũ does

      Gather what the brand has today and plan the contents of the guidebook.

      You approve

      Approve the contents.

    2. Write the usage rulesYou approve

      Draft rules with right and wrong examples.

      Sinh Vũ does

      Write rules for using the logo, colours, type and images. Each rule has examples of do and do not.

      You approve

      Approve the draft.

    3. Set who may edit the guidebook

      Section stating who may edit, how, and who approves.

      Sinh Vũ does

      Write down who may edit it and how, so the guidebook stays correct when the team changes.

      You approve

      No approval needed at this step.

    4. Handover and guidanceYou approve

      Finished guidebook, the owner knows how to use it.

      Sinh Vũ does

      Deliver the guidebook with its files, show the owner how to look things up and update it.

      You approve

      Accept and receive the handover.

    You receive
    • Screen version with a clickable contents page
    • Print version
    • Accompanying source files
  3. Part 3 · Weeks 8 to 12

    Digital design system

    A shared set of interface parts for your website and apps, so new screens are quick and consistent.

    What you prepare: Access to the design files and code in use.

    1. List what existsYou approve

      List of every interface part in use.

      Sinh Vũ does

      List every interface part in use, such as buttons, input fields, cards, and where each is used.

      You approve

      Approve the list.

    2. Set shared rulesYou approve

      Shared rules for colour, type and spacing.

      Sinh Vũ does

      Set shared rules for colour, text size and spacing. Every later part follows them.

      You approve

      Approve the shared rules.

    3. Build one sample partYou approve

      One sample part agreed by both sides.

      Sinh Vũ does

      Build one sample part in full so designers and developers review and approve it together.

      You approve

      Both sides approve the sample part.

    4. Build the full setYou approve

      Full set of interface parts, with usage notes.

      Sinh Vũ does

      Build the remaining parts, each with notes on when to use it and when not to.

      You approve

      Approve the full set.

    5. Handover and trainingYou approve

      Your developers build new screens with the set on their own.

      Sinh Vũ does

      Hand over and train your team. Developers can rebuild a screen using only this set.

      You approve

      Accept and receive the handover.

    You receive
    • Library of interface parts
    • Specification sheet developers can use directly
    • Guide to using each part
  4. Part 4 · Monthly after that

    Monthly brand care

    Sinh Vũ handles your design tasks every month and keeps the brand consistent.

    What you prepare: One person on your side to stay in touch with Sinh Vũ.

    1. Monthly workYou approve

      List of the month's work and source files of each task.

      Sinh Vũ does

      Take the month's design tasks, follow the existing rules, check before anything is posted or printed.

      You approve

      Accept each task.

    You receive
    • Monthly list of work done
    • Source files of each task
Acceptance

Each part is done when it meets every point

These points go into the proposal. You check each one, and sign off the part once all are met.

  1. Part 1 · Weeks 1 to 6

    Brand operating system

    Signed off at stepExpand and train

    You receive
    • Organised brand file library
    • Written brand management rules
    • Guides for each group of users
    Done when
    • Management rules are written down and signed.
    • The pilot group can follow them without asking.
    • Each group has been trained and has a lead person.
    • Files in the library are easy to find thanks to the agreed naming.
  2. Part 2 · Weeks 6 to 8

    Brand guidelines

    Signed off at stepHandover and guidance

    You receive
    • Screen version with a clickable contents page
    • Print version
    • Accompanying source files
    Done when
    • A non-designer reads the guidebook and gets it right without asking.
    • Every file type listed is there, each labelled with what it is for.
    • The do and don't pages show real image examples, not just words.
  3. Part 3 · Weeks 8 to 12

    Digital design system

    Signed off at stepHandover and training

    You receive
    • Library of interface parts
    • Specification sheet developers can use directly
    • Guide to using each part
    Done when
    • Each interface part has every agreed state.
    • Each part has a note on when to use it and when not to.
    • Your developers can rebuild a sample screen from the system alone, without asking.
    • The files open in the software your team already uses.
  4. Part 4 · Monthly after that

    Monthly brand care

    You receive
    • Monthly list of work done
    • Source files of each task
    Done when
    • Each task in the month is accepted on its own, not the whole month at once.
    • At month end you get a list of work done and how much of the allowance was used.
The package is done when all 4 parts are met13 acceptance points · 11 deliverables

Every department and partner takes files from one library, follows one set of rules, approves one way. The brand no longer depends on one person.

Why a package

Hire task by task or take a package

The same services either way. The difference is the order of the work and how many suppliers you deal with.

  • 1person on the project, one contractinstead of 4 separate suppliers
  • 14approvals by you, in the right orderinstead of approving each task on its own
  • 11items you receive, kept in one placeinstead of files scattered around
  • Order

    Each task is done when it is needed. Most often the logo comes first and the direction later, so the logo has to be redone.

    The direction is agreed first and the design follows it. No money spent on redoing.

  • Who you work with

    Each task has its own supplier, and each supplier reads the brand differently.

    One person from Sinh Vũ follows the project from the first meeting to handover.

  • Approval

    Each task is approved on its own, so it is hard to see whether they fit together.

    You approve step by step on the project page and always know where things stand.

  • Source files

    Files sit in many places and you have to ask for them.

    Every file is kept in one place, stored long term by Sinh Vũ on Google Drive.

Cost

Cost by the work

Sinh Vũ does not set one price per package, because a ten-page website is not the same work as a thirty-page one. After hearing your needs, Sinh Vũ sends a proposal with the cost of each task. You can add or remove tasks, and you pay nothing outside the proposal.

  • The proposal lists the cost of each task
  • Paid in two instalments
  • Add or remove tasks before signing
See how Sinh Vũ prices work

Start with Long-term operations

Tell us your needs in a few minutes. Sinh Vũ sends back a proposal with the work, timing and cost.

Get a proposal for this packageMessage Sinh on Zalo

Other packages

See all four packages