Skip to content
03

For founders & product teams

Legal counsel for AI, SaaS and digital-asset startups.

Legal support for the decisions between a promising product and a durable business. Built around your stage, your constraints and your next move.

Built around your stage

From first commit
to the next market.

Your legal priorities change as your company grows. The working model should change with them.

01 / Build

Design the legal foundations.

Before habits become architecture: map product risks, data flows, ownership and the contracts your business will depend on.

  • AI and privacy review of the MVP
  • Founder, contractor and IP arrangements
  • Customer terms and privacy notices
  • Vendor and model-provider diligence

02 / Launch

Go to market with a clearer picture.

Understand the obligations your launch creates and the decisions that need resolving before users, money or data cross borders.

  • Product and regulatory perimeter assessment
  • Consent, disclosures and user journeys
  • Market-entry and transfer analysis
  • Incident and escalation playbooks

03 / Scale

Make enterprise trust repeatable.

Support bigger customers and investment conversations with a coherent account of your contracts, controls and regulatory position.

  • Enterprise contracts and DPA negotiation
  • AI and privacy due-diligence responses
  • Compliance evidence and remediation plans
  • Ongoing product and expansion counsel
Explore startup counsel

Sound familiar?

Real decisions.
Practical counsel.

Illustrative situations where legal work connects directly to product and commercial priorities.

The enterprise deal

Your buyer sends a DPA, AI questionnaire and a security addendum.

Align the legal commitments with what your product can actually do. Review liability, data roles, subprocessors, training restrictions and the evidence behind your answers.

The AI feature launch

A new copilot or agent changes how customers use your product.

Map inputs, outputs, permissions and human approvals. Review model-provider terms, personal-data use, disclosures and escalation before the feature becomes business-critical.

The investment conversation

A diligence request exposes scattered contracts and incomplete policies.

Organise the legal story: IP ownership, customer and vendor commitments, privacy foundations and outstanding regulatory risks. Build a prioritised list of issues to resolve or disclose.

The international expansion

Users, infrastructure and commercial relationships cross borders.

Work through territorial scope, local restrictions, data transfers and contracting. Identify when the plan needs local counsel or specialist advice before committing to a launch.

Good questions. Clear answers.

Before we
get started.

Can an early-stage startup work with you?

Yes. The starting point is the product and the decision you need to make. A focused review can address a launch or vendor question before a broader audit or continuing engagement becomes useful.

What is the difference between an AI audit and a privacy audit?

An AI audit examines the system’s use, responsibilities, governance, transparency and available evaluation evidence. A privacy audit follows personal data, purposes, rights, vendors and transfers. A product that uses personal data in AI may need both; the scope can be coordinated.

Will an audit give us a compliance certificate?

No. These are scoped legal and governance reviews that identify gaps and recommended actions. Certification, statutory conformity assessment and technical assurance are separate activities with their own requirements.

Can you support a company with customers in several countries?

The review starts with your establishment, product, users and target markets. Cross-border work maps the potentially applicable regimes and coordinates jurisdiction-specific advice with local specialists where needed.

Do we need perfect documentation before starting?

No. Bring the product demo, current contracts, vendor list and whatever diagrams or policies exist. Missing evidence is itself a useful finding and helps define a practical first workstream.

How are scope, timing and fees agreed?

After an initial scoping discussion, the proposed engagement sets out the question, deliverables, assumptions, responsibilities and fee basis. The depth of review depends on product complexity, markets and the evidence available.

Ready when you are

Building something the rules haven’t caught up with?

Tell me what you’re building. I’ll tell you what you need. No obligation.

Book an intro call