With nearly two decades of experience, we specialized in graphic design, website development, SEO and social media marketing.

Documented brand systems · Delhi NCR, India & overseas

Your Logo Is Exempt From Contrast Rules. Your Brand Colours Are Not.

Brand guidelines are the written rules that define how a brand is used: the logo, the colour values, the typography, the spacing and the tone, recorded so that anybody can apply them correctly without asking. The test of a set of guidelines is not how it looks. It is whether the people who need it can open it, find the value they want, and paste that value into the tool they are working in.

Most guidelines fail that test. They arrive as a long PDF, the colours are given as Pantone references the designer cannot load, nobody has checked whether the palette is readable, and the developer who needs a hex value ends up picking one off a screenshot. This page is about building the version that gets used.

Open your current guidelines and check
Every colour has a hex value✓ need
Text colours are contrast checked✓ need
Values exist as a file, not only a PDF✓ need
Pantone given as the only reference✗ problem
Longer than your team will ever read✗ problem
If any of the first three is missing, the document is a presentation rather than a specification.

We Contrast Check the Palette Before We Publish It

Every colour pairing intended for text is measured against the W3C thresholds, and the ones that fail are marked as display only rather than quietly left in. Most palettes we are given contain at least one combination nobody should set body copy in.

Colours Are Given Four Ways, Never One

Hex, RGB, CMYK and a Pantone reference where it is relevant. Adobe removed the pre-loaded Pantone books from its apps, so a document specifying Pantone alone now points at something your designer may not be able to open.

The Values Exist as a File, Not Only a Picture

On the top tier you also get the palette and type scale as a machine-readable token file in the W3C format, so your developers import values instead of reading them off a PDF and typing them in.

We Keep It Short Enough to Be Read

A specification people finish beats a brand book that wins awards. We cap the core document deliberately and put the long reference material where it belongs, which is in an appendix nobody has to read to do their job.

Written by Swaranjit Singh, Founder of PIXELS TRAIL, working in branding and design since January 2007. Reviewed October 2026. Pricing and process on this page reflect how we actually work, and are updated when they change.

Filed versus used

Why Most Brand Guidelines Go Unopened

A Document That Gets Filed

  • ✗It arrives as a long PDF and nothing elseSixty pages, beautifully set, and the only way to get a colour out of it is to screenshot a swatch and sample it. Every person who needs a value has to extract it by hand, and they will each get a slightly different answer.
  • ✗Nobody checked whether the palette is readableA soft grey or a mid tone accent looks lovely on a title slide and fails as body text. The guidelines do not say which pairings are safe, so teams use them everywhere and the site becomes hard to read.
  • ✗Colours are specified as Pantone onlyWhich was reasonable when every designer had those books loaded. Since Adobe removed them, a Pantone-only specification is a reference your designer may not be able to open without a separate licence.
  • ✗The rules cover the logo and stopClear space and minimum size are documented in detail, then nothing about tables, forms, charts, captions, email or the dozens of ordinary things your team actually makes every week.
  • ✗There is no way to update itDelivered as a flat export with no working file. The first time a colour changes or a sub-brand appears, the document becomes wrong, and being wrong is worse than being absent because people still follow it.
VS

A Specification That Gets Used

  • ✓Values live where the people using them workHex and RGB for screen, CMYK for print, a Pantone reference where it is needed, and on the top tier a token file your developers can import directly. One source, several formats, no retyping.
  • ✓Every text pairing is measured and labelledAgainst the published thresholds, with the failures marked as display only rather than left for somebody to discover. Your team stops guessing which combinations are safe.
  • ✓The ordinary things are specifiedTables, forms, charts, captions, buttons, email signatures, documents. Less interesting than the logo lockup and far more frequently needed.
  • ✓You get the working filesEditable source, not only the export. When something changes you can update the document rather than commission a new one.
  • ✓Length is a design constraint, not an accidentA short core specification people will finish, with reference detail in an appendix. We would rather deliver thirty pages that get used than eighty that get admired.

