Insights
Software companies
256 guides · page 2 of 6
Code copyright and AI training: where the law stands in 2026
Code copyright and AI training law in 2026: which questions are settled, which are still open, and why a documented license lowers risk for code owners.
Code snapshot vs full git history: what to include in a code license
Code snapshot vs git history for an AI code license: compare value, review effort and secret exposure, then decide which repositories deserve full history.
Confluence to Notion migration: what you lose
Confluence to Notion migration moves current pages but often drops version history, inline comments, macros and permissions. Here is what to archive first.
Construction software companies: what project data you can and cannot license
Construction software data AI licensing starts with ownership: contractor RFIs stay theirs, while your support and engineering records can qualify.
Construction tech M&A in 2026: what acquirers look for in software companies
Construction tech M&A in 2026: why acquirers weigh AI features, field data and platform integrations, and the data-rights items to prepare before a sale.
Conversation intelligence vendors: can you train on or license customer calls?
Can a conversation intelligence vendor train AI on or license customer calls? Rarely. Why processor terms and consent block it, and what you can license.
CRM activity history vs current snapshot: why history matters for AI
CRM activity history value comes from sequence: stage moves, emails, owners and outcomes over time. Why it beats a snapshot, and what to turn on now.
CRM data quality for AI agents: what to fix first
CRM data quality for AI agents starts with four fixes: duplicates, missing deal outcomes, unlogged activity and lost stage history. Here is the order.
CSAT and resolution outcomes: why outcome fields raise support data value
CSAT and resolution data make support tickets checkable for AI developers. See which outcome fields matter, where they break, and how to audit them.
Customer asks 'do you sell our data?': how to answer accurately
When a customer asks 'do you sell our data?', the right answer depends on what you actually do. Three accurate scripts, what to verify, and what to avoid.
Customer-built workflows, templates and configurations: who owns them?
Who owns SaaS configuration data? Separate customer content, customer-built configurations and vendor templates, then check the contract and services SOW.
Customer community forum posts: who owns them and can they be licensed?
Community forum posts licensing turns on poster copyright, your terms' license and privacy law. See the rights table and why forum content often ranks low.
Customer data deletion obligations when your company shuts down
Closing a SaaS company? Map deletion duties across contracts, DPAs, your privacy policy and state law, and see which records may still be licensed.
Customer data hidden in code, tests and fixtures: how to find it
Customer data in test fixtures, seed files, recorded API responses and migrations is common in older code. A hotspot checklist with search patterns that work.
Customer data vs company data: what a SaaS company can actually license
Customer data vs company data decides what a SaaS company can license. Sort every record into one of three classes and find the clause that governs it.
Customer DPAs and de-identified data: what secondary use is allowed?
Read customer DPAs for aggregated, de-identified and improve-the-services carve-outs, then apply a four-part test before any secondary use or license.
Customer prompts and AI feature logs in your product: who owns them?
Customer prompts and AI feature logs ownership turns on four categories: inputs, outputs, feedback and telemetry. See the rights table and a safe default.
Cybersecurity software vendors: what security data you can license
Cybersecurity vendor data licensing: how customer telemetry, threat intelligence and your own detections, playbooks and support records differ.
Data inventory for software companies: Jira, GitHub, Zendesk and Slack
A data inventory for software companies with pre-filled rows for Jira, GitHub, Zendesk and Slack, plus the join keys that connect tickets, issues and code.
Data license vs software license: why licensing code for AI training is different
Data license vs software license for code: how an AI training grant differs from a EULA, source or open source license, and what to fix before signing.
Data monetization for B2B SaaS companies
Data monetization for SaaS companies: compare benchmarks, AI features, data products and licensing your own records, with the rights check each one needs.
Data pulled through Google or Microsoft integrations: can it be licensed?
Google API user data policy rules and Microsoft API terms limit AI training on data pulled through integrations. See what is usually excluded and why.
Data retention policy template for SaaS companies
A data retention policy template for SaaS companies: a schedule by system and record type, owners, legal holds and a review-before-delete rule for history.
Decommissioning a self-hosted GitLab or Jira server: archive checklist
Decommission a self-hosted GitLab or Jira server without losing history: a ten-step archive checklist covering database dumps, files, users and legal hold.
Derivative works clauses in insurance software contracts: what they allow
What a derivative works clause in insurance software contracts allows with customer data, and what it does not authorize for AI training or licensing.
Design docs and technical RFCs: why AI developers value them
Design docs and RFCs record engineering reasoning: proposal, review, decision and outcome. See which documents AI developers value and what to screen first.
Design partner agreements for AI features: data rights to settle up front
A design partner agreement AI data rights checklist: data scope, model scope, feedback, outputs, exit and deletion, with fill-in fields for your own template.
Developer tools companies: what engineering data you hold and can license
Developer tools company data licensing starts with your own repos, issues and reviews. See what you hold, what belongs to customers, and what to check first.
Discount and pricing exception approvals: AI value and confidentiality
Discount approval records show how a deal desk weighs margin, risk and strategy. See which fields AI buyers value and how to license them without price lists.
Do attachments inside tickets and emails add value?
Ticket attachments value depends on type: logs and screenshots often add real signal, while contracts and customer files mostly add risk. Decide by file type.
Do investors need to approve a data licensing deal?
Investor approval for data licensing depends on your charter, investor agreements and loan documents. See where consent rights usually sit and how to check.
Do VC investor rights require consent before licensing company data?
Investor consent under protective provisions can reach an IP license. The charter, investor and loan clauses to check before a VC-backed firm licenses data.
Do you need to back up Jira, GitHub and Zendesk?
Backup for Jira, GitHub and Zendesk: what each vendor keeps after deletion or cancellation, what it does not, and why complete linked history matters later.
Does an acquirer inherit your data licensing agreements?
Data license change of control and assignment explained: what happens in a stock sale, merger or asset sale, and which clauses decide who keeps the license.
Does an aggregated data clause let a SaaS company license data to AI developers?
An aggregated data clause in a SaaS agreement rarely covers licensing records to AI developers. Check five words to see what your clause actually permits.
Does licensing data affect your SOC 2 report?
SOC 2 data sharing with a third party for AI licensing touches access, confidentiality and vendor controls. Learn what evidence to keep before your audit.
Does data licensing revenue count as ARR?
Data licensing revenue rarely counts as ARR for a SaaS company. See how to classify license types, present them to the board and keep investor metrics clean.
Does data licensing revenue count toward your earnout?
Whether data licensing revenue counts toward an earnout depends on the revenue definition. See how GAAP, ARR and subscription definitions treat a license fee.
Does deleting customer data remove it from your AI training sets?
Deleting customer data can clear it from AI training sets but rarely from trained models. See how lineage and retraining keep deletion promises true.
Does licensing data to AI developers affect your SOC 2 report?
SOC 2 and data licensing: when a project to license data to AI developers falls in scope, and the four controls to document so your audit stays clean.
Does licensing source code expose security vulnerabilities?
Licensing source code can expose secrets, unpatched flaws and how your defenses work. See the risk table and the controls that keep exposure small.
Does source code escrow affect licensing your code for AI training?
Source code escrow rarely blocks an AI training license, but three clauses can. What to read in escrow and customer agreements before you license code.
Does venture debt restrict licensing your code or data?
Venture debt can restrict licensing code or data through IP liens, negative pledges and transfer covenants. See which clauses to check and how to get consent.
Dynamics GP end of support: what ISVs and add-on vendors should do
Dynamics GP end of life leaves ISVs and add-on vendors five options: port, maintain, sell, sunset, or preserve and license records. Compare them and plan.
E-commerce software vendors: merchant data vs your own records
Ecommerce platform merchant data ownership, sorted: which order and shopper records belong to merchants, and which vendor records you may license for AI.
Enterprise customers want 'no AI training' clauses: how should SaaS vendors respond?
How a SaaS vendor should answer a no AI training clause: accept limits on customer content, carve out company-created records and track restricted tenants.
ERP partners and VARs: who owns customizations and scripts built for clients?
Who owns ERP customizations a partner builds? The contract decides first. See how bespoke scripts, partner tools and platform code usually split, and why.
Exporting shared inbox history from Front and Help Scout
Export Front and Help Scout conversations with threads and notes intact: why report exports fall short, which fields to keep and what to do before canceling.