Skip to content
Interface language: English
Imperium / Signal

A service under a partner's brand: who needs to know who does the work?

Organise a service under a partner's brand: client contact, corrections, file access, confirmation of delivery and limits on promises.

Article language: English

Concept illustration: a woman rests her hands on the outer two of three round discs mounted on an axis in a navy and red interior.
In this article

A client writes to an agency: “Please just move two elements.” The agency passes the request to a studio, the studio asks which version is correct, and meanwhile the client edits the previous file. Outside there is one brand. Inside there are three workflows and four copies of a document, each treated as current.

A service delivered under a partner's brand, often called white label, needs more than a change of logo. The selling company promises a result to the client while another team performs part of the work. The parties must establish how the need reaches the provider, who resolves questions and how the seller recognises that the result can be passed on. This is the organisation of a particular assignment, not a ready-made contract or an assessment of the parties' legal duties.

What role does the partner actually play?

Imagine a fictional example. An agency prepares communications for an equipment manufacturer, while a small studio produces a digital catalogue under the agency's brand. The agency manages the relationship with the manufacturer and the approved scope. The studio designs the layout and assembles the materials supplied. The manufacturer should receive a coherent result, not have to coordinate both companies itself.

This differs from a referral partnership (in Polish). In a referral, the interested client goes to the provider and agrees the subsequent scope with it. Here the partner remains responsible for managing the service. It also differs from a joint offer with another provider (in Polish), in which both partners present their contributions externally.

Name the roles before starting. Who gathers product data? Who approves its accuracy? Who decides whether a new request falls within scope? Who authorises release of the catalogue? The word “partner” answers none of these questions. One company may perform several roles, but each activity still needs an owner.

Also agree how people in the conversation will be introduced. Working under a shared brand does not justify pretending that someone is employed by another company or attributing authority they do not have. If a studio specialist answers technical questions directly, participants should understand that person's role and decision limits. The specific rules for disclosing subcontracting require appropriate assessment for the arrangement in question.

In the example, the agency can lead all commercial discussions while the studio joins one meeting about the catalogue layout. The studio need not learn the client's entire history. It needs the current materials, the question to be resolved and information on whether a decision at the meeting is final or needs later confirmation by the manufacturer.

How should a correction pass through two teams?

Choose one place to collect changes and one version to which they refer. The client may have several commenters, but the agency should establish who resolves conflicting feedback. The studio should not decide on its own between a sales director's opinion and a brand specialist's comment unless that decision was explicitly assigned to it.

Wix documentation on collecting site feedback describes comments attached to places in a preview. It also says the owner sees all comments, while collaborators see only those received through links they themselves shared. This is a specific visibility limit to check before agreeing on a shared feedback process.

It is not enough to tell the studio that “everything is in the comments”. Confirm whether it can access the same set as the agency. The preview link also needs checking: what material does it open, and who may receive it? In Wix, the described preview mechanism can also expose protected or members-only pages to the recipient. That is a reason to prepare the proper scope of material for review.

Preserve the meaning when passing on a change. “The heading is too big” may mean a problem of proportion, but it may also mean there is no room for the variant name. The agency should pass on the context and intended effect, and the studio should specify exactly what it will change. If the comment is unclear, the question must return to someone able to decide the content instead of circulating as an ever shorter quotation.

With more participants, use the principle from handling one enquiry through several people (in Polish): shared context and an identifiable owner of the answer. This does not require copying everyone into every message. It requires recording which decision applies and what still awaits a decision.

Separate a correction to delivery from new scope. Correcting a wrong name to match approved material is not the same as adding an entire product line. The studio describes the impact of the new request on its work, and the agency confirms the arrangement with the client. Do not promise an external deadline before the provider has checked dependencies and available materials.

Who needs access to which part of the work?

Grant access for the task, not according to how close the business owners are. A person correcting a page layout does not necessarily need the client's order list or accounts. Someone reviewing a preview need not have publishing rights. Record the required scope before inviting further collaborators.

Shopify describes collaborator accounts as partner access approved by an authorised person, with specified roles and the ability to remove access. It recommends checking the expected partner and the permissions requested. This mechanism shows how provider access can be explicitly separated from managing a project under a particular brand; it does not describe every system's capabilities.

