A time-limited demand used to arrive as a letter an adjuster could read in an afternoon. Now it arrives as thousands of pages, generated at machine speed, with days to answer. InFactIQ’s answer, launched at Guidewire Connections 2026, is a machine on the other side: Demand IQ reads the whole demand package, checks every assertion in it against the case record, and hands the adjuster a draft response where each finding cites the page and line it came from.
For brokers, this is not a claims-department curiosity. The demand package is where a liability claim gets its price. What gets checked, what gets missed, and what gets paid above what the evidence supports lands on your client’s loss runs, their renewal, and eventually your desk. Here is what launched, how it works, and the questions worth asking your carrier and TPA partners.
What launched
InFactIQ — a member of the Guidewire Insurtech Vanguards program — released Demand IQ on November 2, 2026, unveiled at Guidewire Connections 2026 in Las Vegas. The product takes in a plaintiff demand letter and its enclosures, compares what the demand asserts with what the records show, flags gaps and inconsistencies, and returns a draft response the claims team can work from.
The company’s framing of the problem, from its launch release: plaintiff firms have raised more than $600 million to generate demands and medical chronologies at machine speed. (That figure is InFactIQ’s, offered in its own release; treat it as the vendor’s sizing of the market it sells into.) The pressure point is real regardless of the exact number: a time-limited demand now arrives with thousands of pages and days to answer, and every assertion in it is still checked against the records by hand. Under that pressure, details get missed — and a missed detail usually means paying for something the evidence does not support.
“The demand letter tells one story and the file may tell another,” said John Sanchez, CEO of InFactIQ. “Until now the question was whether anyone had time to read the whole file before the deadline. Demand IQ reads all of it and shows the adjuster where the two disagree.”
How it works: upload, check, respond
The workflow InFactIQ describes has three steps.
Upload. The claims team drops in the demand letter and its enclosures: medical records, the billing summary, and exhibits. Where the demand carries a time limit, the response deadline is captured on the file from day one and counts down alongside the review.
Check. Demand IQ checks every claim in the demand against every record in the file. It flags what does not line up — the release’s examples are physical therapy sessions claimed versus sessions attended, and a statement of “no prior history” that the records contradict — and what is missing, such as gaps in treatment or bills with no record behind them. Each flag links in one click to the line it came from, so the adjuster can verify the finding rather than take it on faith.
Respond. The adjuster picks a playbook and Demand IQ drafts the response point by point, with a separate reasoning view that sets out each assertion in the demand, the carrier’s position, the evidence that supports it, and what could not be established from the file. Flags the team has not reviewed become open questions rather than disappearing into the letter. From the same file, the team can build an independent medical examination referral packet. Responses export to Word or PDF.
Pricing, per the release: a flat fee per demand package, with no seats, no contracts, and unlimited users on every review. InFactIQ says the platform serves insurance carriers, third-party administrators, insurance defense teams, and litigation firms.
What brokers should ask next
You do not buy this tool. Your clients’ carriers and TPAs do. But the quality of demand review is a claims-outcome question, and claims outcomes are a broker question at renewal time. Five questions worth putting to a carrier or TPA claims partner:
1. When a time-limited demand lands, who reads the whole file before the deadline — and how do you know? The countdown discipline is the product’s first feature for a reason. Ask how deadlines on time-limited demands are captured and tracked today.
2. Are findings cited to the source? A flag that links to the page and line can be verified in a click. A flag that cannot be traced is an opinion, and opinions do not negotiate.
3. What happens to the flags nobody reviewed? In Demand IQ’s design they stay open questions instead of vanishing into the response. Ask your partners what their equivalent is — because the unreviewed discrepancy is the one that gets paid.
4. Can you show the reasoning, not just the letter? The reasoning view — assertion, position, evidence, what could not be established — is the part a broker can actually discuss with an insured after a hard claim. Ask whether anything like it exists in the file your clients’ claims produce.
5. What does demand review cost, and where does it land? A flat fee per package is a knowable number. Compare it with the cost of one paid-but-unsupported line item, and ask how review costs are treated in the claim file.
This is the same discipline as a policy check, run on the other end of the claim: the document says one thing, the record says another, and money moves on the difference. We made that case for the policy itself in our policy check and E&O piece. Demand review is the claims-side version. And like the aerial property scoring now attached to your clients’ roofs, it is another case of a machine reading a file your client never sees — which is exactly why the broker’s questions matter.
The honest limits
Three cautions, because this is a vendor launch and should be read as one.
First, every performance claim here is InFactIQ’s own. There is no independent measurement in the release of how much leakage Demand IQ prevents, and “payment leakage” is the vendor’s term for the problem its product solves. The mechanism — check every assertion against the record, cite the source — is sound on its face. The magnitude is unproven until carriers publish results.
Second, the tool checks the demand against the file. If the file is thin, late, or wrong, the check inherits that. A reasoning view that honestly lists “what could not be established from the file” is only as useful as the team’s discipline about the open questions it leaves behind.
Third, a drafted response is a draft. Time-limited demands carry legal consequences that vary by state and by fact pattern, and no review tool changes who owns the decision to accept, counter, or let a deadline pass. That stays with the claims team and counsel.
InFactIQ is one of several vendors moving into the claims core this cycle — Guidewire itself put agents inside its platform, which we covered in our Guidewire agentic platform explainer. The direction is consistent: the file gets read by machines first. The broker’s job is to make sure someone can show their work.
Informational only — not legal, coverage, or claims-handling advice. Product details and quotations are from InFactIQ’s November 2, 2026 launch release; vendor claims are attributed as claims and have not been independently verified.
Sources: InFactIQ launches Demand IQ at Guidewire Connections 2026 (PRWeb, Nov 2, 2026) · InFactIQ