NorthBrief

Practical guides

Prepare the right questions before the work begins.

Use these guides to organize the product facts, commercial decisions and source material behind common internet-business legal issues.

Browse the guide libraryChoose a service area
Planning desk with a SaaS agreement, data-flow map, campaign brief and platform checklist

Guide library

Guides organized around internet-business decisions

Each guide names the reader, the situation to prepare for and the working output it supports.

SaaS agreement and product details prepared for a customer negotiation

For founders, sales and operations

Enterprise SaaS contract preparation checklist

Gather the deal context, product commitments, data dependencies, negotiation priorities and approval owners before contract review starts.

Read the checklist →

For product and engineering

Product data-flow interview guide

Trace what enters the product, why it is used, where it moves and what users and customers are told.

Read the guide →

For marketing and content

Creator and campaign rights checklist

Record deliverables, approvals, usage rights, disclosures, channels, edits and reuse conditions before production begins.

Read the checklist →

For marketplace and community teams

Platform rules operations map

Connect user permissions, prohibited content, reporting, moderation decisions and communications to real platform operations.

Read the operations map →

For founders, finance and operations

Contract issue chronology template

Organize the agreement, events, correspondence, commercial impact, open points and decision owners before a contract issue expands.

Read the template →

For small digital businesses

Website launch legal inventory

Review customer terms, privacy-facing language, analytics, forms, content rights, claims and ownership before a business website goes live.

Read the inventory →

Guide 01 · Contracts

Enterprise SaaS contract preparation checklist

For

Founders, sales leads and operations teams preparing to review or negotiate an enterprise customer agreement.

Use this when

A prospect has supplied its own agreement, a deal has moved beyond standard online terms, or business teams need to agree their position before a negotiation.

Prepare

  • The latest agreement, order form, statement of work and referenced schedules
  • The product or service description and the customer’s intended use
  • Pricing, term, renewal, payment and implementation assumptions
  • Current security, privacy, support and service-level material
  • Known product dependencies, vendors and delivery limitations
  • The customer’s requested changes and the commercial deadline
  • The owners who can approve product, security, finance and risk positions

Questions to work through

  1. Are the correct entities, product, customer use and commercial documents identified?
  2. Do the scope, implementation and acceptance terms match how the service will actually be delivered?
  3. Which product, support, security or data commitments require confirmation from another team?
  4. How do price, invoicing, renewal, suspension, termination and refunds work together?
  5. Which warranties, indemnities, liability positions or insurance requirements materially change the deal?
  6. Does the agreement depend on a data-processing, security or international-use position that is still unresolved?
  7. Which points are negotiation priorities, acceptable fallbacks or matters requiring senior approval?
  8. Who owns the next response, and what must be decided before the commercial deadline?

Expected working output

A contract preparation record containing the agreement version, deal context, material positions, operational dependencies, approval owners, negotiation priorities and next-response deadline.

Explore SaaS contract support

Guide 02 · Product data

Product data-flow interview guide

For

Product, engineering, security and operations leads preparing a new feature, vendor integration or privacy review.

Use this when

The team is launching or changing a feature that collects, generates, analyzes, shares, stores or deletes information about users, customers or their activity.

Prepare

  • A product walkthrough or current interface screens
  • A simple architecture or data-flow diagram, if available
  • The vendor and subprocessor list relevant to the feature
  • Current privacy notices, consent choices and in-product explanations
  • Customer contract or procurement commitments that describe data handling
  • Retention, deletion and access-control practices
  • Planned users, markets and release date

Questions to work through

  1. What information enters the feature, who provides it and through which interface or integration?
  2. What business and product purposes rely on each information category?
  3. Which systems, people, vendors or customer environments can access or receive it?
  4. Does any provider use inputs, prompts, outputs or telemetry for its own purposes?
  5. What user choice, notice or customer approval exists at the point of collection or change?
  6. How long is the information kept, where can copies remain and what triggers deletion?
  7. Do current notices, contracts, questionnaires and product claims describe the same behavior?
  8. Which open facts or ownership decisions must be resolved before release?

Expected working output

A feature-level data map recording sources, purposes, systems, vendors, user choices, retention points, customer commitments, open questions and release owners.

Review privacy and data support

Guide 03 · Campaigns

Creator and campaign rights checklist

For

Marketing, content and partnership teams working with creators, presenters, talent, photographers, editors or external production partners.

Use this when

A campaign will use a person’s work, name, image, voice, endorsement or audience across brand-owned and third-party channels.

Prepare

  • The campaign brief, audience, markets, channels and publication schedule
  • The proposed deliverables and production responsibilities
  • Creator, talent, agency or production terms already discussed
  • Draft scripts, claims, offers, captions and disclosure language
  • Music, footage, photography, brand assets and other third-party materials
  • The desired edit, translation, paid-media and future-reuse plan
  • The review and approval owners on both sides

Questions to work through

  1. Who creates each asset, and which third-party materials or contributors are involved?
  2. Which deliverables, formats, deadlines and revision rounds are expected?
  3. Where, for how long and in which markets may the content be published or promoted?
  4. Can the brand edit, crop, translate, combine, boost, whitelist or reuse the work?
  5. Which approvals are required before publication, and what happens when campaign details change?
  6. What commercial relationship or material condition needs a clear audience disclosure?
  7. What evidence supports product, performance, testimonial or comparative claims in the content?
  8. What happens to live content, source files and future usage when the relationship ends?

