OmniFlow Brand Center

Relationship to a parent group

No parent-group lockup is approved for OmniFlow. Until a written approval exists, OmniFlow is presented as a standalone brand and no combined lockup may be produced.

OmniFlow connects positioning, websites, SEO, paid media, outbound, webinars, content, social, PR, CRM, automation, and reporting around a clear growth objective.

OmniFlow is a B2B growth partner that builds the system behind qualified pipeline. We set the positioning, build the website and content that supports it, run outbound and paid channels against it, and connect every touch to a CRM so the team can see what is working. The work is delivered as one connected programme rather than isolated channel projects.

OmniFlow is a B2B marketing, demand generation, and growth-systems company. We start with positioning and the buyer outcome, then build the surfaces that carry it: website, content, SEO, paid media, outbound email and LinkedIn, webinars, social, and PR. Every channel writes into a CRM and reporting layer so pipeline, replies, and meetings are traceable to the work that produced them. Our teams operate as an extension of the client's revenue function, with defined stages, agreed measurement, and a named owner for each part of the system. We work with founders and revenue leaders who need demand to be repeatable, and we state clearly where a programme starts, what it covers, and how it is measured.

Make demand generation predictable by connecting the channels, data, and follow-up that most companies run separately.

OmniFlow builds the system that turns attention into qualified pipeline. We connect positioning, website, content, paid, and outbound into one programme, route every response into a CRM, and report on the metrics that decide whether the pipeline is real.

OmniFlow is a B2B marketing, demand generation, and growth-systems company. OmniFlow connects positioning, websites, SEO, paid media, outbound, webinars, content, social, PR, CRM, automation, and reporting around a clear growth objective. Learn more at omniflow.agency.

Tone by context

• Website — confident and concrete; lead with the outcome.
• Outbound email — short, specific, one ask, no hype.
• LinkedIn — operator to operator; share the mechanic, not the boast.
• Client reporting — neutral and exact; state what moved and what did not.
• Support and dashboard UI — plain, instructional, no marketing language.

• Lead with the buyer outcome.
• Use concrete nouns and verbs.
• Explain systems visually and in short language.
• State boundaries adjacent to claims.
• Use proof only when approved.
• End commercial pages with a specific action.

Mechanics

• Sentence case for headings and buttons. No title case, no full caps except eyebrow labels.
• Serial comma. Full stops in body copy, none in headings or button labels.
• Numerals for all quantities and metrics; spell out zero to nine only in narrative prose.
• Dates as 30 July 2026. Currency with an explicit symbol and code where ambiguous.
• One idea per paragraph; keep paragraphs under four lines.

• Never invent new CTA labels; extend the two approved labels instead of replacing them.
• Buttons state the action, never the mechanic (no 'Submit', 'Click here', 'Learn more').
• A secondary CTA may accompany the primary, never compete with it visually.

• Every metric published externally carries its definition, date range, and source.
• Client names, logos, and results require written permission before publication.
• Sample copy and placeholder metrics in templates are labelled as placeholders and must be replaced.
• No guarantees of results, revenue, or ranking. Describe the process and the measurement instead.
• Screenshots of client dashboards are anonymised unless permission covers the specific view.
• Comparative claims about named competitors are not permitted.

Approved variants

• Full colour lockup on light backgrounds — default.
• One-colour light (knockout) on obsidian and photography — used across the dark site header.
• One-colour dark for single-ink print and faxable documents.
• Small-size mark for favicons, app icons, and avatars at or below 32px.

• Obsidian and ivory carry the layout; OmniFlow Blue is the accent, not the background.
• One accent colour per view. Emerald and coral encode state, never decoration.
• No gold and no purple-to-indigo gradients — they are outside this system.
• Gradients are limited to a single subtle blue wash behind large dark surfaces.
• Colour never carries meaning alone: pair it with a label, icon, or pattern.
• Never hardcode hex values in product code — use the semantic tokens listed on each swatch.

Required states

• Default
• Hover — background darkens 10%, no scale transform
• Focus-visible — 2px ring in OmniFlow Blue with 2px offset, never removed
• Active — background darkens 15%, 1px optical press
• Loading — spinner replaces label, width preserved, aria-busy
• Disabled — 50% opacity, non-interactive

Lucide React, 1.5px stroke, 20 or 24px, currentColor. Line only — no filled or duotone icons. Icons support labels; they never replace them.

Flat 2.0 vector diagrams built from the palette: pipeline stages, channel routes, CRM objects. No gradients beyond a single subtle blue wash, no isometric 3D, no cartoon characters, no mascots.

Real commercial work: operators at screens, campaign reviews, reporting sessions. Natural light, restrained editorial grade, muted environments so OmniFlow Blue stays the accent. No stock handshakes, no glass skyscrapers, no fake conference stages.

Essential typography is never rendered into generated imagery — it is composed on top in the layout layer.

Never

• Scroll hijacking
• Cursor replacement
• Autoplay audio
• Endless particle backgrounds
• Motion that delays content

Series order

• Axes start at zero for value comparisons.
• Units and date range are always labelled.
• Source and generation date appear beneath every published chart.
• Missing data is shown as a gap with a note — never interpolated silently.
• Series are distinguishable by label or pattern, not colour alone.
• Gridlines are hairline border colour at 40% opacity.

Never

• 3D charts
• Truncated or misleading axes
• Decorative gauges
• Colour-only encoding

• Body text meets 4.5:1; large text and non-text UI meet 3:1 — verified in the contrast matrix above.
• Focus-visible indicators are never removed; 2px ring in OmniFlow Blue with a 2px offset.
• Interactive targets are at least 44 × 44px on touch surfaces.
• Every image carries meaningful alt text; decorative images use an empty alt.
• One h1 per page and no skipped heading levels.
• Colour never conveys meaning alone.
• prefers-reduced-motion removes all transforms and reveals.
• Social assets ship with a written alt-text suggestion in the caption, not baked into the image.
• Text in exported assets stays above 24px at native size so it survives platform compression.

brandId_assetId_concept_WIDTHxHEIGHT_vVERSION.ext

• Version increments on any visual change; the previous file is retained, never overwritten.
• Concept names are stable — a new concept means a new assetId, not a new version.
• The manifest records filenames, dimensions, formats, status, source assets, and the generating component.
• The master logo file is never overwritten by an export.

• Requests for a new template go to the brand owner with the surface, dimensions, and intended copy.
• Anything published externally is checked against the claims policy and the contrast matrix.
• Templates are edited in code, not in exported files, so every team exports the same current version.

• Colour: convert to CMYK using the values on each swatch; obsidian prints as a rich black (35/23/0/88), never 100% K alone on large areas.
• Resolution: 300dpi minimum for print artwork; the logo is placed as vector wherever the process allows.
• Bleed: 3mm on all edges, 5mm internal safety margin for A4 and US Letter.
• Paper: uncoated or matte stock preferred; avoid high-gloss finishes that shift the blue.
• Single-ink production uses the one-colour dark logo variant.
• This page prints as a clean guide: use Print / save as PDF at the top; navigation and export controls are omitted.