Maciej Lis, a Polish attorney-at-law and digital product co-founder, leads our support for SaaS businesses, platforms and subscription teams. We help launch paid services, develop billing arrangements and negotiate enterprise contracts, matching legal work to the product stage and budget. Advice covers Polish law and applicable EU rules.
Organising processes, reviewing the agreement and planning successive payment-model iterations for a digital platform.
Business outcome: The platform launched quickly, with further payment-model iterations able to be introduced progressively as the business develops.
Terms, a DPA, privacy information and data-migration arrangements prepared ahead of a SaaS product’s planned launch.
Business outcome: The product’s legal framework is prepared for its planned launch and further development. Addressing data migration and changes in Data Act requirements reduces the risk of costly changes to the service model after launch.
Contracts, subscriptions, data arrangements and product rights need to reflect the same service.
A new plan, customer segment or integration can require changes to both the product and its terms.
Agree the contracting model, customer terms, subscription rules, DPA and immediate risks before each customer receives a different set of promises.
New packages, usage-based billing, trials and price increases need a consistent approach across product, communication and documents.
Selling to consumers, and certain sole traders with consumer-like rights under Polish law, brings additional information, complaint and digital-service obligations.
Procurement commonly reviews liability, SLAs, data, security, audits, exit arrangements and the right to use the product.
Establish what data reaches external services, who is responsible for outputs and what needs to change in the terms and documentation.
An investor may ask for evidence of software rights, team agreements, customer terms, DPAs and consistency between the documents and operations.
An API, AI feature, integration, new plan or user group has arrived, but the documents still assume a single model and a narrow service.
It is unclear when plans or prices can change, how customers are notified, what happens to the billing period and when they can terminate.
Subprocessors, transfers, logs, support and integrations are covered only partly, while an enterprise customer expects a clear allocation of responsibilities.
Availability, response times and remedies leave out maintenance, external infrastructure, scheduled downtime and the way uptime is measured.
You sell access to an application and need clear terms for accounts, billing, SLAs, liability, data and termination.
You connect user groups, content, payments or integrations and need to define roles, use rules, moderation and complaints.
Your model involves consumers, trials, automatic renewal, price changes and withdrawal rights.
The product works, but the customer asks about a DPA, security, subprocessors, SLAs, software rights and an exit process.
We scope the work around your next goal: launching sales, changing billing or signing a larger contract.
We first address what is needed for a paid service to launch. Later features are handled in stages so legal spending does not displace the product budget.
Define when billing starts, how plans renew or change and when access ends, reducing grounds for disputed charges and repeated manual support work.
Prepare the terms and answers needed for supplier review so missing DPAs, IP arrangements or SLA rules do not hold up the sale.
Connect changes to plans, payments and features with updates to the terms. The aim is to develop sales without rebuilding the whole document package at each product change.
Your next sales step and the features you are actually launching. We review the purchase flow, payment model, data and first customers’ requirements, then scope the documents and operational changes. Later stages can follow product development.
The B2B or consumer model, purchase flows, plans, data, integrations and existing documents. The scope also depends on whether we draft your terms, negotiate an enterprise customer’s template or review the product implementation. We agree scope and billing before starting.
A product link or demo, a short description of customers and pricing, your next goal and any existing contracts or terms. For data or enterprise matters, a vendor list, DPA and customer questions or draft are useful. You do not need a complete package to get in touch.
Maciej Lis is a Polish attorney-at-law and Data Protection Officer. He is also a co-founder and Product Owner of IMMONA Game, with Tech & Operations responsibilities. He combines work on his own product’s roadmap, contracts and IP with legal support for technology businesses. His experience includes VC discussions on behalf of startups and due diligence for an equity buyer.
Lis.Legal is based in Szczecin. We work remotely with technology businesses across Poland and international teams on matters involving Polish law and applicable EU rules. In-person meetings are available by appointment.
Checkout, billing, data and exit: prepare a B2B SaaS product for paid sales without building a legal package for features that do not exist yet.
Read the articleAn availability percentage only helps when the contract defines the outage, the measurement and the remedy. Learn what to check in a SaaS SLA, from exclusions and credits to recovery and repeated failures.
Read the articleA subprocessor notice can change where customer data goes. Check the authorisation, objection window and service consequences before the proposed change takes effect.
Read the articleA download button does not settle your SaaS exit plan. Check which data must move, the migration timetable, switching charges and the limits of the Data Act.
Read the articleDescribe the product, sales model and next decision. In an introductory conversation, we will identify the documents and risks that need attention at the current stage.
Request a consultation