Most recognizable as "brand work."
Design & Build is where the brand becomes visible. A logo gets designed. A site gets built.
We think of Design & Build as one layer of the operating system. It gets built against the kernel that Research produced β the business model, the competitive map, the audience profile, the positioning framework β and it gets deployed through Activation and runtime Operations.
The design work is the user-facing layer of a product that produces recognition, trust, and pipeline over time.
The phase has two parts. Design is the strategic and creative work that defines what the firm is saying and to whom. Build is the production work that turns the strategy into working assets.
Design: the strategy layer
Brand and service explainers
One declaration, two different lengths. A detailed explainer that articulates what the firm does, for whom, in what form, with what result β the document that gets referenced in proposals, sales conversations, and long-form content. An elevator version compressed to the length of an introduction, usable on a website header, a LinkedIn bio, or a cold outreach subject line.
Most firms have one of these.
Brand story
The why behind the what. Not a founder biography. The narrative that explains why this firm exists, why it does what it does the way it does it, and why a client should care.
A good brand story gives you a center of gravity β a touchstone that every downstream communication builds from.
Philosophy
Mission: what the you do and who you do it for, in operational terms.
Vision: what are you building toward over the next three to five years.
Values: the principles that govern how you work.
Content pillars
Three to four core content areas where you will build authority over time. Not topics you happen to write about β the intellectual territories you intend to own. Each pillar has a reason for existing, an audience it serves, a relationship to your positioning, and a ratio that governs how much of the firm's content falls into it.
Ideal Customer Profile
Research produced the audience profile β who they are, where they are, what they need. Design translates that profile into messaging.
Which segments you target. How the positioning lands differently for a managing partner versus a VP of business development. Where the ICP lives online, what they read, what triggers a purchase, and what language they use to describe their own problem.
Keywords
Search intent mapped to content pillars. Not a list of terms ranked by volume. A structured map showing which pillars target which clusters of search intent, which queries the firm can realistically rank for given its authority position, and which pieces of content address which searches.
Keywords that aren't tied to pillars produce scattered traffic that doesn't convert. Pillars that aren't tied to keywords produce content that nobody finds. The work is joining them.
Build: the production layer
Visual identity system
Logo suite, color palette, typography, visual language, and brand guidelines. Built to function across your active channels: website, email, LinkedIn, proposals, reports, client materials.
Voice and content guidelines
How you sound in written form. Vocabulary, tone, sentence rhythm, what to say and what to avoid. Includes an AI style guide β the framework the content team uses to produce content that sounds like you. This is important infrastructure now. Everyone's content production will touch AI at some point.
Website
Built in Framer or Webflow, depending on the your needs. Fully responsive, with analytics, form integrations, and technical SEO built in from the start.
A working asset that converts, ranks, and can be updated by the firm's team without agency intervention.
Marketing infrastructure
CRM configuration, email automation setup, analytics dashboards, and lead scoring model. The plumbing that makes everything measurable. At Lambent, we build this during Design & Build so that Activation and Operations can produce solid pipeline metrics.
What you get
A complete user-facing layer of the marketing operating system. Brand and service explainers, brand story, philosophy, content pillars, ICP, keyword map, visual identity, voice guidelines, live website, configured CRM, analytics dashboards. Every artifact connected to the others by design rather than assembled after the fact.
You also get the file transfer. Native files, working credentials, administrative access to every platform. If the Lambent engagement ends, you keep everything. The assets are yours from the moment they're built.
Timeline
Four to twelve weeks, depending on scope.
We scope the phase after Research, against the strategic brief Research produced. No surprises, no bloated retainers, no scope creep hidden in change orders.
Vertical considerations
Some industries have specific brand-building requirements that the generic framework has to accommodate.
Staffing and recruiting firms need a visual and verbal identity that works across two audiences simultaneously β the hiring managers who pay the firm and the candidates who make the service possible. The identity has to signal expertise to one and approachability to the other.
Law firms operate in a category where dark-blue-logo sameness is the default. Differentiation matters, but within the bounds of what a managing partner can justify. The visual work has to earn its edge without crossing into territory that feels unprofessional.
Accounting and financial advisory firms sell judgment and trust, which means the brand has to project both. Too playful reads as frivolous. Too traditional reads as invisible. The voice and visual work has to find the register that signals competence without performing it.
Insurance agencies and wealth management firms face regulatory constraints on what can be said in marketing materials. The brand work has to produce something distinct within those constraints rather than treating the constraints as excuses for generic output.
The framework is consistent. The execution is specific.
What happens next
Design & Build produces the user-facing layer. Activation brings it online.
Phase 3 is the ninety-day launch sprint that puts the identity, website, and content strategy to work β the deployment that turns installed software into a running process. The retainer that funds Operations begins during Activation, because the transition from sprint to ongoing function is continuous, not discrete.
A website that launches without Activation and Operations is a website that updates rarely, publishes inconsistently, and quietly falls out of search results over the course of eighteen months. A website that launches into Activation and then into Operations is a website that compounds.