DazzaOPEN BRAND STUDIOBack to Dazza
BRAND & STYLE GUIDE01 / NOVEMBER 2026

Distinctly
Dazza.

The foundations, details and little touches
that make Dazza feel like Dazza.

Get the working files
20 SECTIONS / ONE SHARED LANGUAGEEXPLORE THE GUIDE ↓
01 /

Helpful by nature.

A clear, warm and capable identity for an AI customer service agent that gets things done.

01. Make the useful thing obvious.

Lead with what gets handled. A real answer, a completed task, a clear next step. Show the product doing the work.

02. Give it room.

Large, tightly set headlines. Generous white space. Quiet labels. Let scale and rhythm establish the hierarchy.

03. Add a little personality.

A yellow panel, an asterisk, an understated turn of phrase. Keep the product and the customer’s problem at the centre.

04. Keep people in control.

Explain what happens next. Distinguish an example from a live result. Make a human handover feel natural.

Answers. Actions.
Sorted.
02 /

One place to start.

Use the same foundations for every page, product illustration and marketing asset.

For designers

Start with the colour and type specimens. Build a clear hierarchy before adding illustration or motion. Use the logo files below and keep the identity consistent across formats.

For builders

Use the existing Astro components and shared CSS. Download the tokens, starter and AI brief for new work. Keep the marketing website and the application’s implementation separate.

Based on the live website. The core values and components come from Dazza’s existing source. The form examples, working-file formats and asset rules are guidance added in this edition; they do not change the application.
04 /

A brighter kind of helpful.

White and ink do most of the work. Yellow gives Dazza its unmistakable warmth. Select any swatch to copy its hex code.

The yellow, ink, muted, line and paper tokens are defined in styles.css. White, lead text, canvas and dots are existing literal values, given descriptive names here for reuse. Integration logos retain their own brand colours.
WhiteInkYellow

An illustration of the visual balance, not a measured quota. Avoid giving every section an accent background.

05 /

The right words. Well set.

Inter Tight carries the voice. IBM Plex Mono gives structure to labels, annotations and small details.

PRIMARY / VARIABLE SANS
Aa

Inter Tight

400 body · 500 headlines · 550 buttons · 700 wordmark

SECONDARY / MONOSPACE
Aa

IBM Plex Mono

400–500 · labels, numbering and technical details

Consider it handled.
StyleLive website specificationUse
Homepage displayInter Tight 500 · clamp(86px, 10.4vw, 158px)
0.96 line height · −0.043em tracking
Big brand statement. Mobile: clamp(65px, 15.7vw, 98px), line height 1.02.
Inner-page H1Inter Tight 500 · clamp(44px, 4.9vw, 74px)
0.99 line height · −0.043em
Product and solution titles. Mobile: clamp(42px, 12.4vw, 56px).
Section headingInter Tight 500 · clamp(42px, 4.6vw, 68px)
1.04 line height · −2.04px
Section introductions. Individual components have mobile overrides.
Homepage bodyInter Tight 400 · 19px / 1.5Hero supporting paragraph. Mobile: 15px / 1.6.
Inner-page leadInter Tight 400 · 18px / 1.55Lead text up to 470px wide. Mobile: 16.5px.
ButtonInter Tight 550 · 15pxPrimary actions. Compact variant: 14px on desktop.
LabelIBM Plex Mono · 11px / 1.5 · 1.1px trackingUppercase section labels. Existing CSS requests 450; static files provide 400 and 500.

Use sentence case for headlines. Keep negative tracking on display type, not paragraphs. Load the self-hosted WOFF2 files with font-display: swap.

06 /

Space is part of the system.

A generous outer grid, compact product detail and clear separation between ideas.

010203040506070809101112
FoundationValueApplication
Maximum content width1256pxShared .section-shell.
Wide gutters56px per sidemin(1256px, calc(100% - 112px)).
Tablet gutters40px per sideAt 1150px and below.
Phone gutters20px per sideAt 650px and below.
Key breakpoints1150 / 900 / 650pxAdjust page grids, type and navigation at their existing thresholds.
Hero split1.06fr / 0.94fr · 64px gapCopy alongside a product illustration. Stack on smaller screens.
Section rhythm100px for shared story sectionsUse the component’s own spacing. New sections usually need 64–100px, reduced for phones.
Text measure470px for inner-page leadsKeep paragraphs comfortably readable; avoid full-width body copy.
4
8
12
16
24
32
40
56
64
100

The 12-column diagram is an alignment aid for new layouts. The production CSS uses component-specific grid definitions.

07 /

Soft corners. Clear edges.

Flat surfaces and fine borders keep the interface approachable without making it feel padded.

7pxButtons
8pxChat bubbles
12pxVisual panels
14pxMega-menu
16pxDemo frame

Borders first

Use 1px lines in #E3E5DE to separate quiet panels and content. Where a border is needed to identify an input, use a darker outline with sufficient contrast.

Purposeful rounding

Keep rounded corners proportional to the object. Reserve circles for avatars, status dots and the hero mark. Large pills are not the default shape for page content.

Existing scenes may use restrained depth for stacked UI. Avoid decorative floating cards, glossy effects and large colour gradients.

08 /

A consistent little language.

Use Dazza’s existing line icon set for navigation and product concepts.

Agent
Knowledge
Workflows
Inbox
Testing
Insights
Chat
Email
Security
Connections
Handover
Bookings

Drawn on a 24px grid

1.6px strokes, round caps and joins, currentColor, no fill. Use the existing Icon.astro component at 18–24px. The asterisk is the brand mark, not a general interface icon.

Direction means something

Use an up-right arrow for a destination, a down arrow for an in-page jump and a plus for disclosure. Hide decorative icons from assistive technology; label icon-only controls.

Use SVG arrows in new assets: font fallbacks can turn less common Unicode arrows into empty squares. Integration marks come from the existing brand-logo set.

09 /

Show the work happening.

Dazza’s visual world comes from conversations, connected tools and tasks getting handled.

Your knowledgePolicies, pages & documents
DazzaUnderstands the request
A useful answerClear, relevant, ready to go

Product illustrations

Use the paper or dotted canvas, simple connected nodes and real interface language. Show one task at a time. Keep text readable at its final size and label illustrative data.

Screenshots & photography

Use current product screenshots and genuine business contexts. Remove customer data and credentials. Photos should support a real story; abstract robots and decorative AI brains do not explain the product.

Poster from Dazza’s existing product demonstration on the Wall & Fifth website
The existing product demonstration is the reference for showing Dazza in context. View the demonstration
10 /

A clear next step.

One primary action per decision. A quieter text link gives people another way in.

PropertySpecification
PrimaryInk background, white label. 56px minimum height, 16px × 23px padding, 7px radius.
Hover / focusYellow fill slides up over 500ms. Label becomes ink; a thin ink border appears. Arrow moves 3px right and up.
PressedScale to 0.98. No vertical lift.
Text link15px / 500, 22px gap to arrow, animated underline.
Navigation vs actionUse an anchor for a destination. Use a button for local state changes or form submission.
Disabled extensionUse a native disabled button, a readable muted label and no hover animation. Explain unavailable actions when necessary.
HTML / CSS
<a class="button button-dark" href="https://app.dazza.io/sign-up">
  Start for free <span aria-hidden="true">↗</span>
</a>
<a class="text-link" href="#details">
  A little more about Dazza <span aria-hidden="true">↓</span>
</a>
11 /

The useful pieces.

Live examples in the same visual language, with copyable starting points.

01 / LABEL + HEADING

Your business.
Second nature.

Give Dazza the knowledge to answer like one of your own.

HTML / CSS
<span class="section-label mono">
  <span class="cross" aria-hidden="true">+</span> HOW DAZZA WORKS
</span>
<h2>Your business.<br>Second nature.</h2>
02 / CONVERSATION
Can I move my booking to Friday?
Dazza AI agent · Example
Of course. There’s a slot at 10am on Friday. Shall I move it for you?
Friday, 10amWaiting for your confirmation

Use Convo.astro for production scenes. Label examples and show confirmation before consequential actions.

03 / DISCLOSURE
Can my team stay in control?

Yes. Set the knowledge, permissions and handover rules. Dazza works within them and brings your team in when needed.

What happens when someone needs a person?

The conversation and its context are passed to the team, so the customer does not have to start again.

HTML / CSS
<details>
  <summary>Can my team stay in control?</summary>
  <p>Set the knowledge, permissions and handover rules.</p>
</details>
04 / RESULT + STATUS
All sortedNeeds your teamWaiting for confirmation

Status is always expressed in words. Colour supports the meaning; it does not carry it alone.

HTML / CSS
<span class="sg-status">
  <span class="status-dot" aria-hidden="true"></span> All sorted
</span>

/* Include with the shared Dazza tokens. */
.sg-status {
  display: inline-flex; align-items: center; gap: 8px;
  background: var(--yellow); border-radius: 5px;
  padding: 8px 10px; font-size: 12px; line-height: 1.2;
}
YOUR AI CUSTOMER SERVICE AGENT

Less back-and-forth.
More sorted.

Get the working files
A WALL & FIFTH PRODUCT
12 /

Helpful at every state.

A small set of form patterns for new Dazza pages. These are guide extensions, not a replacement for the application’s form system.

INTERACTIVE EXAMPLE / LOCAL ONLY

This example checks the format. Nothing is sent or saved.

Default & focus

Visible labels above fields. At least 44px control height and 16px input text. Use a clear ink focus ring; keep placeholder text separate from the label.

Error & success

Name the issue beside the field and connect it with aria-describedby. Mark invalid fields with aria-invalid. Announce the result without moving focus unexpectedly.

Loading & disabled

Keep the action’s label clear: “Saving…” or “Checking…”. Prevent repeat submissions while work is in progress. Restore the control and offer a next step if something fails.

13 /

Quietly alive.

Motion should help people follow a change, understand a connection or notice a result.

Consider it handled.
BehaviourTiming / easingUse
Base easingcubic-bezier(0.2, 0.7, 0.2, 1)General transitions.
Expressive ease outcubic-bezier(0.16, 1, 0.3, 1)The shared site’s reveal and interaction easing.
Button fill / arrow500ms / 450msA visible response to hover and focus.
Section revealOpacity 800ms / transform 1000msUse restrained rises; keep content visible when JavaScript is unavailable.
Product sequenceA short, readable progressionRequest → check → result. Stop at the result; offer replay.
Reduced motionShow the finished stateRespect prefers-reduced-motion and the visitor’s pause control.

The guide’s entrance above is a new demonstration using the existing easing. It runs only when replay is requested. Avoid endless decorative loops and scroll effects that hide useful content.

14 /

Clear for more people.

Good service starts with an interface people can read, navigate and understand.

Colour pairingContrast ratioUse
Aa Ink / white16.79:1Normal text passes 4.5:1
Aa Ink / yellow15.11:1Normal text passes 4.5:1
Aa Muted / white5.19:1Normal text passes 4.5:1
Aa Lead / paper5.30:1Normal text passes 4.5:1
Aa White / yellow1.11:1Decorative only · fails normal text
Aa Line / white1.27:1Decorative only · fails normal text

Readable & navigable

Use one H1, a logical heading order, meaningful links, visible focus and a skip link. Keep new body copy at least 16px. Check zoom and text resizing, not just the default view.

More than colour

Use labels and icons with statuses. White text does not work on Dazza yellow. The pale line colour is for decorative separation, not an input’s only identifying edge.

Keyboard & screen reader

Use native buttons, anchors, form controls and details. Support Escape and arrow keys when building custom menus or tabs. Announce copied values and asynchronous outcomes.

Motion & touch

Respect reduced motion. Make new standalone controls at least 44px in each dimension. Keep horizontal scrolling within intentional code or table containers.

Ratios are calculated from the hex values above. They describe these colour pairs, not a full accessibility audit of the website.

15 /

A page with a purpose.

Use the existing building blocks to take someone from a question to a useful next step.

01HeaderA clear route through product, solutions, resources and pricing.
02HeroOne promise, a short explanation, primary action and product scene.
03DemonstrationShow the customer request and what Dazza does with it.
04CapabilitiesKnowledge, actions and handover, in a sequence that fits the page.
05QuestionsAnswer real objections in plain language.
06Closing invitationA yellow panel, a short outcome and one clear action.
07FooterUseful routes, company information and the motion control.

