This is the AI Convo logo, how it is built, and the small number of rules that keep it looking like one piece of considered design instead of a logo that drifted. Read this before you place the mark anywhere.
Two colour treatments, one file each. The blue slash and the word "AICONVO" are one integrated piece of artwork, never a separate icon and wordmark placed next to each other.
Every part of the mark was chosen to say something true about the product, not to look nice in isolation. Two meanings, both intentional, both load-bearing.
A dot, then a forward slash. Read it the way you would read it in a command line or a completed step: something was pending, then it ran. That is deliberate. AI Convo is not a chatbot that answers and stops, it is agentic: it captures the lead, scores it, routes it, and hands it to a person when it should. The mark is the shorthand for that: intent, then a completed action.
You can see the same idea proven on the site itself, not just claimed in a mark: the /agentic page shows the real action log, receipt by receipt.
Look closely at where the slash sits: it is not floating in a box to the left of the name with a gap after it. It is set tight against the wordmark's own "A," not floating beside it as a separate icon.
That is also literally true of the product. Tenant isolation, security, the audit trail: none of it was added later. It was built in from day one, independently penetration-tested by a CREST-accredited firm, not retrofitted after the fact. Built in, not bolted on, twice over.
Zoomed in
Two simple rules keep the mark reading clearly wherever it lands, from a favicon to a proposal cover.
Clear space: keep at least the cap-height of the wordmark (X) free on all four sides, measured from the tallest letter. Nothing else, no nav link, no card edge, no other logo, sits inside that zone.
Below a certain size the slash and the letterforms start to lose their edges, especially on a standard screen. Do not place the full lockup smaller than this.
44px32px24px, nav default18px, hard floorNot hypothetical caution, this list. Two of these shipped on this exact site before they were caught. Codifying them here so no rebuild repeats them.
This one actually happened: an intermediate master file had the mark's rounded top sliced flat, and every export made from it inherited the flattened edge for weeks before anyone caught it. Always re-crop from the original master, never from a downstream export.
Clip lineAlso real: nav overcrowding once forced the logo roughly 15% narrower than its true 5.8:1 ratio, distorting every letterform. Height drives the scale, width stays auto, always. If a container is tight, fix the container, never the logo.
The lockup is one baked image, the slash set tight against the "A" in the master artwork. Rebuilding it from a separate icon and a separate text element with a CSS gap cannot reproduce that closeness, it just pulls the two apart. This was tried once and reversed.
AICONVOInk-on-light or white-on-dark, that is the full list. No tinting the slash to match a client's brand, no gradient fills, no matching it to a slide theme. Blue is the brand, not a variable.
Every swatch below is copied directly from the site's own stylesheet, nothing here is invented for this page.
Two families, one job split cleanly between them: Space Grotesk gives headings their edge, DM Sans carries the reading.
Four files cover every real placement. If you need something these don't cover, ask before improvising a new export.
For light backgrounds. Nav, footer, documents on white or pale canvas.
assets/img/logo-lockup-ink.webp Download .webpFor dark backgrounds. The navy band, decks, dark-mode surfaces.
assets/img/logo-lockup-white.webp Download .webpIcon-only slots exclusively: app icons, chat badges, social avatars. Never rebuild the full lockup from this.
assets/brand/aiconvo-2026-icon-blue.png Download .png
Favicon and OS-chrome badge master, for uncontrolled light or dark backgrounds.
assets/brand/aiconvo-2026-icon-chip.png Download .pngQuestions about a placement not covered here, or need a size these files don't cover? Talk to the team before improvising a new export.