Skip to main content
all case studies
PRODUCT// case study

Brand Sprint — Founder-Led Identity Rebuild

Two weeks to look like a company that ships.

A two-week Brand Sprint for an early-stage founder transitioning from a personal portfolio to a productized studio identity.

Role
Design + build + operate
Client
Sage Ideas Studio (illustrative engagement)
Category
Product
Status
Operational
Brand Sprint — Founder-Led Identity Rebuild hero

Sprint Duration

10 business days

Identity Tokens

12 colors + 6 type

Voice Doc

4 pages

Logo Variants

3 directions, 1 final

Living architecture

Surface ⇄ System

Brand Sprint is presented as both the product people touch and the operating system underneath it: UI, data model, integration path, evidence, and outcome.

Pair with Brand Care
  1. 01Visible productScreenshots and product frames show the user-facing surface without pretending concept art is production proof.
  2. 02Operating architectureThe case includes a system map so the architecture is visible, not buried in prose.
  3. 03Evidence registerMetrics, build logs, diagrams, CI artifacts, and links separate actual work from agency theater.
  4. 04Commercial pathThe page routes qualified buyers toward a matching build, automation, or lab entry.

case flow

Surface ⇄ System

ProblemProductSurface2 screensSystemmappedProof6 metricsRouteservice
A case study should prove both layers: the surface people see, and the system that keeps the product alive after launch.

Brand Sprint operating map

The diagram is intentionally simplified: it shows the buying logic and operating path, not a decorative fantasy architecture.

client

Sage Ideas Studio (illustrative engagement)

category

Product

evidence

metrics

Proof board

Receipts before claims.

This page separates shipped surface, system map, real metrics, and available artifacts so the work can be inspected instead of just admired.

proof assets

7

Screens, gallery, artifacts

screens

2

Real product surfaces

artifacts

5

Available during discovery

Primary evidence

Two weeks. One identity system. Shipped.

Sprint Duration

10 business days

Sprint Duration

10 business days

Identity Tokens

12 colors + 6 type

Voice Doc

4 pages

Logo Variants

3 directions, 1 final

Site Pages Treated

8

Follow-on Rebuild

0

Surface

Product screenshots and interface frames show the user-facing layer. If real assets are unavailable, the page says so instead of dressing mockups as production proof.

System

Architecture diagrams, build logs, and artifacts make the hidden operating layer visible to technical buyers.

See the Brand Sprint tier
01// the problem

What was broken.

Personal portfolios and small-business sites tend to accumulate years of inconsistent visual decisions — four typefaces, three accent colors, mismatched logo treatments, and copy written by different people at different stages of the business. The site works, but it does not feel coherent, and it does not signal seriousness to the small businesses the studio is trying to serve.

The Brand Sprint engagement is designed for exactly this moment. Two weeks, one founder, one identity system shipped end-to-end. No quarterly brand-strategy retainer. No multi-stakeholder workshops. The founder sets the direction, the studio executes the system.

The challenge is compression. A traditional brand rebuild burns three months on discovery and stakeholder rounds before a single asset ships. A Brand Sprint has to land a complete identity — logo, type, color, voice, and a working site treatment — in ten business days without cutting corners on the things that actually matter.

02// the approach

How it was built.

Day 1–2: Discovery. Audit of the existing assets, copy patterns, and competitive landscape. Founder interview to extract the underlying voice and the one-sentence positioning statement. Output: a written brand brief signed off before any visual work begins.

Day 3–5: System design. Custom SVG wordmark and monogram drafted in three directions. Type pairing chosen from a curated shortlist (typically Satoshi or General Sans for body, with a stronger display face for hero moments). Color system: a neutral surface palette plus one signal accent and one secondary, all token-mapped.

Day 6–8: Voice and copy system. Voice document covering tone, vocabulary, sentence rhythm, and the things the brand never says. Boilerplate copy blocks for hero, services, footer, and email signature. Reusable header and CTA patterns.

Day 9–10: Application. Identity applied to the existing site — navigation, hero, service cards, footer, OG image template, and favicon. All tokens written into the design system file. Final handoff package: SVG logo set, color hex/Tailwind tokens, type stack, voice doc, and a one-page brand guide PDF.

03// architecture

The system map.

How the pieces talk to each other.

Brand Sprint ProcessA linear five-stage flow: discovery interviews establish positioning, which informs visual system design, then a component library, culminating in launch.1 · Discoveryinterviews / audit2 · Positioningmessaging frame3 · Visual Systemtype · color · motion4 · Component LibraryTailwind tokens5 · Launchship + monitorfindings docbrand briefdesign tokensReact + Storybooklive siteWEEK 1WEEK 1 → 2WEEK 2WEEK 2WEEK 2Outcomecohesive brand · ready for traffic
04// the numbers

