Insights
Software companies
256 guides · page 3 of 6
Feedback clauses in SaaS contracts: what can a vendor reuse?
A SaaS feedback clause lets a vendor reuse suggestions about its product, but rarely tickets, usage data or customer content. See the clause anatomy.
Field service software vendors: licensing work order data from your platform
Field service software data licensing has two rights paths: your own vendor records or a contractor opt-in program. Homeowner data stays out of both.
Fleet and telematics software vendors: what records you can license
Telematics software vendor data rights: fleet telemetry and driver data belong to customers, but device, support and engineering records may be licensable.
Freemium and prosumer users: why consumer accounts complicate SaaS data licensing
Freemium users data licensing raises consumer privacy and FTC questions that business accounts do not. How to separate consumer accounts and exclude them.
Generative AI for support teams: what your ticket history makes possible
AI for customer support teams works only as well as your ticket history. See which fields deflection, drafting, routing and QA need, and how to check them.
GitHub organization at shutdown: archive repos, issues and PR reviews
A git clone saves code, not issues, pull requests or review threads. Here is how to archive a GitHub organization completely before a company shuts down.
GPL and AGPL code in your repo: can it be part of an AI training license?
GPL and AGPL code complicates an AI training license. A decision rule for which files to exclude, which first-party code to keep and where law is unsettled.
Helpdesk migration: what happens to your old ticket history?
Helpdesk migration ticket history often loses internal notes, attachments and audit events. See what usually moves, what gets dropped and what to export.
How AI is changing software company valuations in 2026
AI impact on SaaS valuations in 2026: the factors buyers now weigh, from AI exposure to proprietary workflow data and rights, and how to document each one.
How long should a company keep CRM records?
There is no single CRM data retention period: contacts, deals, activities and notes each need their own rule. Use this logic before deleting old CRM records.
How long should you keep customer support tickets?
How long to keep support tickets depends on legal minimums, privacy limits and the value of resolved histories. Five tests set retention by ticket type.
How much notice should customers get before a software product is retired?
Software end of life notice period: set it from your contracts, committed terms and customers' migration effort, then add an export window. A rule and checks.
How real bugs in private repositories become coding agent benchmarks
A private repository coding benchmark turns a fixed bug into a scored task. See the issue-to-test flow and the repository traits that make tasks usable.
How to account for data licensing revenue under ASC 606
ASC 606 data licensing revenue for CFOs: point in time or over time for snapshots, refreshes and revenue shares, plus the judgments auditors will test.
How to add AI training rights to your SaaS terms without a customer backlash
Update terms of service for AI training without losing trust: separate content from telemetry, ask for opt-in, give real notice and honor every refusal.
How to answer AI questions in customer security questionnaires
A question bank for the AI section of security questionnaires: model answers on training, model providers and data sharing, plus the evidence to attach.
How to answer an insurance agency's AI vendor evaluation checklist
Insurance agency AI vendor evaluation questions, answered one by one: what to say about training, ownership and retention, and which evidence to attach.
How to answer 'do you sell customer data?' in a security questionnaire
Security questionnaire answers to 'do you sell customer data?' for three cases: no licensing, company records only, and opted-in customer data.
How to archive a GitHub organization before shutting down a company
Archive a GitHub organization before a shutdown: mirror every repo, export issues, pull requests and reviews, keep key Actions logs and transfer ownership.
How to change your terms of service to allow AI training without an FTC problem
Changing terms of service for AI training takes more than a new clause. Use a five-step checklist: prospective use, clear notice, opt-in, DPA fit and records.
How to check if your tickets, issues and commits link up
A Jira commit linkage check in three queries: measure how often tickets, issues and commits connect, score the result, and find where the links break.
How to estimate the size of a codebase for a data license
Estimate codebase size for a data license: lines of code by language, commits, pull requests, contributors and years of history, with a command for each.
How to exclude regulated tenants (BAA, FedRAMP, EU) from a SaaS data license
Exclude regulated tenants from a SaaS data license with a register: tenant flag, reason, source contract and verification query for BAA, FedRAMP and EU.
How to export Azure DevOps work items, repos and pull requests
How to export Azure DevOps work items, repos and pull requests with full history, and keep the links between them intact for an archive, migration or license.
How to export Bitbucket repositories with pull requests and comments
Export Bitbucket pull requests and comments with the code: a mirror clone plus API pulls, the fields worth keeping, and how to prove the export is complete.
How to export PagerDuty incident history
Export PagerDuty incidents with timelines, notes and responders intact: which export path to use, which fields to keep and what to redact before sharing.
How to find and remove secrets from git history before sharing a repo
Remove secrets from git history before a repo leaves your company: scan every ref, rotate keys, rewrite a separate copy, then rescan. Tools compared.
How to remove secrets and credentials from code before licensing it
Remove secrets from git history before licensing code: scan every commit, rotate live keys first, rebuild a delivery copy and verify it with a clean rescan.
How to scan code repositories for secrets before licensing engineering history
Scan repository for secrets across code, pull requests, issues and CI logs before licensing engineering history, then choose rewrite, exclusion or redaction.
How to shut down a SaaS product: customer data export and notice plan
How to shut down a SaaS product without stranding customers: staged notices, a tested data export, proof of deletion, and which company records to keep.
How to use customer data to build AI features in your SaaS product legally
Use customer data to build AI features in SaaS with a rights ladder: in-tenant use, a shared product model and outside licensing, and what each needs.
How to write an AI training clause into your customer terms
Draft an AI training clause for your customer agreement: a six-decision checklist with illustrative wording for scope, de-identification, opt-out and notice.
HR and recruiting software companies: licensing data without candidate risk
ATS software vendors can license some records for AI without candidate risk. A safe-scope table: product and support records in, candidate profiles out.
Illustrative workflow data package: a SaaS company's support-to-fix histories
A workflow data package example for SaaS: how a fictional company linked tickets, Jira issues, pull requests, releases and replies into a licensable manifest.
Indemnities in code licensing deals: who carries open-source license risk?
Indemnity for open source code in a code license for AI training: how first-party warranties, as-is pass-through and liability caps usually split the risk.
Insurance Data Security Model Law: what it means for software vendors
The Insurance Data Security Model Law reaches software vendors through carrier contracts. See what insurers pass down and how it limits reuse of carrier data.
Insurance software vendors: carrier data vs your own records
Insurance software vendor data rights, sorted: which records belong to carriers and policyholders, and which code and support history is yours to license.
Intercom conversations at shutdown: preserving support history
Export Intercom conversations before you cancel: a shutdown checklist for support leads covering transcripts, notes, attachments, ownership and access.
Is AI killing vertical SaaS? What private software owners should do
Is AI killing SaaS? A balanced view for vertical software owners: what agents threaten, what records protect, and three moves to make now.
Is an AI data buyer a sub-processor of your customers' data?
Is an AI data buyer a sub-processor? Usually not when you license de-identified company records. See when the role changes and what your DPA requires.
Is B2B contact data personal data under CCPA?
B2B data is generally CCPA personal data now that the temporary exemption has ended. See which CRM and ticket fields count before you license records.
Is income from licensing code a royalty for tax purposes?
Is code licensing income a royalty for tax purposes? How license and sale terms shape the answer, plus state, sales tax and foreign buyer questions.
Is it legal for a shut-down startup to sell employee Slack messages?
Is it legal to sell employee Slack messages after a startup shuts down? What ownership, notices and privacy law decide, plus a checklist before any deal.
Is licensing data worth it for a 100-person software company?
Is data licensing worth it for a software company of about 100 people? Fit signals, the real effort by role, and the no-files first step before you decide.
Is your SaaS data a moat or a licensing asset?
Is your SaaS data moat a reason not to license? Use a 2x2 of data uniqueness and product dependence to choose a licensing posture for each record family.
Jira and Confluence Cloud at shutdown: backup before the site is deleted
Before you cancel Jira and Confluence Cloud, back up issues, comments, attachments, links and page history in a form you can read after the site is gone.
Jira issues to exclude before a data license: security, HR and legal
Jira issues to exclude from a data license: vulnerabilities, HR and legal tickets and restricted comments. A checklist by project, label and security level.
Jira to Linear (or other tracker) migration: preserving issue history
A Jira migration moves current issues but often leaves changelogs, transitions and links behind. What migrates, what is lost, and the full-export step.