Aeneia conceptual photography

In Webflow, client roles include, among other things, viewing and commenting or editing existing content. Access is assigned to a specific site. This describes platform functionality checked on 30 October 2026; it is not a purchase recommendation or a guarantee that every account has the same capabilities.

For our catalogue, the provider may need photographs and approved product descriptions, but not the manufacturer's entire drive. The agency prepares the appropriate set with source and version information. If the studio finds a gap, it requests the specific material. Sending the whole archive “so nobody has to ask again” transfers the selection problem and increases the amount of information in circulation.

Do not share one login merely so that the agency's brand appears in the change history. Identifiable accounts make it easier to establish who performed an action. This is particularly useful when reversing a change, ending cooperation or arranging cover. The way the team is presented to the client can be agreed separately without obscuring access inside the tool.

At the end of the assignment, agree what remains accessible for later corrections. Receive the files needed for future work, name the owner of publication and remove unnecessary access in accordance with the agreements. Do not assume that automatic expiry of an account on one platform tidies up every copy and other system used in the project.

Also plan cover in both companies. If the studio is waiting for confirmation from an absent person, it should know whether it may continue other sections or must stop everything. The agency needs the same information before replying to the client. The status “in progress” alone hides the difference between work being performed and waiting for a decision.

For recurring assignments, prepare a template for the input package. For the catalogue it might contain a product list, approved descriptions, photographs assigned to variants and brand rules. Identify missing elements on receipt, before the studio starts fitting random files into place. If the agency is still developing the content, agree which elements are drafts and which changes could still affect the layout.

Also check that the template does not carry a previous client into a new project. An email signature, a name in a preview, contact details or sample content may remain after a set is copied. Review these places before the first sharing, not only after the recipient notices. External brand consistency includes small messages as well as the catalogue cover.

What should the seller check before passing on the result?

The agency needs evidence of completion that corresponds to its promise to the client. A studio's “done” message alone does not say which version was checked, whether it includes approved feedback or what remains missing. On the other hand, the agency should not require the provider to confirm substantive matters outside its scope.

For the catalogue, acceptance may include the product list, correct assignment of photographs, presence of agreed language versions and maintenance of the agreed contact route. The manufacturer confirms product data. The studio confirms that it carried out the design using that data. The agency checks the whole within the scope it sells. These confirmations are not interchangeable.

A service map covering contact and backstage work (in Polish) helps. For each event visible to the client, identify what must first happen between the companies. A promised publication date depends, for example, on content approval and corrections being completed. If those conditions remain unknown, the message to the client should preserve that uncertainty.

Before the first assignment, walk through one example: client feedback, agency decision, studio correction and confirmation. Ask what happens if the client adds a comment after the version has been sent for publication. Who notices it? Does it stop publication? How do both companies distinguish accepted feedback from a suggestion awaiting a decision?

Such a trial does not yet prove the quality of the entire partnership. It can reveal simpler gaps before deadline pressure arises. It can be performed on prepared material without client data. In our example, changing one variant name and adding a comment that conflicts with earlier approval is enough. If no one knows who resolves the conflict, the problem is not the layout software.

How can one promise be kept without hiding limits?

Client-facing materials should describe scope, stages and support consistently. That does not mean copying all agency communications into the studio's internal documentation. It means preserving the meaning: if the client was promised a catalogue they can update themselves, the provider must know what the client will later do and how that capability will be handed over.

At first use of the delivered result (in Polish), the contact question returns. Does the client ask the agency to gather the issue, or is there an agreed route to the provider? What happens if the question concerns new scope? Do not leave the decision to the first person who happens to reply.

At Aeneia Design, the starting point can be organising the system of materials, site structure and messages under the brand the recipient sees. Approved roles, scope and feedback rules are needed. Digital experience design does not replace contracts or the organisation of cooperation between the two companies.

Working under another brand requires the people responsible for each stage to know what they pass on. There may be one logo on the file. The version for acceptance and the owner of the answer should also be identifiable, without investigating who last saved “final really”.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear