Skip to content

Internal reference

RogIQ brand

Naming, colors, type, reusable visuals, voice, and asset rules—for anyone creating RogIQ materials, with or without a web background. Not indexed for search; share this link directly with teammates and partners.

Start here

Intro

Who this page is for

Sales, CS, marketing, leadership, partners, and designers who need a single source of truth. You do not need to know how our website is built—use the colors, type, logos, and pattern notes as you would any brand PDF, then send technical questions to whoever owns the site or design system.

How to use it

  1. Pick your job: slides → colors + logos + patterns; copy → voice; contracts → terms + legal center.
  2. Copy what you need: hex values in the color table are one-click copy. Fonts are free on Google Fonts (linked in Typography).
  3. Grab files: final logo packages and templates live in the SharePoint brand library (see Brand Downloads)—not on this page.

Words we use here

  • Role — what the color is for (background, accent, etc.).
  • Value — the actual color code to match in PowerPoint, Figma, or print specs.
  • Build ref — optional shorthand for engineers; ignore it if you are not shipping code.

This guide defines how RogIQ should look, sound, and behave in marketing and product surfaces. When in doubt, prioritize clarity and accessibility over decoration. For production-ready logo files, presentation templates, and additional artwork, use the brand asset library (SharePoint).

Language

Name & Spelling

Company & platform

Use RogIQ — capital R, capital IQ, no space. Do not use "Rog IQ," "Rog-IQ," or "ROGIQ" in sentence case unless matching an all-caps headline style.

Pronunciation

Spoken as "rogue eye-cue" — a nod to doing marketing differently, without implying affiliation with any unrelated brands that use "rogue" in their name.

Product names

  • Brand IQ — two words, title case, for the brand memory product area.
  • Strategy OS, Create, Intelligence, Optimize — match in-product naming and marketing pages.

Avoid

  • Generic phrases like "the IQ platform" without the RogIQ name nearby.
  • Altering spacing or punctuation to force a different reading (e.g. "Rog.IQ").

Lockups

Logo & Usage

Default horizontal lockup includes the wordmark and profile mark. Use full-color on light backgrounds and reversed (white) on dark or photography with sufficient contrast.

RogIQ full-color logo

RGB — light backgrounds

RogIQ reversed logo

Reversed — dark backgrounds

Do

  • Preserve clear space around the lockup equal to at least the height of the "R" cap.
  • Place on solid or subtly textured backgrounds with enough contrast.
  • Use approved files from the asset library for print and external decks.

Don't

  • Stretch, rotate, recolor, add outlines, or combine with unapproved effects.
  • Replace the logotype with system fonts or redrawn letterforms.
  • Crop the profile mark in a way that changes its silhouette.

Primary palette

Color System

We treat dark backgrounds as the default brand look; the light palette is the same structure for people who prefer a bright screen. Lime is the accent for links, highlights, and primary buttons. Use the darkest text token on light fills and the lightest text token on black or near-black for readability.

On the live website, those choices are wired up so the theme can switch automatically; you only need the hex values below to match print, decks, or social.

Marketing theme tokens

Dark mode is the primary RogIQ palette. Light mode keeps the same roles for users who prefer a bright interface.

Dark mode

Primary palette (default on the site when someone picks dark theme)

RoleBuild refValue
Background--color-bg
Primary text--color-text
Secondary text--color-text-secondary
Lime (brand accent)--color-lime
Surface / glass--color-surface
Borders--color-border

Tip: Most teammates only need Role and Value. Tap any value to copy the hex code for slides, email, or specs. The Build ref column is for developers aligning with the live site.

Lime CTA band

Big green call-to-action strips always use the same bright lime () so a button looks identical in light or dark mode. See Patterns & Motifs for the layered background (dots + fine grid + grain) we pair with that band.

Terminal / blog palette

A separate “retro terminal” look for blog and storytelling—fixed colors so it does not flip when the rest of the site changes theme. Live example under Patterns & Motifs; copy values from this table:

Terminal backgroundBlog / retro UI
Terminal textMatches dark-mode lime
Terminal amberAccent in terminal theme

Fonts

Typography

For Google Slides, Word, or Canva: install the same families from Google Fonts — Gabarito, Red Hat Text, IBM Plex Mono, and optional Permanent Marker. The site loads them the same way; the short code names below are for developers only.

  • Gabarito (font-heading) — headlines, navigation, and big display type. Prefer heavy weights (800–900) for hero lines.
  • Red Hat Text (font-body) — paragraphs, descriptions, anything long. Use italics sparingly for emphasis.
  • IBM Plex Mono (font-mono) — UI labels, “system” microcopy, and the terminal-style blocks in Patterns & Motifs.
  • Permanent Marker (.handwritten) — handwritten accent only; never for long passages, forms, or legal text.

