Illustrative fictional example
This page is not legal advice, not an actual analysis, not a customer testimonial, and not based on any uploaded or customer data. Every party, term, score, and finding below was written solely to demonstrate report structure.
Sample contract analysis: fictional software services agreement
This fictional sample shows what an answer-ready contract analysis can look like for a made-up software services agreement between Northstar Studio and Cedar Analytics. It is not legal advice, not a real customer report, and does not contain uploaded data. Use it to understand the report structure, then review your own document and seek counsel where the stakes justify it.
Last reviewed:
Fictional contract context
- Parties
- Northstar Studio, Inc. (customer) and Cedar Analytics LLC (provider)
- Agreement
- Custom reporting dashboard design and implementation
- Fictional value
- $96,000, billed across four milestones
- Initial term
- 12 months, with automatic 12-month renewals
For this demonstration, assume the fictional agreement contains the main body only. No statement-of-work attachments, privacy addendum, security schedule, service-level agreement, insurance certificate, or negotiated side letter was supplied. In a real review, those related documents could materially change every conclusion below.
Executive answer
Illustrative conclusion: do not treat this fictional draft as ready to sign without targeted revision. The core service and fee are understandable, but the combination of subjective acceptance, automatic renewal, no convenience exit, broad background-IP transfer, and uncapped data-security indemnity concentrates commercial risk on Cedar. The priority is to create objective acceptance mechanics, preserve background IP, and put a negotiated boundary around exceptional liability.
Illustrative risk score
68/100
Elevated; not a probability
The score is invented for this example. A real score is only a triage signal and must be read with its supporting findings; it is not a legal conclusion, loss forecast, or guarantee that all important language was identified.
Key risks in the fictional draft
Uncapped data-security indemnity
HighCedar must indemnify Northstar for every third-party claim tied to a security incident, while the general liability cap expressly excludes that indemnity. The fictional clause has no fault standard, control-of-defense procedure, or exclusion for Northstar's actions.
Automatic renewal with a narrow exit window
HighThe agreement renews for another 12 months unless Cedar gives notice at least 90 days before the initial term ends. A missed calendar date could create a full additional term, and the contract gives Cedar no termination-for-convenience right.
Subjective acceptance and payment trigger
MediumInvoices become payable only after Northstar decides a milestone is satisfactory, but the fictional contract includes no objective acceptance tests, response deadline, deemed acceptance, or clear rejection-and-cure process.
Broad ownership transfer
MediumThe intellectual-property clause transfers all deliverables and related materials, without clearly preserving Cedar's pre-existing tools, templates, methods, libraries, or general know-how. That wording could sweep beyond the custom work purchased by Northstar.
Clause-by-clause findings
This section demonstrates the report's clause title, severity, and finding format. The sample does not quote a real contract because no real contract exists behind it.
Services and scope
MediumThe statement of work names three deliverables but does not define dependencies, customer responsibilities, change control, or what happens when Northstar delays access to data. Add an assumptions schedule and a written change-order process.
Fees and payment
MediumThe fictional fee is $96,000 in four milestones, due 45 days after acceptance. Because acceptance has no deadline or measurable test, payment timing is controlled by an undefined customer decision rather than a verifiable event.
Confidentiality
LowBoth parties must protect non-public business information and may disclose it to personnel with a need to know. The clause includes common legal-disclosure language, but it does not state a return-or-destruction process at the end of the engagement.
Intellectual property
MediumNorthstar owns deliverables upon payment, but the definition of deliverables may include Cedar's background materials. A clearer clause would reserve background IP and grant Northstar a license only to embedded elements needed to use the deliverables.
Liability and indemnity
HighOrdinary damages are capped at fees paid in the prior six months, but confidentiality, IP, and data-security indemnities are outside the cap. The sample provides no separate super-cap or reciprocal data-security obligation for Northstar.
Term and termination
HighThe 12-month term automatically renews and can end early only for uncured material breach. There is no convenience right, transition assistance, pro-rata payment rule, or express right to terminate after repeated service or access delays.
Focused commercial term analysis
Payment terms
Four $24,000 milestones are due 45 days after acceptance. The customer can withhold the entire milestone for any dispute, and no late-payment interest or undisputed-amount payment rule appears in the fictional text.
Termination terms
Either party may terminate an uncured material breach after 30 days. There is no termination for convenience, insolvency trigger, transition plan, refund method, or express payment obligation for completed work.
Liability analysis
The six-month fee cap excludes three broad categories. Because the data-security indemnity is both one-sided and uncapped, the apparent general cap does not bound the fictional provider's most serious exposure.
Missing or unclear protections
- Objective acceptance criteria, testing period, and deemed acceptance
- Mutual data-security commitments and an incident-response procedure
- Background-IP reservation and license for embedded provider materials
- Written change-control process for scope, assumptions, fees, and dates
- Termination for convenience with payment and transition consequences
- Service levels, support hours, remedies, and planned-maintenance rules
- Insurance requirements aligned with the risks each party controls
- Order of precedence across the agreement and future statements of work
“Missing” does not always mean “required.” The right protection depends on the service, bargaining position, jurisdiction, regulatory environment, insurance, price, and the parties' operational model. A human reviewer should decide which gaps matter and how any new language interacts with the rest of the deal.
Recommended next steps for this fictional scenario
- 1
Fix acceptance before negotiating payment timing.
Define deliverable-specific tests, give Northstar a short written review period, require detailed rejection reasons, allow Cedar to cure, and deem the milestone accepted if no response arrives on time.
- 2
Separate custom deliverables from background technology.
Create a schedule of Cedar's pre-existing materials, retain ownership of them, and grant Northstar a durable license to whatever background elements are embedded in the paid deliverables.
- 3
Reshape exceptional liability instead of relying on the general cap.
Add fault, causation, notice, defense-control, cooperation, and settlement provisions to indemnities. Consider a negotiated super-cap for specified risks rather than unlimited exposure.
- 4
Create a workable exit and renewal calendar.
Shorten the non-renewal notice, require a renewal reminder, add a convenience right, and state what Northstar must pay and what Cedar must deliver when the engagement ends early.
- 5
Validate the complete agreement with accountable reviewers.
Gather every exhibit, security schedule, privacy addendum, proposal, and incorporated policy. Ask commercial, security, finance, and qualified legal reviewers to confirm that the revised package matches the actual operating model.
How to interpret a real report
Start with the executive summary, then move from high-severity findings to their source clauses. Confirm every number, date, party, obligation, exception, and cross-reference. Review the extracted text for missing pages or formatting loss. Finally, translate confirmed issues into a decision: accept the allocation, negotiate a change, gather more facts, or escalate to a qualified lawyer. The AI contract review guide explains the process, report fields, document limits, and the division of work between AI and legal counsel.
Ready to review your own document?
Use this fictional sample as a map, not as a prediction of your result. Read the product limits, data-handling details, and common questions before uploading a contract.