8-visual-brief.md 2 - Strategy & Positioning Draft Created: 2026-02-23

Visual Brief — Smartbound Custom Signal Engine

Executive Summary

This brief provides direction for the visual identity of Smartbound's Custom Signal Engine rebrand. The visual system should communicate: custom-built craftsmanship, primary source depth, modern intelligence, and professional trust. Avoid generic tech aesthetics and overly playful designs.

1. Brand Personality (Visual Translation)

Personality Attributes → Visual Direction

PersonalityVisual Expression
ExpertClean, professional, sophisticated typography
Craft-focusedHand-crafted elements, not mass-produced feel
PracticalClear hierarchy, functional design, not decorative
HungryBold accents, not safe/beige
PartnerWarm, approachable, not cold/corporate

Brand Archetype

Primary Archetype: The Creator

We build things. Custom signal engines are hand-crafted, not mass-produced. Visuals should feel like something was designed and built, not generated by AI.

Secondary Archetype: The Sage

We have deep knowledge. Primary sources, regulatory expertise, vertical depth. Visuals should convey intelligence and authority.

2. Visual Positioning

Where We Want to Be

PLAYFUL                    PROFESSIONAL
    
Slack, Notion
----+---------------------------+----
| SMARTBOUND | ← Target position
Salesforce, 6sense
GENERIC DISTINCTIVE
Target: Professional but distinctive. Not as playful as Slack, not as corporate as Salesforce. Sophisticated, modern, memorable.

3. Logo Direction

Current Logo Issues

IssueImpact
Generic tech aestheticLooks like 1000 other SaaS logos
No signal referenceDoesn't connect to new positioning
Text + icon disconnectedIcon doesn't reinforce brand
Blue/teal paletteGeneric tech color

New Logo Requirements

Must: Should: Should Not:

Logo Concept Directions

Direction 1: Signal Detection Direction 2: Custom Build Direction 3: Target Focus Direction 4: Abstract Modern Recommendation: Explore Directions 1 and 3. "Signal detection" connects to category name. "Target focus" connects to outcome ("know who to call").

4. Color Palette

Current Palette

New Palette Direction

Primary Color: Deep Navy or Dark Indigo
ColorHexUsage
Primary Dark#1a1a2e or similarHeaders, primary text, logo
Primary Light#16213e or similarBackgrounds, depth
Rationale: Accent Color: Sharp Orange or Electric Yellow
ColorHexUsage
Accent#ff6b35 (orange) or #ffd93d (yellow)CTAs, highlights, signal elements
Rationale: Supporting Colors:
ColorHexUsage
White#ffffffBackgrounds, text on dark
Light Gray#f5f5f5Card backgrounds, dividers
Medium Gray#6b7280Secondary text
Success#10b981Positive signals, metrics
Warning#f59e0bAttention signals

Color Do's and Don'ts

DoDon't
Use accent sparingly for impactOveruse accent (looks cheap)
Dark primary for authorityLight blue (generic tech)
High contrast for accessibilityLow contrast combinations
Consistent usage across touchpointsDifferent colors for different channels

5. Typography

Typography Direction

Primary Font: Modern Sans-Serif
UseWeightSize Range
HeadlinesBold/Semibold32-64px
SubheadsMedium20-28px
BodyRegular16-18px
CaptionsRegular12-14px
Font Recommendations:
OptionStyleFeel
InterGeometric, cleanModern, tech-appropriate
DM SansGeometric, slightly widerFriendly but professional
SatoshiGeometric, modernPremium, distinctive
Space GroteskGeometric, technicalTechnical, engineering feel
Recommendation: Inter or Satoshi. Inter is highly readable; Satoshi is more distinctive.

Typography Hierarchy

HEADLINE (H1)
Bold, 48-64px, Primary Dark

Subheadline (H2) Semibold, 28-32px, Primary Dark

Section Head (H3) Semibold, 22-24px, Primary Dark

Body Text Regular, 16-18px, Dark or Medium Gray

Caption/Label Regular, 12-14px, Medium Gray

Typography Do's and Don'ts

DoDon't
Use consistent hierarchyMix many font families
Ensure readability at all sizesGo below 14px for body
Use web-safe or CDN fontsRequire local font installation
Maintain generous line heightCramped text (line-height < 1.4)

6. Visual Elements

Signal Card Design

Purpose: Visually represent what a delivered prospect looks like.

Components:
  1. Signal Badge (colored indicator)
  2. Signal Title (what happened)
  3. Signal Date (when)
  4. Signal Source (where from)
  5. Impact Summary (why it matters)
  6. Outreach Angle (what to say)
  7. Contact Info (who)
