← Explore practice areas

Marketplace / Product Counsel

Legal perspective through the product lifecycle.

Hire product counsel for development, marketing, online sales, and supplier agreements. Bring the product, its stage, and your legal questions into the brief.

Scope of support

What product counsel
can help with

01

Development and launch

Review product plans, IP questions, contractual obligations and legal risks before launch.

02

Advertising, labels and packaging

Review marketing claims, endorsements, disclosures and product labeling.

03

Safety, warranties and claims

Scope product-safety questions, recalls, warranty terms and product-liability matters.

04

Online products and sales

Review platform terms, privacy policies and legal issues around online transactions and customer data.

05

Suppliers and distribution

Draft and negotiate supplier, manufacturer and distributor agreements.

06

New technologies

Scope legal work for connected products and other emerging technologies described in the brief.

Before a customer AI addendum

Check AI restrictions
against the product.

  1. Separate the two promises

    Fictional example: a software company sells a document-search tool. A customer proposes no model training on its content and no disclosure of that content to third-party AI services. These are invented negotiation positions, not recommended terms. The product lead says the company does not train a model on uploaded documents, but engineering identifies an external model service in the answer-generation path. Ask engineering to describe exactly what information it sends and ask counsel to assess that flow against both restrictions. A statement about training does not answer the separate question of third-party access.

  2. Check current and proposed uses

    In this example, the team has not checked the external provider’s retention settings or terms. The vendor owner should supply the applicable contract, settings and evidence about permitted uses; a claim that the provider neither keeps nor trains on the data remains unverified until checked. Separately, product has proposed using selected customer documents to improve answer quality, but the method and permissions are undecided. Label that as proposed work. Product explains the intended activity; counsel assesses the permissions and obligations before the business decides whether to proceed, change the proposal or leave it out.

  3. Ask for a decision list

    Give counsel the customer’s addendum, main agreement, data terms and the checked use list, with definitions and exceptions included. Request coordinated comments or redlines identifying commitments that fit verified behavior, changes needed in the product or vendor arrangement, and open negotiation points. Name an owner and verification step for each required change. If the proposed solution is to disable a feature for this customer, engineering must establish whether that is possible and how to check it. Revised wording does not change the product by itself. Use information categories and diagrams in the initial packet, and agree how to share supporting material with counsel; this exercise does not establish compliance.

Before you get started

A few useful
hiring questions.

What should product counsel see before we launch a subscription?

Show counsel the customer journey alongside the draft terms: the offer, checkout, confirmation email and account controls. Include the intended launch locations and audience, and label each screen or document with its version. Fictional example: checkout describes a month-to-month commitment, the draft terms describe an annual commitment, and the confirmation email gives a different renewal date. Record those mismatches without choosing which statement is correct. Product and billing owners confirm the intended plan and actual behavior; counsel assesses the legal requirements and proposed wording for the relevant markets. Ask for a list of decisions and required changes across the journey, with an owner for each. After those changes, have the team check the same journey again in a controlled environment and give counsel the resulting screens, messages and unresolved questions. Reviewing the terms alone does not establish that checkout or customer emails match them.

What if the matter is time-sensitive?

State the timing and urgency in the brief and confirm availability with the professional.

What if a customer asks for more than our AI supplier promises?

Give counsel the customer request and the applicable supplier terms side by side. Match the service, data, trigger and exceptions before comparing the headline promises. Identify which commitment your team can perform itself and which depends on the supplier. A supplier contract is one input to the decision; it does not establish how your service actually operates.

Fictional example: a customer's draft asks your company to notify it within 12 hours of becoming aware of a security incident affecting its information. Your model supplier's terms promise notice within 72 hours after the supplier confirms an incident affecting information it processes. These are invented negotiation terms, not legal deadlines or recommended wording. The time periods, starting events and information covered differ. Do not mark the two clauses as matched just because both mention incident notice.

A useful comparison entry could read: “Customer draft v2: 12 hours from our awareness. Supplier terms dated 4 May: 72 hours from supplier confirmation. Gap: different triggers and timing; supplier-covered information must be checked against the actual data flow. Security owner: explain our own detection and notification process, and where it relies on supplier notice. Vendor owner: confirm the terms and service configuration that apply.” Keep incident records and customer information in the agreed restricted location; a fictional entry is enough for an initial scope discussion.

Ask counsel to review the full clauses and definitions with those owners and record the unresolved negotiation choices. A supplier amendment, operational change or different customer commitment may be needed; none is assumed available or acceptable. Verify and record any selected change before closing the issue. Recheck affected comparisons when the deployment, supplier or data flow changes. This exercise does not determine incident-reporting duties or readiness to sign.

The next step

Start with the work
your team needs.

Find product counsel for the scope you have in mind.

Find product counsel