Studio Notes · Behind the build

Two founders, one file: how we actually work together

The promise a business makes and the system that keeps it are usually designed by different people at different times.

Strategy defines the story. Design gives it a form. Then a technical team receives approved screens and figures out how to make them work. Each group may do its part well, yet the finished experience still feels disconnected.

We built Harlien Media around removing that sequence.

Chelsey works on why people should care. Gavin works on how the business will carry that care through websites, platforms, automation, AI systems, CRM, and lead flow. We work in the same files, join the same decisions early, and stay involved as those decisions meet reality.

That does not mean we agree automatically. It means the disagreement happens while there is still time for it to improve the work.

Why the handoff fails

A conventional handoff assumes the brand can be settled before anyone understands the operational consequences.

Imagine a service company promises a highly personal response to every inquiry. The language is approved. The website is designed around warmth and attentiveness. Then the systems team learns that requests enter four inboxes, ownership is unclear, and the team cannot reliably respond within the expectation the brand creates.

The build now has three bad options. It can automate a generic response that weakens the promise, preserve the manual process and accept inconsistency, or reopen decisions everyone thought were finished.

The reverse happens too. A platform team may choose a clean, efficient onboarding flow that reduces every provider to the same fields. Later, the brand team realizes that the provider’s individual perspective is a central reason customers choose. The system has made the important difference difficult to express.

These are not failures of copy or code. They are failures of sequence.

A brand decision creates requirements for the operation. A systems decision changes the experience of the brand. When the disciplines meet only at a handoff, each side inherits constraints it did not help shape.

We would rather surface those constraints when they are still useful information.

Listen: hearing the business from both sides

Our first phase is Listen. We enter the same conversations with different ears.

Chelsey listens for belief, emotion, language, and tension. What does the founder care about enough to protect? What do customers value that the company treats as ordinary? Where does the team use vague language because a harder choice has been avoided? Which stories keep repeating?

Gavin listens for movement, ownership, information, and failure points. How does a lead enter? Where does context live? Who decides what happens next? What requires the founder’s memory? Where does the customer wait while the team reconstructs information?

We do not split discovery into a “brand meeting” and a “technical meeting” unless there is a practical reason. Hearing the same answer matters.

When a founder says, “Every project is custom,” Chelsey may hear a positioning concern. Is customization truly the value, or has the company not named its method? Gavin may hear a systems concern. Which parts actually vary, and which repeated decisions could be structured?

Together, those questions reveal more than either interpretation alone. The business may need to protect meaningful customization while standardizing the path that supports it.

Listening also helps us distinguish a stated aspiration from a current capability. We want to understand both without shaming the distance between them. The distance often becomes the work.

Clarify: making the decisions that govern both

In Clarify, we turn what we heard into a shared set of decisions.

Who is the primary audience? What situation brings them to the business? What promise matters? Why is this company’s approach a better fit? Which offers support that position? What should happen after someone shows interest?

These questions sit across brand and systems.

For example, choosing a primary audience affects the language and visual references, but it also affects intake. A commercial buyer, a homeowner, and a retreat host arrive with different context and need different next steps. If the business insists on serving all three through one generic path, that is not merely a messaging challenge.

Offer architecture works the same way. Chelsey may want to make the choices easier to understand and connect each offer to a clear customer need. Gavin needs to know whether those offers follow distinct workflows, require different information, or should route to different people. A neat row of three service cards can hide a great deal of operational ambiguity.

This is where some of our most useful disagreement happens.

Chelsey will push when a technically convenient category flattens what the customer cares about. Gavin will push when a beautiful promise depends on invisible manual work the business cannot sustain. Neither concern outranks the other by default.

We keep working until the decision can be expressed clearly and carried responsibly.

Design: one experience, not two layers

Design is where the shared decisions take visible and structural form.

Chelsey shapes the narrative, identity, content hierarchy, and moments that create recognition or trust. Gavin maps the paths, data, integrations, states, and rules needed to support the experience.

We often work on the same customer journey from opposite directions.

Consider an inquiry form. Chelsey cares about the emotional threshold. What is the customer being asked to disclose? Does the form feel like an invitation to a conversation or an application to be judged? Does the language reflect how the customer describes the need?

