The pitch is always done by the senior people. That is what closes the deal. The prospect sits across the table from people who have done this before, who have opinions, who push back intelligently, who make the work sound considered and serious.
Then the contract is signed, and the senior people move on to closing the next deal, and the work starts with whoever is available. This is not a secret. Everyone in the industry knows it. Most clients have experienced it. Some have even factored it into how they evaluate proposals, building in a mental discount for the reality that the people pitching are not the people delivering. And yet the model persists, because it is financially rational for studios organized the way most studios are organized.
We built Citara Labs because we wanted to work differently. This essay is an attempt to explain what we observed, what we concluded, and what we actually built as a result.
The typical studio or agency is organized around disciplines. There is a brand team, a design team, a technology team, perhaps a strategy team. Each team has a hierarchy: juniors who do the volume work, mid-levels who manage the process, seniors who make the significant decisions.
This structure exists because disciplines are how you build specialization. A strong brand team, organized around brand work, can develop genuine depth in what makes brand work effective. The same logic applies to design and to engineering. The specialization is real and valuable.
The problem is that the structure optimizes for the studio, not for the client.
The client's problem is never discipline-shaped. A company that needs its brand redesigned also needs the product experience to carry the brand coherently. The product experience needs an engineering foundation that supports it. The engineering needs an AI layer that makes the product intelligent in the ways the market now expects. These are not four separate problems. They are one connected system problem, and every handoff between disciplines is a place where coherence breaks down.
The client's problem is never discipline-shaped. The studio's structure always is.
Brand hands over to product. Product hands over to engineering. Engineering, if the company is lucky, eventually brings in an AI consultancy to bolt intelligence onto what has already been built. Each handoff introduces a gap: in context, in intent, in aesthetic understanding, in the relationship between what was decided and what gets built.
The best studios manage these handoffs skillfully. They have good communication, thorough documentation, careful onboarding of each new team. The handoff still happens, the gap still exists, the product still reflects the fact that more than one team made it.
Before starting Citara Labs, the people who founded this studio worked inside the studios and firms that most companies hire. We had first-hand exposure to how the work actually gets done. Several patterns were consistent enough to feel structural rather than incidental.
Strategy documents that were approved in presentations and then set aside when design started. Not because anyone decided to ignore them, but because the designer who received the brief had not been in the room when the strategy was developed, and the translation between what was decided and what was understood was lossy.
Design work that was handed to engineering teams who rebuilt significant portions of it because the constraints of the underlying system had not been understood when the design was made. Not because the engineers were difficult, but because the designers and engineers had not worked together, and the gap between what was designed and what was buildable had to be resolved in the only direction available: backward.
Clients who had bought four services from four vendors and were trying to coordinate a coherent outcome across all of them, with no single person accountable for whether the sum of the parts actually worked together. The coordination burden sat with the client, who was not organized to carry it.
AI being discussed in every pitch and deployed in almost no implementation, because the engagement model of the studio was not set up to do the sustained engineering work that production AI deployment requires.
The problems we kept observing were not execution problems. They were structural. Better project management would not fix them. Better communication tools would not fix them. Better individual talent would not fix them.
They would be fixed by a different kind of organization: one where the people who develop the brand strategy are present when the product is designed, and present when the engineering choices are made, and present when the AI layer is defined. One where there is no handoff because there is no boundary between the disciplines. One where the senior person accountable for the outcome is present throughout the engagement, not just at the beginning and the end.
Citara Labs is organized around four practices: Brand and Identity, Product Design and Platform Engineering, Digital Twin Visualization, and AI Practice. Each practice is led by a partner. That partner is present throughout every engagement in their domain.
We also operate what we call a Senior Agentic Workforce: a layer of agentic systems that runs alongside the human team and handles the continuous, repetitive, coordination-heavy work that would otherwise consume partner attention. Research synthesis, monitoring, documentation drafting, status tracking. The agents handle the administration. Partners handle the judgment.
We take on fewer engagements than we could. The ones we take on get the attention they deserve.
We take on a small number of engagements each year. We say no more often than we say yes. When we say yes, the people who close the deal are the people who do the work. There is no handoff from the pitch team to the delivery team because there is no distinction between them.
This model works well for companies that have a specific, connected problem that spans brand, product, and intelligence. Companies that are building something serious and want it done once, correctly. Companies that understand that coherence across the full system is worth more than speed across individual parts.
It does not work well for companies that need volume above quality, or speed above coherence, or a vendor they can replace easily if things go wrong. For those companies, there are many excellent options. We are not one of them.
The honest version of our positioning is this: we built the studio we wanted to work at, and we are looking for clients who want to work with that studio. The match is either obvious or it is not. We are comfortable with that.