Expected working output

A campaign rights record connecting each deliverable to its creator, permission, channel, duration, edit rights, disclosure, approval owner and reuse limits.

Review advertising and growth support

Guide 04 · Platforms

Platform rules operations map

For

Product, trust and safety, support, community and operations teams responsible for user submissions or interactions.

Use this when

A marketplace, community, collaboration tool or content platform is creating or revising user rules, reporting paths, moderation practices or content permissions.

Prepare

  • The current journey for account creation, posting, sharing and removal
  • Current user terms, community rules and acceptable-use language
  • The content and conduct categories the service currently reviews
  • Reporting, support, appeal and account-action screens
  • Moderation guidance, roles and escalation paths
  • Records of recurring operational questions or edge cases
  • The markets, user groups and service model in scope

Questions to work through

  1. Who can submit, publish, share or sell content, and what permission do they give the platform?
  2. Which content or behavior categories are restricted, reviewed or handled differently?
  3. How can users and third parties report a problem, and what information does the team need?
  4. Who decides whether to restrict content, features or accounts, and when is escalation required?
  5. What record supports each action, communication and later review?
  6. How are affected users informed, and is there a correction or appeal path?
  7. What happens to removed content, retained records and related account data?
  8. Which product, staffing or support dependencies must change before the public rules change?

Expected working output

An operations map linking each user rule to the relevant product control, report path, decision owner, record, user communication and escalation step.

Explore content and platform support

Guide 05 · Contract issues

Contract issue chronology template

For

Founders, finance, sales and operations teams preparing to address a developing customer, supplier, partner or contractor issue.

Use this when

Delivery, payment, renewal, termination, ownership or another contract expectation has become disputed, unclear or operationally urgent.

Prepare

  • The signed agreement, amendments, orders and referenced schedules
  • Relevant invoices, delivery records, tickets or acceptance records
  • Key emails, messages and meeting notes in their original sequence
  • A list of people involved and their roles
  • The current financial, product, customer and operational impact
  • Upcoming dates, renewal windows, dependencies and business decisions
  • The commercial outcome the business wants to pursue

Questions to work through

  1. Which agreement version and provisions are connected to the issue?
  2. What happened, in what order, and which facts are supported by a source record?
  3. What did each party communicate, promise, deliver, reject or leave unresolved?
  4. Which payment, performance, notice, renewal or termination dates matter to the timeline?
  5. What is the current commercial and operational impact, and how is it changing?
  6. Which facts, documents or decision makers are still missing?
  7. What outcomes are acceptable, and what relationships or dependencies affect that choice?
  8. Who owns communications and decisions while the issue is being reviewed?

Expected working output

A source-linked chronology with the agreement in scope, dated events, supporting records, open factual questions, business impact, desired outcomes and accountable owners.

Explore contract issue support

Guide 06 · Website launch

Website launch legal inventory

For

Founders, marketing, product and operations leads preparing a new company, product, service or campaign website.

Use this when

A business is about to publish or materially change a website that describes an offer, collects enquiries, accepts customers, uses analytics or distributes original and third-party content.

Prepare

  • The staging site or current page inventory
  • The company, product, pricing and customer journey being presented
  • All forms, account, checkout, booking and subscription flows
  • The analytics, advertising, chat, video and embedded service list
  • The source and permission record for copy, images, video, logos and testimonials
  • The evidence behind material product, performance or customer claims
  • The intended audiences, markets, launch date and accountable page owners

Questions to work through

  1. Does the site clearly identify the business, offer, price conditions and customer action?
  2. Which terms apply to visitors, customers, subscribers, contributors or account users, and where are they accepted?
  3. What information do forms, accounts, payments, analytics and embedded tools collect or receive?
  4. Do privacy-facing explanations and user choices match the actual tools and customer journey?
  5. Does the business have permission for every image, video, logo, quotation, testimonial and downloadable asset?
  6. Which product, comparison, savings, performance or scarcity claims need support or clearer conditions?
  7. Are contact, support, cancellation, renewal and complaint paths consistent with the service offered?
  8. Who owns each page after launch, and which product or campaign changes should trigger another review?

Expected working output

A page-level launch inventory recording the relevant terms, data collection points, third-party tools, content permissions, material claims, customer paths, page owners and unresolved launch actions.

Choose the service area for your launch

Read by business moment

Move from the event to the right preparation.

Launching a productSelling to an enterprise customerChanging a vendor or data flowPublishing a creator campaignOperating a user-content platformResponding to a contract issue

Guide anatomy

Useful guidance shows its scope.

Each NorthBrief guide should identify the business situation, intended reader, materials to prepare, decisions to make, dependencies to confirm and the point at which tailored review may be needed.

01

Business situation

02

Intended reader

03

Inputs

04

Questions

05

Decision owners

06

Outputs

07

Fact dependencies

08

Review point

See how NorthBrief works

A live business issue

Have a decision to make rather than a research question?

Choose the service area closest to the work your team needs to move.

Choose a service areaSee the working method
Internet business materials organized around a practical working question