Promissory Fraud or Just a Broken Deal? How Courts Separate the Two — and Why Most Plaintiffs Get It Wrong
Your client was promised delivery by a certain date, a fully funded deal, a product that would perform to spec. None of it happened. Now you are drafting the fraud complaint, and the instinct is to include every broken promise. That instinct will get the fraud count sustained on demurrer. Here is the distinction that matters and how to plead around it.
The Demurrer
What the Law Requires
Fraud requires a misrepresentation of an existing fact. A statement about what the defendant will do in the future — "we will complete the project on time," "we will fund the full amount," "the product will perform as specified" — is not a statement of existing fact. It is a promise, and a broken promise is not fraud.
Tarmann v. State Farm Mutual Automobile Insurance Co. (1991) 2 Cal.App.4th 153, 157-158 remains the foundational authority: a promise of future conduct supports a fraud count only if the complaint pleads present intent not to perform at the time the promise was made, supported by specific facts — not merely by the fact that the promise was later broken. Post-hoc non-performance, without more, does not support the inference that the promisor lacked intent when the commitment was made. Beckwith v. Dahl (2012) 205 Cal.App.4th 1039, 1060; Hills Transportation Co. v. Southwest Forest Industries, Inc. (1968) 266 Cal.App.2d 702, 708.
This is the promissory fraud subspecies. The theory is cognizable under California law, but it demands something the breach of contract count does not: facts, existing at the time of the promise, that support the inference that the defendant never intended to deliver. What the defendant's business records showed at the time, what the defendant told third parties in the same period, what the market conditions were that the defendant knew about — these are the building blocks of a viable promissory fraud claim. The failure to perform is relevant but not sufficient.
The pleading failure is common and predictable. The complaint lists a series of things the defendant said it would do, recites that the defendant did not do them, and concludes that the defendant committed fraud. That complaint pleads breach of contract, not fraud, regardless of how the cause of action is labeled.
What the Corpus Shows
B2B commercial cases in the corpus — business dissolution disputes, contractor agreements, software development contracts, distribution agreements — regularly present the future-promise problem. The pattern is consistent: the complaint combines existing-fact representations and forward-looking commitments in the same paragraph, labels the entire paragraph as "fraud," and does not separately analyze which type of statement is which.
Courts sustaining demurrers on this ground typically identify a set of statements from the complaint, classify each one, and find that the statements the plaintiff relies on most heavily are promises, not existing-fact representations. Where some existing-fact representations appear in the complaint, the court may sustain the demurrer with leave to amend, requiring the plaintiff to separate the two categories.
The "promise of future conduct" sustain is one of the cleaner wins for the moving party on a fraud demurrer because the classification exercise is often straightforward once you read the complaint carefully. Plaintiffs frequently leave the classification work undone.
Where plaintiffs have succeeded on promissory fraud theories in the corpus, the complaints contain specific factual allegations — communications, internal documents, or surrounding circumstances — that predate the promise and support the inference of no intent to perform. Thin complaints that rely solely on the chronology of promise-then-non-performance do not survive.
What Counsel Does
If you are the moving party:
- Read the complaint and list every alleged misrepresentation in a separate analytical column. For each one, ask: is this a statement about an existing or past fact, or is this a statement about what the defendant will do in the future?
- For each future-conduct statement, argue separately that non-performance is not fraud and that the complaint pleads no facts — predating the promise — that support present intent not to perform.
- Quote Tarmann directly: the allegation must be that the defendant had no intent to perform at the time the promise was made. Non-performance alone is insufficient.
- If any existing-fact representations survive your classification, isolate them and argue that they are insufficient to support the remaining fraud elements on their own, or that they fail on another ground (specificity, causation, damages).
- Connect the absence of present-intent facts specifically to the demurrer ground. Do not rely on a generic "future promise is not fraud" argument without grounding it in the specific statements in the complaint.
If you are the opposing party:
- Before filing the complaint, separate existing-fact representations from forward-looking commitments in the pleading. Do this explicitly, in separate numbered paragraphs.
- For existing-fact representations, plead who made the statement, when, to whom, in what form, and why it was false at the time. These are your fraud allegations.
- If you want to include promissory fraud, keep it as a separate count with its own factual basis for present intent. Do not blend it into the existing-fact fraud count.
- For the present-intent allegation, plead facts that predate the promise: what the defendant knew about its financial condition, its operational capacity, or its intentions that contradicts the forward-looking commitment it made. Internal communications, representations to other parties, industry knowledge, or business records the defendant had access to at the time are all viable sources.
- Avoid "knew or should have known" language in the intentional fraud count. That is the negligent misrepresentation standard. Using it in the fraud count conflates the theories and creates a separate demurrer vulnerability.
This article is for educational purposes only and is not legal advice. All frameworks and sample language should be reviewed by a licensed attorney and adapted to your particular client, case, and situation.