What the standards say

Four Numbers That Should Be in Your Guidelines

Three come from published standards and documentation: the W3C’s accessibility guidelines, Adobe’s own help pages and the W3C design tokens format. The fourth is about a claim we have taken off this page. None of them are about taste, which is why they belong in a specification rather than a mood board.

4.5:1

Contrast ratio the W3C sets as the minimum for normal-size text

The W3C’s Web Content Accessibility Guidelines require that text and images of text have “a contrast ratio of at least 4.5:1”, dropping to 3:1 for large-scale text, which it defines as “18 point text or 14 point bold text”, noted as roughly 24px and 18.5px. Now the part that matters for a brand document, and it is genuinely counterintuitive: the same criterion states that “Text that is part of a logo or brand name has no contrast requirement.” So your logo is exempt. Your palette is not. That distinction is where most brand guidelines go wrong, because a colour chosen to look elegant in a logo lockup gets adopted as a text colour by a team that was never told the difference. We measure every pairing intended for text and label the ones that fail as display only, which usually means at least one colour in a palette we are handed comes back restricted.

6

Colour books still pre-loaded in Adobe’s apps, and none of them are Pantone’s

Adobe’s own help page states that “With the October 2023 release, all the Pantone Color books are removed from Illustrator”, following a licensing change, while six other third-party libraries, namely ANPA, DIC, FOCOLTONE, HKS, TOYO and TRUMATCH, “will remain available in Adobe Creative Cloud apps without plugins or third-party licenses”. Using Pantone colours in new work now needs a Pantone licence through a plugin. Existing files keep working: Adobe says documents with pre-loaded books “will continue to load them”. The consequence for a brand document is concrete. A set of guidelines that gives a colour as a Pantone number and nothing else is now pointing at a reference the person reading it may not be able to open. Pantone still matters for print matching and we still include the reference. It just cannot be the only value on the page.

7

Core token types in the W3C design tokens format, which is the machine-readable version of your guidelines

The Design Tokens Community Group format, published as a Final Community Group Report on 28 October 2025 and described there as “considered stable”, defines a token as “information associated with a human readable name, at minimum a name/value pair”, stored in JSON. It specifies seven core types: colour, dimension, font family, font weight, duration, cubic Bézier and number, plus composite types for borders, shadows, gradients and typography. This matters because it is the difference between a brand value your developer reads and retypes and one they import. A palette that exists only in a PDF gets copied by hand into a stylesheet, a Figma file and a slide template, and those three copies drift apart within a year. A token file is one source the others read from. We include one on the top tier and we are honest that smaller teams with no developer will not use it.

0

Primary sources we could find for the brand consistency revenue claim we removed

The previous version of this page claimed, citing unnamed studies, that consistent brand presentation across platforms can lift revenue by as much as 23 percent. We have removed it. The 23 percent figure is quoted across hundreds of agency pages and traces back to a software vendor’s own marketing survey rather than to published research, and the words “studies show” were doing work that no study supports. We could find no primary source, so the honest number here is zero. We are leaving this on the page rather than quietly deleting it, because if you are comparing suppliers you will see that figure again this week, and knowing where it comes from is more useful to you than another agency repeating it. Consistency does have real value. It is just not a number anybody has credibly measured.

Sources: the contrast ratios, the large-text definition and the logo exemption from the W3C’s explanation of success criterion 1.4.3; the Pantone position from Adobe’s Pantone Color Books help page; the token definition and types from the Design Tokens Format Module. Two other things from the old version of this page have gone with the 23 percent claim: a reference to seventeen years of experience, which was out of date, and a client’s own brand recognition survey figure that we had not designed or checked and so should not have been presenting as a result.

Five Checks on the Guidelines You Already Have

Five checks you can run on your existing guidelines in about fifteen minutes, with the document open. They are the same first five things we do when a client sends us theirs.

  • Try to copy a hex value out of the document as text, not as a screenshot
  • Find the rule for body text colour on a white background, and on your darkest brand colour
  • Look for anything covering tables, forms, charts or email signatures
  • Check whether you have the editable source file or only an exported PDF
  • Ask the person who makes the most marketing material when they last opened it

On the first check, if you cannot select the value as text, every colour in your organisation is currently being transcribed by eye. The second is the one that most often fails: there is a palette but no instruction on which pairings are safe for reading, so each person decides. The third shows whether the document covers the logo or covers the brand, and most cover the logo. On the fourth, no source file means the document cannot be corrected, only replaced. The fifth is the real verdict, and if the answer is a shrug, the problem is not that your team is careless. It is that the document was written to be presented rather than consulted.

Our process

A Seven Step Process

01

Audit What Exists

Collect every version of the logo, every colour anybody is using, every font actually installed, and the last ten things your team produced. The gap between what is specified and what is in use is the real brief.

02

Settle the Palette, With Measurements

Fix the values, then measure every pairing intended for text against the published thresholds. Failures get marked display only. This step frequently reduces the usable text palette, which is better found now than after launch.

03

Specify Type as a Scale, Not a List

Sizes, weights, line heights and what each level is for, including the small sizes everybody forgets: captions, table cells, form labels, legal lines.

04

Document the Logo Properly, Then Move On

Clear space, minimum size, the permitted variants and the backgrounds each one survives on. Thorough, and deliberately not the bulk of the document.

05

Cover the Ordinary Applications

Tables, forms, charts, buttons, documents, email, social templates, signage where relevant. Overlaps with marketing collateral design when you want the templates built too.

06

Produce the Values in Every Format Needed

Hex, RGB, CMYK and Pantone where relevant, and on the top tier a token file in the W3C format so developers import rather than retype.

07

Hand Over Source Files and Walk the Team Through It

Editable files, the exported document and a session with the people who will use it. Fifteen minutes of walkthrough does more for adoption than fifteen extra pages.

Core, Full System or System With Tokens

All three columns produce a document. The difference is how many places the values exist in and how much of the system is specified. If you only ever need a logo used correctly on a few things, the first column is honestly enough, and we would rather sell you that than pad it.

Core GuidelinesFull SystemSystem With Tokens
ShapeOne projectOne projectProject plus files
Best forOne or two usersA real teamTeam with developers
Logo rulesFullFullFull
Contrast checkedYesYesYes
ApplicationsEssentialsBroadBroad
Machine-readable valuesNoOn requestIncluded

The first column is a genuine deliverable rather than a teaser. If your brand is applied by one or two people across a handful of things, it covers you, and paying for the third column would buy you a token file nobody opens. Move to the second when several people or outside suppliers are producing material. Move to the third only when you have somebody who writes code, because that is the only person for whom a token file is better than a table.

What you get

What You Get

On every tier the colour values are given four ways, the text colours are contrast checked, and you receive the working files rather than only an exported PDF. Guidelines you cannot update are guidelines that go stale the first time anything changes.

An audit of what you are actually using

Every logo variant, colour and font in live circulation, next to what was supposed to be in use. Usually the most immediately useful page in the project.

Colour values in four formats

Hex, RGB, CMYK and a Pantone reference where it is relevant, so nobody has to convert or guess.

Every text pairing measured and labelled

Against the published thresholds, with the combinations that fail marked display only rather than left ambiguous.

A type scale, down to the small sizes

Including captions, table cells, form labels and legal text, which is where inconsistency is most visible and least documented.

Logo rules that are specific enough to follow

Clear space, minimum sizes, permitted variants and the backgrounds each survives on, with the wrong versions shown alongside the right ones.

Application guidance for ordinary work

Tables, forms, charts, buttons, documents, email and social. The things your team makes weekly rather than once a year.

A machine-readable token file

On the top tier, in the W3C design tokens format, so developers import values instead of transcribing them.

The editable source files

Not only the export. You can correct and extend the document without coming back to us.

A walkthrough with the people who will use it

Recorded if you want it, so new joiners get the same briefing. Adoption is a training problem at least as much as a design one.

Who This Is Built For

Guidelines pay off wherever more than one person makes something with your brand on it. If that is one person using one template, you probably do not need this yet, and we will say so.

Companies where several people make marketing material

The clearest case. Once more than one person produces work, the brand drifts unless the rules are written down somewhere findable.

Businesses that use outside agencies or freelancers

A good specification removes most of the briefing and nearly all of the rework. It is the cheapest thing you can give a new supplier.

Organisations with separate departments or branches

Where each unit produces its own material. Guidelines are what stop you ending up with five versions of one brand.

Companies that have just finished an identity project

Guidelines are the natural next step after brand identity design, and the point at which the identity becomes usable by people who were not in the room.

Businesses that have just rebranded

The window where documentation matters most, because everybody is replacing material at once. Related to rebranding work.

Teams with developers and a product

Where a token file genuinely earns its place, because the brand lives in code as well as in documents.

Businesses without a settled identity yet

The group we redirect. You cannot document rules that have not been decided, and guidelines written over an unresolved identity just make the confusion official.

What actually changes

What Changes in Practice

The honest version: guidelines do not make a brand better. They make a brand consistent, which is a different and narrower thing. The gain shows up as time your team stops losing to decisions that should already have been made. Two engagements, with the parts we can stand behind.

A consulting firm came to us after eight years in business with no formal brand standards and three agencies’ worth of material that did not match. We audited what existed, kept the strongest elements and built a single specification. Their marketing manager told us afterwards that project turnaround had dropped by roughly 40 percent because designers finally had clear direction. That is their estimate of their own workflow rather than something we measured, and we are quoting it as such.

The second was an e-commerce business that had grown from one product line to four, with the identity designed quickly at launch and never documented. The finding that mattered came from their own customer conversations: some buyers did not realise the four lines belonged to the same company. We built a specification covering visual identity, packaging standards and templates. They later reported improved recognition in follow-up surveys, and we have stopped quoting that figure here because we did not design or audit the survey it came from.

Decisions stop being remade every week

Which blue, which logo file, what size the caption is. Each one is small and they are relentless, and a specification ends them.

Briefing a new supplier takes an hour instead of a month

You send one document rather than answering the same questions through three rounds of revisions.

Your material becomes readable, not just attractive

Because the text pairings were measured. This is the change people notice on the website first.

The brand survives staff changes

The rules are in a document rather than in the head of whoever has been there longest.

What the Project Looks Like

A typical full system project. The audit in the first week is often where the uncomfortable discoveries happen, which is why it comes first rather than last.

Week 1: Audit and collect

Every logo file, colour, font and recent piece of material. We report what is actually in circulation against what was meant to be, which is rarely the same thing.

Week 2: Palette and measurement

Values fixed, every text pairing measured, failures marked display only. If the palette needs a safe text tone added, this is where that happens.

Week 3: Type scale and logo rules

The scale down to captions and table cells, then clear space, minimum sizes and permitted variants with wrong-use examples.

Weeks 4 to 5: Applications

Tables, forms, charts, documents, email, social and anything specific to your industry. Drafted as real examples rather than described.

Week 6: Assembly and formats

The document assembled, values exported in every format needed, token file produced on the top tier.

Week 7: Handover and walkthrough

Source files, exports and a session with the people who will use it. Plus a short note on what will need revisiting and roughly when.

Published pricing

What Brand Guidelines Cost

Published. Search for brand guidelines cost India and you will find almost no numbers, which is understandable because scope varies and unhelpful if you are trying to budget. Our brand guidelines pricing is below. The thing that moves it is not page count, it is how many applications need specifying and how much of your existing material has to be untangled first.

Core Guidelines

INR 35,000 to 65,000
approx. USD 422 to 783

