Brand Guidelines

Visual Identity

This guide defines the visual identity and brand standards for OroMiQ. Use it to ensure consistency across all touchpoints, from digital applications to marketing materials.

1.Introduction

The OroMiQ platform comprises three distinct applications, each with its own visual identity built on a shared foundation:

Brand Story

Teams that win on relationships run on conversations: the next call, the next follow-up, the next deal. But most of them are running it on scattered spreadsheets, sticky notes and memory. Things slip. Good leads go cold. Nobody can see the whole picture.

OroMiQ was built by someone who lived that problem and got tired of working blind: one place to work the pipeline, make the calls, run the sequences and keep every follow-up in front of the right person.

Knowing who to call and why is half the job, so optional data layers add live public-record intelligence to your companies and contacts. The core is for any team that runs on relationships.

We're not here to add admin. We're here to keep your team moving.

Mission Statement

To give every team that runs on relationships one place to win and keep clients, and the live public-data intelligence to know who to call and why.

Values

Momentum over admin. The work that wins clients is the next conversation, not the data entry around it. We strip out busywork so your team spends its time moving deals forward.

Clarity, not noise. Teams drown in tools they can't see across. We turn scattered activity into clear signals: what's working, who's busy, where the next pound of revenue is coming from.

Built by someone who has done the work. OroMiQ's founder has worked the pipeline and delivered the work, so we build for how the work actually happens, not how a generic SaaS team imagines it.

Built for what’s next. Sectors change, regulations change, workflows change. We build for adaptability, so the platform shifts when your world does.

Earn trust by proving value. No lock-in, no hiding behind sales processes. We let the product speak. If it's not working for you, you'll know, and so will we.

Primary Logo

The OroMiQ logo is the primary identifier of our brand. It should be used consistently across all communications.

OroMiQ logo

Primary logo, colour on light backgrounds

OroMiQ white logo

White logo, for dark backgrounds

Clear Space & Minimum Size

There must be a minimum clear space of 10px around the logo at all times. This ensures the logo remains prominent and uncluttered regardless of context.

App Icons: Shifted Corner

Every application shares one mark: a gold square O on navy, with its bottom-right corner stepped out in the application's own colour. The shared mark says OroMiQ; the corner says which application you are in.

Website app icon

Website

Near white corner

#F8FAFC

OroMiQ CRM app icon

OroMiQ CRM

Teal corner

#14B8A6

Admin Portal app icon

Admin Portal

Slate blue corner

#A7A9DB

3.Colour Palette

Core Brand Colours

These foundational colours define the OroMiQ brand identity and are used across all applications and touchpoints.

Navy Blue#0F172APrimary brand colour
Gold / Amber#F59E0BSecondary brand colour
Slate Grey#64748BSupporting neutral

Gold Scale (Oro Palette)

The “Oro” gold scale is used primarily on the website and marketing materials. It provides depth and warmth to the brand.

50#FDF8EF
100#FAEFD9
200#F4DCB2
300#EDC481
400#E5A44E
500#DF8D2B
600#D07521
700#AD5B1D
800#8A491F
900#703D1C

Semantic / Status Colours

Semantic colours communicate meaning and status. These must be used consistently across all applications.

Success#16A34AGreen
Warning#D97706Amber
Error#DC2626Red
Info#2563EBBlue

Light Mode Palette

Background#F8FAFCDefault
Surface#FFFFFFPaper / Cards
Text Primary#0F172ANavy
Text Secondary#64748BSlate
Divider#E2E8F0Border

Dark Mode Palette

Background#0F172ANavy
Surface#1E293BDark Slate
Text Primary#F8FAFCNear White
Text Secondary#94A3B8Light Grey
Divider#334155Border

4.Application Themes

Each OroMiQ application extends the core brand palette with a distinct primary colour. This helps team members quickly identify which application they are using while maintaining overall brand cohesion.

Shared Secondary Colour

All applications share the OroMiQ Gold as their secondary colour:

Dark#D97706
Main#F59E0B
Light#FCD34D

OroMiQ CRM