Design Direction:

Signal Engine Diagram

Purpose: Visually explain how a custom signal engine works.

Flow:
PRIMARY SOURCES → SIGNAL ENGINE → WEEKLY FEED → SALES TEAM
    (icons)        (process)       (cards)      (people)
Design Direction:

Icons

Icon Style: Icon Categories Needed:

7. Photography & Imagery

Photography Direction

Avoid: Use Instead:

Illustration Style

If illustration is needed:

Image Treatments

ElementTreatment
ScreenshotsClean borders, subtle shadow
Data visualizationsBrand colors, clear labels
Background patternsSubtle, low opacity, geometric
Source logosGrayscale or brand-appropriate

8. Website Design Direction

Homepage Structure

Hero Section: Value Prop Section: Differentiation Section: Signal Example Section: Social Proof:

Website Design Principles

PrincipleApplication
Clarity over clevernessSimple language, obvious navigation
Show, don't just tellSignal examples, not just descriptions
Mobile-firstResponsive, touch-friendly
FastMinimal scripts, optimized images
AccessibleWCAG 2.1 AA compliance

9. Social Media Direction

LinkedIn

Company Page: Founder Profiles (Devon/Kevin):

Social Post Templates

Post Types:
  1. Signal examples (card format)
  2. Vertical insights (healthcare signals, fintech signals)
  3. Client results (metrics, testimonials)
  4. Primary source spotlights
  5. Competitive comparison
Visual Format:

10. Sales Collateral Direction

One-Pager

Format: 8.5x11, PDF, print-ready

Structure:
  1. Logo + tagline (header)
  2. Problem statement (1-2 sentences)
  3. Solution overview (3 bullets)
  4. Signal example (visual card)
  5. Differentiation (comparison)
  6. Pricing + guarantee
  7. Contact + CTA

Pitch Deck

Format: 16:9, 10-15 slides

Structure:
  1. Title (logo, tagline)
  2. Problem (stats on cold outreach)
  3. Solution (custom signal engine)
  4. How it works (diagram)
  5. Signal example (card)
  6. Differentiation (vs. Autobound, Clay)
  7. Pricing
  8. Case study / results
  9. Process / timeline
  10. CTA

Case Study

Format: 2-page PDF

Structure:
  1. Client + outcome (headline)
  2. Challenge
  3. Solution (signal engine built)
  4. Signal example (actual card)
  5. Results (metrics)
  6. Quote

11. Brand Guidelines Content

Guidelines Document Should Include:

  1. Logo Usage
- Primary logo - Variations (light/dark backgrounds) - Clear space - Minimum size - Incorrect usage examples

  1. Color
- Primary palette - Accent palette - Usage rules - Accessibility contrast ratios

  1. Typography
- Font families - Hierarchy - Usage examples

  1. Visual Elements
- Icons - Signal card format - Diagrams

  1. Photography & Imagery
- Style direction - Do's and don'ts - Treatments

  1. Applications
- Website - Social media - Sales collateral - Email signatures

12. Deliverables List

Phase 3: Creative Development

DeliverableFormatPriority
Logo (primary)SVG, PNGHigh
Logo (variations)SVG, PNGHigh
Color paletteHex codesHigh
Typography specsFont files, CSSHigh
Icon setSVGMedium
Signal card templateFigma, PDFHigh
Website wireframesFigmaHigh
LinkedIn bannersPNGMedium
One-pager templateInDesign, PDFHigh
Pitch deck templatePowerPoint, PDFHigh
Email signatureHTMLMedium

13. Design Review Criteria

Evaluate Designs Against:

CriterionQuestion
PositioningDoes it communicate "custom signal engine"?
DifferentiationDoes it look different from Autobound, Clay?
ProfessionalismIs it appropriate for VP Sales/CRO buyers?
ClarityCan someone understand it in 5 seconds?
MemorabilityWill they remember it tomorrow?
ScalabilityWill it work as we grow?
AccessibilityDoes it meet WCAG 2.1 AA?

14. Timeline

MilestoneWeek
Design brief approvedWeek 3
Logo concepts presentedWeek 3
Logo selectedWeek 3
Color + typography finalWeek 3
Visual system completeWeek 4
Website wireframesWeek 4
Collateral templatesWeek 4
Guidelines documentWeek 4

15. Approval Checklist

Before creative development begins:

This brief guides all visual development. Share with designers before beginning work.