For businesses where one or two people apply the brand. Logo rules in full, a contrast-checked palette in four formats, a type scale and the essential applications. A real specification, just a narrower one.

  • ✓Audit of logos, colours and fonts in use
  • ✓Palette in hex, RGB, CMYK and Pantone
  • ✓Every text pairing contrast checked
  • ✓Type scale including small sizes
  • ✓Full logo rules and wrong-use examples
  • ✓Essential applications documented
  • ✓Editable source files included
  • ✓Typically 2 to 3 weeks

Full System

INR 85,000 to 1,50,000
approx. USD 1,024 to 1,807

For teams and anyone working with outside suppliers. Everything in Core plus broad application guidance covering the ordinary work your team produces weekly, and a walkthrough session.

  • ✓Everything in Core Guidelines
  • ✓Tables, forms, charts and buttons
  • ✓Documents, email and social templates
  • ✓Signage and print where relevant
  • ✓Tone of voice section
  • ✓Walkthrough with your team, recorded
  • ✓Token file on request
  • ✓Typically 5 to 7 weeks

System With Tokens

INR 1,75,000 to 3,00,000
approx. USD 2,108 to 3,614

For organisations with developers and a product, where the brand has to exist in code as well as in documents. Everything in Full System plus a machine-readable token file in the W3C format.

  • ✓Everything in Full System
  • ✓Token file in the W3C JSON format
  • ✓Colour, dimension and type tokens
  • ✓Naming structure documented
  • ✓Figma library structured to match
  • ✓Sub-brand and co-branding rules
  • ✓Governance and update process
  • ✓Typically 8 to 11 weeks

If you are choosing between the first and the second column, the question is how many people make things with your brand on them. One or two, take the first. If you are choosing between the second and the third, the question is simply whether you employ somebody who writes code. If you do not, the token file is a file nobody will open and the second column is the right spend.

What moves our numbers: how many applications need specifying, and how much untangling your existing material needs. A company with one clean logo file and a hex code is a faster project than one with nine logo variants in circulation and nobody sure which is current. If you are also having the templates built rather than only specified, that is marketing collateral design and it is quoted separately so you can see both numbers.

What We Will Not Do

Each of these is common in the category. Each one produces a document that looks impressive and gets used less.

  • ✗We will not write guidelines over an unsettled identityIf the logo or the positioning is still in question, documenting it just makes the confusion official. We will say so and point you at identity work first, even though guidelines are the easier sale.
  • ✗We will not specify a colour as Pantone onlyHex, RGB and CMYK go in alongside it. Since Adobe removed the pre-loaded Pantone books, a single-reference specification points at something your designer may not be able to open.
  • ✗We will not leave text pairings unmeasuredEvery combination intended for reading gets checked against the published thresholds, and the ones that fail get labelled rather than left for somebody to find out.
  • ✗We will not pad the page countLength is a cost, not a feature. We cap the core document and put reference detail in an appendix, and we will push back if you ask for a longer one.
  • ✗We will not hand over exports without source filesGuidelines you cannot edit are guidelines that become wrong and stay wrong. You get the working files on every tier.

Where to Start

Run the first two checks above on what you already have. Try to copy a hex value out of your current document as selectable text, and find the rule that tells somebody which colour to set body text in. If the first fails, every colour in your business is being matched by eye right now. If the second is missing, your palette is being used in ways nobody specified. Send us the document either way, along with your logo files and three or four recent pieces of material, and we will come back with what is missing and which tier fits. If the honest answer is that you need brand identity design before any of this, we will tell you that instead.

Brand Guidelines Questions, Answered

How much do brand guidelines cost in India?

Our published ranges are INR 35,000 to 65,000 for Core Guidelines, INR 85,000 to 1,50,000 for a Full System, and INR 1,75,000 to 3,00,000 for a system with a machine-readable token file. Most businesses that contact us fit the first two. What moves the number is not how many pages you get, which is the wrong thing to buy on, but how many applications need specifying and how tangled your current material is. A company with one logo file and a hex code is a quicker project than one with nine logo variants in circulation and nobody certain which is current. If you see a quote built on page count, ask what is being specified instead, because a sixty page document covering only the logo is worth less than twenty pages covering the work your team actually produces.