Gavin cares about what the business must know to respond well. Can the request be routed from these answers? Are the fields structured enough to support follow-up? What happens if information is missing? Where is consent needed? What should the customer see after submission?

The right form is not the average of those concerns. It is an experience in which the customer feels understood and the team receives useful context.

The same collaboration applies to a chef profile, a pricing page, a client portal, or a proposal workflow. Content and functionality are not separate layers. The information chosen for display affects the decision a person can make. The data gathered behind the screen affects the response the business can provide.

Working in one file is partly literal. We comment, revise, and test the same artifacts. More importantly, it means there is one evolving source of truth for the experience. We do not protect departmental territory by hiding behind separate deliverables.

Build: letting reality argue back

Build is not the point when strategy ends. It is when reality gains a louder voice.

A content hierarchy that looked clear in an outline may feel thin on a real page. A simple booking choice may require data the business has never stored consistently. An automation may reveal that two team members use the same status to mean different things.

We treat those discoveries as information, not implementation annoyances.

Gavin prototypes the behavior early enough that we can see what the system is asking of people. Chelsey reviews not only whether the interface matches the identity, but whether the interaction matches the promise. We bring incomplete versions into conversation because a working path can expose assumptions that a polished presentation hides.

There is a practical rhythm to this. We build a complete slice, test it with real scenarios, note where people hesitate or where the system lacks context, and revise the governing decision if needed. Then we expand.

This prevents a common kind of waste: perfecting a large set of pages or automations before proving that the central exchange works.

It also keeps quality from being reduced to visual consistency or technical correctness. A page can match the design and still make the customer work too hard. An automation can run without errors and still send the wrong feeling at the wrong moment.

The build is ready when the brand promise survives contact with the operational details.

Grow: learning without splitting the work apart

After launch, the business begins producing evidence.

People use unexpected language in inquiries. They pause on a step that seemed obvious. The team develops a manual workaround. One offer attracts attention but sends poor-fit leads. A follow-up message gets replies because it answers the question customers were reluctant to ask.

Grow is the phase where we interpret that evidence together.

Gavin can see where the path slows, where records are incomplete, and where repeated manual actions suggest a missing system. Chelsey can see whether the message is attracting the intended customer, whether the proof supports the claim, and whether the experience is building the kind of trust the brand promised.

The same signal can have several meanings. A low form completion rate could mean the form is technically difficult, asks for too much, appears too early, or follows an unconvincing explanation. Changing the button color is easy. Understanding the cause requires both views.

Growth work therefore returns to the earlier phases. We listen to new evidence, clarify what it means, design a response, build it, and continue learning. The five phases are a sequence, but they are also a loop.

This matters for ongoing partnerships. As a company changes, its message and machinery can drift apart. A new offer gets added without a clear place in the story. A new system creates a process that customers experience as colder. A campaign promises speed that the sales workflow cannot maintain.

Keeping the disciplines together helps the business grow without creating two versions of itself.

The disagreement is the feature

Our working method sounds tidy when written as five phases. The actual work includes friction.

Chelsey tends to protect meaning, nuance, and the human exception. Gavin tends to protect clarity, repeatability, and the integrity of the system. Either instinct can go too far.

Meaning without structure can create a business that delivers beautifully only when the founder is present. Structure without meaning can create an efficient experience no one particularly wants.

So we challenge each other’s defaults.

When Chelsey proposes a richer, more personal experience, Gavin asks what information and labor it requires. When Gavin proposes a cleaner path, Chelsey asks what the path removes that might matter. We are not trying to win the category. We are trying to find the decision that respects the customer and can be kept by the business.

The useful disagreements are specific. We are not debating whether creativity or technology matters more. We are examining whether this field belongs on this form, whether this promise can be routed, whether this profile structure leaves enough room for personality, or whether this automation should send or only draft.

Because we share the outcome, we can revise our own part. The copy can change when the operation cannot responsibly support it. The system can change when efficiency weakens the experience. Neither artifact is treated as sacred simply because it was approved first.

That is the handoff we removed. Not the healthy transition from one kind of work to another, but the boundary that allows each discipline to declare its part finished before the whole thing works.

A business is experienced as one company, so we design it that way.

← All Studio Notes