Gabarito display

Red Hat Text at a comfortable reading size. Use secondary color for supporting lines and keep line length around 60–75 characters where possible.

IBM Plex Mono · STATUS · v1.0 · OK

Quick accent — use sparingly

Writing

Voice & Tone

RogIQ speaks to capable teams who want outcomes, not buzzwords. Keep confidence grounded in specifics.

  • Direct & capable — short sentences, strong verbs, concrete benefits.
  • Human, not corporate — conversational where appropriate; avoid stiff legalese in marketing copy (legal pages excepted).
  • Clever with restraint — personality is welcome; clarity always wins over a joke.
  • Inclusive — avoid idioms that do not translate well; write so scanners and assistive tech stay coherent (meaningful link text, logical headings).

Product UI strings should stay neutral-professional; campaign landing pages can lean slightly bolder while staying truthful about capabilities.

Reuse across channels

Patterns & Motifs

The marketing site reuses the same few background treatments so everything feels like one system. Use this section as a visual recipe book: match the proportions in digital work, or recreate the idea in print with flat textures (no animation required).

Digital vs print

  • Digital — animated dot field, hover drift, and scanlines are fair game on web and motion.
  • Print / PDF — use the static dot grid, flat lime panels, and exported line textures at low opacity; skip scanlines and parallax unless you are deliberately going for a screen-capture aesthetic.

Hero & dark sections

Animated dot field

Lime dots on black in a soft wave. Reacts to pointer movement on desktop; on touch devices or reduced-motion settings it falls back to a still grid automatically.

Move your cursor over this card to see the field flex (desktop).

Site usage: page heroes, legal hub, product headers — see GridWavePattern in the codebase.

Print-safe

Static dot grid

An even lime-on-black dot texture for decks, booth panels, or social templates when you want the same rhythm without motion or canvas weight.

Rebuild as a pattern swatch in Figma or InDesign at ~40px repeat.

Matches the fallback the site uses when animation is off — good for parity with the web.

Lime CTAs

Bright band stack

Homepage-style final CTAs layer three things: dark micro-dots on lime, a hairline orthogonal grid, and a light film grain for depth.

Primary action lives here

Same stack as LimeCTASection / Final CTA — pair with black or white button styles from the lime CTA card rules in the stylesheet.

Together they keep long lime sections from feeling like a flat paint bucket.

Structure

Fine line grid

Very light grid lines over black (marketing) or over lime/white (CTAs) to suggest precision and dashboards without shouting.

On near-black
On white / lime
CSS: .grid-overlay on dark surfaces, .grid-overlay-on-light on lime or white.

Texture

Film grain

A subtle halftone-style noise layered at low opacity so large color fields feel tactile instead of clinical.

Easiest print match: add 3–6% uniform noise in Photoshop or a vector halftone at low contrast.

Use sparingly—typically one grain layer per section, combined with dots or grid, not all three at full strength.

Editorial / blog

Terminal theme

Deep green panel, lime monospace type, optional scanlines—signals “command line / intelligence” and is used where we want a retro-computer story beat.

user@rogiq ~ %

rogiq sync --brand --voice

OK · 3 modules updated

Fixed palette (see color table above); pair with IBM Plex Mono. Digital-first—avoid tiny reversed type in print.

Panels & long-form

Glass card + corner brackets

Frosted or lifted panels with small L-shaped corner accents—used for side navigation, legal docs, and this page’s table of contents.

Example panel: subtle border, soft shadow, corner frame.

In print, fake the glass with a light gray tint + thin border; keep corner brackets minimal so they stay crisp when reproduced small.

When you need production files or alternate crops, start from the SharePoint brand library; use the demos above to explain to an agency how far to push texture and motion.

Files

Brand Downloads

Master logos, working files, and additional campaign assets live in the Haley Marketing SharePoint library. Access is managed by your team admin.

Open brand library

Brand assets

Terms of Use

RogIQ wordmarks, logos, and associated brand assets are proprietary. Use them only for official RogIQ business, authorized partner co-marketing, or other purposes expressly approved in writing. Haley Marketing Group and RogIQ may update these guidelines; continued use after updates constitutes acceptance of the revised rules where your agreement allows.

Nothing on this page overrides a signed contract. If your agreement includes different trademark or co-branding terms, follow the contract.

For general website terms, see the Terms of Service. For privacy practices, see the Privacy Policy.