What is the difference between brand guidelines and a brand style guide?

In practice nothing, and anybody drawing a firm line between them is usually selling one of them. The terms brand guidelines, brand style guide, brand book and brand manual all refer to the same thing: the written rules for applying a brand correctly. You will also see brand book design services and brand style guide design advertised for it, and brand identity guidelines used as the label, and our own brand guidelines design work covers the same ground under whichever name you prefer. What does differ meaningfully is scope. Some documents cover only the logo, with clear space and minimum sizes in detail and nothing else. Others cover the whole system: colour with measured contrast, a type scale down to captions, applications, tone of voice, and the ordinary material a team produces weekly. When you compare suppliers, ignore the name on the cover and ask which of those two you are being quoted for, because the price difference between them is substantial and the names do not signal it.

How long does a brand guidelines project take?

Core Guidelines take two to three weeks, a Full System five to seven, and a system with tokens eight to eleven. The variable that actually drives the timeline is not our drawing speed, it is how quickly we can get a complete picture of what you are using now. The audit in week one needs every logo file, every colour anybody has adopted, the fonts actually installed on your machines and a sample of recent material. Clients who can supply that in a few days finish at the fast end of the range. Clients who have to go hunting through old agency emails and a shared drive nobody has tidied add two or three weeks before design work properly starts, and that is normal rather than a failing.

Do I need brand guidelines if I am a small business?

Often not yet, and we will tell you when that is the case. The honest test is how many people make things with your brand on them. If it is one person using one set of templates, the rules live in their head and that works fine. The moment a second person starts producing material, or you hand work to a freelancer or an agency, the drift begins and a document starts paying for itself immediately in avoided rework and briefing time. So the trigger is not company size or revenue, it is the number of hands. A two-person business that uses three freelancers needs guidelines more than a twenty-person business where one designer makes everything.

What should brand guidelines include?

At minimum: an audit of what is in use, colour values in hex, RGB, CMYK and Pantone where relevant, every text pairing contrast checked, a type scale including the small sizes, and logo rules covering clear space, minimum size and permitted variants with wrong-use examples. A full system adds the ordinary applications, which is the part most documents skip and most teams need: tables, forms, charts, buttons, documents, email signatures, social templates. Tone of voice belongs there too. What should not be in it is forty pages of brand story that nobody consults to get a job done. Put that somewhere else if you want it, and keep the specification to things somebody can act on.

Why do you check colour contrast in a brand document?

Because a palette chosen for a logo gets used for text by people who were never told the difference, and the W3C is explicit about the two not being the same. Its guidelines require a contrast ratio of at least 4.5:1 for normal-size text and 3:1 for large text, while stating that “Text that is part of a logo or brand name has no contrast requirement.” So a soft grey can be perfectly legitimate in a logo and a bad choice for paragraph copy. If the guidelines do not mark that distinction, somebody will eventually set your website body text in the display tone and the result is hard to read, which costs you more than any branding decision in the document. We measure every pairing and label the failures as display only.

Can you work from the brand we already have?

Yes, and that is the majority of what we do. The project starts with an audit rather than a redesign: we collect everything in circulation, identify what is strongest and most consistent, and build the specification around that. Where we find genuine conflicts, two logos both in active use, or a palette with no colour safe for text, we flag them and recommend the smallest change that resolves it rather than proposing a rebrand. If the conclusion is that the identity itself is not settled enough to document, we will say that plainly, because guidelines written over an unresolved identity just record the confusion. That conversation happens before any quote.

What are design tokens and do I need them?