This is a composition guide. Keep only the sections that serve the page; do not force a pricing page, help article or legal page into the same long marketing layout.

16 /

Sounds like someone helpful.

Warm, assured and direct. Dazza makes a complicated task feel manageable.

THE BRAND PROMISE
“Consider it handled.”

A simple outcome. A little reassurance. No need to shout.

Write like thisAvoid thisReason
“Let Dazza check an order, move a booking or start a return.”“Unlock the power of next-generation agentic automation.”Name the actual task.
“Your agent. Your rules.”“Fully autonomous. No oversight needed.”Keep control and responsibility clear.
“I’ll pass this to the team with the details.”“I’m a real person and I’ve personally checked everything.”Identify the AI honestly.
“There’s a slot at 10am. Shall I move it?”“All done!” before the booking changesDistinguish an offer from a completed action.

House style

British English. Dazza in prose; lowercase in the wordmark. Sentence case for headings and actions. Use contractions naturally. “Help centre”, “sign in” as a verb, and “handover” as a noun.

Claims & product facts

Confirm pricing and feature availability against the live product before publishing. Label examples. Use real customer quotes with permission; do not invent ratings, results or integrations.

17 /

Dazza, wherever it shows up.

Carry the same type, colour, space and useful promise into every format.

Dazza
More
sorted.

AI customer service
that gets things done.

DAZZA.IO
Dazza
Your agent.
Your rules.

Helpful by nature.
Yours by design.

A WALL & FIFTH PRODUCT
Dazza
A little
less chat.
A lot more
done.
ANSWERS. ACTIONS. SORTED.
Working formatCanvasComposition
Portrait feed1080 × 1350One headline, one visual idea, logo and a short destination.
Square1080 × 1080A statement or a single product moment.
Vertical story / cover1080 × 1920Keep the key message central and allow room for platform controls.
Landscape / link1200 × 630Short headline beside a simple illustration; make small-scale text readable.
Presentation1920 × 1080 / 16:9One argument per slide. Large type and one supporting visual.
Email image1200 × 600, displayed at 600pxRetain live text and the real button in the email body.
PrintA4 / 210 × 297mmUse vector logos. Confirm bleed, colour profile and final dimensions with the printer.

These are reusable design canvases, not platform upload specifications. Check the destination’s current crop and safe-area requirements before a campaign.

18 /

Build from the same foundations.

Dazza’s marketing site is an Astro static site. Reuse its components instead of recreating the design on every page.

SourceResponsibility
public/styles.cssFonts, core tokens, homepage components, shared buttons and motion.
public/site.cssNavigation, footer and inner-page components.
src/layouts/Base.astroShared shell, metadata, fonts, header, footer and scripts.
src/components/PageHero, Story, Features, Split, Details, Tiles, Steps, Cycle, Statement, Faq, Related, Closing, Icon and Canvas.
src/data/seo.tsPage titles, descriptions and source-file mapping.
public/site.jsShared interaction and motion. Homepage-specific behaviour lives in app.js.
HTML / CSS
---
import Base from "../layouts/Base.astro";
import Closing from "../components/Closing.astro";
---
<Base title="Page title — Dazza" description="A useful description.">
  <section class="section-shell">
    <h1>A clear, useful promise.</h1>
    <p>Explain what Dazza helps the customer do.</p>
  </section>
  <Closing />
</Base>
The snippet shows the shared shell. For a real new page, add its SEO entry and use PageHero or the relevant component with its required props. Scope page-specific CSS; keep existing global styles intact.

Progressive enhancement

Keep content and navigation usable without JavaScript. Do not put a whole page behind animation readiness. Use semantic HTML before adding custom interaction.

Keep the guide current

When a shared token or component changes, update the corresponding guide specimen and working files in the same change. The tokens download is a documented snapshot, not the production CSS dependency.

19 /

Ready to go?

Use this checklist for each new page or asset. Your checks stay in this browser only.

0 / 12 CHECKED
20 /

All the right pieces.

A working set for the next page, pitch or campaign. Version 1.0 · November 2026.

Fonts are included with their SIL Open Font License files. Logo outlines are prepared from Inter Tight and the existing Dazza mark. The starter layouts are editable HTML; they are not Figma or Slides files.