Operating system

Teams get the brand right without asking

Sinh Vũ builds one shared library for the approved logos, templates and documents, with clear approval rules and a workflow for each team. Your people find, approve and do things right on their own, every day.

5 steps · 5 approvals on your side
How Sinh Vũ works

Five steps, clear at every turn

Pick a step to see what Sinh Vũ does, what you decide and what you receive.

Step 01 · Discovery and alignment

Inventory and consolidate in one place

Sinh Vũ does
Inventory the brand assets scattered around and consolidate them in one place, finalize the naming conventions.
You decide
Approve the library structure.Within 3 working days.
You receive
Your brand assets gathered in one place, with an agreed library structure and naming convention.

Step 02 · System and usage rules

Agree the governance rules

Sinh Vũ does
Determine who can upload assets, who approves new items, how to handle expired assets, and what happens in case of naming convention violations.
You decide
Approve the governance rules.Within 5 working days.
You receive
Governance rules stating who uploads, who approves, and how expired assets and breaches are handled.

Step 03 · System and usage rules

Build the daily ways of working

Sinh Vũ does
Establish common workflows: requesting assets, approving new publications, updating versions.
You decide
Approve the workflows.Within 3 working days.
You receive
The core workflows in place: asset requests, new material approval and version updates.

Step 04 · Rollout

Pilot with one team

Sinh Vũ does
Conduct trials with a group first, only expand when that group has used it well and the support workload is manageable.
You decide
Approve the pilot results.Within 5 working days.
You receive
Results from a pilot group, with support numbers to decide whether to roll out.

Step 05 · Rollout

Roll out and train

Sinh Vũ does
Expand by department, train and appoint leaders in each area.
You decide
Sign off the handover.Within 5 working days.
You receive
The system running in every department, each with a trained lead.
01 / 05

We already have an identity and a brand book, so what does an operating system add?

A brand book says what the brand looks like, but not how each team works with it day to day. Assets are scattered, every team keeps its own copy, and the shared drive turns into a dumping ground within a few months. Everything waits on one person to approve, because nobody knows who may approve what. Sinh Vũ gathers the assets in one place, agrees the governance rules before launch, builds the workflows, and pilots with one team before rolling out.

A brand rarely breaks at the identity. It breaks in daily operations.
One continuous flow

From scattered files to teams using it themselves

The system needs an identity and a manual in place first, because it multiplies both across the organisation. It is piloted with one team before rolling out, with a lead in each place.

Part 1

Bring it into one place

Take stock of the scattered assets, bring them into one place and agree the naming convention.

Library structureApproved before building further

Part 2

Governance and workflows

Agree who uploads assets, who approves, and what happens to expired assets, then build the common workflows.

Governance rulesAgreed before launch

Part 3

Pilot, roll out, train

Pilot with one team, and once it runs smoothly roll out department by department, with a lead in each place.

Team leadsOne person per team

Timing

How long until you have it

11 weeksSinh Vũ's part
21 working daysYour time, across 5 approvals

Add the two figures together for the real time from kickoff to handover. Your part follows the approval window of each step, so approving early shortens the schedule.

Before we start

What you need to prepare

  • The person responsible for the brand after handover, this is a mandatory condition.
  • List of departments and leaders in each area.
  • Access rights to the systems in use.
  • Decide on the tools to be used as the repository.

Having these ready keeps the project on schedule. If something is missing, Sinh Vũ can still start, and the handover date moves back accordingly.

Handover

What you receive

Each item comes with its format and what it lets each team do.

An organised asset library

Each team has its own way in and finds the right asset without asking.

Organised library

Governance rules

Know who may approve what, who keeps the library and how rights are granted.

Governance document

A guide for each team

One guide page per team, so new assets go in the right place.

Guides by team

Limited access for partners

Agencies and outside providers see only what they need.

Restricted viewing rights

Library ownership to your company

Admin rights for the library are transferred to the person in charge at your company.

Library owner rights

Sign-off standard

Know in advance what passes

The four points below are agreed before launch. The system only passes once someone on your side takes over the handover.

Signed governance rules

The governance rules are written down and signed, so approval rights are no longer word of mouth.

Signed document

The pilot team can use it

The pilot team uses the system in its daily work without having to ask anyone.

Pilot team observed

Training for each team

Each team has its own training session and a lead right where they work.

List of sessions and leads

Searchable by naming convention

Assets in the library can be found thanks to the naming convention agreed at the start.

Sample assets looked up

Investment

Three tiers by scope

Quoted by scope once Sinh Vũ understands how your operations are structured, as a fixed package. The asset library software subscription is charged separately and stated in the proposal.

Paid once

System build fee

Quoted by scope, fixed as a package once we have heard your needs.

Foundation

A business that needs its assets in one place.

8-10 weeks

Quoted by scope

  • Brand asset library
  • Governance rules and templates
  • Handed over with operating docs
Choose this tier
Popular

Comprehensive

Several departments that need clear approval rules.

11 weeks

Quoted by scope

  • Everything in Foundation
  • Core workflows built
  • Piloted with one team
Choose this tier

In-depth

Many teams that need permissions and proper training.

12 weeks

Quoted by scope

  • Permissions for each team
  • Guidance for staff using the system
  • Training so your team takes over
Choose this tier

Not sure which tier fits? Talk for 5 minutes and Sinh Vũ will suggest one →

Frequently asked questions

Before you send a request for an operating system

It is one place that holds all your brand assets (logos, documents, approved templates), with clear permissions on who may edit and who may only view, and an approval process when several departments or partners use the brand. It is not complex software you have to learn; it is a way of reorganising what you already have so it is tidy and under control.

Guidelines are a static document, printed and left on a shelf; anyone who wants to get it right has to read and apply it themselves. A brand operations system is those guidelines plus a living library, access permissions and an approval process for when new staff or partners need brand assets.

A brand design project creates assets such as a logo and identity. A brand operations system is the next step: it organises and assigns rights for how those assets are used correctly in an organisation with many people and departments, so your team keeps it going over the long term instead of stopping at handover.

Every organisation has a different number of departments, people needing permissions and complexity of approval, so the real scope only becomes clear once Sinh Vũ understands how your operations are structured, and the quote follows that scope. That way you do not pay for parts of the system you will not use.

No. The technology is kept minimal, serving only storage, permissions and approval of brand assets, not multi-purpose software that takes several training sessions to learn. Daily users only need familiar actions such as opening a file and clicking approve.

Yes, that is exactly the goal of a brand operations system, not a tool Sinh Vũ keeps running forever. Before handover, your in-house team is shown how to assign permissions, approve and update assets without depending on Sinh Vũ for every small task.

Source files and all assets always belong to your company; Sinh Vũ only designs and sets up the system initially. Top admin rights are handed to the person you nominate from the moment it is set up.

It suits organisations with several departments, many people who need brand assets, or frequent work with agencies, distributors and outside partners. If you are still small and only one or two people manage the brand, a compact set of guidelines may be enough, and Sinh Vũ will tell you plainly if you do not need this level yet.

Start your brand operating system

Send a few lines about what you need, and Sinh Vũ replies within the working day.