A token is the machine-readable form of a brand value. The W3C design tokens format, published as a Final Community Group Report in October 2025, defines one as “information associated with a human readable name, at minimum a name/value pair”, stored in JSON, with seven core types including colour, dimension, font family and font weight. The practical value is that a developer imports the file instead of reading a hex code off a PDF and typing it in, so your website, your design files and your templates stay in agreement. You need them if you employ somebody who writes code. If you do not, a token file is a file nobody will ever open, and we would rather you spent that money on the applications in the Full System tier.

Should our guidelines specify Pantone colours?

Include the Pantone reference if you print, because it is still how a printer matches a colour reliably, but it can no longer be the only value on the page. Adobe’s help documentation states that as of the October 2023 release all the Pantone Color books were removed from Illustrator following a licensing change, and that using them in new work requires a Pantone licence through a plugin, while six other libraries remain available without one. So a designer opening your guidelines may not be able to load the swatch you have specified. We give every colour as hex, RGB and CMYK alongside the Pantone reference. It takes one extra line per colour and removes an entire category of problem.

Who in my company will actually use this?

Fewer people than you expect, and designing for that is the point. Realistically the heavy users are whoever produces the most material, usually one or two people in marketing, plus any outside designer or agency. Everybody else consults it two or three times a year to find a logo file or a colour. That is why we keep the core document short and put reference detail in an appendix, and why the walkthrough session matters more than extra pages. If you want a single answer to this question before commissioning anything, ask the person who makes the most material what they would need to stop asking you questions. Their answer is a better brief than most formal ones we receive.

What file formats will we receive?

The document as a PDF, the editable source file so you can correct and extend it, the colour values in a format you can copy as text rather than screenshot, logo files in vector and raster for both print and screen, and on the top tier the token file in JSON. The source file matters more than people expect at the time: guidelines without one cannot be corrected, only replaced, so the first small change makes the whole document stale. We hand over working files on every tier for that reason, and it is worth asking any supplier whether they do the same before you commission.

How often should brand guidelines be updated?

There is no useful calendar for this, because guidelines go out of date by event rather than by time. The triggers are a new sub-brand, a new channel you are suddenly producing a lot for, a product line that does not fit the existing system, or a visual change made for a campaign that quietly became permanent. Any of those should prompt an update. Absent them, a sound specification holds for years. What we recommend instead of an annual review is a standing habit: when somebody has to invent a rule to finish a job, that is the signal, and it should get written in rather than repeated from memory. We include a short note at handover on which parts we expect to need revisiting first.

Do you include tone of voice?

In the Full System and above, yes, and kept practical. That means the words you use for your own products and services, the ones you avoid, how formal you are in different contexts, how you handle the specifics your industry gets wrong, and worked examples showing the same message written well and badly. What we do not include is a page of adjectives, because confident, approachable and professional describe almost every company and guide nobody. If you want voice work at more depth than a section, that is its own project and we will quote it separately rather than thinning it into the document.

Can you build the templates as well as specify them?

Yes, and it is a separate line so you can see what each part costs. The guidelines specify how a thing should look; building the actual deck, document, email and social templates your team opens is marketing collateral design. Plenty of clients take the specification from us and have their own designer build the templates, which is a sensible way to spend less. What we would discourage is buying templates without the specification, because then the rules only exist inside the files and the first person who needs something the templates do not cover has nothing to work from.

Do you work with clients outside Delhi?

Yes. We provide brand guidelines services in Delhi and across Delhi NCR, and we work with businesses elsewhere in India and overseas, billing in INR, USD or AED. Being a brand guidelines company India clients can meet in person helps mainly during the audit, where going through material together is faster than exchanging files. Everything after that works remotely without loss. If you want to create brand guidelines for my business is the search that brought you here, the useful first step is the same wherever you are: send us your current document if you have one, your logo files, and three or four recent pieces of material. The audit tells both of us what the project actually is.

Talk to Us About Your Guidelines

Send us whatever you have now, even if it is a logo file and a hex code somebody wrote in an email. We will tell you what is missing, what is wrong, and whether you need guidelines at all or an identity first.