Plus Legal / Ran 2 commands Ran 2 commands All 6 area pages generated. Let me spot-check one to make sure it renders cleanly, then update the services hub to link to the new pages. Spot check technology-ecommerce page header Spot check technology-ecommerce page header Good. Now let me update the services hub page to link to the new area pages instead of in-page anchors. Searched 2 patterns, read 2 files, ran a command Searched 2 patterns, read 2 files, ran a command I need to load TodoWrite back, but let me batch efficient edits. I'll convert the 6
service cards into links. The .service-card CSS already has text-decoration: none; color: inherit; suggesting it was designed for this. Edited 7 files Edited 7 files Let me add a hover state and a subtle arrow indicator so users see the cards are clickable. Edited a file, ran a command Edited a file, ran a command The footer, strategy doc, services hub, and all 6 area pages are done. Here's what's now live in the workspace: Footer — Dispute Resolution added, six areas in correct 01-06 order. View footer.html Strategy doc — London/UK positioning clarified in Sections 5 and 12, change log updated. View plus-legal-seo-strategy.docx Services hub — all six cards now link to their area pages, with a teal arrow that appears on hover and a subtle background lift. View services.html Six area pages — each has full meta/OG/Twitter tags, Service and BreadcrumbList schema, hero with H1 targeting "[area] lawyer. London.", intro, pill list of what's covered, key laws block, watch-outs, practical tips, client examples, pricing/how-we-work mentioning Spain delivery, insight placeholders, related services, and a CTA block. No nav or footer — those sit in Webwave's layout. Commercial Contracts Technology & Ecommerce Intellectual Property Dispute Resolution Financial Services Media & Publishing Before I push on and build the 8 Phase 1 pill pages (SaaS Agreements, NDAs, T&Cs, Outsourcing, Platform Terms, Data Agreements, Licensing, Fintech), worth eyeballing one of the area pages — Commercial Contracts is the reference prototype. If the structure needs adjusting (depth, tone, number of watch-outs, pricing language), better to change it once in the generator than across nine files later. Footer Code · HTML Brave Browser Plus legal seo strategy Document · DOCX Google Drive Services Code · HTML Brave Browser Commercial contracts Code · HTML Brave Browser Technology ecommerce Code · HTML Brave Browser Intellectual property Code · HTML Brave Browser Dispute resolution Code · HTML Brave Browser Financial services Code · HTML Brave Browser Media publishing Code · HTML Brave Browser okay, one thing peter won't like is the h1 headers with London. It may put non-London people off accross all our services? They may think it will be expensive and blah blah blah. What do you think Thought process Thought process You're right — I overweighted the SEO keyword and underweighted the signal it sends. "Commercial contract lawyer. London." in a big serif H1 reads as "we're a London firm, expect London prices and London preferences" even though the reality is Peter-working-from-Spain-for-anyone-in-the-UK. Here's the SEO thing I was overthinking: the H1 is not the main place "London" needs to live for ranking. What actually moves the needle on geo searches is: The title tag (what shows in Google's SERP) — Commercial Contract Lawyer London | Plus Legal The meta description The Service schema's areaServed One natural mention in the intro or sub-hero Stripping London from the H1 loses very little. Google doesn't need a keyword-matched H1 the way it did ten years ago — topical relevance and title-tag match do the heavy lifting now. My suggestion: drop London from every H1, keep it in title + meta + schema + intro. Something like: Page H1 now H1 suggested Commercial Contracts "Commercial contract lawyer. London." "Commercial contract law." Technology & Ecommerce "Technology lawyer. London." "Technology & ecommerce law." IP "Intellectual property lawyer. London." "Intellectual property law." Dispute Resolution "Commercial dispute lawyer. London." "Commercial dispute resolution." Financial Services "Financial services lawyer. London." "Financial services law." Media & Publishing "Media & publishing lawyer. London." "Media & publishing law." Then a sub-hero line doing double duty: geo-signalling for search and positioning for readers — "Senior UK advice. Delivered personally by Peter Lumley-Savile." The "London, working with clients across the UK" line can sit in the intro paragraph below, where it reads as context rather than a claim about who we're for. Want me to make this change across the generator so all 6 pages update together? Happy to also reconsider the tags if you want to pull back further — we could go "Commercial Contract Lawyer UK" instead of "…London" if the London-specific search audience matters less to Peter than not narrowing the net. and keep it in why? it may still put people off in search results Thought process Thought process Fair challenge. You're right — meta descriptions and titles are literally the first thing people read in a search result. "Commercial Contract Lawyer London" in the SERP tells a Manchester or Bristol founder "not for me" before they ever land on the page. And Google actually watches click-through rate as a ranking signal, so turning people off at the SERP costs us twice. The honest SEO tradeoff: we'd lose some of the "[practice] lawyer London" query volume. But (a) those searchers are often people looking for an in-person meeting in London — which isn't Peter anyway, so they're lower-quality leads — and (b) "commercial contract lawyer" on its own is a much bigger pool, and a title that reads as UK-wide wins on CTR there. My recommendation: strip London out of everything visible. Keep it only where it's invisible to humans but visible to Google: H1 → practice-focused, no geo: "Commercial contract law." Title tag → "Commercial Contract Lawyer UK | Plus Legal" (UK is inclusive, not exclusive — nobody gets filtered out by "UK") Meta description → practice and benefit, no city Schema → London in PostalAddress, UK in areaServed — search engines still read the SRA-registered address as a legitimacy signal without us having to paint it on the front door Footer → address stays (legally required anyway) Body copy → one natural mention that Plus Legal is London-registered, buried somewhere like the "how we work" block; no claim about being for Londoners This also updates Section 5 of the strategy doc — the "keep London as primary target" call was wrong given Peter's actual market. I'd flip it to "target practice keywords, let schema + registered address handle geo". Want me to: Update the generator (titles, meta, H1s, hero subs, any body copy that leans on London) Rebuild all 6 area pages Update the strategy doc (Section 5 + change log entry explaining the shift) Or would you rather look at one rewritten page first before I push it across all six? what about creating a London page at some point, to pick up those searches, maybe other big cities too Thought process Thought process Yes, that's exactly the right play — and it's the SEO reason to pull London off the main pages now. You'd be splitting the work: area pages stay UK-wide and practice-focused, city pages do the geo-targeting job properly. Standard SEO pattern, and it works when it's done right. The rule Google actually enforces: each city page has to have genuinely local content, not a template with the city name swapped in. Thin duplicated location pages are classic doorway pages and Google has been whacking them for years. If we do it, we have to invest real words per page. What "genuinely local" means for a remote lawyer: Local business ecosystem context (City of London = finance + fintech, Manchester = tech + media + MediaCity, Edinburgh = finance + gaming/tech) Sector patterns: which legal issues actually come up for businesses in that place A few credibly-cited local stats or regulators (FCA in London, BBC/MediaCity contracts in Manchester) How Peter actually delivers to clients there (honest: remote, calls, London base for occasional in-person when needed) Clear that we're not a high-street local firm pretending to be — we're senior commercial advice that happens to serve that city Cities worth considering, roughly in order of commercial-law ROI: London — biggest commercial market, financial + tech + media + PE concentrated Manchester — tech, media, creative, growing startup scene Edinburgh — finance (asset management) + tech/gaming Bristol — tech, creative, aerospace Leeds — finance, legal services, tech Cambridge — biotech, deeptech (smaller but high-value contracts) Birmingham — general commerce, professional services Structure options: Simple city pages: /commercial-lawyer-london, /commercial-lawyer-manchester — one page per city, covers all six services. Easier to maintain, ~6–8 pages total. Matrix: /services/commercial-contracts/london, /services/technology-ecommerce/manchester etc. — massively more SEO surface (6 areas × 5 cities = 30 pages) but brutal to write well. Only worth it if the first round is earning its keep. I'd suggest phased: London first (obvious, biggest), then Manchester + Edinburgh as the tech/finance hubs outside the capital, then review traffic before going wider. Start with option 1 structure; graduate to option 2 only if London's version is genuinely pulling leads. Want me to: Fold "location pages" into the strategy doc as a new section (Phase 2 or 3, after the pill pages), with the honesty rules, the city list, and the phased plan Proceed with stripping London from the area pages now (independent decision — do this regardless) Hold off on actually building a London page until the area pages and pill pages are in Or do you want to build the London page now, alongside the area pages, since we already have the content legwork done? yes, add to strategy doc, or seo doc? or both? Thought process Thought process Just the one doc — reference/plus-legal-seo-strategy.docx is the living SEO strategy. That's the thing to update. I'll fold the location-pages plan in as a new section (probably Section 8 or 9, after the pill-pages plan), plus flip Section 5's location call to "strip geo from core pages, capture it via dedicated city pages later" and log both in the change log. While I'm in there I'll also update Section 12 (Local SEO) to reflect the shift — less "optimise the hub for London" and more "location work happens on dedicated city pages when we build them". Want me to go and do that now, then move on to the generator changes (H1s, titles, meta, hero subs across all 6 area pages)? yes, update all six pages Ran a command, read a file, edited a file Ran a command, read a file, edited a file Now let me look at Section 12 (Local SEO) and find the right spot for the new location-pages section. Read a file, edited a file Read a file, edited a file Now let me find where the existing sections 8+ sit so I can drop in a new Section 9 for location pages. Let me check the current section numbering. Find all H1 section markers Find all H1 section markers Let me update the cross-references in my recent edits and look for any other section-number refs: Find all Section N cross-references Find all Section N cross-references Time to insert Section 10 (Location pages) and renumber downstream sections. Let me batch the edits: Edited 3 files Edited 3 files Now renumber sections 10-16 to 11-17: Edited 7 files Edited 7 files Now let me read the Section 9 (Pill template) end so I can insert new Section 10 cleanly: Read a file, edited a file Read a file, edited a file I made a typo. Let me fix it: Edited a file Edited a file Now update comment labels and add the change log entry: Edited 6 files, ran a command Edited 6 files, ran a command Now add the change log entry. Let me look at the current change log: Read a file, edited a file Read a file, edited a file Now let me rebuild the strategy doc to verify the build works: Rebuild SEO strategy doc and deploy Rebuild SEO strategy doc and deploy Strategy doc rebuilt (36,730 bytes, up from 33,944). Now the area pages. Let me look at the relevant parts of build-area-pages.js: Ran 3 commands Ran 3 commands Now let me edit each area's fields. I'll preserve London only in the schema blocks (PostalAddress, areaServed) and the one honest SRA-required contextual line (line 951): Edited 13 files, read a file Edited 13 files, read a file Now verify the remaining London references are all either schema or honest SRA context: Verify remaining London refs are schema/SRA context Verify remaining London refs are schema/SRA context All remaining London references are exactly right: Lines 738, 743, 748: schema (invisible, legitimacy signal) Line 951: honest SRA-required context in body copy Now rebuild the pages: Regenerate all 6 area pages Regenerate all 6 area pages Let me spot-check that the changes landed correctly: Verify new titles, H1s and meta descriptions Verify new titles, H1s and meta descriptions All six pages are UK-facing now. London is preserved only in schema and the one honest SRA-required body line. Strategy doc (rebuilt, 36,730 bytes) Section 5 flipped: "strip geography from visible copy, keep London in schema + footer only, capture geo via dedicated city pages" New Section 10 "Location pages" — honesty rules, priority phasing (London first, then Manchester + Edinburgh, then review), URL structure, page map, metadata, word count, when-to-build-when-to-wait Section 13 (was 12) rewritten to match the new approach — local SEO signals live in schema/footer/profiles, visible geo work isolated to city pages Sections 10-16 renumbered to 11-17 Change log carries today's reversal with the earlier superseded entry preserved below for audit trail View plus-legal-seo-strategy.docx Six area pages (rebuilt) H1s, titles and meta descriptions are all practice-focused now. One set of before/after for the title tags: Page Before After Commercial Contracts Commercial Contract Lawyer London | Plus Legal Commercial Contract Lawyer UK | Plus Legal Technology Technology Lawyer London | SaaS... Technology Lawyer UK | SaaS... IP IP Lawyer London | Licensing... IP Lawyer UK | Licensing... Disputes Commercial Dispute Lawyer London... Commercial Dispute Lawyer UK... Financial Services Financial Services Lawyer London... Financial Services Lawyer UK... Media & Publishing Media Lawyer London... Media Lawyer UK... H1s dropped the "London" full-stop entirely and read as practice statements: "Commercial contract law.", "Technology & ecommerce law.", etc. Body copy cleanups: removed "based in London and working with clients across the UK", "London-registered", and similar geo-qualifying phrases from intro paragraphs, client-work ledes and hero sub-lines. Kept the SRA-required line about the firm being registered and regulated at 20 Wenlock Road — that's factual context, not a targeting claim. Commercial Contracts Technology & Ecommerce Intellectual Property Dispute Resolution Financial Services Media & Publishing Next logical moves, in order of SEO payoff: Build the London page now, since the content angle is real (registered address, SRA regulation, City of London finance, tech and media clients) Build the 8 Phase 1 pill pages (SaaS Agreements, NDAs, T&Cs, Outsourcing, Platform Terms, Data Agreements, Licensing, Fintech) Manchester + Edinburgh after London has been live for a review period Want me to press on with the London page next, or knock out the pill pages first? Plus legal seo strategy Document · DOCX Google Drive Commercial contracts Code · HTML Brave Browser Technology ecommerce Code · HTML Brave Browser Intellectual property Code · HTML Brave Browser Dispute resolution Code · HTML Brave Browser Financial services Code · HTML Brave Browser Media publishing Code · HTML Brave Browser are these pages all in the folder? List services pages List services pages Yes — all six are in your Plus Legal folder. Here's the full tree: List all HTML and docx files in workspace List all HTML and docx files in workspace Six new area pages sitting at pages/services/ .html, all timestamped 12:45 from the rebuild. The six empty subdirectories under pages/services/ (one per area) are placeholders for the pill pages — they'll house pages like pages/services/commercial-contracts/saas-agreements.html when we build them. Everything's in place. Ready to build the London page next, or push on with the pill pages — your call. we need an update on services page so links are live or redo to show links to area pages. or whatever is best Thought process Thought process Let me verify the current state of services.html: Check current link structure Check current link structure The six cards on the services hub are already live-linked to their area pages — each with a teal arrow that appears on hover, background lift, and H2 colour shift on hover. Let me also check the services.html H1/title for any London hangovers from the earlier strategy: Check services hub meta and London refs Check services hub meta and London refs Two London hangovers on the services hub that need the same treatment as the area pages. The meta description also mentions "corporate" and "healthcare" which aren't in the six-area line-up on the page. Let me fix those: Edited 2 files, read a file Edited 2 files, read a file Let me verify the final state: Final verify services.html metadata and links Final verify services.html metadata and links Services hub is now fully wired: All six cards are links pointing at the new area pages Hover state: teal → slides in from the right, card background lifts to off-white, H2 shifts to teal Title, meta description, og:title, og:description updated — no more London, no more references to corporate/healthcare services we don't offer Schema's OfferCatalog already lists the correct six services; fixed a trailing comma that would have broken JSON-LD validation Added Twitter card metadata to match the area pages View services.html One thing worth flagging: the schema's service list doesn't currently have url properties linking each service to its area page. A small SEO improvement would be to add "url": "https://pluslegal.co.uk/services/commercial-contracts" etc. to each schema entry — it makes the hub-to-area relationship explicit for search engines. Want me to add that in while we're here? Services Code · HTML Brave Browser yes Edited a file Edited a file Each of the six services in the schema now carries its canonical URL: "@type": "Service", "name": "Commercial Contracts", "url": "https://pluslegal.co.uk/services/commercial-contracts" Google now sees services.html as the hub and the six area pages as the specific services it offers, which helps with (a) how the site shows in rich results and (b) how ranking authority flows between hub and area pages. View services.html Services Code · HTML Brave Browser we've decided on some clarifications: services will basically be the three types of law as done on homepage - contracts, advisory and intellectual property, Clients become Sectors, as listed on top of home page. Remove government and public sector, education, charities and telecoms, separate financial services and insurance. Replace it with On menu bar, make menu bar on home page same as other pages, in menu order put insights after AI Law. Thought process Thought process Before I start restructuring, let me read the homepage so I understand what the three service types and the sector list actually look like there, and see the two different nav bars: Ran 2 commands, read a file Ran 2 commands, read a file Now let me check both nav bars: Ran a command, read a file Ran a command, read a file Now let me check the home page's nav: Ran 2 commands, read a file Ran 2 commands, read a file This is a significant structural change. Let me make sure I get it right. Let me ask a couple of focused questions: are you okay? Thought process Thought process Sorry — yes, I'm fine. I cut off mid-thought instead of firing the question. Let me try again properly: have you updated pages? Thought process Thought process No, nothing updated yet for this round. I paused because the biggest piece — collapsing six area pages into three — is a substantial restructure and I want to confirm the approach before tearing anything up. Also a couple of smaller things in your message I can't tell for sure: The six area pages we just built. Your message says services become three types matching the homepage (Contracts, Advisory, Intellectual Property). What do you want done with the six area pages? Three options: (a) consolidate the content into three new pages at /services/contracts, /services/advisory, /services/intellectual-property and retire the six files, (b) keep the six as sub-pages under three new category pages (so /services/contracts/commercial-contracts etc. — SEO-heavy, more maintenance), (c) discard the six entirely and write three fresh pages (simpler but loses the guide-depth content we've just built). "Replace it with" at the end of the sectors line reads like a truncated sentence. Did something get cut off — replace what with what? "Make menu bar on home page same as other pages." I can't see a difference in the files. home.html has no inline nav — all pages share nav.html. Is the difference something you're seeing in the live Webwave site (e.g. home is using a different layout in Webwave's settings)? If so that's a Webwave config change, not a file edit. The clear-cut stuff I can do without waiting: Rename "Clients" → "Sectors" in the nav and footer, rename the page to sectors, update the URL path Update the sector pill list on home (and the new sectors page): remove Government & Public Sector, Charities & Education, Telecoms; keep Financial Services and Insurance as separate pills (they already are) Reorder the nav so Insights sits after AI Law (new order: About, Services, Sectors, AI Law, Insights, Contact) Update the footer's services column once we land the services restructure Want me to start on the clear-cut items while you answer the three questions above? Or hold the whole lot until we've agreed the restructure? some of the areas are actually sectors Thought process Thought process Ah — that unlocks the structure. If I'm reading it right, three of the six "areas" aren't services at all, they're sectors: Current "area" What it actually is Commercial Contracts Service → Contracts Intellectual Property Service → Intellectual Property Dispute Resolution Service → Advisory (and rename) Technology & Ecommerce Sector — Technology + Ecommerce & SaaS Financial Services Sector — Financial Services Media & Publishing Sector — Media & Entertainment + Publishing That cleans things up a lot. Services answer what we do (three types, matches homepage). Sectors answer who we work with (industries listed in the hero pills). The three pages that turn into sector pages keep all their content — it just gets re-filed. Which gives you: /services hub → three cards: Contracts, Advisory, Intellectual Property /services/contracts — keep most of Commercial Contracts content, broaden scope /services/advisory — built around current Dispute Resolution content, plus regulatory/compliance and commercial-strategy angles from the homepage Advisory card /services/intellectual-property — keep as is /sectors hub → all the sector pills, clickable where we have a page for that sector /sectors/technology (or /sectors/technology-ecommerce) — current Technology & Ecommerce content, reframed as sector page (who we work with in this sector, not what we do for them) /sectors/financial-services — current Financial Services content, reframed as sector page /sectors/media-publishing — current Media & Publishing content, reframed as sector page And down the line: new sector pages for Insurance, Healthcare, Professional Services, etc. when there's a reason to build them. A couple of things to confirm before I start: Is this mapping right? Or does one of them land differently — e.g. do you want Technology and Ecommerce as two separate sector pages, or one combined? "Advisory" service page — does it exist as a genuine practice in Peter's work (regulatory, data protection, commercial strategy, plus disputes) or is it mostly a marketing framing for what's really dispute resolution + ad-hoc counsel? That shapes how substantive the content is. /sectors hub vs individual sector pages — do you want individual SEO-targeted pages for every sector (big content effort), or a single /sectors hub page with pills and only three sector pages built for now (Tech, FinServ, Media)? Once those are settled I can re-plan the work and update the strategy doc before touching any HTML. mapping is correct, split as sass and ecommerce, and technology - 2 areas, first create the sectors hub page and then one template example sector page for one sector Updated todo list, read a file Updated todo list, read a file Now I have the structure to work from. Let me update todos and build: Read 5 files, updated todo list, ran 3 commands Read 5 files, updated todo list, ran 3 commands Now I'll build the Technology sector template page. Updated todo list, created a file, read a file Updated todo list, created a file, read a file Two deliverables built: /sectors hub page — eyebrow "Sectors", H1 "Sector experience that makes a difference", stats strip (20+ / 1,000+ / FTSE 100 to startups), 10 sector cards numbered 01–10 (Technology, SaaS & Ecommerce, Financial Services, Insurance, Media & Entertainment, Publishing, Healthcare & Life Sciences, Professional Services, Retail, Hospitality & Leisure), Technology card is the only one linked for now, others show "Page coming soon". Includes "why sector experience matters" strip, testimonial and CTA. Full schema (LegalService with knowsAbout + BreadcrumbList). /sectors/technology template — built as a proper sector page (framing: who we work with and why this sector is distinct), not a rehash of the old tech service page. Sections: breadcrumb → hero (01 · Technology) → italic intro → 6 "legal realities of building in tech" cards → 3 services grid (Contracts, Advisory, IP — linked to /services/* so when those pages exist they'll resolve) → 4 client-type cards (software founders, enterprise tech buyers, devtools & infrastructure, AI & data) → 6 relevant laws → 6 "six places tech deals go sideways" → 5 "things that save tech deals" → pricing strip → testimonial → 4 related sectors → CTA. Content re-angled around IP-as-asset, ship cycles, enterprise procurement, AI Act, fundraising/exit readiness, international-from-day-one — sector themes rather than service themes. This gives you a reusable template. When you're ready I can stamp out the other 9 sector pages from this shape, then move to the next batch (new /services hub as 3 cards, 3 service pages consolidating content from the 6 old area pages, nav rename to Sectors, footer update, home pill cleanup, strategy doc update). Open the /sectors hub Open the Technology sector template Sectors Code · HTML Brave Browser Technology Code · HTML Brave Browser sectors meta? Thought process Thought process Current metadata on sectors.html: Title (71 chars — a touch long for Google's ~60 char cut-off): "Sectors | Commercial Law Experience Across Every Industry | Plus Legal" Description (222 chars — over the ~155-160 SERP cut-off): "Plus Legal advises businesses across technology, SaaS, financial services, insurance, media, publishing, healthcare, professional services, retail and hospitality. Senior commercial legal experience in every sector we serve." Three things I'd change: "Sectors" as the lead keyword is weak — nobody searches "sectors." Sector-qualified queries go to individual sector pages. This hub's job is brand + nav, so the meta should lean into the sector list (long-tail capture) rather than the word "sectors." Description is running long and currently gets truncated by Google around "healthcare…" Voice shifts to third-person "Plus Legal advises…" — the rest of the site uses "we" and "Peter." Proposed tighter meta: Title (57 chars): Commercial Lawyer by Sector | Plus Legal or, if you want the keyword load: Commercial Law by Sector | Technology, Finance, Media | Plus Legal (66) Description (152 chars): Senior commercial legal advice for technology, SaaS, financial services, insurance, media, healthcare, professional services, retail and hospitality. Want me to apply one of those, or write it a different way? (Happy to mirror the services.html meta voice exactly if you'd prefer they sit as a matched pair.) updated menu bar please Read a file Read a file Three changes needed: rename "Clients" → "Sectors" (with /sectors href), reorder so Insights comes after AI Law. New order: About, Services, Sectors, AI Law, Insights, Contact. Edited 2 files Edited 2 files Done. Both desktop and mobile menus now read: About → Services → Sectors → AI Law → Insights → Contact, with Sectors pointing to /sectors. Claude is AI and can make mistakes. Please double-check responses. Nav · HTML Brave Browser
Technology Lawyer UK | SaaS, Platform & Ecommerce | Plus Legal
02 · Technology & Ecommerce

Technology &
ecommerce law.

One of Peter's two core specialisms. SaaS agreements, platform terms, data processing contracts, reseller and partner deals, online terms. Senior technology law advice for UK businesses — buyer side and supplier side.

Core specialism · SaaS, platform, data, ecommerce · UK-wide delivery

A technology contract is half commercial deal, half operating manual. When it works, nobody notices. When it doesn't, everyone does.

Plus Legal is a specialist technology lawyer working with SaaS businesses, platforms, ecommerce operators and the companies that buy from them. Technology is one of Peter's two core specialisms. Every instruction is handled personally — the thinking and the drafting come from the same senior head.

This page is a plain-English guide to the technology and ecommerce law that shapes these deals — what the page covers, the laws and regulations behind it, and the clauses that tend to leak money. If you are about to sign, renegotiate, or write the template for next year, book a consultation.

What we cover

The technology and
ecommerce work we do.

SaaS, platform, data, ecommerce — the commercial technology stack, front to back. We draft the templates, negotiate the bespoke deals and review what is already on the desk.

SaaS subscription agreements Platform terms of service Data processing agreements International data transfer addenda Reseller & channel agreements Ecommerce T&Cs Software development & MSA API licence agreements Marketplace terms

Dedicated deep-dive pages for some of these topics are on their way. In the meantime, they all sit inside the work we do here.

The legal backdrop

Key laws and
regulations.

Technology and ecommerce sit on top of a busy regulatory backdrop. These are the sources that shape nearly every tech or digital deal Peter touches.

UK GDPR & Data Protection Act 2018

The default backdrop to any deal that touches personal data. Lawful basis, data subject rights, DPIAs, international transfers — the whole framework. Bakes into every SaaS and platform contract.

Privacy & Electronic Communications Regulations (PECR)

Cookies, marketing emails, electronic direct marketing. Sits alongside UK GDPR and often overlooked in consumer-facing tech.

Electronic Commerce (EC Directive) Regulations 2002

Information and contracting requirements for online services. Plain disclosures, order acknowledgements, the basics of lawful online contracting.

Consumer Rights Act 2015

Online sales, digital content and digital services. Quality, conformity, remedies — the consumer-facing half of ecommerce.

Online Safety Act 2023

Duties on user-to-user and search services. Risk assessments, content governance, illegal-content safety duties. Live and evolving under Ofcom.

Platform-to-Business Regulation (P2B)

Transparency, ranking and complaint-handling obligations on online intermediation services. Platform T&Cs need to meet specific standards.

Electronic Communications Act 2000

Electronic signatures are valid across UK commercial contracts. Digital contracting for tech deals is clean when handled properly.

NIS Regulations 2018 & Product Security and Telecommunications Infrastructure Act 2022

Cybersecurity obligations on essential and digital service providers and on connectable consumer products. Increasingly a contractual expectation.

Common pitfalls

Things to watch out for.

Six areas where technology contracts leak money and trust. Spot them early and the deal comes out cleaner.

01
Data Processing Agreements (Article 28 UK GDPR)

Often missing, often wrong. Scope of processing, sub-processor consent, audit rights, international transfers. Legally required and commercially material.

02
International data transfers

The IDTA and EU SCCs post-Schrems II. Addenda have to stay in step with the underlying policy. The mechanism cannot be an afterthought.

03
SLA definitions

"99.9% availability" means nothing without a baseline, a measurement window, exclusions and a credit formula. Vague SLAs fail the moment they matter.

04
Acceptance criteria in bespoke development

Most development disputes start here. If it is not written down, it is not acceptance — and the money conversation never ends.

05
Liability caps in subscription pricing

Caps that equal last-year fees can be trivially low on a five-year contract. Set caps against realistic exposure, not invoice history.

06
Ownership of customisations and integrations

The default rarely matches expectation. Who owns the custom reports, the integrations, the connector built for one customer? Paper it before the work starts.

Peter's practical tips

Five things
that save projects.

From one of Peter's two core specialisms. The tips that separate tech deals that age well from the ones that do not.

01
Map data flows before you paper them.

Personal data, special-category data, international transfers. The contract has to match the diagram; if you cannot draw it, you cannot draft it.

02
Tie SLAs to measurable service credits.

Not vague goodwill. A numerical remedy means the SLA does work. A statement of good intent does not.

03
Say who owns the IP in writing.

Before the work starts. Bespoke code, customisations, training data, integrations. "We'll sort it later" is the phrase that costs money.

04
Plan for supplier failure.

Exit assistance, source-code escrow, data export rights. Build the parachute before you need it. It is cheap now and priceless later.

05
Test the terms against a real use case.

A real customer, a real failure, a real refund request. If the contract falls over on one example, it is not ready.

Who we work with

Technology law for
the whole stack.

Plus Legal works with SaaS founders, platform operators, ecommerce businesses and their enterprise buyers — from the UK and beyond.

SaaS founders & scale-ups

First customer MSAs, enterprise subscription agreements, DPA templates, international expansion terms.

Platform operators

Platform terms of service, marketplace rules, creator and seller agreements, P2B compliance.

Ecommerce & D2C brands

Online T&Cs, subscription rules, payment-processor terms, fulfilment and logistics contracts.

Enterprise buyers & in-house teams

Tech procurement, due diligence on vendors, overflow support on negotiated SaaS and cloud deals.

How we work

Pricing that
behaves itself.

Every engagement is scoped clearly up front and priced on a basis that suits the matter. No open-ended hourly bills. No surprises at the end. Most work in this area falls into one of four pricing models.

Fixed fees Retainer Subscription Secondment

Peter is based in Spain and delivers work remotely for clients across the UK. In-person meetings are arranged when the matter calls for them. The firm is registered and regulated in England and Wales (SRA) at 20 Wenlock Road, London N1 7GU.

See how we work with clients →

Related insights

Writing and thinking
on technology law.

Practical guidance on the technology and ecommerce work this page covers. First pieces publishing soon.

Coming soon

What a SaaS contract should cover

A plain-English guide to the clauses that matter most in a software-as-a-service agreement — from acceptance to liability to exit.

Publishing Q2 2026
Coming soon

Data processing agreements: what actually matters

The Article 28 clauses that carry real weight, and the ones that are drafting habit. A buyer-side and supplier-side read.

Publishing Q2 2026
Coming soon

Platform terms: drafting for growth

How to write platform terms that scale with the business, survive regulator attention, and do not need a rewrite on every funding round.

Publishing Q2 2026
Get in touch

A tech deal
on the table?

SaaS, platform, data, ecommerce — send the draft or the situation. Peter will tell you what the real issue is and what a clean scope of work looks like.