Measured, not asserted.

The real figures from the engagement, printed verbatim. Bars are scaled against the largest comparable magnitude in the set — a secondary cue, never the source of truth.

metric · valuescale 0 – 12
Sprint Duration
10 business days
Identity Tokens
12 colors + 6 type
Voice Doc
4 pages
Logo Variants
3 directions, 1 final
Site Pages Treated
8
Follow-on Rebuild
0
05// built ui

Selected screens.

Real product surfaces from the engagement — not stock illustrations.

Figma component library with 84 reusable design system components
01 / 02

Design system — 84 components, tokens centralized, all states documented in Figma.

07// the build log

What shipped.

The verbatim ship record, given timeline structure.

  1. log · entry 01

    Custom SVG wordmark and monogram, optimized for 24px favicon through 200px hero scale, monochrome-first with an accent color variant.

  2. log · entry 02

    Type system: display + body pairing, full size scale tokenized, line-height and letter-spacing rules documented per breakpoint.

  3. log · entry 03

    Color system: 12 tokens covering surfaces, content, borders, accent, and feedback states. All mapped to Tailwind theme variables and CSS custom properties.

  4. log · entry 04

    Voice document: 4 pages covering tone, sentence rhythm, vocabulary inclusions and exclusions, and 8 before/after copy rewrites from the existing site.

  5. log · entry 05

    Site treatment: navigation, hero block, services grid, footer, and OG image template applied across all critical pages with no broken layouts on mobile.

  6. log · entry 06

    Handoff package: SVG asset library, brand guide PDF, voice document, and a half-day office-hours block to answer follow-up questions during week three.

08// the outcome

What it proved.

Identity shipped on day 10. Site relaunched with the new system on day 11. No follow-on rebuild or retroactive cleanup work needed.

Founder reported the new system reduced time-to-publish on new pages and posts because the voice document and color tokens removed the per-page decision overhead. New pages now ship in hours, not days.

Pattern: a Brand Sprint pairs naturally with a Brand Care retainer. The Sprint sets the system; Brand Care keeps it consistent as the business adds new offers, services, and case studies. Together, they remove the slow drift that normally erodes an identity over the first 18 months.

09// artifacts

Available on request.

  • Brand brief document (template)
  • SVG wordmark and monogram set
  • Color and type token map (Tailwind + CSS)
  • Voice document (template)
  • One-page brand guide PDF
// references

Talk to people on this work.

No fabricated quotes. Reference contacts are shared during discovery, with both parties' consent.

Reference available

Engineering lead

Fintech · 5 years

Worked alongside on production trading systems for 5+ years. Available for technical reference calls — code quality, on-call discipline, incident behavior.

Reference call shared during discovery, both consenting.
Reference available

Founder

Studio engagement

Engaged Sage Ideas for a Ship + Operate combination. Willing to talk about scope discipline, timeline accuracy, and what handoff actually looked like.

Reference call shared during discovery, both consenting.
An identity system has to survive a contractor who's tired and a designer who isn't there. Tokens, not vibes.
// build log · entry 04
// honesty

What almost happened.

Every project has near-misses — decisions that, if we'd kept going, would have shipped a hole. This is the diff between the version that almost made it to prod and the version that did.

// near-miss · 01diff

beforeBrand voice was about to ship as a moodboard — three Pinterest pins and a font choice.

afterA locked voice doc with do/don't pairs, banned words, and three sample paragraphs at H1 / body / microcopy length. Anyone writing for the brand has a reference, not a guess.

costTwo extra days. The next dozen pages were on-brand without a review cycle.

// from the repo

Inline excerpts.

Trimmed, but real. The patterns that made the system survive retries, multi-tenant queries, and a bot that won't hallucinate.

Design tokens as code
typescript
// tokens/brand.ts
export const brand = {
  color: {
    cyan: '#3D5AFE',
    coral: '#E85D3A',
    lime: '#A8C633',
    magenta: '#C7236E',
  },
  surface: {
    base: '#09090B',
    raised: '#12110F',
    overlay: '#1A1917',
  },
  ink: {
    primary: '#F4F2EF',
    muted: '#A8A29E',
    subtle: '#B8B0AB',
  },
} as const

export type BrandColor = keyof typeof brand.color
// Brand color isn't a Figma hex — it's a typed token the app imports.
livebuild a1556e22026-06-19 03:29Z
// solo studio// no analytics resold// every commit human-reviewed