Vertices + Ticks
One tick. Zero disputes.
"A construction industry where trust between project manager, subcontractor, and client rests on evidence — where every project closes clean."
Two naming rationales exist side by side in the source doc — both point at the same idea from different angles.
A vertex is where two lines or edges meet — the language construction blueprints already use to define where rooms, walls, and structural components join. Ticks come from how, on a checklist, you tick something off to denote it's done. Combined: precision of place + confirmation of completion.
Verticks = Verified + Ticks. Every tick is a verified tick — "reported complete" and "verified complete" are not the same thing, and a tick in Verticks only lands once there's a location, a named owner, photo evidence, and sign-off behind it.
To help construction teams close defects with confidence through verified ownership, evidence, and accountability.
Defect close-out in construction is fragmented: a photo without a location, a message without a named trade, a defect marked complete without evidence, a subcontractor who believes an issue is resolved while the client rep still considers it open. Verticks is an AI-native, evidence-based close-out tool — mobile-first, built for gloved hands on noisy, variable-connectivity sites — that makes every defect carry its full evidence chain before it can close.
This is the real captured mark (from inbox/verticks-logo-capture.png), redrawn faithfully in SVG — not the earlier placeholder concept. A sharp letter V, built from 2–3 nested chevron outline strokes in near-black blue-gray, no rounding — "has to be sharp, as that's where two lines meet." A long tapered calligraphic green tick sweeps through it: its corner sits in the V's vertex region, a short leg tucks into the right arm, and the long leg sweeps up-right past the V's edge into a thin curving tail. A cluster of small slate-blue parallelogram dashes sits upper-left, echoing the left arm's angle, shrinking toward the vertex. Colour logic from the source doc: green = "yes, safe, go"; blue = "blueprint" — construction blueprints are no longer literally blue, but the association still reads instantly.
Small palette, used with purpose — navy is the ground, not an accent; green and cobalt carry semantic meaning, not decoration. This palette was derived from the reference Construction Seed Pack deck, not from the captured logo (see the palette note below).
Status chips built from the semantic palette:
OPEN IN PROGRESS AWAITING VERIFICATION VERIFIED COMPLETE DISPUTEDThese two palettes do not currently match, and this page is not silently merging them. The captured logo (inbox/verticks-logo-capture.png) and the updated source doc describe a distinct, more muted logo palette — cream ground, near-black ink V, forest green, slate-blue accents. The digital palette used across the rest of this site (and the earlier brand direction) was derived separately from the reference Construction Seed Pack deck — deep navy, spring green, cobalt. Reconciling them (does the logo palette become the product's UI palette? does the digital palette stay as a separate "app" system with the logo as a standalone mark? do they meet in the middle?) is an open brand decision, not yet made.
Real, unstaged job-site photography — hi-vis, hard hats, gloved hands holding a phone up to a wall or fixture, shot at the moment of evidence capture. Colour graded toward deep navy in shadows/midtones so photography sits inside the same mood as the type system. Accent green/cobalt appears only as UI overlays (status chips, pins, ticks) composited on top — never as a photo colour grade.
Bright daylight corporate-stock construction photography, blueprint-and-handshake cliches, hi-vis worn as costume rather than documentary reality, any photography that isn't tied to the actual product moment of capturing evidence.
Paste-ready prompt for generating a full Google Slides brand identity presentation from this direction.
You are a senior brand designer producing a Brand Identity presentation in Google Slides for a construction-tech startup called Verticks.
CONTEXT
Verticks (from "Vertices" + "Ticks" — also read as "Verified" + "Ticks," two naming rationales that coexist in the source material) is an AI-native, evidence-based defect close-out tool for commercial construction. Problem: defect close-out is fragmented — photos without a location, unclear ownership, "reported complete" treated as the same thing as "verified complete." Verticks fixes this by requiring every defect to carry a location, a named owner, photo evidence, and a verified sign-off before it can be marked closed. It is mobile-first, built for site workers wearing gloves in noisy, variable-connectivity environments.
Headline: "One tick. Zero disputes."
Brand mission: "To help construction teams close defects with confidence through verified ownership, evidence, and accountability."
Vision statement (use verbatim where a vision slide is needed): "A construction industry where trust between project manager, subcontractor, and client rests on evidence — where every project closes clean."
Logo — REAL, ALREADY CAPTURED (do not redesign it; render it as faithfully as possible from this description, since no vector file is provided): a sharp capital "V" built from 2–3 nested chevron outline strokes in a near-black blue-gray ink (#232B33), crisp pointed vertices with no rounding anywhere ("has to be sharp, as that's where two lines meet"). A long, tapered, calligraphic green tick (#3E6B3A) sweeps through it: its corner sits in the V's vertex region, a short leg tucks into the V's right arm, and the long leg sweeps up and to the right, past the V's outer edge, finishing in a thin curving tail. At the upper-left of the V sits a cluster of 4–5 small slate-blue (#4A6B85) parallelogram dashes arranged in two diagonal rows, echoing the angle of the V's left arm, shrinking in size toward the vertex. The whole mark sits on a cream/off-white ground (#F0EEE2). Colour logic behind the mark: green = "yes, safe, go"; blue = "blueprint" (construction blueprints are no longer literally blue, but the association still reads instantly).
DESIGN LANGUAGE TO FOLLOW EXACTLY
TWO PALETTES EXIST AND ARE NOT YET RECONCILED — use them for their own stated purposes below, and include one slide that explicitly names this as an open brand decision rather than silently merging them.
Logo palette (use ONLY for the logo mark itself and any slide showing the logo in its native context):
- Cream ground: #F0EEE2
- Ink (V strokes): #232B33
- Forest green (tick): #3E6B3A
- Slate blue (dash cluster): #4A6B85
Digital palette (use for all other slide backgrounds, UI mockups, status chips, and the deck's own visual system — derived separately from a reference construction industry deck, not from the logo):
- Primary / Navy (dominant ground colour, used the way a "stage" is used — most surfaces): #071033
- Navy tint (for cards/panels on the navy ground, one step lighter): #10193F
- Secondary / Cobalt (action, in-progress, primary buttons, links): #1652F0
- Secondary / Spring Green (verified, complete, success state): #7DF5A0
- Neutral / White (only neutral at full value, backgrounds and reversed type): #FFFFFF
- Neutral / Light grey (body backgrounds on white, cards): #F5F6FA
- Neutral / Mid grey (secondary/caption text on white): #6B7280
- Neutral / Charcoal (primary body text on white): #14151A
- Semantic / Success: #7DF5A0 (pair with #071033 text for contrast, not white)
- Semantic / Warning (pending/awaiting verification): #FFB020
- Semantic / Danger (disputed/reopened): #FF5A5F
- Semantic / Info (informational, same as cobalt): #1652F0
Typography:
- Display / headline font (section titles, big statements, logo lockup type): use "Bricolage Grotesque" (Bold/ExtraBold, available free on Google Fonts) — a rounded, slightly playful geometric grotesque with big open counters. If unavailable, fall back to "Baloo 2" (Google Fonts, weight 700–800) for an even more rounded, bubble-edged alternative.
- Body / UI font (all running text, data, labels, defect descriptions — must stay highly legible at small sizes and at arm's length): use "Inter" (Google Fonts, weights 400/500/600) as the primary choice, closest free equivalent to premium grotesques like Neue Haas Grotesk or Suisse Int'l. Fall back to "IBM Plex Sans" if Inter is unavailable.
- Typographic rule to follow throughout the deck: display font ONLY for headlines/section titles/big numbers; body font for everything else. Never mix them within one text block.
Imagery / photography style (describe in on-slide captions and use for any placeholder image blocks; do not fabricate real photos — use described placeholders or abstract compositions):
- Real, unstaged-feeling job-site photography: hi-vis vests, hard hats, gloved hands holding a phone up to a wall/fixture/ceiling, tablets on site.
- Shot at the moment of evidence capture specifically (phone camera framing a defect, not generic "builders shaking hands" stock photography).
- Colour grading pulled toward deep navy in shadows/midtones so photography sits inside the same dark, confident mood as the rest of the deck; accent green/cobalt should only appear as UI overlay elements (status chips, location pins, tick marks) composited on top of the photography, never as a colour grade on the photo itself.
- Explicitly avoid: bright daylight corporate-stock construction photography, blueprint-and-handshake cliches, hard-hat-and-hi-vis worn as costume rather than as documentary reality.
Motif system (use throughout the deck as a structural device, not just decoration):
- Solid squares in navy/cobalt/green/white, used as a loose scattered grid (echoing blueprint/plan-view geometry and doubling as a checkbox reference).
- The square is the system's core shape: status chips are squares, photo-evidence frames are square-cornered, location pin markers use the square as a base.
- Section header treatment: rounded-corner navy pill/banner containing white display-font text, numbered (e.g. "01 — Brand story"), directly echoing a reference construction industry deck's section-header convention.
TONE
Confident, precise, warm — not corporate-enterprise, not playful/startup-quirky. Every design decision should read as intentional given the real constraint that end users are on active construction sites wearing gloves, often in bright daylight or poor lighting, with unreliable connectivity.
DELIVERABLE
Produce a Google Slides presentation (16:9) with exactly these slides, in this order:
1. Cover — Verticks wordmark in the display font on the navy ground (digital palette), the real logo mark rendered in its native cream/ink/green/slate colours inset in a card so it isn't recoloured onto navy, headline "One tick. Zero disputes."
2. Vision & mission — the vision statement and the brand mission ("To help construction teams close defects with confidence through verified ownership, evidence, and accountability") set large in the display font on navy, white text, minimal.
3. Naming — two rationales, side by side: Idea 1 "Vertices + Ticks" and Idea 2 "Verified + Ticks — every tick is a verified tick."
4. The problem — 3–4 short lines translating the close-out fragmentation problem (location, ownership, reported-vs-verified) into brand-voice statements, not a data dump.
5. Brand principles — a 3-across grid: "Evidence over assertion," "Every defect has an owner," "Rigorous, not bureaucratic" (or equivalent principles derived from the brand direction) — each principle as a headline with one supporting line.
6. Logo — primary lockup — render the real captured V-and-tick mark as described above, on its native cream ground, at hero size. Caption the colour logic (green = yes/safe/go, blue = blueprint).
7. Logo — construction detail — a diagram showing the three nested chevron strokes of the V, the tick's short leg / bend / long tapered tail, and the slate dash cluster, each callout-labelled.
8. Logo misuse — a "don't" slide (don't recolour the mark outside the logo palette, don't round the V's vertices, don't distort, don't place on busy photography).
9. Colour palette — logo palette — cream, ink, forest green, slate blue swatches with hex codes, labelled "used for the logo mark only."
10. Colour palette — digital palette — Navy, Cobalt, Spring Green, White swatches with hex codes and one-line usage rule for each, labelled "used for product/site surfaces."
11. OPEN DECISION — palette reconciliation — a slide that states plainly, in the deck's own voice, that the logo palette and digital palette have not been reconciled yet, shows both side by side, and poses the open question (does the product UI adopt the logo palette, does the logo get a digital-palette variant, or do they stay deliberately separate systems) rather than picking an answer for the team.
12. Colour palette — semantic/functional (digital palette) — Success, Warning, Danger, Info swatches with hex codes, shown applied to example status chips (Open / In Progress / Awaiting Verification / Verified Complete / Disputed — matching real defect statuses from the product).
13. Typography — display font specimen (Bricolage Grotesque, weights, sample headline "One tick. Zero disputes.") with the Baloo 2 fallback noted.
14. Typography — body font specimen and hierarchy scale (Inter, weights, a small type-scale table: H1/H2/body/caption with point sizes).
15. Photography style — real, unstaged job-site photography at the moment of evidence capture, graded toward navy in shadows, digital-palette UI overlays composited on top; shown as a described mood board / placeholder grid with captions (do not claim real photos exist).
16. Product application preview — a mocked mobile screen (digital palette) showing a single defect record (location tag, owner, photo evidence thumbnail, status chip, verify/tick action) demonstrating the full system in context.
17. Voice and tone — 3–4 short guidance lines (e.g. "State evidence, don't editorialise," "Never claim verified without a human sign-off," matching the product's own constraint that it must not claim work is complete without authorised verification).
18. Thank you / contact placeholder — navy ground, wordmark, real logo mark inset on its native cream card.
For every slide, use only the exact hex codes and font names specified above, keeping the logo palette and digital palette strictly separated per their stated uses. Do not invent additional colours, fonts, or claim any finished logo file (beyond the description given), photography asset, or product screenshot already exists — everything visual should be built live in Slides using shapes, text, and the specified palette/type, clearly presented as brand direction and concept mockups rather than final production assets.