A B2B SaaS founder was three days from signing a pilot agreement with a Fortune 500 retailer when our Risk Calculator flagged a risk score of 8.4 out of 10 — driven almost entirely by a single clause in section 11.3.
1The situation
Marcus had been chasing this deal for eight months. A Fortune 500 retailer wanted to pilot his inventory forecasting platform across 12 distribution centers. The contract was 34 pages. His startup had no in-house legal counsel. A law firm quoted $4,500 to review it. He uploaded it to Contracta HQ instead.
2What the AI found
The Risk Calculator returned a score of 8.4 out of 10 — flagging 6 critical issues and 4 high-severity concerns. The most dangerous: Section 11.3, titled "Work Product and Intellectual Property," contained a perpetual, irrevocable, royalty-free license grant that effectively transferred ownership of any improvements Marcus's team made to the platform during the pilot — to the Fortune 500 client.
In plain English: if Marcus's team fixed bugs, added features, or optimized the algorithm during the 90-day pilot, those improvements would legally belong to the retailer. The clause was written to look like a standard "work made for hire" provision but was significantly broader.
3The redline negotiation
Marcus used Contracta HQ's Clause Redliner to compare the original clause against a standard SaaS pilot IP provision. The AI scored the original as "Severely Favorable to Client" and generated a counter-proposal that: (1) limited the license grant to the pilot period only, (2) excluded pre-existing IP and platform improvements, and (3) added a carve-out for general know-how.
He sent the counter-proposal to the Fortune 500's legal team. After two rounds of back-and-forth, they accepted a modified version that protected his core IP.
4The outcome
Deal signed. Pilot launched. Marcus retained full ownership of every line of code his team wrote. The $180K ARR pilot converted to a full contract six months later.
"I would have signed that thing without a second thought," he said. "Section 11.3 looked like standard boilerplate. It was buried on page 22 of a 34-page document. There's no way I would have caught it."
Tools used in this story