<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Davis Blog</title><description>Notes on brand, campaigns, and digital from the Davis team.</description><link>https://baselayer-davis.pages.dev/</link><language>en-US</language><atom:link href="https://baselayer-davis.pages.dev/rss.xml" rel="self" type="application/rss+xml"/><item><title>The brief is the product</title><link>https://baselayer-davis.pages.dev/blog/the-brief-is-the-product/</link><guid isPermaLink="true">https://baselayer-davis.pages.dev/blog/the-brief-is-the-product/</guid><description>Most launches fail upstream. Treat the brief like a shipped artifact — not a kickoff ritual you survive and forget.</description><pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate><content:encoded>Agencies love a kickoff. Clients love a kickoff. Nobody loves the week after, when the “aligned” brief turns into three different interpretations of the same sentence.

We treat the brief as a product: something you can point at, argue with, and measure against.

## What a usable brief holds

A brief that survives contact with production usually answers five things without poetry:

1. **The action that pays** — booking, demo, waitlist, purchase. One primary.
2. **Who has to move** — not a persona deck, a decision-maker and a moment.
3. **What we refuse to be** — the competitive edge often lives in the exclusions.
4. **Constraints that are real** — budget, legal, channel, timeline.
5. **How we’ll know** — the metric and the window we’ll read it in.

If any of those are fuzzy, the creative will invent them. That’s expensive invention.

## Write it down, then stop talking

Verbal alignment evaporates. The written brief becomes the spine for strategy, creative, and digital — same document, same owners, same finish line.

&gt; If it isn’t in the brief, it isn’t in the scope. If it isn’t in the scope, it isn’t on the invoice.

Ship the brief like you’d ship a landing page: clear hierarchy, no orphan ideas, one call to action for the team.</content:encoded><category>Strategy</category><category>briefing</category><category>process</category><category>outcomes</category></item><item><title>Why rebrands die in the CMS</title><link>https://baselayer-davis.pages.dev/blog/why-rebrands-die-in-the-cms/</link><guid isPermaLink="true">https://baselayer-davis.pages.dev/blog/why-rebrands-die-in-the-cms/</guid><description>A beautiful identity means nothing if the website still speaks like the old company. Brand and build have to ship together.</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate><content:encoded>We’ve seen it too many times: the guidelines land, the launch film lands, and the site still runs on a template that was designed for a different decade of the company.

The brand didn’t fail. The handoff did.

## The PDF is not the system

Guidelines are a reference. The CMS, components, and messaging hierarchy are where the brand actually lives for customers. If those stay frozen, the new identity is cosplay.

What we insist on shipping with identity work:

- A **messaging hierarchy** editors can follow without a strategist on call
- **Components** that encode type, color, and spacing — not one-off page art
- A **content model** that matches how the company actually publishes
- A **first wave of pages** that prove the system under real copy

## One room beats three vendors

When strategy, creative, and digital sit in separate shops, the site becomes the compromise layer. Put them in one brief and the CMS stops being where brands go to die.

The test is simple: can a marketer publish next Tuesday without inventing a new visual language? If not, you launched a deck — not a brand.</content:encoded><category>Brand</category><category>identity</category><category>web</category><category>systems</category></item><item><title>Campaigns need a spine</title><link>https://baselayer-davis.pages.dev/blog/campaigns-need-a-spine/</link><guid isPermaLink="true">https://baselayer-davis.pages.dev/blog/campaigns-need-a-spine/</guid><description>Pretty creative without a conversion path is a mood board with a media budget. Build the action first, then dress it.</description><pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate><content:encoded>Creative directors and performance leads fight because they’re optimizing different objects. One wants the idea to sing. The other wants the CPA to behave. Both are right — and both lose when the campaign has no spine.

## Start with the action

Before concepts, lock the path:

- Where does the click land?
- What happens in the first five seconds?
- What is the single ask?
- What do we measure in week one vs. week four?

Then make the idea that can carry that path across paid, owned, and earned without falling apart in a 9:16 crop.

## Weekly beats quarterly

We don’t wait for a “big reveal.” Work shows up weekly. Creative and media stay in the same readouts so you’re not optimizing a beautiful idea into oblivion — or sanding a sharp idea into beige.

&gt; Launch isn’t the end. Stay for the first wave. Tighten the story while the spend is still warm.

Campaigns with a spine feel obvious in hindsight. That’s the point.</content:encoded><category>Campaigns</category><category>launches</category><category>performance</category><category>creative</category></item><item><title>Show the work weekly</title><link>https://baselayer-davis.pages.dev/blog/show-the-work-weekly/</link><guid isPermaLink="true">https://baselayer-davis.pages.dev/blog/show-the-work-weekly/</guid><description>Big reveals create big surprises. A weekly artifact rhythm keeps clients in the problem — and out of panic.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><content:encoded>The big reveal is a theater tradition that somehow colonized agency project plans. It produces gasps, then revision rounds that burn the schedule you pretended you had.

We show work weekly. Not polished for applause — real enough to decide.

## What “show the work” means

Every week, the client sees an artifact they can react to:

- A tightened brief or messaging map
- Routes or frames, not a vibe deck
- A working prototype or content template
- A measurement sketch for the launch window

Feedback is scheduled. Decisions are logged. Orphan opinions don’t become silent requirements.

## Trust is a cadence

Partners stay on the work. The same people who sold the job sit in the reviews. That rhythm is how you avoid the classic betrayal: a mid-project “direction change” that was actually three weeks of unspoken doubt.

If your process can’t survive a weekly look, it can’t survive a launch.</content:encoded><category>Process</category><category>collaboration</category><category>delivery</category><category>trust</category></item><item><title>Content systems beat content calendars</title><link>https://baselayer-davis.pages.dev/blog/content-systems-beat-calendars/</link><guid isPermaLink="true">https://baselayer-davis.pages.dev/blog/content-systems-beat-calendars/</guid><description>Calendars fill squares. Systems decide what gets made, who owns it, and how the brand keeps talking after launch week.</description><pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate><content:encoded>A content calendar without a system is a guilt spreadsheet. It tells you what you hoped to publish. It doesn’t tell you how the work gets made when everyone is busy shipping the campaign.

## Build the engine first

Before the month view, define:

- **Pillars** tied to the commercial story, not random topics
- **Formats** with templates — so every piece doesn’t start from zero
- **Owners** for draft, edit, approve, and distribute
- **A recycle path** — how a case study becomes social, email, and sales enablement

Then the calendar becomes a schedule against a machine that already runs.

## Always-on is a product

Campaigns spike. Systems compound. The brands that feel “always on” aren’t heroic — they’re operational. Editorial rhythm, voice guidelines people use, and a CMS that doesn’t fight the writer.

If your content dies when the agency leaves the Slack, you bought output. Buy a system instead.</content:encoded><category>Content</category><category>editorial</category><category>operations</category><category>brand</category></item></channel></rss>