Yes. Many museums and cultural institutions have in-house communications or design staff. We're comfortable collaborating, supplementing, or providing strategic leadership where needed.
We lead, your team contributes. We own strategy, design, and build, with your staff providing institutional knowledge, content, and approvals. Common when an organization wants outside perspective or lacks capacity for a project of this size alongside daily operations.
Your team leads, we supplement. You own the brand and direction, and we provide specific capability: development, a system your team applies, or capacity during a demanding period. Common for institutions with strong design staff but no developer.
Genuine co-production. Your designers and ours work together, usually with us handling architecture and technical build while your team leads visual expression. This works well when institutional visual identity is a real internal competency, which in museums it frequently is.
We are comfortable in all three. What matters is deciding which one at the start rather than discovering it through friction.
Cultural institutions often run several relationships at once: an exhibition design firm, an AV or interactive vendor, a PR agency, sometimes a separate fundraising consultancy.
We are used to that. The practical requirements are clear scope boundaries, agreement on who owns the brand system when several parties apply it, and a shared understanding of where handoffs occur.
The most common failure is not conflict between agencies. It is ambiguity about who decides, which leaves the institution mediating between vendors rather than getting work done.
A single point of contact with authority to make decisions or route them quickly. Institutions with many stakeholders, and museums usually have many, benefit enormously from one person who can consolidate input.
Clarity about which decisions require curatorial, executive, or board review, and when those bodies meet. Review cadence in this sector is often tied to meeting schedules, and mapping that at kickoff prevents avoidable delay.
The most important thing we do when working alongside internal staff is build something they can genuinely own.
That means content models that match how your team thinks about programming, documentation written for the people who will actually use it, and training that covers real tasks rather than a feature tour. A site your communications coordinator can update confidently is worth more than a more elaborate one that requires calling us.
We are glad to stay involved for ongoing support. We would rather that be a choice than a dependency.
For related reading see our arts and culture practice, or explore our work with arts and museum organizations.
