Why we redesigned our logo (and what we kept)

We spend a lot of time telling clients that their brand is the first thing a visitor judges — before the copy, before the offer, before anything loads below the fold. So it's a little humbling to admit how long we ran on a mark that was, if we're honest with ourselves, a placeholder that stuck around.

This month we finally rebranded. New mark, new lockup, a proper brand package, and one small animation we're unreasonably proud of. This post is the story of that process — partly because we find behind-the-scenes posts more useful than polished announcements, and partly because most of the lessons apply to any small business owner staring at their own logo wondering if it's time.

Why now

Not boredom. Boredom is the worst reason to rebrand — you see your own logo a hundred times more often than any customer does, and you'll get tired of it long before they do.

The real trigger was that the business had outgrown the mark. What started as a website studio now builds client portals, internal applications, and the systems underneath them. The old logo didn't say any of that. When the least considered thing your clients see is your own brand, you've stopped practicing what you preach — and that gap eventually shows up in trust.

Why we didn't design it ourselves

Here's the part that might seem strange coming from a design studio: we didn't design our own logo. We hired a specialist. On purpose. And we'd do it again.

Websites and applications are our trade. Design in that world means structure, hierarchy, and flow — building a system that quietly guides a visitor from "who are these people" to "let's talk," or an interface a dispatcher can read at a glance at 6am. We've spent years mastering exactly that, and it's the thing we'd put up against anyone.

Logo design is a different craft. It's the art of compressing an entire business into a single shape that still works at sixteen pixels, embroidered on a polo, and printed in one color on an invoice. It sits next to what we do, but next to is not the same as inside. A general contractor who's genuinely great at what he does still brings in a master electrician — not because he couldn't wire an outlet, but because he knows the difference between "can do it" and "mastered it."

This is also how we run client projects. When a project needs a new identity, we don't moonlight as logo designers — we bring in specialists we trust and direct the integration, so the logo and the site are designed as one system instead of two things stapled together. The result is better than either of us would produce alone, and it's the same reason clients hire us instead of wrestling a page builder: specialization wins.

So if you're vetting any provider — us included — and they claim to personally master everything from logos to SEO to custom applications, ask which of those they'd actually stake their name on. The honest ones will tell you. The other ones just became easier to spot.

The brief, and what came back

The brief we handed over was short: the name is literal — Layer Logic — so make the mark literal too. Layers, stacked and connected, with enough geometry to feel engineered rather than decorative.

What came back was two concepts that were almost identical: three interlocking square frames, stacked in perspective, rendered in teal, white, and gray. The only difference between them — genuinely the only one — was that in the first concept, the top layer had a little title bar with three dots. A browser window. In the second, it was a clean, plain frame.

We sat with both longer than we expected to, and picked the one without the dots. The reasoning: the browser window pins the mark to websites. We build websites, but we also build things that aren't websites — and a literal browser reference in the logo would age the way the floppy-disk save icon aged. The abstract version says what we actually mean: layered systems that fit together. Literal details date; abstract shapes travel.

What the layers mean

The mark is three frames locked into each other, and the arrangement isn't decorative. It's how we think about the businesses we work with: the website is the visible layer on top, the applications and workflow tools sit in the middle, and the systems everything runs on sit underneath. Each layer only works because it locks into the one below it. That's the logic in Layer Logic.

On color, we deliberately evolved rather than erased. The teal stayed in the family — anyone who knew the old mark will recognize the new one as the same studio, just sharper. Rebrands that torch every existing association pay for it in recognition; you're allowed to keep what works.

What a real logo package includes

If you hire a designer and all you get back is a JPG, you got a picture, not a brand. Here's what a proper delivery looks like — and what we received:

• Vector source files (AI, EPS) — the masters. Everything else can be regenerated from these. If you only insist on one thing, insist on these.
• SVG files — what your website will actually use. They scale to any size without blurring and stay tiny.
• Print-ready PDFs — for the day someone asks for your logo on a banner, a vehicle wrap, or a sponsorship packet.
• Color codes — exact values in RGB for screens and CMYK for print, so your teal is the same teal everywhere.
• Font names — the exact typefaces in the lockup, so future materials match.
• Mockups — the logo on real-world objects. Less practical, great for sanity-checking that the mark works off-screen.

Two pieces of housekeeping advice that sound obvious and get skipped constantly: confirm in writing that you own the source files, and store them somewhere private, backed up, and findable. A logo that exists only as an attachment in a three-year-old email thread is a liability with a delay on it.

The part nobody warns you about: the rollout

A logo isn't finished when the designer delivers it. It's finished when it survives every context you actually use it in — and that took us as long as choosing it.

Our site ships in both light and dark themes, and the new mark has a white layer. On a dark background it's crisp; on a white page it vanishes entirely. So the "one logo" immediately became four files: a light version, a dark version, and mark-only variants of each for small spaces. Then a favicon, which has to read at sixteen pixels. Every one of those is a decision the original delivery doesn't make for you.

And because a rebrand should be a little bit fun: first-time visitors to our homepage now watch the mark draw itself, layer by layer, before it dissolves into the site. It plays once per visit, on purpose — a brand moment should be a greeting, not a toll booth.

The practical takeaway: budget as much attention for the rollout as for the selection. Make a list of everywhere your logo lives — site, favicon, social profiles, proposals, invoices, email signatures, login screens — and don't call the project done until the old mark is gone from all of them. A half-rolled-out rebrand reads worse than no rebrand.

If you're staring at your own logo

• Don't rebrand out of boredom. Familiarity is an asset you paid years for.
• Do rebrand when the business has outgrown the mark — when your logo describes what you used to do.
• Evolve rather than erase. Keep a color, a shape, something that carries recognition across.
• Sweat the smallest details. Three dots changed the entire meaning of ours. Ask what each element says, and whether it'll still say it in ten years.
• Test in real contexts before announcing. Dark backgrounds, tiny sizes, print. The gaps show up fast.
• Use a specialist. Your web developer shouldn't moonlight as your logo designer — and anyone who claims to master both should be able to explain why you should believe them.
• Get the source files. Seriously.

Wondering how your own brand actually lands with the people it's supposed to reach? That's exactly what our brand analysis is for — an honest outside read, whether or not you ever hire us to change anything.