The teal palette conveys trust and steady professionalism. Its light shade is the corner of the CRM app icon.

Dark#0F766E
Main#0D9488
Light#14B8A6

Admin Portal

The slate blue palette conveys calm, measured control. Its light shade is the corner of the Admin app icon.

Dark#556A8A
Main#556A8A
Light#A7A9DB

Website

The website uses the core brand directly: navy surfaces, the Oro gold scale for emphasis, and near white text. Near white is the corner of the website icon.

Navy#0F172A
Gold#F59E0B
Near White#F8FAFC

5.Typography

Primary Typeface

Inter

Inter is the primary typeface used across all OroMiQ applications and communications. It is a clean, modern sans-serif designed for screen readability.

Font stack: Inter, Roboto, Helvetica, Arial, sans-serif

Weights: 300 (Light), 400 (Regular), 500 (Medium), 600 (Semi-Bold), 700 (Bold), 800 (Extra-Bold)

Email

Emails sent from OroMiQ use Arial, Helvetica, sans-serif at 12pt, the size Outlook calls 12. Inter is not installed on most recipients' computers, so a web-safe face is the only way the email arrives looking the way it was written.

Type Scale

ElementSizeWeightLine Height
H12.5rem (40px)600 (Semi-Bold)1.2
H22rem (32px)600 (Semi-Bold)1.3
H31.75rem (28px)600 (Semi-Bold)1.3
H41.5rem (24px)500 (Medium)1.4
H51.25rem (20px)500 (Medium)1.4
H61rem (16px)500 (Medium)1.5
Body 11rem (16px)400 (Regular)1.5
Body 20.875rem (14px)400 (Regular)1.5

6.UI Components & Design Principles

Border Radius

Product UI uses soft corners, sized to the job: 6px on controls, 10px on cards and surfaces, 14px on dialogs and menus, and fully rounded pills.

The logo and the app icons keep their sharp corners. Softer components make dense CRM screens calmer to work in; the sharp mark keeps the brand precise.

Component Specifications

Buttons

  • Text transform: None
  • Font weight: 500 (Medium)
  • Border radius: 6px

Cards & Surfaces

  • Border radius: 10px
  • Border: 1px divider, with a soft navy-tinted shadow
  • Light bg: #FFFFFF / Dark bg: #1E293B

Form Fields

  • Size: Small variant
  • Style: Standard (underlined)
  • Border radius: 6px

All applications fully support both light and dark modes. Colours and surfaces adapt automatically using the defined light and dark mode palettes.

7.Incorrect Logo Usage

To maintain brand consistency, the OroMiQ logo should never be modified, distorted, or presented in ways that compromise its integrity.

OroMiQ

Do not stretch or distort

The logo must maintain its original proportions. Never stretch horizontally or vertically.

OroMiQ

Do not compress or squash

Never reduce the height or compress the logo to fit a space. Resize proportionally only.

OroMiQ

Do not rotate

The logo should always appear horizontally level. Never angle or tilt it.

OroMiQ

Do not recolour

Only use approved brand colours. Never apply unapproved colours to any part of the logo.

OroMiQ

Do not reduce contrast

The logo must remain clearly visible. Never place it on backgrounds that reduce legibility.

OroMiQ

Do not place on busy backgrounds

Avoid placing the logo over images, patterns, or complex backgrounds that compete for attention.

OroMiQ

Do not add effects

Never apply drop shadows, glows, bevels, 3D effects, or other visual embellishments to the logo.

OroMiQ

Do not outline or hollow

The logo should always appear as solid filled text. Never convert it to an outline or stroke version.

OroMiQ

Do not skew or italicise

Never apply perspective, skew, or faux-italic transformations. Use the logo exactly as supplied.

OroMiQ

Correct usage

The logo should always be used in its original form, unmodified, properly proportioned, and on a clean background with sufficient contrast. Use only the approved white-on-dark or dark-on-white versions.

8.Usage Guidelines

Do

Don’t

9.Accessibility

All colour combinations must meet WCAG 2.1 Level AA contrast requirements: